From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 26 Nov 2012 16:51:55 -0500 Subject: [U-Boot] [PATCH 1/2] mkconfig: Make CONFIG_SYS_BOARD_NAME default to the configured target name In-Reply-To: <1353966064.18021.15.camel@home.hno.se> References: <1353842534.17518.10.camel@home.hno.se> <20121125174359.10CAA20105B@gemini.denx.de> <1353866129.28559.50.camel@home.hno.se> <20121125200108.8726D20105B@gemini.denx.de> <1353918095.10834.9.camel@home.hno.se> <20121126093241.3F9AC201056@gemini.denx.de> <20121126210556.GA8657@bill-the-cat> <1353966064.18021.15.camel@home.hno.se> Message-ID: <50B3E47B.7090804@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/26/12 16:41, Henrik Nordstr?m wrote: > m?n 2012-11-26 klockan 14:05 -0700 skrev Tom Rini: > >> I think part of the solution is that in the environment now we >> have board_name for the unique run-time-determined board we are >> on (which defaults to CONFIG_SYS_BOARD). In each of these >> Allwiner SoCs do we have the ability to tell at run-time what we >> are on, or only build-time? > > Only build-time. There is no hardware board ID of any kind on the > boards. But it mostly matters for SPL to know you have the right > SPL for the board, and cosmetics to have main u-boot report the > right board model (not important). > > But the more I think about it I think we will move all the > important board parameters to a configuration header added to the > SPL binary image, and we will then also add board name there. There > is simply too many boards needing slightly different parameters but > almost the same. This is why, sooner rather than later I believe, we need to come up with a good way to pass device trees in and around, asap. An SPL that contains a device tree for the correct board (and passes along to U-Boot which could in turn pass along to the kernel if it's a full tree) would solve your problem, yes? - -- Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQs+R7AAoJENk4IS6UOR1WM14P/0ZUEk8E7+Qwmn1aGkXfRZBC 3cN06jWVBfio31Ic1HMJJJNoOsHgGLuV9hRI9Gl0U/9o4pvVLtI6tfIQB0rHdkDr HYwiAeq6fuJV/HE+oOsEt+DKn/NZsQd3U45TL1oK5A53Bfqh56LDuieqJnZ1FE2F 2G2Bi3VfMaP/Fx4VhIJpDrE3UkWZH4uzkjV7B2BeCfPaY02cEUbIsCYksPAUPxat E9lXgVYE+HThHPfYVZOcDpf+R3NPwfNqT0y7d256bMmxQW6C6W6sJjK0JsmeEQWm M+drhxaWXihtQ5pOUxSSgW5XOTbvdtJDA+vVLegPG0fjNKpAJStEsYPy2QJeZEzQ HtTLX7EPuKk55t+vUVB5k5e6BIT8WUSu2nzxi4N9D6pZgE80DdeTIw6Ez+KfR10x MiPaFpvLq3db7fzIg2GAoCiNppcimZPSBISRZyrUsZTDyXtsEgDqTqOOAcvmO6lY 9nHIFGAHG4QDW76Y1dW4/KkqI9TIwm6oph31sL/IgmhQ0R0TlwTKxV71ia4jwSOg qSs3O2qK+LvgNCNqPgeLljRML2PdyoWsA17sTcmsh4Na9B1O0rRFEbFBCAiCZsug toacIVgySbKdLucCHxcD7vS7IGSioVOsa+fPa7wSlKySLMcBxeooMqxR1+cqXsh7 /Kf4StcSqoMr8I7Mitgy =uk8l -----END PGP SIGNATURE-----