public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@comcast.net>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
	alan@lxorguk.ukuu.org.uk, 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: Mon, 06 Feb 2006 22:33:34 -0500	[thread overview]
Message-ID: <43E8150E.9030801@comcast.net> (raw)
In-Reply-To: <E1F6I3G-0003fw-00@chiark.greenend.org.uk>

Matthew Garrett wrote:

>Andrew Morton <akpm@osdl.org> wrote:
>
>  
>
>>That's bad.
>>    
>>
>
>Given that libata goes through the scsi layer at the moment, shifting
>from the traditional PATA drivers to the libata ones is going to result
>in a shift from hdfoo to sdbar. We're not really looking forward to this
>from the distribution point of view, though I think the same thing
>happened in the past when shifting from the ancient SATA drivers to the
>libata ones.
>
>  
>
Well, the badness mentioned above is the swapping of what gets loaded 
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 
when switching between mm and release, which is bad, but is a problem 
that can be overcome with the use of labels instead of device names.

Perhaps from a distribution standpoint, moving to a label method of 
describing what gets mounted where would be best, rather than worrying 
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.


  reply	other threads:[~2006-02-07  3:33 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 [this message]
2006-02-07 11:10                   ` Alan Cox
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=43E8150E.9030801@comcast.net \
    --to=safemode@comcast.net \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgarrett@chiark.greenend.org.uk \
    --cc=rdunlap@xenotime.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