On Fri, Mar 15, 2002 at 08:00:24PM +0100, Bart De Schuymer wrote: > Hello Harald, > > I have had a user complaining about sparc64 incompatibilities for the kernel > patch I am maintaining. > My code uses [g,s]etsockopt like iptables. > I have been to the Sparc64 mailing list where they suggested ugly things > like making an __u64 out of a pointer to put it in a struct, or changing > unsigned int to __u32 in the structs. The main problem I have is that the > struct size in the kernel is different from that of the userspace. > Now, I double checked the iptables structs used in the communication, and > they use unsigned int happily. > So, I was hoping that someday somebody would enlighten me how the > kernel-userspace communication for iptables can work on the Sparc64. Could > you? A few hints would satisfy I think...
I don't have a very clear view on the user32/kernel64 issue on sparclinux either, sorry. I haven't done any hacking on that platform yet, so don't expect any explanation or help from me ;) On the other hand, I would gladly appreciate any pointers to information on what precicely the issues are. > cheers, > Bart -- Live long and prosper - Harald Welte / [EMAIL PROTECTED] http://www.gnumonks.org/ ============================================================================ GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+ V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*)
