Skip to content

patches to allow DTB to be appended to the ARM zImage

Tony Lindgren linux-arm-kernel linux-arm-msm linux-devicetree 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 3 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 3 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.

Read the v1 thread

Cover letter [PATCH 0/3] patches to allow DTB to be appended to the ARM zImage
Quoted 14 lines · Grant Likely
Quoted 13 lines · Arnd Bergmann
Quoted 3 lines · On Tuesday 14 June 2011 23:21:52 Nicolas Pitre wrote:

Otherwise, if the revision number is effectively non probable, then I would guess it is the device tree's purpose to carry that information somehow, right? ?Maybe this can be appended to the board name string?

That's what I meant with adding it to "compatible", which is a list of strings with varying degrees of detailed information, e.g.

?ti,omap7
?ti,omap7-squirrelboard
?ti,omap7-squirrelboard-v3
?ti,omap7-squirrelboard-v3.17b

Quoted 7 lines
Quoted 3 lines

You can match the list against a specific revision or a less specific identifier if you just want to know whether you are on a squirrelboard or a hamsterboard.

Yes, that's generally the right way to handle it. In practice I've not seen many cases where it is really required, but it doesn't hurt if somebody wants to include it in the DT for their board.

Appending the ATAG_REVISION to "compatible" and also setting system_rev to ATAG_REVISION like we already do should work.

Just to clarify things abit: We just can't generate .dts files for all existing hardware. It would require dumping out system_rev and other ATAGs on tens or hundeds of pieces of hardware.

Regards,

Tony