public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nick Maximov <maxs@techno.spb.ru>
To: MTD Mailing List <mtd@infradead.org>
Subject: GRUB bootloader as firmware
Date: Mon, 26 Jun 2000 10:54:42 +0400	[thread overview]
Message-ID: <3956FE32.B38F1EF8@techno.spb.ru> (raw)

Now I got success with CVS archive
version of MTD. I used kernel 2.2.16 on Ampro CM/p5e+M-Systems Doc2000
(8Mb)
with latest code from CVS.

Kernel was successfully compiled, and my DiskOnChip
was detected after module installation (in order: mtdcore, doc2000,
docprobe, nftl).
I can read and write Linux native partition on my DOC using /dev/nftla1,

BUT! When I create Linux FS (type 83) by fdisk /dev/nftla
command, I LOSE compability with original DOC firmware (doc123.exb),
and system did not boot from flash.

I saw here some discussion about grub loader structurized as firmware
code.
I have 2 utilities from Ampro (the original M-Systems pupdate.exe and
pformat.exe
are incompatible with Ampro CM/p5e)

Documentation said that I have 3 areas in flash - CPU BIOS, Flash
firmaware
and BIOS extention. 

** Which area I have to update with grub firmware? I tried to update 
BIOS extention area with grub_firmware but system does not boot.
Doc firmware area is not large enough to fit compiles firmware...

Can I create DOC boot disk with grub using /dev/nftla? 
Or NFTL-MTD is not compatible with DOC firmware? (I use doc123.exb to
load
original firmware and doc2.fff to boot from HDD).


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

                 reply	other threads:[~2000-06-26  6:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3956FE32.B38F1EF8@techno.spb.ru \
    --to=maxs@techno.spb.ru \
    --cc=mtd@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