public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Munira Ahmed <munira.ahmed@radixs.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: map and chip drivers
Date: Fri, 20 May 2005 10:35:04 +0100	[thread overview]
Message-ID: <1116581705.5777.43.camel@icampbell-debian> (raw)
In-Reply-To: <1116580638.18096.133.camel@server11>

On Fri, 2005-05-20 at 17:17 +0800, Munira Ahmed wrote:
> > Breaking things down a little more, in the mtd stack there are 3 kinds of drivers.
> > map drivers that describe how to talk to a given flash chip.
> > probe drivers that identify what kind of chip you have.
> > chip drivers that know how to speak a command set and let you flash your chip.
> 
> 
> I really don't understand the difference between the map and the chip
> driver? 
> 
> talk to a given flash !
> speak a command set!
> 
> ain't they the same?

The map driver takes care of physically accessing the flash, while the
chip driver knows what to do with each type of flash. So the map driver
provides the method for the chip driver to actually access the flash.

For example we have boards at work which have flash chips mapped at
various physical addresses (differing between boards), some devices have
paged flash, with an i/o register to select the page and a physical
address where the current page is mapped. I'm sure there are other ways
of arranging things.

The board-specific map drivers takes care of all these differences,
while the chip driver is shared between multiple boards because the
underlying chips are the same in each case.

Ian.
-- 
Ian Campbell
Current Noise: Slayer - Fictional Reality

BOFH excuse #13:

we're waiting for [the phone company] to fix that line

  reply	other threads:[~2005-05-20 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20  9:17 map and chip drivers Munira Ahmed
2005-05-20  9:35 ` Ian Campbell [this message]
2005-05-20  9:50   ` Munira Ahmed

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=1116581705.5777.43.camel@icampbell-debian \
    --to=ijc@hellion.org.uk \
    --cc=linux-mtd@lists.infradead.org \
    --cc=munira.ahmed@radixs.com \
    /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