| 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
| ||
|
Date: Fri, 7 Dec 2012 21:16:06 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Michal Simek <monstr@...str.eu> Cc: linux-arch@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: Using IO functions across ARM, PPC and Microblaze architectures > Because I need to use IO functions which will behave > on arm as little endian and on powerpc as big endian > and on microblaze depends on endian setting. > I haven't found any IO function which I could use by 3 architectures > without using preprocessor macros or runtime detection Its a rather weird mix. We can do "always big" and "always little" > 1. Using helper function + preprocessor macros > (using static inline function also possible) Then someone comes along and sticks a daughterboard into the system with the same device the other way around and there are years > 2. Using function pointers Probably smarter. 8250.c works this way and it has to handle some extremely bizarre mappings. > b) Runtime initialization - here is the question if there is > any standard function which I could use. Set the pointers up and pass them as data with your platform device, that way the function definitions are buried in your platform code where they depend. Alan -- 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