From: Jonas Holmberg <jonas.holmberg@axis.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: chip drivers
Date: 06 Feb 2002 14:49:42 +0100 [thread overview]
Message-ID: <1013003382.14724.2.camel@pcjonashg> (raw)
In-Reply-To: <8523.1012575879@redhat.com>
> > 0x00000000 - 0x003FFFFF 4MiB CFI chip
> > 0x00400000 - 0x005FFFFF 2MiB jedec only chip
> > 0x00600000 - 0x009FFFFF 4MiB CFI chip
>
> You'd need three maps, three probe calls. Although I suppose you could have
> a single map driver for the first and last chips where the access calls do
> something like:
> return *(volatile __u32 *) (addr + (addr>0x400000?0x200000:0));
>
> You probably don't want that though. 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.
Can you explain that a bit further? I can't figure out how use
add_mtd_partitions (current CVS) when I want to make a partition that
starts in one map and ends in another. Since the map is an argument to
app_mtd_partitions I must make two calls to add_mtd_partitions, right?
But how do I make add_mtd_partitions merge the start of the device (in
the endo of the first map) with the end of the device (in the beginning
of the other map)?
/Jonas
next prev parent reply other threads:[~2002-02-06 13:38 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 ` chip drivers Jonas Holmberg
2002-02-05 16:48 ` Jonas Holmberg
2002-02-06 13:49 ` Jonas Holmberg [this message]
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=1013003382.14724.2.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox