From: Jun Sun <jsun@mvista.com>
To: linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: IDE woos in BE mode 2.6 kernel
Date: Thu, 24 Jun 2004 16:45:51 -0700 [thread overview]
Message-ID: <20040624164551.H29225@mvista.com> (raw)
Anybody has tried IDE disks in big endian mode with 2.6 kernel?
I seem to have troubles with Malta board.
Current malta board has CONFIG_SWAP_IO_SPACE defined and therefore
all inw, inl and their friends are byte-swapped in BE mode. As a
results all IDE IO ops (such as ide_inw, etc) do swapping too.
A quick experiement shows those IDE IO ops should not do swapping.
Anybody knows why?
Apparently fixing the above is not enough. I either encountered
failure to read partition table or having DMA error. Any clues
here?
I suppose this problem really should exist for other arches
with BE support. Anybody knows how other arches deal with this?
Thanks.
Jun
next reply other threads:[~2004-06-24 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:45 Jun Sun [this message]
2004-06-25 8:45 ` IDE woos in BE mode 2.6 kernel Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2004-09-17 19:18 Manish Lachwani
2004-09-18 14:19 ` Atsushi Nemoto
2004-09-24 23:40 ` Manish Lachwani
2004-09-25 14:41 ` Atsushi Nemoto
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=20040624164551.H29225@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.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