All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Linux-MTD <linux-mtd@lists.infradead.org>
Subject: Latest Grub CVS results in UnitSizeFactor problems
Date: Tue, 13 Aug 2002 01:06:34 -0400	[thread overview]
Message-ID: <3D5893DA.F0BE2B16@opersys.com> (raw)

I've been playing around with the latest Grub code from CVS
on a 32MB DOC 2000. There was no way to get the NFTL code in
MTD to recognize the DOC once the firmware image was written
using: doc_loadbios /dev/mtd0 grub_firmware
I always got the following message when loading the nftl module:
Sorry, we don't support UnitSizeFactor 0x6e

When using Grub 0.92, however, everything works fine (except
that I had to steal the configure.in, stage1/Makefile.am and
stage2/Makefile.am from the CVS to get 0.92 to build because
I have the latest automake/autoconf versions).

I tried digging around the Grub source code to see where the
problem originates from so that I could fix it, but I don't
have the time to become a grub-internals guru. I can see that
the "ANAND" character string has something to do with the
position where the media header is being looked for, but the
only place I can find this string is in a C call to strcmp().
Beats me how this can be used as a marker.

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

                 reply	other threads:[~2002-08-13  5:03 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=3D5893DA.F0BE2B16@opersys.com \
    --to=karim@opersys.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 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.