All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: libata - success with 82801AA IDE
Date: Wed, 29 Oct 2003 16:44:58 -0500	[thread overview]
Message-ID: <3FA034DA.8020102@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0310291626210.29421@marabou.research.att.com>

Pavel Roskin wrote:
> Hello!
> 
> I just want to report that Intel 82801AA IDE controller (8086:2411) is
> working with libata from 2.6.0-test9-bk3.  I applied following patch:

Cool.



> I have a CD-ROM as master on the the secondary channel (normally seen as
> /dev/hdc), but it doesn't support DMA, so it wasn't detected.

Well, even so, ATAPI support is very incomplete at the moment.  That's a 
bigger reason why PATA support isn't receiving more love, at the moment.


> I don't know if there is any interest in developing the "parallel IDE"
> support.  I see that the option to enable it is not present in Linux
> configuration.  Anyway, that's a device that can be added to the
> device table if PATA support is here to stay.

I find it quite useful locally, and will be finishing up cable detection 
(currently PATA is limited to UDMA/33) soon.  However, with my 
apologies, I won't be applying your patch -- for the moment.  Before any 
more PATA PCI ids are added, I'll need to go through the docs and 
drivers/ide/pci/piix.c, to determine precisely PATA chipset speed 
limits:  UDMA/133 for some, UDMA/100, etc.  Your patch is a bit 
incorrect in that it does not truly reflect the maximum speed of the 
82801AA chipset.

In any case, the executive decision has been made "drivers/ide for PATA, 
libata for SATA", so that's the overall direction.

Thanks,

	Jeff




      reply	other threads:[~2003-10-29 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 21:37 libata - success with 82801AA IDE Pavel Roskin
2003-10-29 21:44 ` 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=3FA034DA.8020102@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.