From: Jeff Garzik <jgarzik@pobox.com>
To: Ed Sweetman <safemode@comcast.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.16-rc1-mm2 pata driver confusion
Date: Tue, 24 Jan 2006 09:51:09 -0500 [thread overview]
Message-ID: <20060124145109.GC23269@havoc.gtf.org> (raw)
In-Reply-To: <43D5CC88.9080207@comcast.net>
On Tue, Jan 24, 2006 at 01:43:20AM -0500, Ed Sweetman wrote:
> I have an nforce4 based motherboard. Currently i'm using the amd/nvidia
> driver under the normal ide,ata driver section (2.6.14).
>
> It appears that the new ata code is hiding under scsi/sata drivers,
> including apparently pata code. This alone reads confusing, pata
libata PATA support is under development. Use only if you feel lucky.
Really lucky. I mean, really really lucky.
> 1. Atapi is most definitely not supported by libata, right now.
Not true.
> 2. whether libata sets the controller up better or not, ide cdroms MUST
> be loaded before libata is or the ide controller will be detected as
> "already in use" and the cdrom drivers wont have any device to attach
> to, since unlike scsi drivers, ide drivers dont probe the hardware on
> controllers to see if any driver has claimed them.
Either use drivers/ide or libata for PATA, not both.
> 3. For hdd's alone, the pata libata + sata drivers are a "complete"
> replacement for the ide drivers and thus, if you dont have atapi
> devices, you dont need to compile in ide support.
Again, ATAPI works just fine.
> 4. moving to pata libata drivers _will_ change the enumeration of your
> sata devices, it seems that pata is initialized first, so when setting
> up your fstab entries and grub, you'll have to take into account how
> many pata devices you have and offset your current sata device names by
> that amount.
Enumeration of devices depends on which driver is loaded first.
Check your /etc/modprobe.conf.
Jeff
next prev parent reply other threads:[~2006-01-24 14:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 6:43 2.6.16-rc1-mm2 pata driver confusion Ed Sweetman
2006-01-24 14:51 ` Jeff Garzik [this message]
2006-01-24 15:29 ` Alan Cox
2006-01-24 17:05 ` Randy.Dunlap
2006-01-24 17:08 ` Randy.Dunlap
2006-01-24 21:13 ` Alan Cox
2006-01-24 17:13 ` Alan Cox
2006-01-24 22:17 ` Ed Sweetman
2006-01-24 22:27 ` Randy.Dunlap
2006-01-24 23:01 ` Ed Sweetman
2006-01-24 23:07 ` Randy.Dunlap
2006-01-25 1:56 ` Ed Sweetman
2006-01-25 16:53 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
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=20060124145109.GC23269@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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).