From: Doug Ledford <dledford@redhat.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>,
LK <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.4.3 and new aic7xxx
Date: Tue, 06 Mar 2001 15:09:47 -0500 [thread overview]
Message-ID: <3AA5440B.8FAAB728@redhat.com> (raw)
In-Reply-To: <200103061847.f26IlaO06717@aslan.scsiguy.com>
"Justin T. Gibbs" wrote:
>
> >This is just to report on a the behavior of this driver. I've a dual
> >channel Adaptec 7895 controller. The adapter BIOS is configured to boot
> >from devices in channel B. I boot from a disk connected to channel B
> >and when the kernel loads the driver the disks from channel A are seen
> >first, resulting in the drive names changing from, say sda to sdb. This
> >does not happen with 2.2.18 or 2.4.2. Is there an option to reverse the
> >order? I saw some of the options in the code, but none about this.
>
> Can you provide me with a dmesg from a boot with aic7xxx=verbose?
> I just tested this on a 3940AUW and the behavior was as expected.
> Perhaps you have a motherboard based controller that has no seeprom?
> I don't know how to detect flipped channels in that configuration
> but I'll see what I can find out.
Your driver uses the new PCI probe code, so there is no gaurantee that you'll
see channel A before channel B. So, if you haven't seen channel A yet, you
won't already have read the Channel B Primary bit in the SEEPROM. So, my
guess would be that you should modify the code so that when presented with the
B or C channel of a device, maybe you should make a call to load_seeprom() (or
whatever it is in your driver) for Channel A, grab the bits you need that are
only on channel A's SEEPROM, save them off, then read the Channel B/C SEEPROM
entry as needed. That should solve the problem anyway. Of course, it could
simply be something else that is wrong and I could be smoking crack ;-)
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
next prev parent reply other threads:[~2001-03-06 20:08 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 [this message]
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
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=3AA5440B.8FAAB728@redhat.com \
--to=dledford@redhat.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raffo@neuronet.pitt.edu \
/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