From: Jes Sorensen <jes@trained-monkey.org>
To: dsaxena@mvista.com
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>,
Christoph Hellwig <hch@infradead.org>,
"David S. Miller" <davem@redhat.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix ppc ioremap prototype
Date: 04 Sep 2003 12:36:45 -0400 [thread overview]
Message-ID: <m3ekywbjdu.fsf@trained-monkey.org> (raw)
In-Reply-To: <20030904155856.GB31420@xanadu.az.mvista.com>
>>>>> "Deepak" == Deepak Saxena <dsaxena@mvista.com> writes:
Deepak> What happens if I have a device that can be either ISA or
Deepak> connected directly to a local memory bus? The driver should be
Deepak> able to ioremap(some resource) and then read/write the device
Deepak> without having to have ugly #ifdefs to deal with different bus
Deepak> types.
You can't do that reliably, some architectures requires different
access for ISA vs PCI vs random-other busses. The driver needs to be
aware what bus it's trying to go through.
Deepak> Example in point is the CS8900a device which is hooked
Deepak> up directly to a FPGA on the local memory bus with the
Deepak> bytelanes backwards. The ammount of hacking done in the
Deepak> driver to get around that is ugly. It would be much nicer if
Deepak> the driver still just did read*/write* and the platform level
Deepak> code could deal with all the translation issues. This requires
Deepak> a generic API for all I/O devices.
That might be nicer from the driver perspective but it will make
readb/writeb a lot more complex and inefficient for no reason on some
architectures.
The driver will have to know whether it's on a PCI, ISA or directly
attached anyway when it's probing so it's perfectly reasonable to
expect it to deal with that when it's accessing the registers as well.
Cheers,
Jes
next prev parent reply other threads:[~2003-09-04 16:37 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 20:32 [PATCH] fix ppc ioremap prototype Christoph Hellwig
2003-09-04 0:33 ` Paul Mackerras
2003-09-04 7:13 ` Christoph Hellwig
2003-09-04 7:25 ` David S. Miller
2003-09-04 7:30 ` Russell King
2003-09-04 7:38 ` Christoph Hellwig
2003-09-04 8:09 ` David S. Miller
2003-09-04 8:12 ` Linus Torvalds
2003-09-04 8:10 ` David S. Miller
2003-09-04 8:28 ` Christoph Hellwig
2003-09-04 10:06 ` Benjamin Herrenschmidt
2003-09-04 11:03 ` Paul Mackerras
2003-09-04 12:21 ` Geert Uytterhoeven
2003-09-04 12:41 ` Paul Mackerras
2003-09-04 12:41 ` David S. Miller
2003-09-04 12:57 ` Geert Uytterhoeven
2003-09-04 15:58 ` Deepak Saxena
2003-09-04 16:15 ` Geert Uytterhoeven
2003-09-04 16:36 ` Jes Sorensen [this message]
2003-09-04 23:18 ` Paul Mackerras
2003-09-05 20:56 ` Geert Uytterhoeven
2003-09-04 16:41 ` Linus Torvalds
2003-09-04 16:43 ` David S. Miller
2003-09-04 17:06 ` Linus Torvalds
2003-09-04 17:03 ` David S. Miller
2003-09-04 17:16 ` Linus Torvalds
2003-09-04 17:13 ` Jeff Garzik
2003-09-04 17:24 ` Linus Torvalds
2003-09-05 8:02 ` Eric W. Biederman
2003-09-04 8:22 ` Christoph Hellwig
2003-09-04 9:29 ` Christoph Hellwig
2003-09-04 10:07 ` Benjamin Herrenschmidt
2003-09-04 9:21 ` Paul Mackerras
2003-09-04 9:36 ` David S. Miller
2003-09-04 9:48 ` Russell King
2003-09-04 9:51 ` Christoph Hellwig
2003-09-04 12:38 ` Paul Mackerras
2003-09-04 12:59 ` Paul Mackerras
2003-09-04 13:01 ` David S. Miller
2003-09-04 14:15 ` Matt Porter
2003-09-04 14:12 ` David S. Miller
2003-09-04 13:30 ` Russell King
2003-09-04 15:50 ` Deepak Saxena
2003-09-04 16:09 ` David S. Miller
2003-09-04 10:34 ` Alan Cox
2003-09-04 10:33 ` David S. Miller
2003-09-04 12:42 ` Jeff Garzik
2003-09-04 12:43 ` David S. Miller
2003-09-04 14:36 ` Matt Porter
2003-09-04 14:30 ` David S. Miller
2003-09-04 15:26 ` Matt Porter
2003-09-04 16:03 ` David S. Miller
2003-09-04 15:35 ` Linus Torvalds
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=m3ekywbjdu.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=davem@redhat.com \
--cc=dsaxena@mvista.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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