From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] uboot clock configuration on mpc5200 boards
Date: Wed, 21 Nov 2007 14:41:11 +0100 [thread overview]
Message-ID: <20071121134111.GV11448@pengutronix.de> (raw)
In-Reply-To: <20071121130042.26426246B5@gemini.denx.de>
On Wed, Nov 21, 2007 at 02:00:42PM +0100, Wolfgang Denk wrote:
> > How do you handle the fact that device trees do not cover the whole
> > system, i.e. chips behind SPI and I2C busses?
>
> The device tree is supposed to contain a complete hardware
> description, i. e. including devices attached to such busses.
Yes, it is supposed to, but reality is different. Ok, so we have to
double-code everything until the world has achieved perfectionism.
> [How do you handle this with an ARM machine ID? ;-) ]
Well, we don't have to. Linux has a driver model which handles all this
once you know the machine. No need to duplicate everything. Redundancy
is generally a bad thing.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
prev parent reply other threads:[~2007-11-21 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 23:12 [U-Boot-Users] uboot clock configuration on mpc5200 boards Jon Smirl
[not found] ` <9e4733910711201700o75f74c20k243b42d2595491dd@mail.gmail.com>
2007-11-21 2:16 ` Grant Likely
2007-11-21 2:37 ` Jon Smirl
2007-11-21 7:01 ` Robert Schwebel
2007-11-21 11:21 ` Wolfgang Denk
2007-11-21 12:14 ` Robert Schwebel
2007-11-21 13:00 ` Wolfgang Denk
2007-11-21 13:41 ` Robert Schwebel [this message]
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=20071121134111.GV11448@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=u-boot@lists.denx.de \
/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