From: Heiko Schocher <hs@denx.de>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] 8xx: Add support for the MPC852 based board from keymile.
Date: Wed, 19 Mar 2008 07:51:46 +0100 [thread overview]
Message-ID: <47E0B802.9040003@denx.de> (raw)
In-Reply-To: <20080318191918.6505ba41@kernel.crashing.org>
Hello Vitaly,
Vitaly Bordug wrote:
> On Tue, 18 Mar 2008 09:04:14 +0100
> Heiko Schocher wrote:
[...]
>> OK. Another thought about this. Shouldnt this table go in the dts?
>> A device node like
>>
>> cpm_pin {
>> pins = <port pin flags>;
>> };
>>
>> would be nice, or?
>>
> This has been a disputable question some time ago, and decided (or it looks like decided) that devtree describes hardware, and not the way it is configured at the moment. Therefor, best way for pin stuff is considered, as Scott mentioned, to set up stuff inside the firmware.
OK, I dont want to start a new discusion about that, but I always thought
(maybe learned, not sure anymore ;-) Linux should be as much independent
as possible from the bootloader(=firmware). If the firmware doesnt make
things right Linux maybe hang ... :-(
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2008-03-19 6:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 9:24 [PATCH v2] 8xx: Add support for the MPC852 based board from keymile Heiko Schocher
2008-03-14 23:25 ` Stephen Rothwell
2008-03-18 7:13 ` Heiko Schocher
2008-03-18 7:33 ` Stephen Rothwell
2008-03-18 8:04 ` Heiko Schocher
2008-03-18 15:11 ` Scott Wood
2008-03-18 16:19 ` Wolfgang Denk
2008-03-18 16:56 ` Scott Wood
2008-03-18 16:19 ` Vitaly Bordug
2008-03-19 6:51 ` Heiko Schocher [this message]
2008-03-17 22:46 ` Scott Wood
2008-03-18 8:07 ` [PATCH v3] " Heiko Schocher
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=47E0B802.9040003@denx.de \
--to=hs@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=sfr@canb.auug.org.au \
--cc=vitb@kernel.crashing.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).