From: Alexander Aring <alex.aring@googlemail.com>
To: christian.buettner@rafi.de
Cc: barebox@lists.infradead.org
Subject: Re: Create NAND Partition through barebox
Date: Thu, 29 Mar 2012 14:08:31 +0200 [thread overview]
Message-ID: <CAB_54W6ta+Gx+=j+NuspKkixkx5oQyg=OtwuHZx9bcDKg8d97A@mail.gmail.com> (raw)
In-Reply-To: <OF440839EF.2383F590-ONC12579D0.00410F43-C12579D0.004184D1@o0802.rafi.inhouse>
[-- Attachment #1.1: Type: text/plain, Size: 1834 bytes --]
Hi,
you can create NAND Partitons with nand_parts variable in /env/config.
For example nand_parts="256k(barebox)ro,128k(bareboxenv),3M(kernel),-(root)"
nand -a nand0.* only creates a bb device that will handle badblocks if they
appear.
Cheers
Alex
Am 29. März 2012 13:55 schrieb <christian.buettner@rafi.de>:
> Hi,
>
> i need to create a NAND Partition through the barebox prompt to be able to
> flash a kernel image on it.
>
> This is the current devinfo of my target:
>
> barebox:/ devinfo
> devices:
> `---- imx_serial0
> `---- cs0
> `---- mem0
> `---- 0x00000000-0x1fffffff: /dev/ram0
> `---- mem1
> `---- 0x00000000-0x1fffffff: /dev/ram1
> `---- imx_iim0
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank0
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank1
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank2
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank3
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank4
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank5
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank6
> `---- 0x00000000-0x0000001f: /dev/imx_iim_bank7
> `---- ramfs0
> `---- devfs0
> `---- mem2
> `---- 0x00000000-0x000018ab: /dev/defaultenv
> `---- mem3
> `---- 0x00000000-0xfffffffe: /dev/mem
> `---- cs1
> `---- fec_imx0
> `---- miidev0
> `---- 0x00000000-0x0000003f: /dev/phy0
> `---- eth0
>
> drivers:
> imx_serial
> ramfs
> devfs
> imx_iim
> fec_imx
> miidev
> mem
>
>
> I tried using
> $ nand -a /dev/nand0.*
>
> Nothing happens..
> What is wrong?
>
> - - Christian
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
>
[-- Attachment #1.2: Type: text/html, Size: 3822 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-03-29 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 11:55 christian.buettner
2012-03-29 12:03 ` Eric Bénard
2012-03-29 12:32 ` Antwort: " christian.buettner
2012-03-29 12:34 ` Eric Bénard
2012-03-29 12:40 ` Alexander Aring
2012-03-29 12:59 ` Antwort: " christian.buettner
2012-03-29 13:01 ` Eric Bénard
2012-03-29 13:42 ` Franck Jullien
2012-03-30 12:03 ` Antwort: " christian.buettner
2012-03-29 12:08 ` Alexander Aring [this message]
2012-03-29 12:15 ` christian.buettner
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='CAB_54W6ta+Gx+=j+NuspKkixkx5oQyg=OtwuHZx9bcDKg8d97A@mail.gmail.com' \
--to=alex.aring@googlemail.com \
--cc=barebox@lists.infradead.org \
--cc=christian.buettner@rafi.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