| To: | Ladislav Michl <ladis@linux-mips.org> |
|---|---|
| Subject: | Re: Removal of ____raw_readq() and ____raw_writeq() from asm-mips/io.h |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Wed, 28 Jan 2004 17:01:37 +0100 |
| Cc: | Jes Sorensen <jes@wildopensource.com>, Kevin Paul Herbert <kph@cisco.com>, linux-mips@linux-mips.org |
| In-reply-to: | <20040128150828.A19525@linux-mips.org> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <1075255111.8744.4.camel@shakedown> <20040128094032.GB900@kopretinka> <yq07jzcz6sp.fsf@wildopensource.com> <20040128150828.A19525@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Wed, Jan 28, 2004 at 03:08:28PM +0000, Ladislav Michl wrote: > eh? I said nothing about PCI device. These ____raw_writeq are > used in board specific code. Anyway, defining struct sb_registers > and ioremaping it would be nice solution (I didn't read code too > carefully, so maybye not in this particular case where registers > are 64bit width, but I definitely prefer it in board specific code > over read[bwl]/write[bwl]). Also readq/writeq seems mips specific, > so rants about portability doesn't apply. They're not MIPS specific; they're just not so common because some people still believe 64-bit is something esotheric they don't need ;-) Try grep -lw readq include/asm-*/io.h - 6 architectures implement it. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux 2.6 on AMD Alchemy Au1500, Dan Malek |
|---|---|
| Next by Date: | Re: [patch] pg-r4k.c bugs for R4600 rev.2.0, Dominik 'Rathann' Mierzejewski |
| Previous by Thread: | Re: Removal of ____raw_readq() and ____raw_writeq() from asm-mips/io.h, Ladislav Michl |
| Next by Thread: | Re: Removal of ____raw_readq() and ____raw_writeq() from asm-mips/io.h, Jes Sorensen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |