From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Use of several CFI flash chips physically mapped in memory
Date: Thu, 4 Dec 2003 11:12:24 +0100 [thread overview]
Message-ID: <000001c3ba4f$214be2f0$5201a8c0@GEG2400> (raw)
In-Reply-To: <20031203181613.75859C5F5F@atlas.denx.de>
Hi,
I work on a custom 8250 board with a 2.4.18 Linux kernel.
This board provides two AMD CFI flash devices.
Nowaday I only use the first chip which I map in the physical memory.
I create several partitions with RW or RO accesses and I use
CRAMFS and/or JFFS2 images. This works fine.
Now I would want to use the following functionalities :
1) I want to protect the first partition of the first device
that contains a firmware which does not belong to the Linux system.
Can I mislead Linux and provide the first sector address after
the firware as the start address of the device. I don't know
how the gen_probe process will react. So as Linux does not know
the firware space and it can't erase the firmware sectors.
2) I want to use the two devices as a virtual one with many
partitions splitted at will. The two chips are physically mapped in
sequence. In my kernel, I have the following variables
CONFIG_ELINOS_NR_MTD_DEVICES "Maximum number of MTD devices" and
CONFIG_MTD_CONCAT MTD "Concatenating support". But they seem to be unused.
3) I want to use two 16 bits access chips physically mounted in parallel
to make a virtual 32 bits access chip. Do solutions exist for this case ?
4) Finally, what about flash fast programming issues ?
Nowaday it is very slow to erase or program many sectors with
the character access driver.
In my kernel, I have the following message
if (cfi->fast_prog) {
/* In cfi_amdstd_write() we frob the protection stuff
without paying any attention to the state machine.
This upsets in-progress erases. So we turn this flag
off for now till the code gets fixed. */
printk(KERN_NOTICE "cfi_cmdset_0002: Disabling fast programming due to c
ode brokenness.\n");
cfi->fast_prog = 0;
}
Thanks
Special thanks to Gary Thomas for his reply about File system boot strategy.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-04 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 17:48 ram root filesystem AlessandroPPC
2003-12-03 18:16 ` Wolfgang Denk
2003-12-04 10:12 ` Gérard Guével [this message]
2003-12-05 8:36 ` R: " AlessandroPPC
2003-12-04 0:08 ` problem using both mpc857dsl fec and scc1 Dennis Khoo
2003-12-05 11:11 ` Jaap-Jan Boor
2003-12-05 18:53 ` Dennis Khoo
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='000001c3ba4f$214be2f0$5201a8c0@GEG2400' \
--to=gguevel@interfaceconcept.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).