From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Justin Clacherty <justin@redfish-group.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Intel P30, locked sectors?
Date: Wed, 06 Sep 2006 16:19:00 +0200 [thread overview]
Message-ID: <44FED8D4.6080505@kernelconcepts.de> (raw)
In-Reply-To: <44FED831.60704@redfish-group.com>
Justin Clacherty schrieb:
> Nils Faerber wrote:
>> I had hoped that the P30 chips would be supported now, but it seems they
>> are not fully. How can I unlock the sectors, if that is really the issue
>> here.
> P30 flash is supported in that it supports CFI. You can read and write
> to it as long as it's unlocked. CFI does not support automatic
> unlocking, it assumes if it's locked, it's locked for a reason. The
> bootloader has to ensure that the sectors occupied by the rootfs are
> unlocked before mounting the filesystem. We're using P30 here without
> problems.
Hmm... OK.
Just in theory, can one write to a locked sector?
I ask because I flashed the very same rootfs to the chip using the
bootloader. The bootloader, which is BLOB BTW, seems to be able to write
to the chips and the contents written also seems to be OK (since I can
boot and mount the rootfs).
> Justin.
Cheers
nils faerber
--
kernel concepts GbR Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
next prev parent reply other threads:[~2006-09-06 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 13:50 Intel P30, locked sectors? Nils Faerber
2006-09-06 14:16 ` Justin Clacherty
2006-09-06 14:19 ` Nils Faerber [this message]
2006-09-06 15:12 ` Justin Clacherty
2006-09-06 14:25 ` Nicolas Pitre
2006-09-06 14:30 ` Nils Faerber
2006-09-06 15:17 ` Justin Clacherty
2006-09-06 15:24 ` Nicolas Pitre
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=44FED8D4.6080505@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=justin@redfish-group.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