From: Andre Hedrick <andre@linux-ide.org>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: IDE janitoring comments
Date: Tue, 24 Sep 2002 20:57:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10209242056570.6896-100000@master.linux-ide.org> (raw)
In-Reply-To: <20020924112732.B1060@linux-m68k.org>
Switch the transport on the fly for the channel based on the OPCODE.
Easy to say harder to do.
Andre Hedrick
LAD Storage Consulting Group
On Tue, 24 Sep 2002, Richard Zidlicky wrote:
> On Mon, Sep 23, 2002 at 05:28:03PM -0700, Andre Hedrick wrote:
> >
> > Poke in your own special ide-ops function pointers.
> > This should have been allowed on a per chipset/channel bases.
>
> I need different transfer functions depending on whether drive
> control data(like IDENT,SMART) or HD sectors are to be transfered.
> Control data requires byteswapping to correct bus-byteorder
> whereas sector r/w has to be raw for compatibility.
>
> So that will require 2 additional iops pointers and some change
> in ide_handler_parser or ide_cmd_type_parser to select the
> appropriate version depending on the drive command.
>
> Richard
>
next prev parent reply other threads:[~2002-09-25 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 15:09 IDE janitoring comments Benjamin Herrenschmidt
2002-09-23 22:01 ` Richard Zidlicky
2002-09-23 7:29 ` Benjamin Herrenschmidt
2002-09-24 0:28 ` Andre Hedrick
2002-09-24 9:27 ` Richard Zidlicky
2002-09-24 11:35 ` Benjamin Herrenschmidt
2002-09-24 12:41 ` Benjamin Herrenschmidt
2002-09-25 3:57 ` Andre Hedrick [this message]
2002-08-24 15:15 Benjamin Herrenschmidt
2002-08-24 20:14 ` Alan Cox
2002-08-24 21:01 ` Andre Hedrick
2002-08-24 22:28 ` Benjamin Herrenschmidt
2002-08-24 20:56 ` Andre Hedrick
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=Pine.LNX.4.10.10209242056570.6896-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rz@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).