linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: hip04: move bootwrapper to SRAM
Date: Tue, 13 Jan 2015 18:28:32 +0800	[thread overview]
Message-ID: <54B4F350.5040007@hisilicon.com> (raw)
In-Reply-To: <3703587.1qvjMFgdrL@wuerfel>



On 2015/1/13 17:02, Arnd Bergmann wrote:
> On Tuesday 13 January 2015 16:42:38 Wei Xu wrote:
>> On 2015/1/13 16:33, Arnd Bergmann wrote:
>>> On Tuesday 13 January 2015 11:13:34 Wei Xu wrote:
>>>> There is 8MB SRAM in hip04.
>>>> Moving the bootwrapper into SRAM could avoid to worry about poking
>>>> holes into DRAM memory or allocation algorithms either.
>>>>
>>>> Signed-off-by: Wei Xu <xuwei5@hisilicon.com>
>>>> ---
>>>>  arch/arm/boot/dts/hip04.dtsi | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm/boot/dts/hip04.dtsi b/arch/arm/boot/dts/hip04.dtsi
>>>> index 2388145..f0dfac7 100644
>>>> --- a/arch/arm/boot/dts/hip04.dtsi
>>>> +++ b/arch/arm/boot/dts/hip04.dtsi
>>>> @@ -22,7 +22,7 @@
>>>>  
>>>>         bootwrapper {
>>>>         compatible = "hisilicon,hip04-bootwrapper";
>>>> -       boot-method = <0x10c00000 0x10000>, <0xe0000100 0x1000>;
>>>> +       boot-method = <0xe00f0000 0x10000>, <0xe0000100 0x1000>;
>>>>         };
>>
>> Hi Arnd,
>>  
>>> Is this backwards compatible with old firmware?
>>
>> Sorry, it is not backwards compatible.
>> Another reason is that it could support opensuse 
>> more smoothly.
>>
>> I have updated the firmware and uploaded it 
>> into Linaro Hisilicon git tree last month.
>> We will update the wiki on Linaro soon.
>>
>> Do you think it is OK?

Hi Arnd,

> Generally speaking it's not ok to change firmware interfaces in
> an incompatible way. The preferred way to handle this would be
> to have the firmware that puts the boot wrapper into a different
> place also update this property, if at all possible.

I very agreed with you.

But before we have two kind of firmwares one is boot from SVC supporting
PXE/NAND/SATA/GRUB booting and the other is boot from HYP just supporting NAND
booting.
This time we updated the firmware and made it boot from HYP supporting 
PXE/NAND/SATA/GRUB as we hoped(thanks for Alex's supporting!).

Since we have to publish a new firmware I think it is a chance to 
update the dts of kernel. How do you think about it?

Best Regards,
Wei

> This unfortunately means that you will have to yet again publish
> a firmware update image.
> 
> 	Arnd
> 
> .
> 

  reply	other threads:[~2015-01-13 10:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  3:13 [PATCH] ARM: dts: hip04: move bootwrapper to SRAM Wei Xu
2015-01-13  8:33 ` Arnd Bergmann
2015-01-13  8:42   ` Wei Xu
2015-01-13  9:02     ` Arnd Bergmann
2015-01-13 10:28       ` Wei Xu [this message]
2015-01-13 10:33         ` Alexander Graf
2015-01-13 13:30           ` Arnd Bergmann
2015-01-14 10:51           ` Mark Rutland
2015-01-14 11:03             ` Alexander Graf
2015-01-14 12:00               ` Mark Rutland
2015-01-13 13:35         ` Arnd Bergmann
2015-01-13 14:18           ` Frediano Ziglio
2015-01-13 15:27             ` Arnd Bergmann
2015-02-20 15:30               ` Frediano Ziglio

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=54B4F350.5040007@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=linux-arm-kernel@lists.infradead.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).