From: Jonas Holmberg <jonas.holmberg@axis.com>
To: jmzhong@dtvia-usoft.com
Cc: jffs-dev@axis.com, linux-mtd@lists.infradead.org
Subject: Re: How to understand :interleave,numeraseregions and regions
Date: 24 Jan 2002 09:57:34 +0100 [thread overview]
Message-ID: <1011862654.27784.0.camel@pcjonashg> (raw)
In-Reply-To: <200201240304.g0O349RM018586@krynn.axis.se>
On Thu, 2002-01-24 at 11:00, jmzhong@dtvia-usoft.com wrote:
> Hi,all,
> Could you tell me where the notation about drivers/mtd/chips/amd_flash.c in the
> source code of uClinux is?
> I want to know about struct amd_flash_private {
> int device_type;
> int interleave;
> int numchips;
> unsigned long chipshift;
> // const char *im_name;
> struct flchip chips[0];
> };
>
> struct amd_flash_info {
> const __u16 mfr_id;
> const __u16 dev_id;
> const char *name;
> const u_long size;
> const int numeraseregions;
> const struct mtd_erase_region_info regions[4];
> };
> How to understand :interleave,numeraseregions and regions?
numeraseregions is the number of elements in the regions array. A region
is an area of the chip that contains sectors of the same size (usually
there are a few regions in the boot block and one region for the other
sectors). interleave is the number of chips that are mounted in parallel
on the bus. The amd_flash driver only supports 16-bit devices with a
buswidth of 16 or 32 bits (interleave 1 or 2).
I would like to ask the MTD people why it's necessary to have a variable
for device_type? Isn't it always possible to calculate the device_type
(buswidth / interleave)?
Best regards
/Jonas
next parent reply other threads:[~2002-01-24 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201240304.g0O349RM018586@krynn.axis.se>
2002-01-24 8:57 ` Jonas Holmberg [this message]
2002-01-24 9:13 ` How to understand :interleave,numeraseregions and regions David Woodhouse
2002-01-24 18:49 Jonas Holmberg
2002-01-24 21:22 ` David Woodhouse
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=1011862654.27784.0.camel@pcjonashg \
--to=jonas.holmberg@axis.com \
--cc=jffs-dev@axis.com \
--cc=jmzhong@dtvia-usoft.com \
--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