public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: samuel@Update.UU.SE (Samuel ]slund)
To: Katey Yu <katey.Yu@ositech.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: write-protected
Date: Tue, 15 Aug 2006 17:36:49 +0200	[thread overview]
Message-ID: <20060815153649.GF3622@Update.UU.SE> (raw)
In-Reply-To: <007020085773234AAACE3B66E13C18E8D71CB3@MAILSRVR.ositech.com>

On Mon, Aug 14, 2006 at 04:44:01PM -0400, Katey Yu wrote:
> Hello,
> 
> When I mount /dev/mtdblock3 in flash I get  block " block device
> /dev/mtdblock3 is write-protected, mounting read-only". I should get
> mtdblock_open?
> 
> Could somebody tell me what's wrong?
> 
>  
> 
>  
> 
> mount -t jffs2  /dev/mtdblock3 /var/tmp
> 
> mount: block device /dev/mtdblock3 is write-protected, mounting
> read-only

You do not give very much information about your system...
Ok, assuming you have set up the block device correctly.

I had a similar problem that boiled down to that the driver
from the manufacturer hardcoded the partition to be read-only.

in my case the apropriate file was:
linux/arch/arm/mach-ks8695/ks8695_mm.c

The partition had been set read-only by adding:
  .mask_flags = MTD_WRITABLE

to the partition struct.

HTH
//Samuel

  reply	other threads:[~2006-08-15 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 20:44 write-protected Katey Yu
2006-08-15 15:36 ` Samuel ]slund [this message]
     [not found] <007020085773234AAACE3B66E13C18E8D71D08@MAILSRVR.ositech.com>
2006-08-15 21:34 ` write-protected Samuel ]slund

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=20060815153649.GF3622@Update.UU.SE \
    --to=samuel@update.uu.se \
    --cc=katey.Yu@ositech.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