From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Richard Zidlicky" <rz@linux-m68k.org>
Cc: "Andre Hedrick" <andre@linux-ide.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
<linux-kernel@vger.kernel.org>
Subject: Re: IDE janitoring comments
Date: Mon, 23 Sep 2002 09:29:42 +0200 [thread overview]
Message-ID: <20020923072942.21213@192.168.4.1> (raw)
In-Reply-To: <20020924000134.A210@linux-m68k.org>
>we have one special problem on m68k, on some machines the IDE
>bus is byteswapped (unrelated to cpu endianness). For historical
>and performance reasons data to the HD is by default read and
>written in this "wrong" order (thus the bswap/swapdata option)
>and special fixup code is used in ide_fix_driveid (see
>M68K_IDE_SWAPW). However data returned by IDE_DRIVE_CMD is not
>treated in any way, so that eg WIN_SMART data end up in the
>wrong order on those machines and this is something I would
>like to fix properly.
>I figure I would define ata_*_{control,data} to handle special
>data resp raw HD data and modify ide_handler_parser to return
>specialised interrupt handlers or set some additional flag.
>
>Any thoughts?
You just need to provide your own ide-ops doing the right
thing, I don't think you need to touch ata_*_data if you
properly implement "s" ops {in,out}s{b,w,l} for your hwif.
Ben.
next prev parent reply other threads:[~2002-09-24 7:41 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 [this message]
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
-- 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=20020923072942.21213@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.