From: Udo van den Heuvel <udovdh@xs4all.nl>
To: openembedded-devel@openembedded.org
Subject: Re: PATCH: make h2200-bootloader load & depend on mtdblock
Date: Thu, 24 Jul 2008 15:43:37 +0200 [thread overview]
Message-ID: <48888709.40906@xs4all.nl> (raw)
In-Reply-To: <1216905807.6103.32.camel@dax.rpnet.com>
Richard Purdie wrote:
> On Thu, 2008-07-24 at 15:04 +0200, Udo van den Heuvel wrote:
>> Richard Purdie wrote:
>>> Yes, its standard practise to RRECOMMEND kernel modules since if they're
>>> built into the kernel you get build failures otherwise. The RRECOMMEND
>>> is a standard approach and well tested.
>> Apart from this discussion, sorry to interrupt, but does mtdchar
>> 9related to mtdblock I guess) actually work?
>> On my H2200('s) it fails to properly flash a kernel.
>> It doesn't matter much now because we boot from SD, but nevertheless it
>> is strange.
>> The mtd folks refuse to help me when I repeatedly queried them.
>
> Yes, mtdchar usually works.
'usually' sounds atypical here:
http://bugs.openembedded.net/show_bug.cgi?id=4354
but also:
http://bugs.openembedded.net/show_bug.cgi?id=4324
and:
http://bugs.openembedded.net/show_bug.cgi?id=4362
So a whole slew of flash-related issues, all based on mtd-related code.
My ipaq ran win2003 mobile fine.
> It may not do exactly what you expect though
That is what I observe, others see similar issues.
Udo
next prev parent reply other threads:[~2008-07-24 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 23:48 PATCH: make h2200-bootloader load & depend on mtdblock Paul Eggleton
2008-07-24 1:06 ` Rolf Leggewie
2008-07-24 7:19 ` Koen Kooi
2008-07-24 8:08 ` Paul Eggleton
2008-07-24 9:01 ` Koen Kooi
2008-07-24 9:08 ` Richard Purdie
2008-07-24 13:04 ` Udo van den Heuvel
2008-07-24 13:23 ` Richard Purdie
2008-07-24 13:43 ` Udo van den Heuvel [this message]
2008-07-24 19:50 ` Paul Eggleton
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=48888709.40906@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.