19.10.2017 15:36, Christian Ehrhardt wrote: > On Thu, Oct 19, 2017 at 2:01 PM, Philipp Kern <pk...@debian.org > <mailto:pk...@debian.org>> wrote: > On 02/03/2016 09:27 AM, Viktor Mihajlovski wrote: > > On 02.02.2016 01:01, Dimitri John Ledkov wrote: > >> On Fri, 17 Aug 2012 11:21:04 +0200 bastien ROUCARIES > >> <roucaries.bast...@gmail.com <mailto:roucaries.bast...@gmail.com>> > wrote: > >>> Please add http://repo.or.cz/w/s390-tools.git > <http://repo.or.cz/w/s390-tools.git> for booting s390 from qemu. it port > virtio. > >>> I have ported the pach queue to recent s390-tools. Not tested only > merge without conflict. > >> Is this still required? I see that qemu-2.5 has support for booting El > >> Torito .iso images, and it boots Debian off virtio block drives just > >> fine. > >> > >> Granted, it looks like debian packaging strips the s390 firmware file, > >> and doesn't rebuild it. Maybe that should simply be fixed and that's > >> it? > > Right, including the firmware file would be the proper way to enable > > QEMU for booting on s390.
There's no way to include firmware on debian without actually building it, and building it, as far as I can see, only works on s390 architecture. That's why we don't build other firmware stuff - either lack of cross- compiler on all necessary architectures, or the requiriment to have actual system of the necessary architecture (virtual or real). It'd be nice to have it all in one place. > If I understand it correctly, this is now obsoleted by the fact that > qemu dropped s390-virtio and runs with their own s390-ccw rom now that's > built from the qemu source. Is that correct? Can we close the s390-tools > bug at least? And I suppose arrange for s390-ccw.rom to be shipped from > the qemu package? > > > On Ubuntu there already is: /usr/share/qemu/s390-ccw.img > which works for me as part package qemu-system-s390x. > > That is part of the suggested contribution in bug 874347 already. > See #2 in that bug and the suggestion to accept it without an ubuntu: label > in d/control-in. Debian has much stricter policy wrt blobs (DFSG), and debian builds for more architectures (the firmware, if it is part of qemu-system-s390 package, needs to be built on all architectures where this binary package builts, or it needs to be a separate arch-all package). I'll take look at all this once again. It looks like the s390-tools bug can be closed indeed. Thanks, /mjt
