05.08.2014 00:37, Vagrant Cascadian wrote: > On 2014-08-02, Michael Tokarev wrote: >> Since qemu 2.1, there's a e500 ppc emulation implemented in qemu. >> However, due to DFSG, we have to strip blobs from the source packages, >> and while qemu do provide u-boot.e500 sources, it can only be built >> on a powerpc platform. Since debian already have u-boot package, >> we need to modify it so it provides this firmware, so that qemu can >> use it. > > Is this as simple as enabling the qemu-ppce500 in u-boot? If so, this > bug could be reassigned to u-boot.
No it is not, and no, it shouldn't be just reassigned. This bug is for me to track what should be done on the qemu side, not on the u-boot side, I mean, at some point I should add a Depends: or Recommends: to install u-boot.e500 automatically. For u-boot, additional bugreport might be filed, so this qemu bugreport can refer to u-boot bugreport. And no, this is not just a matter of enabling qemu-ppce500 (if it does what I think it does). Because... > Although on non-powerpc systems, it would require configuring a system > with powerpc as a foreign architecture to be able to use > multi-arch... but then installing u-boot:powerpc might work for this > purpose. ..because of this. Just like for all other ROMs we have in qemu, we need either a cross-arch depends/recommends to work automatically, which is not something we have now, or we need an arch-all package instead of arch-specific package. So this rom should not only be enabled in u-boot, but it should become an arch-all package built on ppc. Alternatively we may do what Aurelien played with yesterday -- building all this firmware during qemu build using cross-compiler tools and package it in right qemu-system-foo binary, to stop growing number of "slave" qemu packages like this. This applies to other roms too, eg palcode, slof, etc, and to roms already packaged like arch-all packages. But using cross-compilers (actually _building_ cross-compilers during build, build-depending on binutils-source and gcc-source) is quite a bit ugly... Thanks, /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
