From: Daniel Mack <daniel@caiaq.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBI on NAND flash again
Date: Thu, 4 Jun 2009 11:37:05 +0200 [thread overview]
Message-ID: <20090604093705.GE26688@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090604092707.43A40832E416@gemini.denx.de>
On Thu, Jun 04, 2009 at 11:27:07AM +0200, Wolfgang Denk wrote:
> >
> > Oh well - you're right. The code failed in vmalloc() due to a too small
> > CONFIG_SYS_MALLOC_LEN which I needed to augment to 512kB.
>
> But then a big, fat error message is needed there!
In vmalloc(), yes. That bug could hit any code that deals with
dynamically allocated memory.
Daniel
next prev parent reply other threads:[~2009-06-04 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 18:05 [U-Boot] UBI on NAND flash again Daniel Mack
2009-06-04 6:42 ` Stefan Roese
2009-06-04 6:50 ` Daniel Mack
2009-06-04 6:56 ` Stefan Roese
2009-06-04 8:06 ` Daniel Mack
2009-06-04 8:15 ` Stefan Roese
2009-06-04 8:51 ` Wolfgang Denk
2009-06-04 9:07 ` Daniel Mack
2009-06-04 9:17 ` Stefan Roese
2009-06-04 9:27 ` Wolfgang Denk
2009-06-04 9:37 ` Daniel Mack [this message]
2009-06-04 8:35 ` Wolfgang Denk
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=20090604093705.GE26688@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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