Thread (2 messages) 2 messages, 2 authors, 2006-09-28

RE: [PATCH 10/11] Add MPC8360EMDS board support

From: Li Yang-r58472 <hidden>
Date: 2006-09-28 06:37:29

Possibly related (same subject, not in this thread)

-----Original Message-----
From: Jon Loeliger [mailto:jdl@jdl.com]
Sent: Wednesday, September 27, 2006 10:14 PM
To: Li Yang-r58472
Cc: Vitaly Bordug; linuxppc-dev@ozlabs.org; Paul Mackerras
Subject: Re: [PATCH 10/11] Add MPC8360EMDS board support
=20
So, like, the other day "Li Yang-r58472" mumbled:
=20
quoted
Agreed.  As we are adding more devices to the device tree, we should
also have a guideline clearly stated for adding new nodes.

I'm adding MURAM as a new node under QE bus.  Please comment.
                muram@10000 {
                        device_type =3D "memory";
                        ranges =3D <0 00010000 0000c000>;

                        data-only@0{
                                reg =3D <0 c000>;
                        };
                };

- Leo
=20
So, does it make sense for this node to participate in the early scan
of memory available during the early_init_dt_scan_memory() pass?
=20
Are all "memory" type nodes regarded as system memory during the early
scan?  If so, it needs to use a new device_type "muram" I think.
Out of curiosity, is "data-only" a standard thing, or did you make
that up too?  What's it mean?
Well, it is from kernel code of cpm/cpm2 era.  It defines the MURAM area
which can be freely allocated.  The base and size of such area vary
between chips and revisions, even boards.

- Leo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help