From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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: Tue, 04 Jan 2005 21:42:31 -0500 [thread overview]
Message-ID: <41DB5417.8020608@pobox.com> (raw)
In-Reply-To: <1104886199.17176.115.camel@localhost.localdomain>
Alan Cox wrote:
> That means
> - Hotplug (controller and disk)
mostly either there, or easy to add
> - CHS
nod
> - "Not quite generic" IDE DMA (eg CS5520)
> - VDMA (eg CS5520)
existing hooks can handle these
> - IORDY timers (not handled well in drivers/ide but needed)
I think I know what this is.
> - Funky Maxtor "LBA48.. maybe" oddments
details?
> - Missing slave detection
Not missing, master/slave has been working for ages. Needed for
combined mode, where a SATA device can appear as a slave.
> - Controller errata hooks (modes, drives, timings, "dont touch during an
> I/O" etc)
Controller hooks for most situations already exist, for the most part.
Device hooks are what is lacking.
> - Drive nIEN bugs
ditto above ("device hooks are lacking")
> - No nIEN cases
already handled in at least one case (AHCI)
> - Drives that don't do some DMA/modes right
easily doable with existing hooks
> - 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)
heh, interesting
> - Serialize (RZ1000, CMD640, some 469, etc)
non-trivial but doable (and planned-for)
> - Bandwidth arbiter (not in drivers/ide but needed)
interesting
> - Non PCI shared IRQ mess 8(
details?
Thanks,
Jeff
next prev parent reply other threads:[~2005-01-05 2:42 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
2005-01-05 2:42 ` Jeff Garzik [this message]
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=41DB5417.8020608@pobox.com \
--to=jgarzik@pobox.com \
--cc=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=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.