From: Jonas Holmberg <jonas.holmberg@axis.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: chip drivers
Date: 04 Feb 2002 16:47:50 +0100 [thread overview]
Message-ID: <1012837670.4248.5.camel@pcjonashg> (raw)
In-Reply-To: <8523.1012575879@redhat.com>
> Register them as three separate chips
> and then use the partition code that's been fixed to let you combine ranges
> of separate devices into one 'partition' rather than just split devices up.
I haven't got past the probing part yet. I'm trying to use cfi_probe and
jedec_probe to find all chips in a really big window. So when the
cfi_probe or the jedec_probe has found something I make a copy of the
map it used and increase map_priv_1 (used by the read and write
callbacks as in physmap.c) in the new map. The new map is then used for
the next probe.
The problem is that I cannot determine if a previous probe found any
alias or not. I must not probe where an alias has been found by a
previous probe since the next probe will think it is a new chip and not
recognize it as an alias (sinze it will think that it found the chip at
location zero). And I must continue probing until the end of the window.
Do I have to change the interface of the probe functions (I need the
address of the last found alias without "manually" looking for aliases
like the probe functions do)?
/Jonas
next prev parent reply other threads:[~2002-02-04 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 11:06 chip drivers Jonas Holmberg
2002-02-01 13:34 ` David Woodhouse
2002-02-01 13:47 ` Jonas Holmberg
2002-02-01 13:49 ` David Woodhouse
2002-02-01 14:49 ` Jonas Holmberg
2002-02-01 15:04 ` David Woodhouse
2002-02-04 10:52 ` Patch for jedec_probe Jonas Holmberg
2002-02-05 3:06 ` David Woodhouse
2002-02-04 15:47 ` Jonas Holmberg [this message]
2002-02-05 16:48 ` chip drivers Jonas Holmberg
2002-02-06 13:49 ` Jonas Holmberg
2002-02-06 14:22 ` David Woodhouse
[not found] <Pine.LNX.4.44.0202070041040.1927-100000@lapdancer.baythorne.internal>
2002-02-07 12:20 ` Jonas Holmberg
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=1012837670.4248.5.camel@pcjonashg \
--to=jonas.holmberg@axis.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 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.