Ticket #11568 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

OFW - ARM - add flattened device tree support

Reported by: wmb@… Owned by: wmb@…
Priority: normal Milestone: Not Triaged
Component: ofw - open firmware Version: not specified
Keywords: Cc: dilinger@…, jon.nettleton@…, saadia@…
Action Needed: review Verified: no
Deployments affected: Blocked By:


The upstream Linux kernel already supports the flattened device tree format, with a pointer passed in r2. OFW on ARM should export a flattened tree.

Change History

Changed 3 years ago by wmb@…

  • cc dilinger@…, jon.nettleton@…, saadia@… added
  • status changed from new to assigned

Initial implementation by svn 2800, with test build at dev.laptop.org:~wmb/a4c11ma.rom . By default, that build exports the old ATAGs thing in r2. If you type "use-fdt" before booting, it will instead export the flattened device tree via r2.

This is just a first step. The device tree needs a lot of work, to

a) Ensure that necessary device nodes are present in the right form. One example is the twsi node, which should be split into multiple twsi@address nodes.

b) Add interrupts properties to all relevant nodes.

The Linux kernel needs work too...

Changed 3 years ago by Quozl

Q4C12 has this OpenFirmware change.

Changed 3 years ago by martin.langhoff

  • milestone changed from Not Triaged to 11.3.1

Changed 3 years ago by Quozl

  • next_action changed from code to add to build

Q4D06 adopts flattened device tree by default. Can be disabled with:

false to use-fdt?

Changed 2 years ago by Quozl

  • next_action changed from add to build to review
  • milestone changed from 11.3.1 to Not Triaged

as part of the 11.3.1 build os885 ticket check ... some of this is already in build, i'm not sure what else needs to be done on this ticket, nor which milestone to plug it in to.

Changed 2 years ago by wmb@…

  • status changed from assigned to closed
  • resolution set to fixed

Device tree work is proceeding full steam ahead and no longer needs to be tracked.

Note: See TracTickets for help on using tickets.