Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: linux-mips@oss.sgi.com
Subject: Re: new asm-mips/io.h
Date: Mon, 26 Nov 2001 20:09:46 +1100	[thread overview]
Message-ID: <20011126200946.A8408@dea.linux-mips.net> (raw)
In-Reply-To: <20011126.123545.41627333.nemoto@toshiba-tops.co.jp>; from nemoto@toshiba-tops.co.jp on Mon, Nov 26, 2001 at 12:35:45PM +0900

On Mon, Nov 26, 2001 at 12:35:45PM +0900, Atsushi Nemoto wrote:

> A last cleanups for io.h looks bit wrong.  Please apply.

Yes, the byteswapping stuff (CONFIG_SWAP_IO_SPACE) also got lost.

> By the way, I have some boards which require special I/O routines.
> Some of these boards need byteswap on PCI I/O region but noswap on ISA
> region.  And some of these boards do not require byteswap but need
> swap the address ('port' values).  I added following codes to support
> these boards.  Is it worth to apply?

Not as is - the kernel has changed, so your patch wouldn't apply anymore.
Aside of that I don't think we'll have any alternative to do something
along the lines of your patch.  There are for example systems where the
high 8 bits of the I/O or memory address on the ISA bus are supplied in
a separate register of the chipset, not as part of the memory address
itself.  It's really remarkable how much bad taste some hardware designers
have ...

  Ralf

  reply	other threads:[~2001-11-26 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26  3:35 new asm-mips/io.h Atsushi Nemoto
2001-11-26  9:09 ` Ralf Baechle [this message]
2001-11-27  4:04   ` Atsushi Nemoto
2001-11-27  7:06     ` Ralf Baechle
2001-11-27 10:10       ` Atsushi Nemoto
2001-11-27 14:19         ` Ralf Baechle
2001-11-27 17:44       ` Jun Sun

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=20011126200946.A8408@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=nemoto@toshiba-tops.co.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