From: Erik Mouw <erik@harddisk-recovery.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Xose Vazquez Perez <xose@wanadoo.es>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: two sym53c8xx.o modules
Date: Thu, 9 Oct 2003 14:24:28 +0200 [thread overview]
Message-ID: <20031009122428.GF11525@bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0310090826290.2569-100000@logos.cnet>
On Thu, Oct 09, 2003 at 08:41:49AM -0300, Marcelo Tosatti wrote:
> On Thu, 9 Oct 2003, Xose Vazquez Perez wrote:
> > kernel 2.4 has two modules with *same name*:
> > /lib/modules/2.4.XX/kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.o
> > /lib/modules/2.4.XX/kernel/drivers/scsi/sym53c8xx.o
> >
> > "# modprobe sym53c8xx" tries to load sym53c8xx.o first and then sym53c8xx_2/sym53c8xx.o
> > bug or feature?
> >
> > should be sym53c8xx_2/sym53c8xx.o renamed to sym53c8xx_2/sym53c8xx_2.o ?
>
> One should not have both drivers loaded at the same time, so I think this
> is alright.
No, it's not allright. Modprobe can't distinguish between
sym53c8xx_2/sym53c8xx.o and sym53c8xx.o, you have to figure out the
full path and insmod one of them manually. Xose is right in that
sym53c8xx_2/sym53c8xx.o should be renamed in sym53c8xx_2/sym53c8xx_2.o.
Compare with aic7xxx and aic7xxx_old.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
| Data lost? Stay calm and contact Harddisk-recovery.com
next prev parent reply other threads:[~2003-10-09 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 0:43 two sym53c8xx.o modules Xose Vazquez Perez
2003-10-09 11:41 ` Marcelo Tosatti
2003-10-09 12:24 ` Erik Mouw [this message]
2003-10-09 12:38 ` Matthew Wilcox
2003-10-09 13:11 ` Erik Mouw
2003-10-09 13:21 ` Matthew Wilcox
2003-10-09 14:04 ` Erik Mouw
2003-10-09 15:44 ` Xose Vazquez Perez
2003-10-09 13:00 ` Marcelo Tosatti
2003-10-09 16:05 ` Xose Vazquez Perez
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=20031009122428.GF11525@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=xose@wanadoo.es \
/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