From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Thu, 14 Nov 2013 14:37:48 -0700 Subject: [RFC DTC PATCH] dtc: add symlink (-L) output to dtbs In-Reply-To: <20131114191622.GC21549@obsidianresearch.com> References: <1384201760-16785-1-git-send-email-jason@lakedaemon.net> <52814AFB.3070600@wwwdotorg.org> <528275B7.6050209@wwwdotorg.org> <20131112193012.GR10335@titan.lakedaemon.net> <52828C77.20001@wwwdotorg.org> <20131114162859.GX10335@titan.lakedaemon.net> <52851DC8.203@wwwdotorg.org> <20131114191622.GC21549@obsidianresearch.com> Message-ID: <528542AC.4080405@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 11/14/2013 12:16 PM, Jason Gunthorpe wrote: > On Thu, Nov 14, 2013 at 12:00:24PM -0700, Stephen Warren wrote: > >> I don't think a distro should need to know the DTB filename at all. >> Rather, the/a bootloader should know which platform it's running on, and >> provide a variable/... to the boot script/... that defines the DTB >> filename. That would completely remove all the knowledge of DTB >> filenames from distros. > > At some point the distro has to install a dtb into some cannonical > place so the bootloader can find it.. > > Are you thinking that distros will have to ship a /boot/dtbs/*.dtb > with every dtb from the kernel build? Yes. How else would the distro support booting the install on arbitrary boards? > What happens when you install two different versions of the kernel? /boot/zImage-$version /boot/dtbs-$version/*.dtb > What about boot schemes that can load a kernel version dependent dtb? I think that's solved by installing the DTB files in a kernel-version-specific directory. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [RFC DTC PATCH] dtc: add symlink (-L) output to dtbs Date: Thu, 14 Nov 2013 14:37:48 -0700 Message-ID: <528542AC.4080405@wwwdotorg.org> References: <1384201760-16785-1-git-send-email-jason@lakedaemon.net> <52814AFB.3070600@wwwdotorg.org> <528275B7.6050209@wwwdotorg.org> <20131112193012.GR10335@titan.lakedaemon.net> <52828C77.20001@wwwdotorg.org> <20131114162859.GX10335@titan.lakedaemon.net> <52851DC8.203@wwwdotorg.org> <20131114191622.GC21549@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20131114191622.GC21549-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jason Gunthorpe Cc: Jason Cooper , Mark Rutland , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Pawel Moll , Ian Campbell , Rob Herring , Rob Landley , Olof Johansson , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" List-Id: devicetree@vger.kernel.org On 11/14/2013 12:16 PM, Jason Gunthorpe wrote: > On Thu, Nov 14, 2013 at 12:00:24PM -0700, Stephen Warren wrote: > >> I don't think a distro should need to know the DTB filename at all. >> Rather, the/a bootloader should know which platform it's running on, and >> provide a variable/... to the boot script/... that defines the DTB >> filename. That would completely remove all the knowledge of DTB >> filenames from distros. > > At some point the distro has to install a dtb into some cannonical > place so the bootloader can find it.. > > Are you thinking that distros will have to ship a /boot/dtbs/*.dtb > with every dtb from the kernel build? Yes. How else would the distro support booting the install on arbitrary boards? > What happens when you install two different versions of the kernel? /boot/zImage-$version /boot/dtbs-$version/*.dtb > What about boot schemes that can load a kernel version dependent dtb? I think that's solved by installing the DTB files in a kernel-version-specific directory. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html