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: Wed, 06 Apr 2005 13:13:52 +0100	[thread overview]
Message-ID: <4253D280.6090308@infocell-its.com> (raw)
In-Reply-To: <4252EC5D.4090806@ieee.org>

 > There is a small (but important) fix to
> memory size detection, which shouldn't affect you since you're not using 
> initrd (I think).
No, you're right - I'm not using initrd.

> There is also a new option in doc_bootstub.h: #define DEBUG_BUILD.  This 
> will print out some interesting info during the "Installing DOCBoot" 
> phase, and wait for a keypress.

--------------------------------------------------------------
Award Modular BIOS v4.51PG, An Energy Star Ally
...
HS-4020 VER:1.4

Cyrix MediaGX With MMX-S CPU at 300MHz
Memory Test :   64000K OK + 1536 shared memory

Award Plug and Play BIOS Extension v1.0A
...
Installing DOCBoot.
doc_seg = 0xD000    setup_seg = 0x2000
int15/88 returns 0xF600    initrd_start = 0x000000
top of low mem = 0x0280k    handler seg = 0x9FC0
   -- Press any key --
--------------------------------------------------------------

...<snip>...
Loading kernel ... page 0x.... <- this seems to start at zero and be 
going up at roughly 0x200 a second up to 0xFFFF then restarting at zero 
again over and over.

Just to give you a clearer picture, the bzImage is 1148021 bytes and 
doc_spl is 1187472 bytes. The nandwrite command wrote doc_spl from 0 up 
to the erase block at 0x118000 which is well within the 0x208000 
firmware area. The board is a Boser HS-4020 v1.4.

Unfortunately, assembler is greek to me!

- Zeri

  reply	other threads:[~2005-04-06 12:11 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
2005-04-05 19:51               ` Dan Brown
2005-04-06 12:13                 ` Zeri Virgo [this message]
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=4253D280.6090308@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