Re: [RFC PATCH 00/12] Merge common OpenFirmware device tree code

On Tuesday 06 October 2009 23:49:04 Grant Likely wrote:

However, I've completely devoted to this work for at least the next
two months, so there are plenty more patches to follow.  Once I've
got all the common code merged between Microblaze, PowerPC and Sparc
I'll be fix the endian problems and making it easily usable by other
architectures like ARM and MIPS.  Lots of work to be done.

Is there any news on getting QEMU to parse a device tree to figure out what 
hardware to emulate?  (I.E. using the device tree code to let qemu provide 
configurable board emulations instead of hardwiring them in C code?)

Also, what would be involved in getting x86 to (at least have the option to) 
use the device tree stuff?

Rob
-- 
Latency is more important than throughput. It's that simple. - Linus Torvalds

On Wed, Oct 7, 2009 at 1:09 AM, Rob Landley [off-list ref] wrote:

On Tuesday 06 October 2009 23:49:04 Grant Likely wrote:

quoted

However, I've completely devoted to this work for at least the next
two months, so there are plenty more patches to follow. =A0Once I've
got all the common code merged between Microblaze, PowerPC and Sparc
I'll be fix the endian problems and making it easily usable by other
architectures like ARM and MIPS. =A0Lots of work to be done.

Is there any news on getting QEMU to parse a device tree to figure out wh=

at

hardware to emulate? =A0(I.E. using the device tree code to let qemu prov=

ide

configurable board emulations instead of hardwiring them in C code?)

Not that I have, but I expect that I will be hacking on QEMU as part
of this work.

Also, what would be involved in getting x86 to (at least have the option =

to)

use the device tree stuff?

It would be very easy once the endian issues are worked out since the
device tree is just a data format to be parsed.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.