From: Dan Brown <dan_brown@ieee.org>
To: "Carlos, John J USAATC" <john.carlos@atc.army.mil>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Doc_loadbios fails? Docboot?
Date: Mon, 20 Dec 2004 14:57:32 -0500 [thread overview]
Message-ID: <41C72EAC.50308@ieee.org> (raw)
In-Reply-To: <EFF9A3506F74924AB5CC77BDC66E793518139B@atcml01.atc.army.mil>
I'm CC'ing the list on this since other people may benefit.
Carlos, John J USAATC wrote:
>Dan,
>
> Maybe you can answer some questions for me. I use dformat to create the
>BDK and BDTL partitions. The BDK is 2 Meg and the BDTL the remainder. My
>/proc/mtd shows just one entry mtd0.
>
This sounds like the problem. My guess is that you did not compile MTD
partition support into your kernel. If partition support is not
available, I think only one device (mtd0) gets created, which is not
what you want. See if you can verify that this kernel config option is
turned on.
>I then try to follow your guide lines
>for docboot. I use mtd0 in the nand_eraseall and the nandwrite function. I
>write the doc_spl and then reboot (init18 hook). I can't boot from the doc.
>I have lilo on a floppy and when I direct lilo (on a floppy) to boot from my
>hard drive the inftla chip is gone/messed up and the driver doesn't see an
>inftla1.
>
> Could you tell my why this might be?
>
>
Since you did a nand_eraseall/nandwrite to mtd0, you erased your
*entire* device, and then wrote docboot to the beginning. Not what you
intended at all :)
Let me know if you have any success. If this works for you, I should
update the docboot instructions to tell people they need partition support.
-Dan
next parent reply other threads:[~2004-12-20 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EFF9A3506F74924AB5CC77BDC66E793518139B@atcml01.atc.army.mil>
2004-12-20 19:57 ` Dan Brown [this message]
2004-12-20 12:47 Doc_loadbios fails? Docboot? Carlos, John J USAATC
2004-12-20 13:35 ` 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=41C72EAC.50308@ieee.org \
--to=dan_brown@ieee.org \
--cc=john.carlos@atc.army.mil \
--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