Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: linux-ide@vger.kernel.org
Subject: Re: [RFC][DOC] writing IDE driver guidelines
Date: Sat, 5 Jun 2004 12:49:59 -0700	[thread overview]
Message-ID: <20040605194959.GA13228@buici.com> (raw)
In-Reply-To: <200405151923.50343.bzolnier@elka.pw.edu.pl>

On Sat, May 15, 2004 at 07:23:50PM +0200, Bartlomiej Zolnierkiewicz wrote:
> - IDE is going into full host driver model
>   so write host driver for your interface

Can you tell me what this means?  Is arm/rapide.c an example?  If not,
what *is* and example?  Is the arm/ide_arm.c *not* the right way?

> - see drivers in drivers/ide/arm and drivers/ide/legacy for examples
>   (especially m68k and arm specific drivers)
> 
> - do not use ide_setup_ports()

Hmm.  macide in legacy does.  Is this, then, a bad bad example legacy?

The piece I'm missing is how to replace the ioops functions for my
platform.  I could implement something in ide-iops.c.  Is that the way?



  parent reply	other threads:[~2004-06-05 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-15 17:23 [RFC][DOC] writing IDE driver guidelines Bartlomiej Zolnierkiewicz
2004-05-15 17:34 ` Jeff Garzik
2004-05-15 17:58   ` Bartlomiej Zolnierkiewicz
2004-05-15 18:13     ` Bartlomiej Zolnierkiewicz
2004-05-15 22:23     ` Jeff Garzik
2004-05-16  1:00       ` Marc Singer
2004-05-16 19:34         ` Bartlomiej Zolnierkiewicz
2004-05-16 19:26       ` Bartlomiej Zolnierkiewicz
2004-05-16  0:51     ` Marc Singer
2004-05-16 19:33       ` Bartlomiej Zolnierkiewicz
2004-06-05 19:49 ` Marc Singer [this message]
2004-06-05 20:36   ` Bartlomiej Zolnierkiewicz
2004-06-05 22:13     ` Marc Singer
2004-06-05 22:37       ` 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=20040605194959.GA13228@buici.com \
    --to=elf@buici.com \
    --cc=linux-ide@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