On Fri, 15 May 2009, David Woodhouse wrote: > On Fri, 2009-05-15 at 14:51 +0100, Jamie Lokier wrote: > > > > Eek, can you say a bit more about the ARM EABI mismatch? > > > > I would like to run a shiny modern ARM EABI kernel and userspace, but > > also need to run one or two OABI binaries (from the gcc 2.95 era) on > > the same kernel which I cannot recompile because they're built with > > closed source libraries only supplied as OABI. > > > > Does that not work at all? > > > > If it does work, which part of userspace must be EABI to work? > > It was just a note of caution that sometimes we _do_ change the ABI. > > I'm not 100% sure offhand whether the EABI kernel can support OABI > userspace; I didn't think so though. Yes it can, for basic stuff. That means basic system calls with issues are fixed up when necessary. This does not include things like ioctls though, and in this case your mileage may vary. Notably, ALSA is known to fail, some features of iptables too. See documentation at the top of arch/arm/kernel/sys_oabi-compat.c to get an idea of what to watch for. It is also possible to extend on what is already there for specific needs that are not covered by the current set of fixups (and contribute it back). But complete coverage is almost impossible to achieve and pointless. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
