From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot sunxi fel plan for v2015.04
Date: Sun, 15 Feb 2015 17:38:48 +0100 [thread overview]
Message-ID: <54E0CB98.4080501@redhat.com> (raw)
In-Reply-To: <20150215164304.185dc30e@i7>
Hi,
On 15-02-15 15:43, Siarhei Siamashka wrote:
> On Fri, 13 Feb 2015 16:50:49 -0500
> Tom Rini <trini@ti.com> wrote:
>
>> On Fri, Feb 13, 2015 at 09:19:08AM +0100, Hans de Goede wrote:
>>> Hi Siarhei and Simon,
>>>
>>> I'm wondering what the plan is wrt sunxi FEL booting for u-boot
>>> v2015.04 I know that you both have been working on this, and I
>>> think that for v2015.04 Simon's latest set probably is the best
>>> way forward for now, we're going to need parts of that set
>>> anyways for the more complete solution Siarhei has.
>>>
>>> we could replace the patch adding all the #ifdef's to start.S
>>> with code saving / restoring PCR15 and friends, that would be
>>> more cleaner.
>>>
>>> So I see 2 ways forwards for v2014.05
>>>
>>> 1) Go with Simon's latest set as is.
>>> 2) Take the first patches from Simon's set and replace the
>>> on adding he #ifdef's to start.S with one saving / restoring
>>> the necessary regs
>>>
>>> I've a slight preference for 2. Siarhei, can you perhaps prepare
>>> a patch-set for 2 for merging for v2014.05 ?
>>
>> And when everyone is happy I'll take it via the sunxi tree (And try and
>> see about giving it a spin on my Lime2). Thanks!
>
> Thanks for clarifying this.
>
> Simon, could you please confirm that you are not going to do anything
> anymore with the third patch from your sunxi FEL fixes set?
>
> Hans, could you please queue Simon's patches in the sunxi next branch
> just like Tom suggested (and after the status of the third patch becomes
> more clear)?
I'm fine with taking Simon's patch-set as is, and upstreaming it through
the sunxi tree, but the start.S changes are not really sunxi specific, so I
think they need Alberts ack?
Tom are you ok with taking these without Albert's ack?
And/or Albert can we have your ack for:
http://patchwork.ozlabs.org/patch/437580/
http://patchwork.ozlabs.org/patch/437581/
http://patchwork.ozlabs.org/patch/437582/
(the 2nd one is not really ARM specific, but still)
Regards,
Hans
next prev parent reply other threads:[~2015-02-15 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 8:19 [U-Boot] u-boot sunxi fel plan for v2015.04 Hans de Goede
2015-02-13 14:17 ` Simon Glass
2015-02-13 19:53 ` Siarhei Siamashka
2015-02-13 21:50 ` Tom Rini
2015-02-15 14:43 ` Siarhei Siamashka
2015-02-15 15:46 ` Simon Glass
2015-02-15 16:38 ` Hans de Goede [this message]
2015-02-16 16:42 ` Tom Rini
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=54E0CB98.4080501@redhat.com \
--to=hdegoede@redhat.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.