linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: PATA drivers queued for 2.6.19
Date: Tue, 05 Sep 2006 16:48:32 -0400	[thread overview]
Message-ID: <44FDE2A0.3080705@tmr.com> (raw)
In-Reply-To: <1157371363.30801.31.camel@localhost.localdomain>

Alan Cox wrote:
> 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.
> 
> 
I still use that interface, although I can't say it's critical if I 
can't upgrade at some point. There are some other users in the local UG, 
but they are probably not ever going to upgrade.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.

  parent reply	other threads:[~2006-09-05 20:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 11:01 PATA drivers queued for 2.6.19 Jeff Garzik
2006-09-04 12:02 ` Grant Coady
2006-09-04 12:07   ` Jan Engelhardt
2006-09-04 12:35     ` Tomasz Torcz
2006-09-04 13:35       ` Jan Engelhardt
2006-09-05 13:26     ` Helge Hafting
2006-09-05 14:39       ` Alan Cox
2006-09-05 16:51         ` Grant Coady
2006-09-05 17:57           ` Krzysztof Halasa
2006-09-05 21:24             ` Grant Coady
2006-09-04 12:12   ` Jeff Garzik
2006-09-04 13:27   ` Alan Cox
2006-09-04 12:02 ` Alan Cox
2006-09-04 12:10   ` Jan Engelhardt
2006-09-04 12:15     ` Jeff Garzik
2006-09-05 13:30   ` John Stoffel
2006-09-05 13:46     ` Sergei Shtylyov
2006-09-05 15:10       ` John Stoffel
2006-09-05 20:48   ` Bill Davidsen [this message]
2006-09-06  7:48     ` Alan Cox
2006-09-04 21:31 ` Andras Mantia
2006-09-05  2:25   ` Jeff Garzik
2006-09-21 11:55 ` Lennert Buytenhek
2006-09-22  9:51   ` Jeff Garzik
2007-01-28 20:21     ` cirrus ep93xx pata driver (was: Re: PATA drivers queued for 2.6.19) Lennert Buytenhek
2007-05-29  1:27       ` cirrus ep93xx pata driver Jeff Garzik
2007-05-29  1:48         ` Lennert Buytenhek
2007-05-29  2:58           ` Jeff Garzik

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=44FDE2A0.3080705@tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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).