From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Eric Mudama <edmudama@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Albert Lee <albertcc@tw.ibm.com>,
IDE Linux <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@maxeymade.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: libata PATA support - work items?
Date: Wed, 05 Jan 2005 00:50:05 +0000 [thread overview]
Message-ID: <1104886199.17176.115.camel@localhost.localdomain> (raw)
In-Reply-To: <41DB299C.3030405@pobox.com>
On Maw, 2005-01-04 at 23:41, Jeff Garzik wrote:
> So, that said, I think it is important for libata to fully support PATA,
> if it is to support it at all. That means handling the errata that Alan
> always bugs me about, and that means handling C/H/S support as well.
I think so. If it supports all the features of the old IDE layer we get
to have a party when we eliminate the need for drivers/ide once and for
all.
That means
- Hotplug (controller and disk)
- CHS
- "Not quite generic" IDE DMA (eg CS5520)
- VDMA (eg CS5520)
- IORDY timers (not handled well in drivers/ide but needed)
- Funky Maxtor "LBA48.. maybe" oddments
- Missing slave detection
- Controller errata hooks (modes, drives, timings, "dont touch during an
I/O" etc)
- Drive nIEN bugs
- No nIEN cases
- Drives that don't do some DMA/modes right
- Crazy shit "Don't DMA from the page below 640K" (not handled by
drivers/ide but an AMD errata
fixed by using a PS/2 mouse)
- Serialize (RZ1000, CMD640, some 469, etc)
- Bandwidth arbiter (not in drivers/ide but needed)
- Non PCI shared IRQ mess 8(
Hopefully most of this can be buried away in a pata-errata.c 8)
next prev parent reply other threads:[~2005-01-05 1:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 10:42 libata PATA support - work items? Albert Lee
2005-01-01 19:19 ` Eric Mudama
2005-01-03 20:56 ` Greg Freemyer
2005-01-03 21:20 ` Eric Mudama
2005-01-03 22:09 ` Bartlomiej Zolnierkiewicz
2005-01-04 23:43 ` Jeff Garzik
2005-01-04 23:41 ` Jeff Garzik
2005-01-05 0:50 ` Alan Cox [this message]
2005-01-05 2:42 ` Jeff Garzik
2005-01-05 3:43 ` Alan Cox
2005-01-05 2:56 ` Andi Kleen
2005-01-05 12:59 ` Bartlomiej Zolnierkiewicz
2005-01-04 23:32 ` Jeff Garzik
2005-01-06 8:51 ` Albert Lee
2005-01-06 21:29 ` Alan Cox
2005-01-06 23:07 ` Bartlomiej Zolnierkiewicz
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=1104886199.17176.115.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=axboe@suse.de \
--cc=bzolnier@gmail.com \
--cc=dwm@maxeymade.com \
--cc=edmudama@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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 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.