From: "Gérard Roudier" <groudier@free.fr>
To: Andreas Boman <aboman@goofy.nerdfest.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17 has 2 modules named sym53c8xx.o
Date: Fri, 11 Jan 2002 21:01:27 +0100 (CET) [thread overview]
Message-ID: <20020111204356.G1567-100000@gerard> (raw)
In-Reply-To: <20020111000052.34204997.aboman@goofy.nerdfest.org>
On Fri, 11 Jan 2002, Andreas Boman wrote:
> 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.
next prev parent reply other threads:[~2002-01-11 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 5:00 Andreas Boman
2002-01-11 5:55 ` Keith Owens
2002-01-11 20:01 ` Gérard Roudier [this message]
2002-01-11 20:33 ` Andreas Boman
2002-01-11 23:38 ` Gérard Roudier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020111204356.G1567-100000@gerard \
--to=groudier@free.fr \
--cc=aboman@goofy.nerdfest.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome