From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: linux-kernel@vger.kernel.org, B.Zolnierkiewicz@elka.pw.edu.pl,
linux-ide@vger.kernel.org
Subject: Re: Any guides for adding new IDE chipset drivers?
Date: Tue, 17 Feb 2004 07:41:31 -0800 [thread overview]
Message-ID: <20040217074131.5061fc5f.rddunlap@osdl.org> (raw)
In-Reply-To: <1077028026.31892.153.camel@cambridge.braddahead.com>
On Tue, 17 Feb 2004 14:27:06 +0000 Alex Bennee <kernel-hacker@bennee.com> wrote:
| On Monday 16 of Febuary 2004 09:40:21 PST, Bart wrote:
| >On Monday 16 of February 2004 18:04, Alex Bennee wrote:
| >
| >> Is there a driver that can be held of as an example of good taste and
| >> the "right" way to implement a chipset driver?
| >
| >Yep. Please take a look at drivers/ide/arm/icside.c.
| >It is well written, quite simple and has DMA support.
|
| Thanks. I'll base my driver on this one as it does seem quite easy
| to follow. However I'm wondering what the point of the begin/end functions
| are. The dma_read/write functions just seem to call dma_count which starts the
| dma requests going.
|
| Am I missing something here? Is all that required from the higher level a single
| call to dma_read/write or should I be expecting a series of calls to setup a transfer?
|
|
| >If you have any questions/issues feel free to ask
| >on linux-ide@vger.kernel.org mailing list.
|
| Hmmm, vger seems to be ignoring my subscribe requests.
|
| Is the list archived anywhere? None are listed on VGER.
http://marc.theaimsgroup.com/?l=linux-ide
--
~Randy
kernel-janitors project: http://janitor.kernelnewbies.org/
next prev parent reply other threads:[~2004-02-17 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 14:27 Alex Bennee
2004-02-17 15:41 ` Randy.Dunlap [this message]
2004-02-17 19:10 ` Bartlomiej Zolnierkiewicz
2004-02-18 10:41 ` Alex Bennee
-- strict thread matches above, loose matches on Subject: below --
2004-02-16 17:04 Alex Bennee
2004-02-16 17:39 ` 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=20040217074131.5061fc5f.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=kernel-hacker@bennee.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 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®