public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: hip04: move bootwrapper to SRAM
Date: Tue, 13 Jan 2015 14:35:17 +0100	[thread overview]
Message-ID: <4774908.c54zTnV4pN@wuerfel> (raw)
In-Reply-To: <54B4F350.5040007@hisilicon.com>

On Tuesday 13 January 2015 18:28:32 Wei Xu wrote:
> 
> > 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?

The intention is certainly good. If you expect no further incompatible
changes, how about adding another .dts file for this machine that can
work with the old firmware?

	Arnd

  parent reply	other threads:[~2015-01-13 13:35 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
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 [this message]
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=4774908.c54zTnV4pN@wuerfel \
    --to=arnd@arndb.de \
    --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