From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Subject: ioread64()?
Date: Thu, 7 Sep 2006 16:41:42 +0200 [thread overview]
Message-ID: <200609071641.48513.eike-kernel@sf-tec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Hi,
I'm looking for a way to access 64 or 128 bit of device space in a single
access. For smaller accesses I use ioread32() and friends. But which way
should I do it for the next bigger accesses? Casting the iospace to something
like u64* looks very suspicious to me. Any better ideas?
Greetings,
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-09-07 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 14:41 Rolf Eike Beer [this message]
[not found] <fa.zgAWvZQAAp+6nKV9Kd93QR7HZHw@ifi.uio.no>
2006-09-07 23:23 ` ioread64()? Robert Hancock
2006-09-13 20:34 ` ioread64()? Arnd Bergmann
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=200609071641.48513.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--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 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.