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: Tue, 05 Apr 2005 13:00:21 +0100	[thread overview]
Message-ID: <42527DD5.4080009@infocell-its.com> (raw)
In-Reply-To: <425181A7.2010809@ieee.org>

Dan Brown wrote:
> A recent modification to support variable-sized
> ecc_calc and ecc_code arrays didn't take into account the possibility of 
> NULL oobsel.  Fixed in CVS.
> 
> Let me know if DOCBoot finally works for you, please!

OK... diskonchip probing was fine with a fresh chip. Here's what I've
tried...

Built a kernel with MTD etc linked in (temporarily including hard-disk
stuff) and verified booting it from the hard-disk (obviously the 
diskonchip driver doesn't show the firmware partition, but that's ok).

Used M-Systems dformat (from tffs_5.1.4_DOS_TOOLS.zip) to resize the
firmware area
     A:\> DFORMAT /WIN:D000 /BDKL0:2M

Rebooted into a kernel with modules and ran
     # modprobe diskonchip show_firmware_partition=1
     # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 04000000 00004000 "DiskOnChip 2000 (NFTL Model)"
mtd1: 00208000 00004000 " DiskOnChip Firmware / Media Header partition"
mtd2: 03df8000 00004000 " DiskOnChip BDTL partition"

Edited docboot/cmdline to
     root=/dev/mtdblock1 rootfstype=jffs2 ro

Uncommented "#define OLD_DOC2K" in doc_bootstub.h

Copied in the bzImage I'd tested booting from hard-disk.
     # make
     # flash_eraseall /dev/mtd1
     # nandwrite -o /dev/mtd1 doc_spl
     # flash_eraseall -j /dev/mtd2

Tested mounting and unmounting /dev/mtdblock2 which seemed OK. (My 
cmdline above assumes that this will show as /dev/mtdblock1 when the 
linked-in driver is loaded.)
Rebooted and disabled/removed all other boot devices. As the BIOS gets 
going, I see "Installing DOCBoot." then a "System Configurations" page with
     ...<snip>...
     Verifying DMI Pool Data .........
     Loading kernel... _

where the "_" is a flashing cursor. The keyboard is unresponsive and 
nothing further happens :(

By the way, I have not yet copied any files to the jffs2 filesystem on 
/dev/mtdblock1 except a small text file to test the filesystem.

Any ideas? I'd really like to get this going.

Thanks again,

- Zeri

  reply	other threads:[~2005-04-05 11:58 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
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 [this message]
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=42527DD5.4080009@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