> It seems a new sym53c8xx was added in 2.4.17, and now there are 2 modules,
> both named sym53c8xx.o (CONFIG_SCSI_SYM53C8XX and
> CONFIG_SCSI_SYM53C8XX_2). This was noticed since my mkinitrd script isn't
> smart enough to destinguish the two. Leading to the question how does
> modprobe? Comparing this with the naming scheme used for the two aic7xxx
> modules (aic7xxx.o and aic7xxx_old.o) it seems like its a bug to me, in
> either case I'd appritiate some input from somebody clued in on the issue.
This is a compatibility feature. Just select _the_ driver you want to use
but not both. The bug is to build the both drivers without special needs
or goal.
Renaming a driver object module will break compatibility of old linux
installations depending of the driver selected, and also may break
flexibility for who knows what he is doing.
By the way, if it ever happens one of the two modules to be renamed in
2.4, it is the old version that will be. As a result, the patch you sent
me directly that renames the new version is exactly what I donnot want to
be done.
In kernel 2.5, SYM53C8XX_2 will replace SYM53C8XX. I already agreed with
the proposal to remove the old driver version, and I suggested so
implicitely, obviously, by providing SYM53C8XX_2. I hope this will also
happen in 2.4 series, but probably a bit later.
Gérard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/