From: Tiejun Chen <tiejun.china@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, akpm@linux-foundation.org
Subject: Re: [v1 PATCH 1/1] Fix 64bit Maple Host Bridge Address and Size Nodes
Date: Tue, 14 Apr 2009 18:11:58 +0800 [thread overview]
Message-ID: <7a800c8d0904140311q5bdb98c4t327131175d16a36d@mail.gmail.com> (raw)
In-Reply-To: <3C36E383-13A3-49E9-B87B-D22D966B6F79@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
Segher,
Thank you very much for your review.
I already re-send this patch as you expect and please check this:
[v2 PATCH 1/1] Fix 64bit Maple Host Bridge 'reg' property
Best Regards
Tiejun
2009/4/14 Segher Boessenkool <segher@kernel.crashing.org>
> In the DTB tree created by firmware on some Maple 64bit targets, such as
>> ATCA6101,
>> these two properties, address&size, should be 2.
>>
>
> And they are.
>
> But the actual corresponding values
>> of host bridge node are set 1 incorrectly by the firmware, we have to
>> provide one
>> fixup function to fix that.
>>
>
> It is the "reg" property that is incorrectly encoded as-if
> #address-cells and #size-cells were 1.
>
> Please fix the commit message (and subject line).
>
> + name = "/hostbridge@f8000000";
>> + hb = call_prom("finddevice", 1, 1, ADDR(name));
>>
>
> It's interesting that the firmware can find your node this way,
> it won't match the "reg"! Looks like there is more than one
> bug in there.
>
> Code looks good,
>
> Reviewed-by: Segher Boessenkool <segher@kernel.crashing.org>
>
>
> Segher
>
>
[-- Attachment #2: Type: text/html, Size: 2117 bytes --]
next prev parent reply other threads:[~2009-04-14 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 10:46 [PATCH 1/1] Fix 64bit Mapple Host Bridge Address and Size Nodes tiejun.china
2009-04-03 10:46 ` [v1 PATCH 1/1] Fix 64bit Maple " tiejun.china
2009-04-14 8:11 ` Segher Boessenkool
2009-04-14 10:11 ` Tiejun Chen [this message]
[not found] <49E2A2D2.2000606@windriver.com>
2009-04-13 2:27 ` Tiejun Chen
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=7a800c8d0904140311q5bdb98c4t327131175d16a36d@mail.gmail.com \
--to=tiejun.china@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@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).