From: Jim Paris <jim@jtan.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA]
Date: Tue, 18 Dec 2001 02:03:44 -0500 [thread overview]
Message-ID: <20011218020344.A10509@neurosis.mit.edu> (raw)
In-Reply-To: <20011217193432.A7115@dea.linux-mips.net>; from ralf@oss.sgi.com on Mon, Dec 17, 2001 at 07:34:32PM -0200
> ISA, the good old stonage PC bus system with all it's limitations that also
> infected some MIPS systems.
Let me restate my problem differently, and perhaps a bit more clearly
(as I see it):
My system (Vadem Clio 1000, vr4111) has a VG-469 (i82365) PCMCIA
controller with IO port space at 0x14000000, and IO memory space
at 0x10000000.
The i82365 driver makes the following (reasonable?) expectations:
1) it can use check/request/release_region on I/O ports
- this works fine.
2) it can use in[bwl] and out[bwl] with absolute port numbers
- this also works fine.
3) it can use check/request/release_mem_region on I/O memory
- this fails, because the iomem resource map contains the kernel:
> -more /proc/iomem
00000000-00ffffff : System Ram
00002000-001bc6af : Kernel code
001cf300-00299fff : Kernel data
(this seems very wrong to me, since the kernel is most definately
not in the I/O memory space; real memory, of course, but I/O memory??)
4) it can use ioremap, and then read[bwl] and write[bwl] with the result
- this fails with the current ioremap; neither ioremap nor read/write[bwl]
take isa_slot_offset into account
Am I misunderstanding how this stuff is supposed to work? Is the
i82365 driver doing anything wrong?
(The i82365 driver also makes the incorrect assumption that PCMCIA IRQs
directly correspond to system IRQs, but this is definately a problem
with the driver and I've fixed that.)
-jim
next prev parent reply other threads:[~2001-12-18 8:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 20:15 [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA] Jim Paris
2001-12-17 21:34 ` Ralf Baechle
2001-12-18 5:45 ` Jim Paris
2001-12-18 7:03 ` Jim Paris [this message]
2001-12-18 4:03 ` hanishkvc
2001-12-18 18:10 ` Jun Sun
2001-12-18 18:45 ` Jim Paris
2001-12-18 18:45 ` Jim Paris
2001-12-18 19:09 ` Jun Sun
2001-12-18 19:30 ` Ralf Baechle
2001-12-19 9:40 ` Geert Uytterhoeven
2001-12-18 18:25 ` Ralf Baechle
2001-12-18 18:57 ` Jim Paris
2001-12-18 19:21 ` Jun Sun
2001-12-18 20:58 ` Ralf Baechle
2001-12-18 21:28 ` Jim Paris
2001-12-18 21:53 ` Maciej W. Rozycki
2001-12-19 9:34 ` Geert Uytterhoeven
2001-12-22 12:47 ` Ralf Baechle
2001-12-18 19:16 ` Jun Sun
2001-12-18 19:31 ` Ralf Baechle
2001-12-18 19:36 ` Jun Sun
2001-12-18 20:02 ` Karsten Merker
2001-12-18 20:22 ` Maciej W. Rozycki
2001-12-18 22:28 ` Ralf Baechle
2001-12-19 9:34 ` Geert Uytterhoeven
2001-12-19 16:47 ` Ralf Baechle
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=20011218020344.A10509@neurosis.mit.edu \
--to=jim@jtan.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/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.