public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Meade <mark@lakeshoremicro.com>
To: linux-mtd@lists.infradead.org
Cc: ilatypov@superbt.com
Subject: Re: DiskOnChip 2000 and Millenium support in GRUB bootloader
Date: Mon, 11 Mar 2002 13:06:35 -0500	[thread overview]
Message-ID: <200203111306968.SM01632@there> (raw)

On Sun, 10 Mar 2002, Ilguiz Latypov wrote:

> I was able to test the grub_firmware file produced by the patch on a 64M
> DoC 2000.  Yes, I could get to the GRUB prompt and play with "root (dc0,"
> command.  GRUB can access the configuration file and the kernel image
> stored in ext2 partition.  The partition was created on top of NFTL block
> device layer.
>
> Mark Meade has offered few improvements to the patch.  I think there are 2 
> latest changes that may be of interest to you:
>
>  a) New configuration option --enable-diskonchip-biosnetboot will make 
>      GRUB firmware to attach itself to INT 18h (BIOS network boot) rather 
>      than to INT 19h (BIOS bootstrap loader).  If you try that option, 
>      enable network boot in BIOS as well.
>
>   b) The DoC SlowIO register is no longer read when fetching the data 
>      from the flash memory.
>
> I updated the patch.  It is available at
>    
> http://savannah.gnu.org/patch/?func=detailpatch&patch_id=164&group_id=68

Ilguiz,

I have been testing your latest patch with the DoC Millennium.  I'm able to 
get a GRUB prompt only after forcing the 512-byte-page code (doc_stage1b.S) 
to address 0x100.

Normally, it looks like the 256-byte/page code ends up at 0x100, and the 
512-byte at 0x200.  With the DoC 2000, this insures that the proper code 
(loaded by the IPL) ends up at 0x100.

Since the Millennium is XIP, jumping to 0x100 ends up running 256-byte-page 
code, which doesn't work in this case.

You mentioned that there are DoC Millennium parts based on 256-byte-page 
chips -- so my hack to force the 512-byte code to 0x100 will not work 
correctly for all Millennium parts.

Any thoughts or ideas?

Thanks,

Mark

             reply	other threads:[~2002-03-11 17:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 18:06 Mark Meade [this message]
2002-03-12 21:07 ` DiskOnChip 2000 and Millenium support in GRUB bootloader Ilguiz Latypov
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15 22:05 Mark Meade
     [not found] <Pine.LNX.4.44.0203041529100.20113-100000@server.superbt.com>
2002-03-04 21:48 ` Mark Meade
2002-03-04 20:54 ilatypov
2002-03-02  2:51 Mark Meade
     [not found] <87k7sxevml.wl@enter.planet.of.kuicr.kyoto-u.ac.jp>
2002-03-01  2:44 ` Ilguiz Latypov
2002-03-01  7:19   ` David Woodhouse
2002-03-20  8:48     ` Yoshinori K. Okuji
2002-02-26  0:39 Vadim Khmelnitsky
2002-02-26  0:26 Vadim Khmelnitsky
2002-02-26  1:06 ` David Woodhouse
2002-02-23  0:23 Vadim Khmelnitsky
2002-02-21 22:50 Vadim Khmelnitsky
2002-02-22  5:37 ` Ilguiz Latypov
2002-02-22 16:17   ` Mark Meade
2002-02-22 16:59     ` Ilguiz Latypov
2002-02-22 20:32       ` Mark Meade
2002-02-22 22:38         ` Ilguiz Latypov
2002-02-20 22:25 Mark Meade
2002-02-20 23:38 ` Ilguiz Latypov
2002-02-21  1:01   ` Mark Meade
2002-02-21 22:08     ` Ilguiz Latypov
2002-02-21 22:13       ` Ilguiz Latypov
2002-02-21 22:32       ` Mark Meade
2002-02-19 22:51 Ilguiz Latypov

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=200203111306968.SM01632@there \
    --to=mark@lakeshoremicro.com \
    --cc=ilatypov@superbt.com \
    --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