From: Jamie Lokier <jamie@shareable.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: u-boot-users@lists.sourceforge.net,
Bernard Blackham <bernard@largestprime.net>,
linux-mtd@lists.infradead.org
Subject: Re: [U-Boot-Users] ubi and u-boot
Date: Fri, 18 Apr 2008 17:59:57 +0100 [thread overview]
Message-ID: <20080418165957.GG31520@shareable.org> (raw)
In-Reply-To: <1208536808.6654.6.camel@vader.jdub.homelinux.org>
Josh Boyer wrote:
> On Fri, 2008-04-18 at 22:21 +0800, Bernard Blackham wrote:
> > [apologies for the cross post]
> > Is anyone working on ubi/ubifs support in u-boot?
>
> I am not aware of anyone actively working on porting UBI to upstream
> U-Boot at this exact moment.
Is it even a good idea? The UBI (version 1 :-) initial scan is not
fast for large flash, and if the bootloader does it too, that's twice
as much time to boot.
However, if there was a protocol for bootloader to pass the scan
results to the booted kernel, that would be very nice.
-- Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Lokier <jamie@shareable.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ubi and u-boot
Date: Fri, 18 Apr 2008 17:59:57 +0100 [thread overview]
Message-ID: <20080418165957.GG31520@shareable.org> (raw)
In-Reply-To: <1208536808.6654.6.camel@vader.jdub.homelinux.org>
Josh Boyer wrote:
> On Fri, 2008-04-18 at 22:21 +0800, Bernard Blackham wrote:
> > [apologies for the cross post]
> > Is anyone working on ubi/ubifs support in u-boot?
>
> I am not aware of anyone actively working on porting UBI to upstream
> U-Boot at this exact moment.
Is it even a good idea? The UBI (version 1 :-) initial scan is not
fast for large flash, and if the bootloader does it too, that's twice
as much time to boot.
However, if there was a protocol for bootloader to pass the scan
results to the booted kernel, that would be very nice.
-- Jamie
next prev parent reply other threads:[~2008-04-18 17:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 14:21 ubi and u-boot Bernard Blackham
2008-04-18 14:21 ` [U-Boot-Users] " Bernard Blackham
2008-04-18 16:40 ` Josh Boyer
2008-04-18 16:40 ` Josh Boyer
2008-04-18 16:59 ` Jamie Lokier [this message]
2008-04-18 16:59 ` Jamie Lokier
2008-04-18 17:49 ` Bernard Blackham
2008-04-18 17:49 ` Bernard Blackham
2008-04-20 22:22 ` Wolfgang Denk
2008-04-20 22:22 ` Wolfgang Denk
2008-04-21 12:05 ` Artem Bityutskiy
2008-04-21 13:36 ` Ricard Wanderlof
2008-04-21 13:36 ` Ricard Wanderlof
2008-04-21 13:44 ` Josh Boyer
2008-04-21 13:44 ` Josh Boyer
2008-04-21 13:50 ` Artem Bityutskiy
2008-04-21 14:01 ` Artem Bityutskiy
2008-04-22 11:44 ` Ricard Wanderlof
2008-04-22 11:44 ` Ricard Wanderlof
2008-04-22 1:09 ` [U-Boot-Users] How to set CPU speed to 266mhz s3c2410? p
2008-04-23 7:05 ` michael
2008-04-23 7:44 ` Martin Krause
2008-04-23 23:58 ` p
2008-04-22 12:30 ` [U-Boot-Users] ubi and u-boot Jamie Lokier
2008-04-22 12:30 ` Jamie Lokier
2008-04-18 19:19 ` Josh Boyer
2008-04-18 19:19 ` Josh Boyer
2008-04-20 16:04 ` Jamie Lokier
2008-04-20 16:04 ` Jamie Lokier
2008-04-20 16:44 ` Josh Boyer
2008-04-20 16:44 ` Josh Boyer
2008-04-20 17:29 ` Jamie Lokier
2008-04-20 17:29 ` Jamie Lokier
2008-04-21 1:05 ` Hamish Moffatt
2008-04-21 1:05 ` Hamish Moffatt
2008-04-19 9:25 ` Artem Bityutskiy
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=20080418165957.GG31520@shareable.org \
--to=jamie@shareable.org \
--cc=bernard@largestprime.net \
--cc=jwboyer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=u-boot-users@lists.sourceforge.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 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.