From: Jeff Garzik <jgarzik@pobox.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA ATAPI work in progress
Date: Thu, 13 May 2004 17:44:38 -0400 [thread overview]
Message-ID: <40A3EC46.4050909@pobox.com> (raw)
In-Reply-To: <1084484186.4524.3.camel@patibmrh9>
Pat LaVarre wrote:
>>Are you willing to work
>
>
> Yes I want to learn.
>
> I figure I can learn fastest by helping.
>
>
>>on a separate, pre-requisite patch:
>>
>>We need to split ata_bmdma_start_{pio,mmio} into separate "setup" and
>>"start" pieces.
>>
>>This would involve adding a "bmdma_setup" hook to struct
>>ata_port_operations in include/linux/libata.h, and then doing a simple
>>update of all the SATA drivers, to use the default libata-core
>>implementations.
>
>
> Sorry as yet I understand very little of the above.
>
> Until corrected I will guess I should next:
> 4) Report back here for next assignment.
hehe
The above is something that applies to all of libata, and changes the
libata API so that ATAPI is doable.
It looks something like:
1) add ->bmdma_setup hook to include/linux/libata.h
2) walk through each of drivers/scsi/*ata_*.c and make an adjustment
like the following:
.bmdma_start: ata_bmdma_start_mmio,
+ .bmdma_setup: ata_bmdma_setup_mmio,
3) create new functions ata_bmdma_setup_{mmio,pio}.
4) move EVERYTHING except the final writeb() from ata_bmdma_start_mmio
to ata_bmdma_setup_mmio.
5) do the same for ata_bmdma_{start,setup}_pio.
at this point, it is highly likely that sata_promise.c and sata_sx4.c
are broken, but the other drivers should work 100%.
for bonus points,
6) fix sata_promise and sata_sx4
otherwise I can do that.
The only hardware required for this task is a SATA hard drive and SATA
host controller.
Jeff
next prev parent reply other threads:[~2004-05-13 21:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 20:20 SATA ATAPI work in progress Pat LaVarre
2004-05-12 20:40 ` Jeff Garzik
2004-05-12 23:14 ` Pat LaVarre
2004-05-13 15:07 ` Pat LaVarre
2004-05-13 20:56 ` Jeff Garzik
2004-05-13 21:16 ` Jeff Garzik
2004-05-13 21:25 ` Jeff Garzik
2004-05-13 21:36 ` Pat LaVarre
2004-05-13 21:44 ` Jeff Garzik [this message]
2004-05-13 21:49 ` Jeff Garzik
2004-05-14 18:23 ` Pat LaVarre
2004-05-14 18:55 ` Jeff Garzik
2004-05-14 19:37 ` when limited to a single DRQ block per disk transaction Pat LaVarre
2004-05-14 19:50 ` Jeff Garzik
2004-05-14 20:12 ` Pat LaVarre
2004-05-14 23:47 ` SATA ATAPI work in progress Pat LaVarre
2004-05-15 0:02 ` Pat LaVarre
2004-05-15 0:38 ` Jeff Garzik
2004-05-15 13:06 ` Pat LaVarre
2004-05-15 13:49 ` Pat LaVarre
2004-05-15 15:27 ` Jeff Garzik
2004-05-15 15:49 ` Pat LaVarre
2004-05-15 15:56 ` Pat LaVarre
2004-05-15 16:04 ` Pat LaVarre
2004-05-15 16:32 ` Jeff Garzik
2004-05-15 16:43 ` Pat LaVarre
2004-05-15 16:50 ` Pat LaVarre
2004-05-15 16:30 ` Jeff Garzik
2004-05-15 0:46 ` [PATCH] " Jeff Garzik
2004-05-15 13:08 ` Pat LaVarre
2004-05-15 13:10 ` Pat LaVarre
2004-05-15 14:13 ` Pat LaVarre
2004-05-14 18:28 ` Pat LaVarre
2004-05-14 18:38 ` Jeff Garzik
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=40A3EC46.4050909@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=p.lavarre@ieee.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.