From: Carles Perello <carles.perello@ieee.org>
To: linux-mtd@lists.infradead.org
Subject: redboot partition parsing
Date: 05 Nov 2003 15:34:35 +0100 [thread overview]
Message-ID: <1068042874.6863.4.camel@stream.amrsystems.com> (raw)
Hello,
Since I downloaded last CVS mtd tree, I am struggling with both 2.4.18
and 2.4.21 kernels to be able to read redboot partitions again...
I do have redboot parser compiled:
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_CONCAT is not set
CONFIG_MTD_REDBOOT_PARTS=y
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_AFS_PARTS is not set
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
and the flash is correctly probed:
-- SA11xx Flash probe. Please report results.
* Probing 0x00000000: MSC = 0xfff8 32 bit <6>SA1100-flash: Found 2 x16
devices at 0x0 in 32-bit mode
Intel/Sharp Extended Query Table at 0x0031
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
pass
* Probing 0x08000000: MSC = 0x75fe 16 bit <4>genprobe_new_chip called
with unsupported buswidth 2
CFI: Found no SA1100-flash device at location zero
failed
* Probing 0x10000000: MSC = 0x1822 32 bit <4>CFI: Found no SA1100-flash
device at location zero
failed
* Probing 0x18000000: MSC = 0x0011 32 bit wrong type
* Probing 0x40000000: MSC = 0xfffc 16 bit <4>genprobe_new_chip called
with unsupported buswidth 2
CFI: Found no SA1100-flash device at location zero
failed
* Probing 0x48000000: MSC = 0xf71f 16 bit <4>genprobe_new_chip called
with unsupported buswidth 2
CFI: Found no SA1100-flash device at location zero
failed
-- SA11xx Flash probe complete.
and no output form the redboot partition parser...
any hint?
cheers
--
Carles Perello <carles.perello@ieee.org>
reply other threads:[~2003-11-05 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1068042874.6863.4.camel@stream.amrsystems.com \
--to=carles.perello@ieee.org \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.