From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: linux-ide@vger.kernel.org
Subject: Re: H8/300 target support patch
Date: Tue, 17 Feb 2004 23:55:54 +1100 [thread overview]
Message-ID: <1077022554.1080.7.camel@gaston> (raw)
In-Reply-To: <m2lln2ndnu.wl%ysato@users.sourceforge.jp>
> > Your IDE bus is flipped backward ? The next one who do that should
> > lose all rights to do any kind of HW design... Or is it a big endian
> > platform ? In this case, use normal flipping inw/outw for IOs and
> > non-flipping for stream IOs (insw/outsw)
>
> This architecture is big endian.
A big endian architecture needs the standard inx/outx macros to
be byteswapped, but _not_ the insw/outsw. That should be all
done properly from the standard macros in your asm/io.h, you
should _not_ have to byteswap normal transfers.
> It was my misunderstanding that did not use asm/io.h.
> It is the patch which it corrected to use it.
> h8300/h8_ide_iops.h becomes needless.
Ben.
next prev parent reply other threads:[~2004-02-17 12:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 6:05 H8/300 target support patch Yoshinori Sato
2004-02-15 14:40 ` Bartlomiej Zolnierkiewicz
2004-02-16 16:09 ` Yoshinori Sato
2004-02-16 16:40 ` Bartlomiej Zolnierkiewicz
2004-02-16 22:07 ` Benjamin Herrenschmidt
2004-02-16 22:09 ` Benjamin Herrenschmidt
2004-02-17 11:33 ` Yoshinori Sato
2004-02-17 12:55 ` Benjamin Herrenschmidt [this message]
2004-02-19 16:12 ` Yoshinori Sato
2004-02-19 16:34 ` Bartlomiej Zolnierkiewicz
2004-02-20 12:28 ` Yoshinori Sato
2004-02-20 15:25 ` Bartlomiej Zolnierkiewicz
2004-02-20 17:58 ` Yoshinori Sato
2004-02-20 18:42 ` Bartlomiej Zolnierkiewicz
2004-02-22 16:30 ` Yoshinori Sato
2004-02-22 17:08 ` Bartlomiej Zolnierkiewicz
2004-02-22 17:28 ` Bartlomiej Zolnierkiewicz
2004-02-26 16:46 ` Yoshinori Sato
2004-02-26 19:26 ` Bartlomiej Zolnierkiewicz
2004-02-28 17:02 ` Yoshinori Sato
2004-02-28 17:55 ` 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=1077022554.1080.7.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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