From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Richard Zidlicky" <rz@linux-m68k.org>,
"Andre Hedrick" <andre@linux-ide.org>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: IDE janitoring comments
Date: Tue, 24 Sep 2002 14:41:33 +0200 [thread overview]
Message-ID: <20020924124133.29552@192.168.4.1> (raw)
In-Reply-To: <20020924113535.11318@192.168.4.1>
>>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.
>
>No, it doesn't. There are already separate iops for control
>and datas, typically {in,out}{b,w,l} are for control (though
>only "b" versions are really useful and {in,out}s{b,w,l} are
>for datas.
Oops, sorry, I mis-read you
Well, if you have proper iops that swap for normal datas, then
you can use the "normal" fixup routines for control datas
like ident, the same we use on PPC or other BE archs.
The problem is typiucally the same for everybody here: the
swapping of datas themselves must be done so that you get an
exact image of the datas in memory, then you need additional
fixup to "interpret" some of these (ident, smart, ...)
Ben.
next prev parent reply other threads:[~2002-09-24 12:36 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 [this message]
2002-09-25 3:57 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
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=20020924124133.29552@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.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