From: Russ Dill <Russ.Dill@asu.edu>
To: "Edward A. Hildum" <ehildum@mail.arc.nasa.gov>
Cc: linux-mtd@lists.infradead.org
Cc: Ilguiz Latypov <ilatypov@infradead.org>
Subject: Re: DoC + GRUB booting problem
Date: 11 Apr 2003 18:30:34 -0700 [thread overview]
Message-ID: <1050111033.4189.1.camel@russ.local> (raw)
In-Reply-To: <5.1.1.5.2.20030411130135.018a6698@mail.arc.nasa.gov>
> The bootloader is definitely the M-Sys BIOS extension. My
> impression is that for DoC 2000s, the BIOS extension is in a ROM that can't
> be changed. I am still trying to verify that, but if its true, I have to
> deal with it. If it can be changed, like in a DoC Millenium, I could be in
> business.
its not a ROM, its the first page of the DOC. Grub changes it over to
looking like a network boot rom (as apposed to looking like a hard disk)
> So far, I have only used DFORMAT as described in the GRUB/MTD Readme_doc
> file. I haven't tried using doc_loadbios yet, but if the BIOS extension
> code is in ROM, I will still have to change its checksums to get it to
> load. Since M-Sys hasn't told me (yet) what format DFORMAT expects from
> binary files, doc_loadbios may indeed be the best way to proceed.
I always use doc_loadbios, just don't forget to make sure there is
enough space before the NTFL
--
Russ Dill <Russ.Dill@asu.edu>
next prev parent reply other threads:[~2003-04-12 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 18:19 DoC + GRUB booting problem Edward A. Hildum
2003-04-11 7:50 ` Ilguiz Latypov
[not found] ` <Pine.LNX.4.44.0304110336470.3790-100000@CPE00e0292061fa-CM 014370001917.cpe.net.cable.roger>
2003-04-11 20:10 ` Edward A. Hildum
2003-04-12 1:30 ` Russ Dill [this message]
2003-04-14 9:33 ` David Woodhouse
2003-04-12 12:30 ` Henrik Nordstrom
2003-04-13 2:33 ` 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=1050111033.4189.1.camel@russ.local \
--to=russ.dill@asu.edu \
--cc=ehildum@mail.arc.nasa.gov \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.