From: Joachim Pihl <jpihl@nevion.com>
To: buildroot@busybox.net
Subject: [Buildroot] Strange MTD problem (ARM)
Date: Mon, 7 Dec 2009 09:36:15 +0100 [thread overview]
Message-ID: <op.u4j7ikxlyqa4qb@jap> (raw)
This may not be related to Buildroot, but I am completely stumped:
# ls -al /dev/mtdblock*
brw-r----- 1 root root 31, 0 Dec 3 12:26 mtdblock0
brw-r----- 1 root root 31, 1 Dec 3 12:26 mtdblock1
brw-r----- 1 root root 31, 2 Dec 3 12:26 mtdblock2
brw-r----- 1 root root 31, 3 Dec 3 12:26 mtdblock3
#
#
#
# cp mtdblock2 /dev/mtdblock2
#
# ls -al /dev/mtdblock*
brw-r----- 1 root root 31, 0 Dec 3 12:26 mtdblock0
brw-r----- 1 root root 31, 1 Dec 3 12:26 mtdblock1
-rw-r--r-- 1 root root 6815744 Dec 7 17:58 mtdblock2
brw-r----- 1 root root 31, 3 Dec 3 12:26 mtdblock3
#
Running 2009.11 on PXA255 with a 2.6.27.39 preemptible kernel, EABI,
running the same patches used for 2.6.27.10 (OABI and non-preemptible)
where it worked.
mtd_debug write /dev/mtd2 0 0x680000 mtdblock2 works, results does not
seems correct for /dev/mtd1.
Does anyone know where to look, so far I strike out on the google searches.
--
Joachim Pihl
Senior R&D Engineer
Nevion Europe
Tel: +47 33 48 94 66
Fax: +47 33 48 99 98
Mobile: +47 91 33 98 91
jpihl at nevion.com
www.nevion.com
------------------------------------------------------
The Global Video Transport Leader
------------------------------------------------------
next reply other threads:[~2009-12-07 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 8:36 Joachim Pihl [this message]
2009-12-07 8:34 ` [Buildroot] Strange MTD problem (ARM) Peter Korsgaard
2009-12-07 8:52 ` Joachim Pihl
2009-12-07 8:57 ` Peter Korsgaard
2009-12-07 9:17 ` Joachim Pihl
2009-12-07 9:28 ` Peter Korsgaard
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=op.u4j7ikxlyqa4qb@jap \
--to=jpihl@nevion.com \
--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