On Tue, 7 Jun 2011 10:20:57 -0300, Christian Robottom Reis kiko@canonical.com wrote:
That's true, and I didn't finish my original sentence but I would have pointed out that more complete hardware packs would contain other vendor-supplied binaries. Having a version for them described would be great to have for debugging reasons, but I guess it's available in the packaging?
Yeah, they have a version number. Whether that's meaningful or not is up to the packager.
We now produce files like
http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3/20110607/0/imag...
to make it easy to see what's included without having to download and extract the hwpack.
My main motivation is around the kernel (answering the question "what kernel is being used for this hwpack") though I guess it applies to anything we have source for. Apart from the kernel and bootloader, are we supplying anything in the hwpack we have source for?
Taking a look at panda-x11-base it requests that it include:
linux-image-linaro-omap linux-headers-linaro-omap u-boot-linaro-omap4-panda x-loader-omap4-panda libegl1-sgx-omap4 libgles1-sgx-omap4 libgles2-sgx-omap4 libopenvg1-sgx-omap4
so just kernel and bootloader.
The actual hwpack contains a bit more (it contains everything that isn't already in the rootfs that is needed to satisfy the dependencies of the above too)
http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda-x11-base/201106...
It contains more that we have source for, but given that they aren't the primary things that the hwpack is for I'm not sure that we need make it as easy to go to the source (so knowing the version and where the package was taken from to get you going is probably good enough for now.)
Therefore it looks like we mainly need to concern ourselves with the kernel and bootloader as you suggest.
Thanks,
James