On Fri, Mar 08, 2013 at 12:03:15AM +0800, Peter Maydell wrote: > On 7 March 2013 23:56, Gerd Hoffmann <kra...@redhat.com> wrote: > > Peter Maydell wrote: > >> In general having blobs in our allegedly source tarball is pretty > >> ugly. Either it's a source release or it isn't. We can do a > >> release-of-blobs tarball too if we want, but it doesn't need > >> to be in the source tarball > > > > This is easily doable, just an update to scripts/make-release to spew > > two tarballs (one source, one blobs). > > > > We probably want update the build process to build the blobs by default > > (if the compilers needed are installed). Blueswirl started that already > > for sparc firmware I think. > > Earlier in this thread it's been stated that this often produces > subtly broken blobs... >
Would it be possible to have a testsuite to validate such blobs. For example the breakage which happens recently is due to the size of the bios reaching 128kB. This is something easy to check. On the QEMU side, we should definitely have an autotest system trying to boot a few guests (and if possible with some !linux) to detect such issues. That's not something easy to do, maybe that could be a good GSoC project? -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net
