public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "stiger" <bhe@jadechip.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: flash unlock on VPB
Date: Sat, 05 Feb 2005 03:14:26 -0000	[thread overview]
Message-ID: <004901c3eb96$aff0ee10$33050a0a@jadechip.net> (raw)
In-Reply-To: Pine.LNX.4.61.0502042136340.25997@localhost.localdomain

thx.

Is there any code to real call unlock?

i see many map drivers only set
.mask_flags   =  MTD_WRITEABLE
and then call add_mtd_partitions()
but i didn't see any real unlock in map drivers.

so, how can they do when they want to use writeable root filesystem in flash ?


----- Original Message ----- 
From: "Nicolas Pitre" <nico@cam.org>
To: "stiger" <bhe@jadechip.com>
Cc: <linux-mtd@lists.infradead.org>
Sent: Saturday, February 05, 2005 10:39 AM
Subject: Re: flash unlock on VPB


> On Thu, 5 Feb 2004, stiger wrote:
> 
> > hello,
> > 
> > i'm using VPB + kernel 2.6.9
> > but i found the flash cannot write, it should be unlocked first.
> > 
> > if not use root filesystem in flash, I can use flash_unlock to unlock the
> > flash.
> > but if burn root filesystem into flash, i have to change the kernel code.
> > 
> > i add these code at driver/mtd/mtdpart.c->add_mtd_partitions()
> > 
> >         if((slave->mtd.flags & MTD_WRITEABLE) && slave->mtd.unlock ){
> >             slave->mtd.unlock(&(slave->mtd), 0, slave->mtd.size );
> >         }
> > 
> > now, it works.
> > but i think it's a stupid way to do this.
> > is there any other way to do this ?
> 
> The unlock is usually called from the map driver in that case.
> 
> 
> Nicolas

      reply	other threads:[~2005-02-05  3:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05  2:20 flash unlock on VPB stiger
2005-02-05  2:39 ` Nicolas Pitre
2005-02-05  3:14   ` stiger [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='004901c3eb96$aff0ee10$33050a0a@jadechip.net' \
    --to=bhe@jadechip.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nico@cam.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