From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] DTS cleanup
Date: Thu, 13 Sep 2007 18:56:39 +0200 [thread overview]
Message-ID: <39e2f86a62574776183feb82935cd79c@kernel.crashing.org> (raw)
In-Reply-To: <8FFFBF2E-8255-40FB-836D-AB5B19222DD9@kernel.crashing.org>
>>> * built-in for non-standard buses (ISA, PCI)
>>
>> "built-in" is some weird CHRP property, so yes we don't need it
>> or want it.
>
> Do you suggest we get ride of it from ISA nodes as well?
Yes. You aren't CHRP so you don't have to follow the CHRP binding.
Of course it is good to copy from that binding where it makes sense,
but how is "built-in" useful to you?
>>> * Fixed ranges on lite5200*
>>
>> This has a problem still:
>>
>>> model = "fsl,mpc5200";
>>> compatible = "mpc5200";
>>> revision = ""; // from bootloader
>>> - #interrupt-cells = <3>;
>>> device_type = "soc";
>>> - ranges = <0 f0000000 f0010000>;
>>> - reg = <f0000000 00010000>;
>>> + ranges = <0 f0000000 0000c000>;
>>> + reg = <f0000000 0000c000>;
>>
>> That makes "reg" and "ranges" identify an identical address range,
>> which means no subnode can claim any address in that range, so the
>> "ranges" property should go. Alternatively, the "reg" might be
>> claiming too big a space.
>>
>> Which is it?
>
> Yeah, I think it should be 0x100 for the 'soc' regs on 52xx so I'll
> set regs to that.
Okido.
Did I say "nice cleanups, thank you!" already? :-)
Segher
next prev parent reply other threads:[~2007-09-13 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 16:54 [PATCH] [POWERPC] DTS cleanup Kumar Gala
2007-09-12 22:10 ` Segher Boessenkool
2007-09-13 3:08 ` Kumar Gala
2007-09-13 16:56 ` Segher Boessenkool [this message]
2007-09-13 21:04 ` Kumar Gala
2007-09-14 16:28 ` Jon Loeliger
2007-09-14 18:11 ` Kumar Gala
2007-09-17 3:24 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39e2f86a62574776183feb82935cd79c@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).