From: David Woodhouse <dwmw2@infradead.org>
To: Ilguiz Latypov <ilatypov@superbt.com>
Cc: Linux MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: DOC2000 + GRUB/LILO booting problems
Date: Mon, 18 Mar 2002 15:57:49 +0000 [thread overview]
Message-ID: <23171.1016467069@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0203181034060.13911-100000@server.superbt.com>
ilatypov@superbt.com said:
> I agree it might be impossible for the kernel to mount a partition
> formatted within NFTL layer if NFTL data structures in the beginning
> of the flash chip are overwritten. But I don't know the exact details
> of the NFTL layer myself.
It would be impossible. The two erase blocks at the beginning of the NFTL
are required.
> The GRUB bootloader needs around 96K at minimum. NFTL layer can be
> set up after the bootloader only. It seems the start of the NFTL
> layer will be detected automatically by the kernel. In my
> understanding, the kernel will simply search for a signature in every
> erase unit of the chip to find the beginning of NFTL layer.
Correct. The best way to do this is to use the DOS dformat program to
reserve that 96KiB, then put Grub in afterwards. We should probably work
out how to make the .EXB file format that DFORMAT uses, so we can actually
use DFORMAT to program Grub too.
--
dwmw2
next prev parent reply other threads:[~2002-03-18 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 15:34 DOC2000 + GRUB/LILO booting problems Ilguiz Latypov
2002-03-18 15:57 ` David Woodhouse [this message]
2002-03-18 16:17 ` Veselin Mijuskovic
[not found] ` <Pine.LNX.4.44.0203181430360.23362-100000@server.superbt.com>
2002-03-19 11:24 ` Veselin Mijuskovic
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 15:20 Veselin Mijuskovic
2002-03-14 16:06 ` Ilguiz Latypov
2002-03-18 13:48 ` Veselin Mijuskovic
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=23171.1016467069@redhat.com \
--to=dwmw2@infradead.org \
--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