From: Dan Brown <dan_brown@ieee.org>
To: Zeri Virgo <zerivirgo@infocell-its.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [UPDATE] DOCBoot support for NFTL-based DOC2000
Date: Thu, 31 Mar 2005 15:35:34 -0500 [thread overview]
Message-ID: <424C5F16.8010809@ieee.org> (raw)
In-Reply-To: <424C1C58.3000905@infocell-its.com>
Zeri Virgo wrote:
> 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)...
Hmm. Looks like I broke something when I changed the code to scan the
entire device for media headers. Some questions for you:
- What size is your DOC?
- How big is your firmware area? (I'm assuming you resized it using
the DOS-based tools)
- Did the diskonchip driver work for you without crashing before my
latest changes? (Obviously this would be with a standard-sized firmware
area)
- Can you tell me what kind of crash it is? NULL pointer dereference, etc?
- What information (if any) is printed when the DOC is detected, before
the crash? I'm interested in information about the number and sizes of
NAND chips, number of chips per floor, etc.
> 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?
I didn't see anything wrong in your config options.
-Dan
next prev parent reply other threads:[~2005-03-31 20:35 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
2005-03-31 20:35 ` Dan Brown [this message]
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=424C5F16.8010809@ieee.org \
--to=dan_brown@ieee.org \
--cc=linux-mtd@lists.infradead.org \
--cc=zerivirgo@infocell-its.com \
/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