Lines Matching refs:Firmware
1 Booting the Linux/ppc kernel without Open Firmware
138 Firmware specification. However, in order to make life easier
173 b) Entry with a flattened device-tree block. Firmware loads the
201 a) Boot from Open Firmware. If your firmware is compatible
202 with Open Firmware (IEEE 1275) or provides an OF compatible
224 Firmware client interface. It is also used by "kexec" to
228 Firmware, and thus should be implemented according to the
327 which will generate a flattened device-tree from the Open Firmware
417 way to avoid overriding critical things like, on Open Firmware
519 the Open Firmware IEEE 1275 device-tree. It's basically a tree of
529 format definition (as it is in Open Firmware). Version 16 makes it
566 property. Real Open Firmware implementations provide a unique
692 implementation of Open Firmware or an implementation compatible with
693 the Open Firmware client interface, those properties will be created
704 The general rule is documented in the various Open Firmware
795 While earlier users of Open Firmware like OldWorld macintoshes tended
816 While Open Firmware provides more flexible usage of 8859-1, this
836 PCI binding to Open Firmware, and your interrupt tree as documented
962 This node is a bit "special". Normally, that's where Open Firmware
1240 representation defined as part of the Open Firmware specifications,
1242 booted using Open Firmware. Binding documentation for new devices
1259 document "Open Firmware Recommended Practice: Interrupt