From: Ben Dooks <ben@fluff.org.uk>
To: "lp4u@inwind.it" <lp4u@inwind.it>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: Nand detect
Date: Tue, 28 Sep 2004 11:55:23 +0100 [thread overview]
Message-ID: <20040928105523.GC22627@home.fluff.org> (raw)
In-Reply-To: <I4QXWY$DC028C17BCE4F7375CD8E760DCF56467@libero.it>
On Tue, Sep 28, 2004 at 12:17:22PM +0200, lp4u@inwind.it wrote:
> Hi,
>
> I've a s3c24210 board with BAST architecture, with 2 NAND on board.
> I've compiling the kernel 2.6.9-rc2 after patched it with:
> - patch-2.6.9-rc2-bk11
> - dm9k-rc2.patch
> - patchin (mtd 2004/09/19)
> - nand_multi1.diff
the next release should be in mtd, and we will be able to do
away with the nand_multi1.diff
[snip]
> Bad eraseblock 3946 at 0x03da8000
> No NAND device found!!!
> s3c2410-nand: registered device sets:
> s3c2410-nand: set 0, SmartMedia:error 1
> s3c2410-nand: set 1, chip0:ok:
> Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
> 0x00000000-0x00004000 : "Boot Agent"
> mtd: Giving out device 0 to Boot Agent
> 0x00004000-0x00400000 : "/boot"
> mtd: Giving out device 1 to /boot
> 0x00400000-0x04000000 : "user"
> mtd: Giving out device 2 to user
> s3c2410-nand: set 2, chip1:ok:
> Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
> 0x00000000-0x00004000 : "Boot Agent"
> mtd: Giving out device 3 to Boot Agent
> 0x00004000-0x00400000 : "/boot"
> mtd: Giving out device 4 to /boot
> 0x00400000-0x04000000 : "user"
> mtd: Giving out device 5 to user
> s3c2410-nand: set 3, chip2:error 1
>
> I don't get work with the NAND, why?
> MTD detect 5 devices, I've only 2 NAND. Why, occurs that?
each mtd device node is 1 partition, not one chip.
> The proc/ is empty, there aren't device, why?
/proc is for information, not device nodes.
> Must I work with /dev/mtdN or /dev/mtdblockN?
/dev/mtdX and /dev/mtdblockN are the proper devices to
use for accessing the NAND partitions
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2004-09-28 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 10:17 Nand detect lp4u
2004-09-28 10:55 ` Ben Dooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-23 9:54 NAND detect lp4u
2004-09-23 10:53 ` Ben Dooks
2004-09-22 15:55 lp4u
2004-09-22 20:29 ` Ben Dooks
2004-09-23 7:11 ` Thomas Gleixner
2004-09-23 9:48 ` Ben Dooks
[not found] ` <20040923191506.GE25491@home.fluff.org>
2004-09-23 23:05 ` Ben Dooks
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=20040928105523.GC22627@home.fluff.org \
--to=ben@fluff.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=lp4u@inwind.it \
/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