public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Q: Probing for devices > buswidth???
Date: 09 Oct 2001 01:04:17 -0600	[thread overview]
Message-ID: <m3wv25fg5q.fsf@DLT.linuxnetworx.com> (raw)
In-Reply-To: <30115.1002610420@redhat.com>

David Woodhouse <dwmw2@infradead.org> writes:

> ebiederman@lnxi.com said:
> >  Just so I understand.  There are chips with a 16-bit interface that
> > you can put in a crippled mode such that they pretend use only an 8
> > bit bus.  But the id logic is the same as when the are on a 16-bit
> > bus?
> 
> Basically, yes. They are 16-bit devices, with the A0 line selecting which 
> 16-bit word you should look at - and all the 'magic' addresses must be 
> placed on the address bus starting at A0. But they decided they wanted to 
> be able to use them with an 8-bit bus, so they added an 'A-1' address line 
> too.
> 
> > I'm just trying to comprehend this weird situation.
> 
> Do yourself a favour - don't. Just accept it. Or do me a favour and take 
> responsibility for it from now on :)

I'll probably take responsiblity for the legacy jedec side of things.
Or at the very least I'll be a very active tester/user.  So I want
enough understanding so that I don't look at someone else's code and
say that is broken, and be wrong.  I have fixed a whole bunch of small
bugs already.  Currently I have 4 map drivers completed and a 5th one
to write, and none of them use these nice new chips.  The worst case
is the driver for the boot rom on the eepro100 it doesn't even
implement block erase, just chip erase.  

Anyway my smorgase board currently looks like:
eepro100 boot rom.
BIOS on AMD766 southbrige.
BIOS on the l440gx motherboard.
BIOS on Compaq DS10
BIOS connected to the ICH2 (Intel firmware hub.) 
   [This one I should be getting started on in a couple of hours].

Eric

  reply	other threads:[~2001-10-09  6:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09  5:23 Q: Probing for devices > buswidth??? Eric W. Biederman
2001-10-09  6:45 ` David Woodhouse
2001-10-09  6:50   ` Eric W. Biederman
2001-10-09  6:53     ` David Woodhouse
2001-10-09  7:04       ` Eric W. Biederman [this message]
2001-10-09 13:19     ` Kenneth Johansson
2001-10-09 13:22       ` David Woodhouse
2001-10-09 13:56         ` Kenneth Johansson

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=m3wv25fg5q.fsf@DLT.linuxnetworx.com \
    --to=ebiederman@lnxi.com \
    --cc=dwmw2@infradead.org \
    --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