public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Zeri Virgo <zerivirgo@infocell-its.com>
To: Dan Brown <dan_brown@ieee.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [UPDATE] DOCBoot support for NFTL-based DOC2000
Date: Thu, 31 Mar 2005 16:50:48 +0100	[thread overview]
Message-ID: <424C1C58.3000905@infocell-its.com> (raw)
In-Reply-To: <4249C357.2040600@ieee.org>

Dan Brown wrote:
> As promised (albeit somewhat delayed), I have just checked into CVS some 
> changes to DOCBoot supporting NFTL-based DOC2000 devices.

Thanks for this - it's just what I need!

Unfortunately my 2.6.11.5 kernel patched with mtd/patchkernel.sh, is 
crashing with the following stack trace (I've just jotted down the 
symbols)...

EIP is at nand_do_read
...
nand_read+0x2c/0x30
find_media_headers+0x3e/0x150
nftl_scan_bbt+0x8f/0x360
nand_scan+0x466/0x940
doc2000_count_chips+0x4e/0x60
init_nanddoc+0x34b/0xad0
do_initcalls
...


The MTD section of my .config is below (I removed NFTL because I'm only 
going to be using JFFS2, ok?). Is there anything obviously wrong here?

- Zeri


CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not setCONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PLATRAM is not set
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
# CONFIG_MTD_BLOCK2MTD is not set
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND=y
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_IDS=y
CONFIG_MTD_NAND_DISKONCHIP=y
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
# CONFIG_MTD_NAND_NANDSIM is not set

  reply	other threads:[~2005-03-31 16:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 21:06 [UPDATE] DOCBoot support for NFTL-based DOC2000 Dan Brown
2005-03-31 15:50 ` Zeri Virgo [this message]
2005-03-31 20:35   ` Dan Brown
2005-04-01  1:33     ` Zeri Virgo
2005-04-01  2:13       ` Dan Brown
2005-04-04 15:05         ` Zeri Virgo
2005-04-04 18:04           ` Dan Brown
2005-04-05 12:00             ` Zeri Virgo
2005-04-05 19:51               ` Dan Brown
2005-04-06 12:13                 ` Zeri Virgo
2005-04-06 12:29                   ` Zeri Virgo
2005-04-06 13:12                     ` Dan Brown
2005-04-06 14:48                       ` Zeri Virgo
2005-04-06 16:29                         ` Dan Brown
2005-04-06 18:23                           ` Dan Brown
2005-04-07 14:27                             ` Dan Brown
2005-04-07 21:45                               ` Zeri Virgo
2005-04-08 15:41                                 ` Dan Brown

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=424C1C58.3000905@infocell-its.com \
    --to=zerivirgo@infocell-its.com \
    --cc=dan_brown@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox