Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] VFS: Cannot open root device "mtd ...
Date: Thu, 14 Oct 2010 14:23:57 +0200	[thread overview]
Message-ID: <4CB6F65D.1090401@visionsystems.de> (raw)
In-Reply-To: <0C11C5BF0B29FD43A8D0250F711D497F7F66397800@ex01-ubitronix.ubitronix.local>

 Hello abhiash,

> Boardfile that I am using is at91sam9260ek_defconfig.
>
> In the file -->
> output/build/linux2.6.34.1/arch/arm/mach-at91/board-sam9260ek.c
>
> The name is mentioned as "Partition 1" and "Partition 2" for the MTD partition.
>
> I have not altered this file
>
> Specifying it as /dev/Partition 1 in the uboot env.... it takes it as Partition

These partition name will be used for other operations, device names are still the same /dev/mtdblockX

> Partition1 gives the same errors.
>
> What should be the next try ?

You'll have to modify

output/build/linux2.6.34.1/arch/arm/mach-at91/board-sam9260ek.c

/*
 * NAND flash
 */
static struct mtd_partition __initdata ek_nand_partition[] = {
        {
                .name   = "Boot", 		/* /dev/mtdblock0 */
                .offset = 0,
                .size   = SZ_2M,
        },
        {
                .name   = "Kernel",		/* /dev/mtdblock1 */
                .offset = MTDPART_OFS_NXTBLK,
                .size   = SZ_2M,
        },

        {
                .name   = "File System",	/* /dev/mtdblock2 */
                .offset = MTDPART_OFS_NXTBLK,
                .size   = MTDPART_SIZ_FULL,
        },
};

Then your kernel params should look like this:

'mem=64M console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2'

Best regards,
Yegor

      reply	other threads:[~2010-10-14 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  9:48 [Buildroot] VFS: Cannot open root device "mtd Abhishek Ashtekar
2010-10-14 10:11 ` Yegor Yefremov
2010-10-14 10:59   ` Abhishek Ashtekar
2010-10-14 12:23     ` Yegor Yefremov [this message]

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=4CB6F65D.1090401@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox