From: "Anand Patil" <anandpatil@ti.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: region_info_user and otp_info
Date: Tue, 7 Nov 2006 20:19:50 +0530 [thread overview]
Message-ID: <01bf01c7027b$fc0334d0$5ef5180a@ent.ti.com> (raw)
In-Reply-To: 1162899909.19697.13.camel@crusty.rchland.ibm.com
Josh,
I got a AMD NOR Flash AM29LV256M,
It supports a feature called as Secured Silicon Sector (i.e. a
256 byte region which can be programmed only once)
To access the above feature a particular command sequence has to
be issued
How can I know whether the above feature is already
incorporated in the MTD release OR
else we need to support it at the driver layer?
Warm Regards,
Anand Patil
----- Original Message -----
From: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
To: "Anand Patil" <anandpatil@ti.com>
Cc: <linux-mtd@lists.infradead.org>
Sent: Tuesday, November 07, 2006 5:15 PM
Subject: Re: region_info_user and otp_info
> On Tue, 2006-11-07 at 09:20 +0530, Anand Patil wrote:
>> Hi,
>> I am new bee to MTD user land,
>>
>> 1) Iam not getting what region information refers to in MTD?
>
> Some chips have multiple erase regions. These regions can have
> eraseblocks of different size than the rest of the chip. That is what
> the structure is reporting.
>
>
>> 2) I did'nt get the purpose of the below strucuture defined and its
>> usage ?
>
> OTP stands for One Time Programmable. Some chips have an area that is
> only writable once. It can be used to store serial numbers, or whatever
> you'd like to store as long as you only need to write that information a
> single time. That is what this structure is referring to.
>
> josh
>
>
prev parent reply other threads:[~2006-11-07 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 3:50 region_info_user and otp_info Anand Patil
2006-11-07 11:45 ` Josh Boyer
2006-11-07 14:49 ` Anand Patil [this message]
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='01bf01c7027b$fc0334d0$5ef5180a@ent.ti.com' \
--to=anandpatil@ti.com \
--cc=jwboyer@linux.vnet.ibm.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