public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Ricky Beam <jfbeam@bluetopia.net>
Cc: Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: MTD and Adapter ROMs
Date: Fri, 07 Sep 2001 16:43:36 +0100	[thread overview]
Message-ID: <4569.999877416@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0109071132370.1190-100000@sweetums.bluetronic.net>
In-Reply-To: <Pine.GSO.4.33.0109071132370.1190-100000@sweetums.bluetronic.net>


jfbeam@bluetopia.net said:
>  Well, you explain where the f*** module "cfi" is located.  It took me
> a few hours to figure out what module is, in fact, "cfi". 

Heh, sorry about that. It's been fixed in my tree for a while - I should 
send Linus an update.

>  The question becomes, what section of the rom should not be erased?
> If I erase the entire 128k and then reset the system before getting a
> good image back in there, I'm betting it'll disappear from the bus.
> It's already screwed up to the point it no longer shows up in PCI
> space as itself -- which was entertaining to see the bad BIOS post and
> then not find itself :-)

Can't answer that. Try applying BIOS upgrades and downgrades, and seeing 
which ranges of the chip actually change?

> 00:03.0 Class ff80: 11ff:00ff (rev 03)
>  (that's supposed to be 1103:0004)

Looks like it's a pair of 8-bit flash devices side-by-side on a 16-bit bus, 
and you've managed to erase just one of them.


--
dwmw2



      reply	other threads:[~2001-09-07 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07  3:19 MTD and Adapter ROMs Ricky Beam
2001-09-07 10:13 ` David Woodhouse
2001-09-07 14:04   ` Ricky Beam
2001-09-07 14:14     ` David Woodhouse
2001-09-07 15:37       ` Ricky Beam
2001-09-07 15:43         ` David Woodhouse [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=4569.999877416@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jfbeam@bluetopia.net \
    --cc=linux-kernel@vger.kernel.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