From: Andrew Morton <akpm@zip.com.au>
To: "H . J . Lu" <hjl@lucon.org>
Cc: hogsberg@users.sourceforge.net, jamesg@filanet.com,
Jens Axboe <axboe@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: sbp2.c on SMP
Date: Sun, 11 Nov 2001 21:14:35 -0800 [thread overview]
Message-ID: <3BEF5ABB.78254C5F@zip.com.au> (raw)
In-Reply-To: <3BEF27D1.7793AE8E@zip.com.au>, <3BEF27D1.7793AE8E@zip.com.au>; from akpm@zip.com.au on Sun, Nov 11, 2001 at 05:37:21PM -0800 <20011111205411.B30782@lucon.org>
"H . J . Lu" wrote:
>
> > Incidentally, it would be nice to be able to get this driver working
> > properly when linked into the kernel - it makes debugging much easier :)
> >
>
> I guess I can try that. The only main issue will be the order of
> initialization.
>
Actually, it almost works. If you link the drivers into the kernel
and, after bootup, attach a firewire drive and run rescan-scsi-bus.sh
it will pick up the new devices. It's just the bus scan at initcall
time which fails.
-
next prev parent reply other threads:[~2001-11-12 5:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 1:37 sbp2.c on SMP Andrew Morton
2001-11-12 4:54 ` H . J . Lu
2001-11-12 5:14 ` Andrew Morton [this message]
2001-11-12 5:28 ` H . J . Lu
2001-11-12 8:50 ` Alan Cox
2001-11-12 17:34 ` Jens Axboe
2001-11-14 3:17 ` H . J . Lu
2001-11-14 7:21 ` Andrew Morton
2001-11-16 3:32 ` H . J . Lu
2001-11-16 16:15 ` Kristian Hogsberg
2001-11-16 16:30 ` H . J . Lu
2001-11-16 21:25 ` H . J . Lu
2001-11-16 22:40 ` Kristian Hogsberg
2001-11-26 15:43 ` Oops 2.4.15-pre1aa1 Sven Heinicke
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 4:49 sbp2.c on SMP Douglas Gilbert
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=3BEF5ABB.78254C5F@zip.com.au \
--to=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=hjl@lucon.org \
--cc=hogsberg@users.sourceforge.net \
--cc=jamesg@filanet.com \
--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