From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Mon, 04 Aug 2008 10:05:37 -0500 Subject: [U-Boot-Users] using a flat device tree to drive u-boot config In-Reply-To: <9e4733910808040802j41ecd0d3r8bc14a1e297ec4b9@mail.gmail.com> References: <9e4733910808021858i766307b1q45b5bace59996d03@mail.gmail.com> <20080803075105.CB07E248C1@gemini.denx.de> <9e4733910808040802j41ecd0d3r8bc14a1e297ec4b9@mail.gmail.com> Message-ID: <48971AC1.2010206@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Jon Smirl wrote: > BTW, how do know which DT to dynamically interpret? If you are > installing a universal uboot you still are going to have to install a > different DT in each model. If you're installing a different DT you > might as well install a different uboot. That's what I was thinking, too. Maybe on some boards, the DTB can be stored on some other type of memory that is easier to update during the manufacturing process. In that case, I can see how some vendors would like on u-boot.bin for all boards. Other than that, I don't see the point of having a generic u-boot.bin. -- Timur Tabi Linux kernel developer at Freescale