From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ed Sweetman <safemode@comcast.net>
Cc: Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
Andrew Morton <akpm@osdl.org>,
harald.dunkel@t-online.de, linux-kernel@vger.kernel.org,
rdunlap@xenotime.net
Subject: Re: 2.6.16-rc1-mm2 pata driver confusion + tsc sync issues
Date: Tue, 07 Feb 2006 11:10:29 +0000 [thread overview]
Message-ID: <1139310629.18391.7.camel@localhost.localdomain> (raw)
In-Reply-To: <43E8150E.9030801@comcast.net>
On Llu, 2006-02-06 at 22:33 -0500, Ed Sweetman wrote:
> first from the testing branch to the upstream patches. In mm, sata
> gets loaded before pata in libata land. In alan cox's patches it's the
> reverse. This results in different device names for the same config
Thats just down the shape of the Makefile. It'll get resolved in the
merge of the code upstream over time according to the order Jeff puts
them in
> Perhaps from a distribution standpoint, moving to a label method of
> describing what gets mounted where would be best, rather than worrying
One reason I've not worried about this is I use Fedora so it "just
works"
> about scsi naming schemes or ide ones. Just think of the fun of a
> system with multiple usb storage devices and such.
> I'm just not sure if grub and the kernel "root=" parameter can handle it.
They can't but they don't need too. See the Fedora/Red Hat mkinitrd
script and tools. The 'root' is the initrd and the tools it contains
find the real root by label. No kernel hackery needed.
next prev parent reply other threads:[~2006-02-07 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 16:53 2.6.16-rc1-mm2 pata driver confusion Randy.Dunlap
2006-01-26 11:09 ` Ed Sweetman
2006-01-30 11:43 ` Alan Cox
2006-01-30 15:36 ` Randy.Dunlap
2006-02-03 21:54 ` Ed Sweetman
2006-02-06 16:39 ` Randy.Dunlap
2006-02-06 19:34 ` Harald Dunkel
2006-02-06 19:56 ` Alan Cox
2006-02-07 2:28 ` Ed Sweetman
2006-02-07 1:26 ` 2.6.16-rc1-mm2 pata driver confusion + tsc sync issues Ed Sweetman
2006-02-07 1:35 ` Andrew Morton
2006-02-07 1:53 ` Matthew Garrett
2006-02-07 3:33 ` Ed Sweetman
2006-02-07 11:10 ` Alan Cox [this message]
2006-02-07 3:43 ` Ed Sweetman
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=1139310629.18391.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=rdunlap@xenotime.net \
--cc=safemode@comcast.net \
/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;
as well as URLs for NNTP newsgroup(s).