From: Erik Mouw <erik@harddisk-recovery.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] QD65xx I/O ports
Date: Tue, 13 Apr 2004 15:47:08 +0200 [thread overview]
Message-ID: <20040413134708.GB13298@harddisk-recovery.com> (raw)
In-Reply-To: <200404090050.24841.bzolnier@elka.pw.edu.pl>
On Fri, Apr 09, 2004 at 12:50:24AM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 06 of April 2004 13:31, Geert Uytterhoeven wrote:
> > I/O port numbers can be larger than 8-bit on many platforms (this caused a
> > warning when {out,in}b() cast reg to a pointer on platforms with memory
> > mapped I/O)
>
> Was VESA Local Bus ever used on something else than 486?
IIRC there were early Pentium boards with VESA Local Bus (VLB), but my
memory is vague about that.
> I think it's better to just add "depends on X86" to drivers/ide/Kconfig.
VLB is nothing more than ISA with a 32 bit address and data bus. That
is exactly how many busses on embedded CPUs work, but with the
difference that they map the ISA 16bit memory and IO space somewhere in
their 4GB memory space.
For example: the Digital/Intel StrongARM SA-11x0 has a 32 bit bus,
which (with the help of some glue logic) works like a 32 bit ISA bus.
Quite some embedded hardware emulates a 16 bit ISA bus by mapping the
ISA memory and IO space in a special memory area which can live
anywhere in the 4GB space, and that's why Geert wants an unsigned long
address in {out,in}b().
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2004-04-13 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 11:31 Geert Uytterhoeven
2004-04-08 22:50 ` Bartlomiej Zolnierkiewicz
2004-04-13 13:47 ` Erik Mouw [this message]
2004-04-14 1:40 ` Cef (LKML)
2004-04-14 1:52 ` 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=20040413134708.GB13298@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®