From: Matt Hsu <matt@0xlab.org>
To: Rob Landley <rob@landley.net>
Cc: celinux-dev@tree.celinuxforum.org,
linux-embedded@vger.kernel.org, Andy Green <andy@warmcat.com>
Subject: Re: [Celinux-dev] CELF Project Proposal- Refactoring Qi, lightweight bootloader
Date: Mon, 21 Dec 2009 13:51:23 +0800 [thread overview]
Message-ID: <4B2F0CDB.3050305@0xlab.org> (raw)
In-Reply-To: <200912202045.37159.rob@landley.net>
Rob Landley wrote:
> However, if that's your minimum then you can't use the bootloader to re-flash
> the device, which is kind of handy. (It gives you an un-bricking fallback
> short of pulling out a jtag.)
Hi Rob,
Well, Boot from SD is your good friend.
If you look at the platform that Qi which is supported, most of them
all have this feature.
If you notice the trend of SoC, booting from peripherals becomes a
must.
Once you step into kernel via Qi, kernel provides you everything
such as mtd utils to re-flash device.
We don't need to support programming the device in the bootloader
anymore.
Don't reinvent the wheel.
>
> Looking at the screen shot there, you've got code to parse ext2 filesystems.
> What is your definition of "minimal"?
>
Enough to boot into Linux.
> Rationale for not providing a boot menu is you don't want to mess with video
> init.
Nope, the centric idea of Qi, is let kernel deal with everything it
could handle.
The video init should be handled by kernel stead of bootloader.
The following clip demonstrate the advantage of Qi bootloader:
http://www.youtube.com/watch?v=ol9LWBKXXwQ&feature=related
- Faster booting time
- Get rid of flash on display device when stepping into kernel
Hope these could clear your doubt.
Cheers,
Matt
next prev parent reply other threads:[~2009-12-21 5:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 8:31 CELF Project Proposal- Refactoring Qi, lightweight bootloader Matt Hsu
2009-12-17 9:21 ` Andy Green
2009-12-21 19:30 ` [Celinux-dev] " Wolfgang Denk
2009-12-21 19:32 ` Mike Frysinger
2009-12-21 20:17 ` Andy Green
2009-12-21 21:38 ` Wolfgang Denk
2009-12-21 22:38 ` Andy Green
2009-12-21 23:17 ` Wookey
2009-12-21 23:19 ` Robert Schwebel
2009-12-22 8:22 ` Andy Green
2009-12-22 11:12 ` Robert Schwebel
2009-12-22 22:23 ` Andy Green
2009-12-22 23:28 ` Robert Schwebel
2009-12-23 8:38 ` Andy Green
2009-12-23 8:56 ` Robert Schwebel
2009-12-23 9:29 ` Andy Green
2009-12-23 9:43 ` Robert Schwebel
2009-12-27 7:27 ` Rob Landley
2009-12-27 10:09 ` Andy Green
2009-12-28 0:21 ` Rob Landley
2009-12-28 11:33 ` Andy Green
2009-12-27 7:17 ` Rob Landley
2009-12-27 9:54 ` Andy Green
2009-12-27 23:15 ` Rob Landley
2009-12-28 10:27 ` Andy Green
2009-12-28 19:57 ` Peter Korsgaard
2009-12-28 20:20 ` Andy Green
2009-12-29 4:25 ` Rob Landley
2009-12-29 11:11 ` Andy Green
2009-12-17 23:13 ` Tim Bird
2009-12-21 2:45 ` [Celinux-dev] " Rob Landley
2009-12-21 5:51 ` Matt Hsu [this message]
2009-12-21 8:00 ` Rob Landley
2009-12-21 9:54 ` Andy Green
2009-12-21 20:49 ` Wookey
2009-12-23 2:28 ` Jamie Lokier
2009-12-23 8:48 ` Andy Green
2009-12-29 13:13 ` Jamie Lokier
2009-12-29 13:36 ` Andy Green
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=4B2F0CDB.3050305@0xlab.org \
--to=matt@0xlab.org \
--cc=andy@warmcat.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-embedded@vger.kernel.org \
--cc=rob@landley.net \
/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).