From: Tim Riker <Tim@Rikers.org>
To: alex@foogod.com
Cc: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] I-Opener fix (again)
Date: Wed, 13 Dec 2000 13:20:02 -0700 [thread overview]
Message-ID: <3A37D9F2.6FB11D82@Rikers.org> (raw)
In-Reply-To: <20001211152331.M10618@draco.foogod.com> <Pine.LNX.4.10.10012122217440.4894-100000@master.linux-ide.org> <20001213114046.B19902@draco.foogod.com>
Andre,
What are the "laptops that have CFA devices that do not come on channels
in a pair" systems you refer to?
This patch fixes the iopener and other systems here at Lineo that have
2nd drive flash. The only other way we have been booting these is with
"hdb=noprobe" which just disables the 2nd drive flash. hdb=flash does
not fix it.
alex@foogod.com wrote:
>
> On Tue, Dec 12, 2000 at 10:47:35PM -0800, Andre Hedrick wrote:
> >
> > Basically if the setting of
> >
> > * "hdx=flash" : allows for more than one ata_flash disk to be
> > * registered. In most cases, only one device
> > * will be present.
> >
> > fails then I will look into this but, the breaking of laptops that have
> > CFA devices that do not come on channels in a pair canb not happen.
> > If you have a vender unique setting that will follow always the way
> > I-Opener's are setup then that is better.
>
> Ok, there are two things here:
>
> 1) "hdx=flash" _does_ fail, because the flash-related code clobbers hda
> _after_ hda's detection phase, when it's looking at hdb (which is flash).
>
> 2) I can see no situation where hdb detection should ever override the
> _already_performed_ detection of hda in this way.
>
> Basically, as is, the kernel finds hda (traditional IDE device), configures it
> normally, then finds hdb (flash), and clobbers all the correct info it already
> detected for hda. This seems just plain wrong.
>
> -alex
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-13 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 23:23 [patch] I-Opener fix (again) alex
2000-12-13 6:47 ` Andre Hedrick
2000-12-13 19:40 ` alex
2000-12-13 20:20 ` Tim Riker [this message]
2000-12-13 20:26 ` alex
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=3A37D9F2.6FB11D82@Rikers.org \
--to=tim@rikers.org \
--cc=alex@foogod.com \
--cc=andre@linux-ide.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