On Thu, Mar 31, 2011 at 11:41 AM, Loïc Minier <loic.min...@linaro.org> wrote: > On Fri, Apr 01, 2011, Shawn Guo wrote: >> As the .dtb files will be naturally generated in the same kernel >> folder as kernel image sits, why do not we ship .dtb in the same >> folder as kernel image /boot?
Version numbers. If two kernel packages are installed, that means two sets of .dtb files. At the very least they would need to be in a subdirectory that encodes the 'uname -r' value. > > You could say the same of kernel modules; problem is that there might > be many .dtbs and that would clutter /boot IMHO. So I think /lib is > more sensible, but I'm open to hear good arguments! > >> The .dtb files will be generated and shipped with unique name, which >> comes from .dts file name. But I intend to use the generic name, >> maybe something like board.dtb along with l-m-c, just like we use >> zImage and u-boot for all platforms in boot partition, so that l-m-c >> does not need to encode platform specific dtb filename. > > I don't think this would work in the upstream kernel or kernel > packaging: the same linux-image.deb will provide support for multiple > boards, for instance linux-image-mx51 supports for efikamx, efikasb, > mx51evk, so the package needs to ship three .dtb files. right. > > However, it will likely be needed to copy this dtb in a place where > u-boot can read it, for instance in the boot partition probably as an > u-boot image: uDeviceTree just like uImage, uInitrd etc.; I don't care > too strongly about the name. Yes; the .dtb for the specific board needs to be in the right place for u-boot to find it. g. _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
