RFC Create generic board init and move ARM and x86 to it
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest1 of 19 patches 0 repliesNew
1 of 19 patches is in this archive. The cover letter announces 19.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/19 | Introduce generic global_data | +0 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [RFC PATCH 0/19] Create generic board init and move ARM and x86 to it
Hi Wolfgang,
Quoted 11 lines · Wolfgang Denk
Dear Simon Glass,
Quoted 4 lines · In message <CAPnjgZ2jS8kzCt06LbYnXSyEKm6ck8apm=P1YqqDtnZ0+q9dhw@mail.gmail.com>…
Well let's see how we go with the incremental approach - hopefully we can get the same result with less pain and risk, and not too much work.
Did you miss my proposal not to change the existing coe for all boards, but to provide anew implementation and convert boards one by one? What do you think about such an approach?
My idea was to migrate each arch to the 'pure processing loops' implementation I have just posted for x86. We can then factor out the processing loop code into common code leaving just the init function arrays in arch/foo/lib/board.c
We can then look at how to deal with the disparate init sequences - I'm going to have a look at my new 'initcall' proposal to see if that is viable
- If so, we auto generate init_sequence.c
Regards,
Graeme