From: Jeff Garzik on

I just pulled the "pata-drivers" branch of libata-dev.git into the
"upstream" branch, which means that Alan's libata PATA driver collection
is now queued for 2.6.19.

Testing-wise, these PATA drivers have been Andrew Morton's -mm tree for
many months. Community-wise, no one posted objections to the PATA
driver merge plan, when Alan posted it on LKML and linux-ide.

The following must be in all caps, though:

drivers/ide IS STILL THE PATA DRIVER SET THAT USERS AND DISTROS SHOULD
CHOOSE.

At this time, drivers/ide should not be added to
Documentation/feature-removal-schedule.txt. The libata PATA driver set
should be considered experimental still, and there remains a few
user-visible differences between the two trees:

* Host-protected area (HPA) not ignored in libata, which means disk
sizes differ between drivers/ide (whole disk) and libata (whole disk
minus HPA).

* The obvious change between /dev/hdX to /dev/sdX

* /dev/sdX supports fewer partitions than /dev/hdX (16 versus 64, IIRC)

* /dev/sdX does not support all the HDIO_xxx ioctls that /dev/hdX does.
In practice, the ioctls we ignored are ones that very few people care
about.

* ARM, PPC and other non-x86 platform drivers are severely
under-represented.

As an aside, I would love to see paride updated to use libata, but we
can probably count the number of paride users on one hand these days...

Jeff



--
VGER BF report: U 0.499983
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Alan Cox on
Ar Llu, 2006-09-04 am 07:01 -0400, ysgrifennodd Jeff Garzik:
> The following must be in all caps, though:
>
> drivers/ide IS STILL THE PATA DRIVER SET THAT USERS AND DISTROS SHOULD
> CHOOSE.

Except optionally for the following for chips not handled by or broken
totally in drivers/ide:

pata_mpiix - some early pentium era laptops
pata_oldpiix - original "PIIX" chipset
pata_radisys - embedded chipset

The other apparently "libata only" chips are pata_jmicron and
pata_optidma. There are patches to handle these as "generic" PCI IDE in
the base 2.6.18 tree already so only features will be lost (eg mode
switching). As Jeff implies distributions should be using drivers/ide
for the Jmicron PATA and the Opti DMA PATA for now.

> * /dev/sdX supports fewer partitions than /dev/hdX (16 versus 64, IIRC)
>
> * /dev/sdX does not support all the HDIO_xxx ioctls that /dev/hdX does.
> In practice, the ioctls we ignored are ones that very few people care
> about.

Add "/dev/sr*" does not support partitions. (That needs fixing anyway)

> * ARM, PPC and other non-x86 platform drivers are severely
> under-represented.

libata needs changes for this too. I have some stuff saved from the
older discussions to look at.

> As an aside, I would love to see paride updated to use libata, but we
> can probably count the number of paride users on one hand these days...

and thats without using fingers or thumbs.


--
VGER BF report: H 0.235691
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Grant Coady on
On Mon, 04 Sep 2006 07:01:13 -0400, Jeff Garzik <jeff(a)garzik.org> wrote:

>
>I just pulled the "pata-drivers" branch of libata-dev.git into the
>"upstream" branch, which means that Alan's libata PATA driver collection
>is now queued for 2.6.19.
>
>Testing-wise, these PATA drivers have been Andrew Morton's -mm tree for
>many months. Community-wise, no one posted objections to the PATA
>driver merge plan, when Alan posted it on LKML and linux-ide.

Too friggin' hard to test Alan's stuff for older IDE here, therefore
ignored so far :( I have some old hardware that Alan is addressing,
even an old IBM 260MB PCMCIA HDD.

I can't see an easy way to arrange multi-boot with different /etc/fstab
depending if I'm trying /dev/hdaX or /dev/sdaX. Parallel '/' partitions?


Plus, 2.6.18-rcX fails too early in boot on one machine (p100 IBM 365X)
for any testing. Suggestions welcome...

Grant.

--
VGER BF report: U 0.488991
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jeff Garzik on
Grant Coady wrote:
> I can't see an easy way to arrange multi-boot with different /etc/fstab
> depending if I'm trying /dev/hdaX or /dev/sdaX. Parallel '/' partitions?

That's actually pretty darn easy, with a modern distro. Use filesystem
labels, and LABEL= in your /etc/fstab.

The LABEL= feature allowed me to bounce between drivers/ide and libata a
dozen times a day, when I was doing the initial libata development.

Jeff



--
VGER BF report: H 3.84798e-12
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jan Engelhardt on

>> * /dev/sdX does not support all the HDIO_xxx ioctls that /dev/hdX does.
>> In practice, the ioctls we ignored are ones that very few people care
>> about.
>
>Add "/dev/sr*" does not support partitions. (That needs fixing anyway)

scd*/sr* is usually CDROM, which in the rarest case have a partition table,
don't they? (sd* stands for Scsi Disk, but what's the r in sr standing
for?)

>> As an aside, I would love to see paride updated to use libata, but we
>> can probably count the number of paride users on one hand these days...
>
>and thats without using fingers or thumbs.

0? Could it be removed then? [I'm waiting for loud objection screams from
paride users...]



Jan Engelhardt
--

--
VGER BF report: H 4.996e-16
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/