From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.3 and new aic7xxx
Date: 6 Mar 2001 22:11:45 -0800 [thread overview]
Message-ID: <984jf1$1hj$1@penguin.transmeta.com> (raw)
In-Reply-To: <3AA5CA13.8C19FC7E@neuronet.pitt.edu> <200103070546.f275keO22502@aslan.scsiguy.com>
In article <200103070546.f275keO22502@aslan.scsiguy.com>,
Justin T. Gibbs <gibbs@scsiguy.com> wrote:
>>I've a Super P6SBS motherboard with a builtin dual channel Adaptec 7890
>>Ultra II scsi controller. I'm attaching the console grab when booting
>>2.4.3-pre2. The controller BIOS is configured to boot off the disk with
>>scsi id 0 on channel B.
>
>It looks like Doug was right to think that the functions can be
>presented to the device driver in reverse order. I should have
>a patch for you early tomorrow.
It should be easy enough to make the PCI layer sort the devices, and you
might not be the only driver that wants to see subfunction 0 before
subfunction 1.
I suspect it's easier to just make the PCI layer call the probe function
in that order, instead of working around it in your driver. Jeff?
Linus
next prev parent reply other threads:[~2001-03-07 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 5:08 Kernel 2.4.3 and new aic7xxx Rafael E. Herrera
2001-03-06 11:44 ` Alan Cox
2001-03-06 14:38 ` Justin T. Gibbs
2001-03-06 18:47 ` Justin T. Gibbs
2001-03-06 20:09 ` Doug Ledford
2001-03-06 20:40 ` Justin T. Gibbs
2001-03-07 5:41 ` Rafael E. Herrera
2001-03-07 5:46 ` Justin T. Gibbs
2001-03-07 6:11 ` Linus Torvalds [this message]
2001-03-07 7:22 ` Aaron Tiensivu
2001-03-07 18:46 ` Rafael E. Herrera
[not found] ` <200103070611.WAA01595@penguin.transmeta.com>
2001-03-07 21:55 ` Jeff Garzik
2001-03-07 22:43 ` Justin T. Gibbs
2001-03-07 22:56 ` Jeff Garzik
2001-03-07 23:35 ` Justin T. Gibbs
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='984jf1$1hj$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.