From: Kumar Gala <galak@kernel.crashing.org>
To: "Li Yang-r58472" <LeoLi@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul <paulus@samba.org>
Subject: Re: [PATCH 3/3] 8349emds default dts updates for USB change
Date: Mon, 5 Feb 2007 21:31:12 -0600 [thread overview]
Message-ID: <EF78DCF9-DEC9-4D2F-AE0E-AD416BE91B81@kernel.crashing.org> (raw)
In-Reply-To: <989B956029373F45A0B8AF02970818900D41BD@zch01exm26.fsl.freescale.net>
On Feb 5, 2007, at 9:17 PM, Li Yang-r58472 wrote:
>> -----Original Message-----
>> From: Kumar Gala [mailto:galak@kernel.crashing.org]
>> Sent: Monday, February 05, 2007 11:07 PM
>> To: Li Yang-r58472
>> Cc: Paul; linuxppc-dev@ozlabs.org
>> Subject: Re: [PATCH 3/3] 8349emds default dts updates for USB change
>>
>>
>> On Feb 5, 2007, at 3:10 AM, Li Yang wrote:
>>
>>> Signed-off-by: Li Yang <leoli@freescale.com>
>>> ---
>>> arch/powerpc/boot/dts/mpc8349emds.dts | 6 ++++++
>>> 1 files changed, 6 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/arch/powerpc/boot/dts/mpc8349emds.dts b/arch/powerpc/
>>> boot/dts/mpc8349emds.dts
>>> index efceb34..ba31af1 100644
>>> --- a/arch/powerpc/boot/dts/mpc8349emds.dts
>>> +++ b/arch/powerpc/boot/dts/mpc8349emds.dts
>>> @@ -39,6 +39,11 @@
>>> reg = <00000000 10000000>; // 256MB at 0
>>> };
>>> + bcsr@f8000000 {
>>> + device_type = "board-control";
>>> + reg = <e2400000 8000>;
>>
>> Are the bcsr's at f8000000 or e2400000?
>
> According to the default u-boot configuration in tree, it is e2400000.
Fine, so what is it bcsr@f8000000?
- k
prev parent reply other threads:[~2007-02-06 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 9:10 [PATCH 3/3] 8349emds default dts updates for USB change Li Yang
2007-02-05 15:06 ` Kumar Gala
2007-02-06 3:17 ` Li Yang-r58472
2007-02-06 3:31 ` Kumar Gala [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=EF78DCF9-DEC9-4D2F-AE0E-AD416BE91B81@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=LeoLi@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).