public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: ian.nelson@echostar.com
Cc: "mtd@infradead.org" <mtd@infradead.org>
Subject: Re: A pair of stupid questions, I hope
Date: Tue, 17 Apr 2001 23:11:57 +0100	[thread overview]
Message-ID: <10503.987545517@redhat.com> (raw)
In-Reply-To: <3ADC7273.DB541A9C@echostar.com>


ian.nelson@echostar.com said:
> My manufacturing people want a test that responds yes or no to the
> question "is this sector locked?"

> This seems like it should be pretty easy, but where and how do I
> determine that? Is it something that is stored in the mem_region?
> There are lock and unlock ioctls but it's not obvious to me how to
> query if a sector is locked? What is the proper way to do this? 

Yeah, we should support that, but we currently don't have an API for it, and
obviously that means there's no code to do it for any of the currently
supported chipsets. Fairly trivial to do though. I'm not feeling inventive 
tonight. Propose an API extension and if it offends my sensibilities I'll 
have to think of something myself.


ian.nelson@echostar.com said:
>  It's looking more and more like we're going to move from 2MB to a 4MB
> flash.  Supposedly the 4MB is banked and it's some Toshiba part that
> isn't listed in the code as supported yet.  Do we already support
> anything like that?  It looks easy enough to add support for a new
> part and I'm eager to give it a try but I don't know about this
> convoluted banking thing.  Any advice?

If it's a NOR part it ought to be fairly trivial. If it's NAND, supporting
the part itself shouldn't be too hard, but JFFS2 doesn't work safely on it
yet. JFFS should, although I haven't tried it myself. And obviously you 
can't boot from NAND flash unless you have an external ROM or NOR flash 
somewhere for the CPU power-up vector.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-04-17 22:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 16:42 A pair of stupid questions, I hope Ian S. Nelson
2001-04-17 22:11 ` David Woodhouse [this message]
2001-04-18  0:04   ` Ian S. Nelson
2001-04-18  8:02     ` David Woodhouse
2001-04-18 16:41       ` JFFS2 as root FS Joakim Tjernlund
2001-04-18 16:50         ` David Woodhouse
2001-04-18 17:00           ` Joakim Tjernlund
2001-04-18 17:05             ` David Woodhouse
2001-04-18 18:58               ` Joakim Tjernlund
2001-04-18 17:11         ` Vipin Malik
2001-04-18 19:24           ` Joakim Tjernlund
2001-04-18 20:19             ` Vipin Malik
2001-04-18 22:00               ` Joakim Tjernlund
2001-04-19  8:28                 ` Florian Schirmer / TayTron
2001-04-19 10:26               ` Joakim Tjernlund
2001-04-19 13:02                 ` Florian Schirmer / TayTron
2001-04-19 12:45                   ` Joakim Tjernlund
2001-04-19 13:02                     ` David Woodhouse
2001-04-19 14:55                       ` Nicolas Pitre
2001-04-19 16:44                 ` Vipin Malik
2001-04-19 19:59                   ` Joakim Tjernlund

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=10503.987545517@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ian.nelson@echostar.com \
    --cc=mtd@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