mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: <linux-kernel@vger.kernel.org>
Subject: ATA/ATAPI driver development
Date: Sat, 19 May 2001 23:01:18 -0700	[thread overview]
Message-ID: <000901c0e0f2$499590a0$6daaa8c0@Kevin> (raw)

I'm getting ready to make some changes to the ide-floppy driver (to support
dynamic media change notification), and after spending a few days reviewing
most of the IDE driver code (ide, ide-disk, ide-cd, ide-floppy and
ide-probe), I think I've got a good handle on what needs to be done.
However, since what I need to do involves sending some ATA (not ATAPI)
commands to the drive, that will add some complexity to the ide-floppy
driver. I'm not opposed to that, but it appears that many of the other
drivers (ide, ide-disk and ide-cd) already have code to send an ATA command
(writing to the registers), and interrupt handlers to handle sending or
receiving the buffer(s) of data that the command wants to transfer.

Is this the way it is intended to be, with this code duplicated in multiple
subdrivers? The sheer complexity of the DMA interface would make me think it
would be far better for this "infrastructure" stuff to all be in ide.c, and
just be used by the subdrivers. I can certainly make yet another copy of the
code for the few commands that ide-floppy will need to be able to issue, but
before I went about that I thought I'd see if there was a better plan...
Thanks for your attention.


                 reply	other threads:[~2001-05-20  5:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000901c0e0f2$499590a0$6daaa8c0@Kevin' \
    --to=kevin@labsysgrp.com \
    --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®