linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk, alan@redhat.com
Subject: Re: [patch 9/9] pata_legacy: restructure and revamp
Date: Tue, 18 Dec 2007 17:08:42 -0500	[thread overview]
Message-ID: <476844EA.10204@garzik.org> (raw)
In-Reply-To: <200712140001.lBE01j6b025453@imap1.linux-foundation.org>

akpm@linux-foundation.org wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> 
> Rework the pata_legacy driver to have an internal way to plug multiple
> legacy interface types and designs into the driver.
> 
> This driver supports
> 	- Generic legacy ISA on primary/secondary and tertiary ports
> 	- BIOS or jumper configured legacy ports
> 	- VLB controllers that snoop the mode set for PIO
> 		(Cirrus CLPD7220, Adaptec AIC25VL01)
> 	- Promise PDC20230
> 	- Holtek 6560A/B
> 	- Opti VLB controllers
> 	- QDI 6500/6580/6580DP controllers
> 
> The new driver also adds an "all" option so you can load all the PCI
> drivers you have, decide you have a controller that is totally unknown and
> then load pata_legacy all=1 to grab the primary/secondary ports as a last
> resort fallback.
> 
> TODO:
> 	Add ST412 support (needs some kind of geometry hook in libata core code)
> 	Winbond W83759A in programmable mode (aka DTC2278)
> 	Find more insane VLB controllers to support
> 
> This driver obsoletes pata_qdi, which can go once this is settled in.
> 
> Signed-off-by: Alan Cox <alan@redhat.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  drivers/ata/pata_legacy.c |  765 ++++++++++++++++++++++++++++--------
>  1 file changed, 607 insertions(+), 158 deletions(-)

ACK but needs rediffing



      reply	other threads:[~2007-12-18 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14  0:01 [patch 9/9] pata_legacy: restructure and revamp akpm
2007-12-18 22:08 ` Jeff Garzik [this message]

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=476844EA.10204@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=linux-ide@vger.kernel.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).