sbc8641d: misc fixes and generic board enablement
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 6 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 0/6] sbc8641d: misc fixes and generic board enablement
Quoted 21 lines · [Re: [PATCH 0/6] sbc8641d: misc fixes and generic board enablement] On…
Quoted 14 lines · [Re: [PATCH 0/6] sbc8641d: misc fixes and generic board enablement] On…
Quoted 11 lines · Paul Gortmaker
The sbc8641d is not really a state of the art board anymore, but it does have the distinctive feature of being one of the relatively few SMP powerpc boards around. Combined with its small form factor, it remains a useful testing platform. So here we enable the generic board support so that it can remain in tree.
It turns out that in bringing the board forward, we've run into the size limit for the image, due to inevitable expansion, which led to some odd testing behaviour, depending on .config settings etc. Here we increase the image space from two 128k sectors to three, so we should be good for as long as the board remains relevant now.
Quoted 4 lines
Thanks for finding this. I am going to grab this for the release and I might re-word a commit or two. I have one ask tho, can you look at using
CONFIG_BOARD_SIZE_LIMIT, perhaps in a generic way so that we catch more "oops, the board grew too big, run-time now will fail!" issues?
Quoted 4 lines
Yeah, I'll have a look -- I was kind of surprised that it didn't scream at me when this happened during the build, since I'd think we have all the information at our fingertips to do a build bug on or similar, and I can't be the 1st one bitten by this.
So, it seems we already have this in a "generic" way via BOARD_SIZE_LIMIT but hardly anyone sets that for their board.
u-boot$git grep -l CONFIG_BOARD_SIZE_LIMIT include/ include/configs/bf548-ezkit.h include/configs/bf609-ezkit.h include/configs/bfin_adi_common.h include/configs/cm-bf537e.h include/configs/cm-bf537u.h include/configs/colibri_pxa270.h include/configs/colibri_vf.h include/configs/pcm052.h include/configs/tcm-bf537.h include/configs/vf610twr.h
u-boot$
Can we just assign CONFIG_SYS_MONITOR_LEN to CONFIG_BOARD_SIZE_LIMIT if the latter isn't explicitly set? Or will that not be valid in some cases?
Paul.
--
Quoted 9 lines
P.
--Quoted 3 lines
Signature · 2 lines
-- Tom