On Tue, Oct 23, 2007 at 06:15:22PM -0700, Stephen Neuendorffer wrote:
[snip]
> / {
> #address-cells = <1>;
> #size-cells = <1>;
> model = "system.mhs";
> chosen {
> bootargs = "root=/dev/xsysace/disc0/part2";
> interrupt-controller = <101>;
inter
I've incorporated a good portion of the combined feedback and pushed the
gen_mhs_devtree patches back to Grant.
The few things I haven't done are relatively cosmetic (like getting rid
of linux,phandle references, decimal vs. hex, and the 'embedded \0')
,
The one significant problem that I'm not s
On Tue, Oct 23, 2007 at 09:34:37AM +0200, Michal Simek wrote:
> Hi David,
> I remove some labels from my generator. I created fake system with some
> peripherals.
> There are 3 buses and 3 bridges.
> Can you check it and tell me what is wrong?
Grant's comments all seem reasonable, apologies if
ev@ozlabs.org
> Subject: RE: [microblaze-uclinux] Re: [microblaze-uclinux]
> RE: [PATCH v3] Device tree bindings for Xilinx devices
>
> >> In my opinion will be better generate only parameters which
> >> you want not all.
> >> That smells with unusable parameters.
>
On 10/23/07, Michal Simek <[EMAIL PROTECTED]> wrote:
> Hi David,
> I remove some labels from my generator. I created fake system with some
> peripherals.
> There are 3 buses and 3 bridges.
> Can you check it and tell me what is wrong?
>
> Thanks,
> Michal Simek
>
> / {
> model = "mONStR";
Hi David,
I remove some labels from my generator. I created fake system with some
peripherals.
There are 3 buses and 3 bridges.
Can you check it and tell me what is wrong?
Thanks,
Michal Simek
/ {
model = "mONStR";
chosen {
bootargs = "root=/dev/xsysace/disc0/pa
On Tue, Oct 23, 2007 at 06:07:56AM +0200, Michal Simek wrote:
> >> In my opinion will be better generate only parameters which
> >> you want not all.
> >> That smells with unusable parameters.
> >
> >In the long term, this may be true. In the short term:
> >1) dtb size is not the key problem
> Ye
>> In my opinion will be better generate only parameters which
>> you want not all.
>> That smells with unusable parameters.
>
>In the long term, this may be true. In the short term:
>1) dtb size is not the key problem
Yes of course
>2) making sure that everything works is a key problem.
>3) The
rg; Wolfgang Reissnegger
> Subject: [microblaze-uclinux] Re: [microblaze-uclinux] RE:
> [PATCH v3] Device tree bindings for Xilinx devices
>
> Hi Steve and all,
> >Here's a full .dts generated using an updated version of
> >gen_mhs_devtree.py, following the proposal.
> >
Hi Grant,
>> Hi Steve and all,
>> >Here's a full .dts generated using an updated version of
>> >gen_mhs_devtree.py, following the proposal.
>> >It happens to be a microblaze system, but you get the idea.
>>
>> I think that is no good idea generate dts with all information.
>> Especially informatio
On 10/19/07, Michal Simek <[EMAIL PROTECTED]> wrote:
> Hi Steve and all,
> >Here's a full .dts generated using an updated version of
> >gen_mhs_devtree.py, following the proposal.
> >It happens to be a microblaze system, but you get the idea.
>
> I think that is no good idea generate dts with all i
Hi Steve and all,
>Here's a full .dts generated using an updated version of
>gen_mhs_devtree.py, following the proposal.
>It happens to be a microblaze system, but you get the idea.
I think that is no good idea generate dts with all information.
Especially information about PVR - number 2 means -
12 matches
Mail list logo
