| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-id: <4500A9EF.40807@shaw.ca> Date: Thu, 07 Sep 2006 17:23:27 -0600 From: Robert Hancock <hancockr@...w.ca> To: Rolf Eike Beer <eike-kernel@...tec.de> Cc: linux-kernel@...r.kernel.org Subject: Re: ioread64()? Rolf Eike Beer wrote: > 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 There's no portable way to do this as far as I'm aware, for the likely reason that on many architectures it's impossible to do it in one access.. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@...pamshaw.ca Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists