-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/26/12 17:01, Henrik Nordström wrote:
> mån 2012-11-26 klockan 16:51 -0500 skrev Tom Rini:
>
>> 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 conta
mån 2012-11-26 klockan 16:51 -0500 skrev Tom Rini:
> 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 al
-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 default
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-t
On Mon, Nov 26, 2012 at 10:32:41AM +0100, Wolfgang Denk wrote:
> Dear Henrik Nordstr??m,
>
> In message <1353918095.10834.9.ca...@home.hno.se> you wrote:
> > s??n 2012-11-25 klockan 21:01 +0100 skrev Wolfgang Denk:
> >
> > > I think you should avoid doing that. It's ugly, and I see no real
> > >
Dear Henrik Nordström,
In message <1353918095.10834.9.ca...@home.hno.se> you wrote:
> sön 2012-11-25 klockan 21:01 +0100 skrev Wolfgang Denk:
>
> > I think you should avoid doing that. It's ugly, and I see no real
> > advantages for it.
>
> Avoid using the same board config file for multiple bo
sön 2012-11-25 klockan 21:01 +0100 skrev Wolfgang Denk:
> I think you should avoid doing that. It's ugly, and I see no real
> advantages for it.
Avoid using the same board config file for multiple boards even when
they differ only in one config parameter or in the SoC model mounted on
the board?
Dear Henrik Nordström,
In message <1353866129.28559.50.ca...@home.hno.se> you wrote:
>
> > I don't see what the difference is between CONFIG_SYS_BOARD (which is
> > the board name) and CONFIG_SYS_BOARD_NAME ?
>
> CONFIG_SYS_BOARD is the board config name, which may differ from the
> board name gi
sön 2012-11-25 klockan 18:43 +0100 skrev Wolfgang Denk:
> > echo "#define CONFIG_SYS_BOARD \"${board}\"" >> config.h
> > +echo "#define CONFIG_SYS_TARGET \"${BOARD_NAME}\"" >> config.h
>
> I don't see what the difference is between CONFIG_SYS_BOARD (which is
> the board name) and CONFIG_SYS_BOARD
Dear Henrik Nordström,
In message <1353842534.17518.10.ca...@home.hno.se> you wrote:
> This change makes CONFIG_SYS_BOARD_NAME globally available as the configured
> target name, avoiding the need to define manually for boards having multiple
> targets sharing the same board implementation.
> ---
This change makes CONFIG_SYS_BOARD_NAME globally available as the configured
target name, avoiding the need to define manually for boards having multiple
targets sharing the same board implementation.
---
include/config_fallbacks.h |4
mkconfig |1 +
2 files changed,
11 matches
Mail list logo
