Hi Wolfgang.
On Dec 8, 2010, at 1:38 PM, Wolfgang Denk wrote:
> If you want to make this switchable at runtime, then we should
> probably use an environment setting.
I experimented with this, but could never determine the
best way to cover all behavior. Do we have a variable that
indicates "don't update DT?" If so, it means we have to
place all values in the DT, when it's really nice for U-Boot
to do some of that for us. In fact, we want U-Boot to update
many things it discovers, just not the few we wish to actually
(sometimes) define for ourselves.
The other alternative (granted, I'm not as smart as I used
to be :-)) was to have an environment variable that specified
which node we didn't want updated by U-Boot. For now,
that seems reasonable since there is only one, but is that
the general approach we want in the future? It also presents
the challenge of having to update both environment and
the provided DT.
I just wanted to make these points, as I did try some alternatives
but never found anything acceptable. By looking at key values
in the DT, at least it was confined to one place.
This feature is needed, so I propose we let it exist in the
form we have found useful and let it evolve over time as
others gain some experience.
Thanks.
-- Dan
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
