From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bricked when trying to attach UBI
Date: Thu, 20 Dec 2012 00:17:43 +0530 [thread overview]
Message-ID: <50D20BCF.6060105@gmail.com> (raw)
In-Reply-To: <50D205D4.2030103@denx.de>
On 12/19/2012 11:52 PM, Stefan Roese wrote:
<snip>
>> I think its the right time to sync the UBI code with the current kernel
>> tree. But it seems like a huge work. Any suggestions?
>
> Yes, syncing with the latest UBI/UBIFS code would be the best solution.
> Even though a try with an increased malloc area as suggested by Andreas
> might be a chance.
>
> And yes, this re-sync with the latest-and-greatest Linux code version is
> of course a bigger task. It has been suggest as part of booting from an
> UBI volume task to the celinux forum:
>
> http://lists.celinuxforum.org/pipermail/celinux-dev/2012-April/000543.html
Yeah. I had queried sometime back on the activity of this task.
> But nothing has happened till now. Any volunteers? But please keep in
> mind that intensive testing is required before the current (stable?)
> code version can be replaced.
>
Looks like the MTD layer might needs to be patched up as well at some
places. What do you think?
Regards,
Vikram
next prev parent reply other threads:[~2012-12-19 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 11:28 [U-Boot] Bricked when trying to attach UBI Luca Ceresoli
2012-12-19 15:24 ` Andreas Bießmann
2012-12-19 15:56 ` Luca Ceresoli
2012-12-19 16:09 ` Andreas Bießmann
2012-12-19 17:37 ` Luca Ceresoli
2012-12-20 12:44 ` Holger Brunck
2012-12-20 16:02 ` Luca Ceresoli
2013-01-02 14:37 ` Luca Ceresoli
2012-12-19 17:32 ` Vikram Narayanan
2012-12-19 18:22 ` Stefan Roese
2012-12-19 18:47 ` Vikram Narayanan [this message]
2012-12-19 18:57 ` Vikram Narayanan
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=50D20BCF.6060105@gmail.com \
--to=vikram186@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox