public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Joe Robertson <jmrobert5@mchsi.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Need a working gub_firmware.
Date: Fri, 19 May 2006 20:48:49 -0500	[thread overview]
Message-ID: <446E7581.2040501@mchsi.com> (raw)
In-Reply-To: <1148071495.2566.3.camel@shinybook.infradead.org>

Well, DINFO 5.1.4 reports them as NFTL.

However I notice that DINFO 5.1.4 reports the TrueFFS as 5.1.4, BUT 
using DINFO 5.1.2 on THE SAME CHIP reports TrueFFS as 5.1.2!?
So the diagnostic tool may be wrong. Could be part of my problem.

I am going to go thru the grub-0.92 patch thouroghly sometime this 
weekend.  If anyone has any specs or docs they can share with me on the 
2202(or 2200) series (Msys 5.1.x tools), I would appreciate it.  I've 
got to understand my build chain and find out what works.  I know lots 
of stuff that doesn't work.

I need Grub because we use the serial/console choice, boot menus and a 
few other features.  This all worked once upon a time, but we've updated 
compilers and tools and other parts.  Grub 0.92 won't even compile under 
gcc 3.3.x.  I need to fix all this.

Also what is the difference between the code in patches/ for grub-0.92 
and the code in the grub/ folder???

Thanks, and have good weekend.

Joe
jmrobert5[at]mchsi.com


David Woodhouse wrote:
> On Fri, 2006-05-19 at 16:05 +0000, jmrobert5@mchsi.com wrote:
> 
>>Shouldn't a MSys 5.1.4 tools work with 2202 chips?  Which one writes the NFTL
>>Header?  It seems like my grub_firmware can't read the header. 
> 
> 
> Are the 2202 chips not the new ones which use INFTL?
> 

      reply	other threads:[~2006-05-20  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 16:05 Need a working gub_firmware jmrobert5
2006-05-19 20:44 ` David Woodhouse
2006-05-20  1:48   ` Joe Robertson [this message]

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=446E7581.2040501@mchsi.com \
    --to=jmrobert5@mchsi.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