n Loeliger
> > > Cc: [EMAIL PROTECTED];
> > > linuxppc-dev@ozlabs.org; Michal Simek; git
> > > Subject: Re: Xilinx EDK BSP generation of device trees for
> > > microblaze and PowerPC
> > >
> > > On 11/24/07, Stephen Neuendorffer
> > >
Here's what I've gotten so far:
Hard_Ethernet_MAC: [EMAIL PROTECTED] {
#address-cells = <1>;
#size-cells = <1>;
[EMAIL PROTECTED] {
compatible = "xlnx,xps-ll-temac-1.00.a",
"xl
On 11/24/07, Stephen Neuendorffer <[EMAIL PROTECTED]> wrote:
>
Thanks for all this work; comments below.
>
> Here's what I've gotten so far:
>
> Hard_Ethernet_MAC: [EMAIL PROTECTED] {
> #address-cells = <1>;
> #size-cells = <1>;
>
Stephen Neuendorffer; Segher Boessenkool; David Gibson;
> Jon Loeliger
> Cc: [EMAIL PROTECTED];
> linuxppc-dev@ozlabs.org; Michal Simek; git
> Subject: Re: Xilinx EDK BSP generation of device trees for
> microblaze and PowerPC
>
> On 11/24/07, Stephen Neuendorffer
> <[E
On Sun, Nov 25, 2007 at 03:47:12PM -0700, Grant Likely wrote:
> On 11/24/07, Stephen Neuendorffer <[EMAIL PROTECTED]> wrote:
[snip]
> > So: the mpmc generates a 'memory' node, corresponding to it's memory
> > interface. It also gets a separate entry which contains the (optional, not
> > present i
On Mon, Nov 26, 2007 at 01:44:02PM -0800, Stephen Neuendorffer wrote:
[snip]
> > > reg = < 81c0 40 >;
> >
> > If these registers are addressable, then the parent needs a
> > 'ranges' property.
>
> I thought ranges weren't necessary in a 1:1 mapping?
You were
t; > linuxppc-dev@ozlabs.org; Michal Simek; git
> > Subject: Re: Xilinx EDK BSP generation of device trees for
> > microblaze and PowerPC
> >
> > On 11/24/07, Stephen Neuendorffer
> > <[EMAIL PROTECTED]> wrote:
> > >
> >
> > Thanks for al
