mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Parallel ATA with libata status with the patches I'm working on
Date: Thu, 3 Nov 2005 15:58:12 +0100	[thread overview]
Message-ID: <58cb370e0511030658tb23cecds2ed8cc63570a68d5@mail.gmail.com> (raw)
In-Reply-To: <1131029686.18848.48.camel@localhost.localdomain>

On 11/3/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Core Features Fixed
> - Per drive tuning
> - Filter quirk lists
> - Single channel support

Are these the same changes that have been recently pushed into
Linus' tree without any previous public review or some new ones?

> And To Add
> - Specify PCI bus speed
> - HPA
> - IRQ mask
> - PIO only LBA48
> - Serialize
> - CRC downspeed
> - Mixed legacy/native mode (most work done)
>
> Drivers so far written for the libata parallel work I'm doing

Are the patches available somewhere?

> ALI
> Driver written with equivalent support to the drivers/ide one. Needs
> core changes for LBA48 PIO only
>
> AMD
> Driver written, given basic testing and equivalent to current
> drivers/ide

Functionality can't be the same as drivers/ide because libata
lacks some core features.

> CS5520
> Driver written, some debug work to do. Works unlike the drivers/ide one

Please fix drivers/ide also if not a big problem.

> HPT34X
> Driver written, functionality same as drivers/ide. Needs more testing.

Same comment as for AMD.

> Serverworks
> Written, equivalent functionality to drivers/ide plus some bugs fixed

Ditto.  Also please backport fixes to drivers/ide.

Thanks,
Bartlomiej

  parent reply	other threads:[~2005-11-03 14:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 14:54 Alan Cox
2005-11-03 14:48 ` Russell King
2005-11-03 15:02   ` Bartlomiej Zolnierkiewicz
2005-11-03 15:28     ` David S. Miller
2005-11-03 15:48       ` Bartlomiej Zolnierkiewicz
2005-11-03 16:27         ` Alan Cox
2005-11-03 15:56     ` Alan Cox
2005-11-03 20:55     ` Krzysztof Halasa
2005-11-03 21:29       ` Bartlomiej Zolnierkiewicz
2005-11-03 22:29         ` Krzysztof Halasa
2005-11-03 22:48           ` Bartlomiej Zolnierkiewicz
2005-11-03 22:54         ` Alan Cox
2005-11-04  1:30           ` Rogério Brito
2005-11-04 13:38             ` Alan Cox
2005-11-04 13:41             ` Alan Cox
2005-11-04 23:10               ` Russell King
2005-11-04 23:19                 ` Benjamin Herrenschmidt
2005-11-03 15:58   ` Alan Cox
2005-11-03 15:30     ` Russell King
2005-11-03 16:23       ` Alan Cox
2005-11-04  3:35       ` Jeff Garzik
2005-11-04  3:35     ` Jeff Garzik
2005-11-04  8:43       ` Xavier Bestel
2005-11-03 14:58 ` Bartlomiej Zolnierkiewicz [this message]
2005-11-03 15:49   ` Alan Cox
2005-11-03 15:34     ` Bartlomiej Zolnierkiewicz
2005-11-04  0:14     ` Mark Lord
2005-11-04  0:17       ` Mark Lord
2005-11-04  1:18         ` Alan Cox
2005-11-04  3:49 ` Jeff Garzik
2005-11-05 22:31   ` Mark Lord
2005-11-04  6:43 ` Benjamin Herrenschmidt
2005-11-04  7:00   ` Jeff Garzik
2005-11-04 13:34   ` Alan Cox
2005-11-04 21:50     ` Benjamin Herrenschmidt
2005-11-06 20:41       ` Alan Cox

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=58cb370e0511030658tb23cecds2ed8cc63570a68d5@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®