From: Matt Sealey <matt@genesi-usa•com>
To: Robert Schwebel <r.schwebel@pengutronix•de>
Cc: linuxppc-dev@ozlabs•org, m8@semihalf•com,
Sascha Hauer <sha@pengutronix•de>,
Wolfram Sang <wsa@pengutronix•de>
Subject: Re: [PATCH] [POWERPC] mpc5200: Switch mpc5200 dts files to dts-v1 format
Date: Sat, 19 Apr 2008 19:49:57 +0100 [thread overview]
Message-ID: <480A3ED5.5060709@genesi-usa.com> (raw)
In-Reply-To: <20080419133658.GJ13814@pengutronix.de>
I wholeheartedly agree, although the difference between gpt and timer
and pic vs interrupt-controller (actually interrupt-controller is meant
to be a property of the interrupt controller, not a device type.. weird)
was chosen because they did not conflict with what might be considered
"standard device_types" with real OF (Forth, CIS) interfaces like read,
write, ping, world-peace etc.
However since Linux doesn't care about the interface provided by the
firmware and only reads the tree, and real OF interfaces MIGHT need
to be provided by these items on real OF firmwares, I don't see why
they should not be used.
A problem arises; how do you decide when you name something after what
it is rather than the documentation acronym? What does the 5200B CDM
turn into? The XLB arbiter module? What about the rest of the SIU?
There really needs to be a standards committee for this, that has good
experience with device trees and BSPs, and can work with the device
vendors and board manufacturers (Freescale for example) directly, with
them on the committee, who can give the docs a run though before any
board ever hits the streets...
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
Robert Schwebel wrote:
> On Fri, Apr 18, 2008 at 09:10:04AM -0700, Grant Likely wrote:
>> Update dts files to current format
>
> Is it somehow possible that this device tree stuff is *not* changed over
> and over again and break everything out there? When people have not even
> agreed on basic things like decimal vs. hex numbers, the whole idea
> should be developed out-of-tree, then stabilize and *then* be submitted
> to the Linux mainline.
>
> Is it also really necessary to change like "gpt" vs. "timer" and "pic"
> vs. "interrupt-controller" all the time? If you compare the last
> mainline kernels, each one got a fundamental change in the naming, each
> time breaking anyone who doesn't have his stuff in the mainline yet.
>
> Sorry, but this is simply annoying, and the whole "the only thing we
> have to do is to define it once and be done then" is crap.
>
> Robert
next prev parent reply other threads:[~2008-04-19 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 16:10 [PATCH] [POWERPC] mpc5200: Switch mpc5200 dts files to dts-v1 format Grant Likely
2008-04-19 13:36 ` Robert Schwebel
2008-04-19 15:55 ` Grant Likely
2008-04-19 18:49 ` Matt Sealey [this message]
2008-04-21 8:43 ` Sascha Hauer
2008-04-21 13:21 ` Grant Likely
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=480A3ED5.5060709@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=m8@semihalf$(echo .)com \
--cc=r.schwebel@pengutronix$(echo .)de \
--cc=sha@pengutronix$(echo .)de \
--cc=wsa@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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