From: Segher Boessenkool <segher@kernel.crashing.org>
To: olof@lixom.net (Olof Johansson)
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 6/7] Holly DTS
Date: Sat, 5 May 2007 22:49:50 +0200 [thread overview]
Message-ID: <cbcd7823ea9b0f17f998670915719a05@kernel.crashing.org> (raw)
In-Reply-To: <20070505191306.GB23524@lixom.net>
>>> + PowerPC,750@0 {
>>
>> Needs to be PowerPC,750CL etc.
>
> Why _needs_?
Because that's what the PowerPC binding says:
Open Firmware standard property. The value of the
is property shall be of the form: =93PowerPC,<name>=94,
where <name> is the name of the processor chip which
may be displayed to the user.
> Apple never used anything else than PowerPC,G5, no matter
> what generation chip.
I don't care what Apple did in their device trees,
they made many mistakes.
>>> + tsi109@c0000000 {
>>> + device_type =3D "tsi-bridge";
>>
>> Don't put a "device_type" here, it is useless
>> (and undefined). There are more like this, but
>> perhaps Linux (wrongly) probes on "device_type"
>> for those, so the kernel would need updating
>> first.
>
> Josh is just using the precedence that the other platform gives, the
> driver is keying off of device_type. While that should be fixed, =
that's
> a separate issue.
Yes I know, I tried to explain that already, but
seems I failed :-)
> I'm sure they'd welcome a driver patch from you.
It's on my todo list.
>>> + bus-frequency =3D <0>;
>>
>> 0?
>
> Filled in by bootloader/wrapper?
I don't think it is?
> Other dts'es are similar. Could be nice
> to have a comment next to it if that's the case.
Yeah. There's also this ?? syntax now I believe.
Segher
next prev parent reply other threads:[~2007-05-05 20:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 16:13 [PATCH v2 0/7] Add support for 750CL Holly board Josh Boyer
2007-05-05 16:14 ` [PATCH v2 0/1] Add tsi108_pci.h for common PCI functions Josh Boyer
2007-05-05 16:15 ` [PATCH v2 2/7] Generalize tsi108 PHY types Josh Boyer
2007-05-05 16:16 ` [PATCH v2 3/7] Generalize TSI 108 PCI setup Josh Boyer
2007-05-05 16:17 ` [PATCH v2 4/7] Add support for 750CL Holly board Josh Boyer
2007-05-07 4:22 ` Paul Mackerras
2007-05-07 10:32 ` Josh Boyer
2007-05-05 16:19 ` [PATCH v2 5/7] Holly defconfig Josh Boyer
2007-05-05 16:20 ` [PATCH v2 6/7] Holly DTS Josh Boyer
2007-05-05 17:21 ` Segher Boessenkool
2007-05-05 18:12 ` Josh Boyer
2007-05-05 20:44 ` Segher Boessenkool
2007-05-05 21:36 ` Josh Boyer
2007-05-06 0:47 ` Segher Boessenkool
2007-05-05 19:13 ` Olof Johansson
2007-05-05 19:46 ` Josh Boyer
2007-05-05 20:51 ` Segher Boessenkool
2007-05-05 20:49 ` Segher Boessenkool [this message]
2007-05-07 17:50 ` Loeliger Jon-LOELIGER
2007-05-09 0:49 ` David Gibson
2007-05-09 7:40 ` Stephen Rothwell
2007-05-09 10:29 ` Josh Boyer
2007-05-09 15:28 ` Segher Boessenkool
2007-05-10 23:54 ` David Gibson
2007-05-12 12:02 ` Segher Boessenkool
2007-05-14 0:24 ` David Gibson
2007-05-14 12:33 ` Segher Boessenkool
2007-05-14 16:16 ` Scott Wood
2007-05-06 0:40 ` David Gibson
2007-05-07 13:11 ` Josh Boyer
2007-05-08 0:06 ` David Gibson
2007-05-05 16:20 ` [PATCH v2 7/7] Holly bootwrapper Josh Boyer
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=cbcd7823ea9b0f17f998670915719a05@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).