From: Jagan Teki <jagannadh.teki@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Call for participation in the U-Boot Mini Summit 2014
Date: Wed, 24 Sep 2014 18:45:00 +0530 [thread overview]
Message-ID: <CAD6G_RTevbaihdtoAe=3k2QmUA_YD=ZGBKgs8V=s01Kh_zsbpw@mail.gmail.com> (raw)
In-Reply-To: <20140905175349.GK25506@bill-the-cat>
On 5 September 2014 23:23, Tom Rini <trini@ti.com> wrote:
> On Fri, Sep 05, 2014 at 07:30:35PM +0200, Marek Vasut wrote:
>
> [snip]
>> > It's easier to work with than fitImage.
>>
>> In which way?
>
> In most developer work flows at least zImage then uImage then fitImage
> are the easiest to work with, in that order, for ARM. For ARM64 Image
> in the next release will probably release uImage as the easiet to work
> with.
>
> fitImage seems useful in a lot of deployment scenarios. Having to craft
> up a good skeleton device tree in most cases is an annoying to overcome
> barrier for a development workflow.
Just an additional info:
In fact I was advertising a lot for this possible boot scenarios [2]
talk in India
last year other than U-Boot Mini 2013 starting from legacy to fit.
What I understand that developers are very interested and they
asked more possible useful scenarios with in the fitimage stuff
like loading different kernels (as part of visualization) etc.
May it would be good if any one is interested to talk on that more.
[1] http://www.denx.de/wiki/U-Boot/OpenSourceIndia2013
thanks!
--
Jagan.
next prev parent reply other threads:[~2014-09-24 13:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 17:12 [U-Boot] Call for participation in the U-Boot Mini Summit 2014 Detlev Zundel
2014-08-11 15:48 ` Przemyslaw Marczak
2014-08-11 21:08 ` Tom Rini
2014-08-12 0:02 ` Masahiro YAMADA
2014-08-12 0:49 ` Marek Vasut
2014-08-12 8:34 ` Igor Grinberg
2014-08-22 3:26 ` Masahiro Yamada
2014-08-30 16:36 ` Marek Vasut
2014-08-30 18:22 ` Lukasz Majewski
2014-09-03 16:36 ` Detlev Zundel
2014-09-03 16:34 ` Detlev Zundel
2014-08-12 0:45 ` Marek Vasut
2014-09-03 16:39 ` Detlev Zundel
2014-09-04 15:01 ` Marek Vasut
2014-09-05 15:50 ` Scott Wood
2014-09-05 17:30 ` Marek Vasut
2014-09-05 17:53 ` Tom Rini
2014-09-05 18:08 ` Simon Glass
2014-09-05 19:21 ` Tom Rini
2014-09-24 13:15 ` Jagan Teki [this message]
2014-08-12 7:15 ` Lukasz Majewski
2014-09-03 16:56 ` Przemyslaw Marczak
2014-09-18 8:52 ` Alexey Brodkin
2014-09-19 4:27 ` Marek Vasut
2014-09-23 11:50 ` Alexey Brodkin
2014-10-02 16:05 ` Detlev Zundel
2014-08-12 7:23 ` Lukasz Majewski
2014-09-03 16:46 ` Detlev Zundel
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='CAD6G_RTevbaihdtoAe=3k2QmUA_YD=ZGBKgs8V=s01Kh_zsbpw@mail.gmail.com' \
--to=jagannadh.teki@gmail.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.