On Tue, 24 Jan 2006, Randy.Dunlap wrote:
> On Tue, 24 Jan 2006, Alan Cox wrote:
>
> > On Maw, 2006-01-24 at 01:43 -0500, Ed Sweetman wrote:
> > > problem. The problem is that there appears to be two nvidia/amd ata
> > > drivers and I'm unsure which I should try using, if i compile both in,
> > > which get loaded first (i assume scsi is second to ide) and if i want my
> > > pata disks loaded under the new libata drivers, will my cdrom work under
> > > them too, or do i still need some sort of regular ide drivers loaded
> > > just for cdrom (to use native ata mode for recording access).
> >
> > The goal of the drivers/scsi/pata_* drivers is to replace drivers/ide in
> > its entirity with code using the newer and cleaner libata logic. There
> > is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes
> > are using libata and the additional patch patches still queued.
>
> What is "MPIIX" anyway?
>
> and while I'm looking at the config menu, why do both
> Compaq Triflex and Intel PATA MPIIX say (Raving Lunatic)?
Lots of them say Raving Lunatic. Are all of these Alan's libata
patches?
> > > 1. Atapi is most definitely not supported by libata, right now.
> >
> > It works in the -mm tree.
> >
> > > 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.
> >
> > Or use labels. As you move into the world of hot pluggable hardware it
> > becomes more and more impractical to guarantee drive ordering by name.
> >
> > You can mix and match the drivers providing you don't try and load both
> > libata and old ide drives for the same chip. Even then it should fail
> > correctly with one of them reporting resources unavailable.
> >
> > In fact I do this all the time when debugging so I've got a stable disk
> > for debug work and a devel disk.
>
>
--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
