Alan Cox <[EMAIL PROTECTED]> writes: >> Delightful. So what are the options here? Start packing the device table >> structs is the obvious quick fix. Declaring cross-compilation unsupported >> isn't really viable, and I guess determining padding differences is far from >> easy. > > There are some ugly options: > > Cross compile a test object containing nothing but > > struct whatever fred; > > then dump it with the relevant cross nm
Everything would be much easier if all those driver_data members of the device table structs would not be there. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
