From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] mtdparts
Date: Tue, 6 Sep 2005 20:02:48 +0200 [thread overview]
Message-ID: <20050906180248.GA5160@orphique> (raw)
Hi there.
I'm just trying to sync with U-Boot development and found a little
regresion in new mtdparts code. Previously I was using custom partition
function, which let me do precisely what I wanted.
mtd0 - U-Boot
mtd1 - env
mtd2 - r_env
mtd3 - rootfs0
mtd4 - rootfs1
... etc
In above scheme my custom part function allowed only chpart [34], so it
was not even possible to change partition to evn sector for example.
Moreover it was pretty easy to construct kernel command line this way:
setenv bootargs '$bootargs root=/dev/mtdblock$partition ro rootfstype=jffs2'
And everything worked nicely. That is no longer case and it's real pain
with both NOR and NAND devices used in system.
Prefered solution for me is to fix kernel to be able to mount root
filesystem from MTD device given by name (root=mtd:rootfs0) unless
someone has better idea :-). Something which would work also with 2.4
kernels would be appreciated.
ladis
next reply other threads:[~2005-09-06 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 18:02 Ladislav Michl [this message]
2005-09-06 19:47 ` [U-Boot-Users] mtdparts Wolfgang Denk
2005-09-07 8:29 ` Ladislav Michl
2005-09-07 8:51 ` Wolfgang Denk
2005-09-07 9:45 ` [U-Boot-Users] Does anyone use Lan91c96 in U-Boot? Bryan Wu
2005-09-07 10:30 ` [U-Boot-Users] mtdparts Andreas Engel
2005-09-07 12:54 ` Wolfgang Denk
2005-09-07 13:37 ` Ladislav Michl
2005-09-12 22:25 ` Wolfgang Denk
2005-09-13 15:00 ` Ladislav Michl
2005-09-15 8:49 ` [PATCH] voiceblue update (Re: [U-Boot-Users] mtdparts) Ladislav Michl
2006-07-22 19:05 ` [U-Boot-Users] [PATCH] voiceblue update (Re: mtdparts) Wolfgang Denk
2006-07-25 15:00 ` Ladislav Michl
2006-10-29 10:36 ` Stefan Roese
2005-09-08 10:49 ` [U-Boot-Users] mtdparts Andreas Engel
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=20050906180248.GA5160@orphique \
--to=ladis@linux-mips.org \
--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