From: Ralph Siemsen <ralphs@netwinder.org>
To: Thorsten Haas <haas@deutaeit.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CFI physmap - how to create partitions
Date: Wed, 18 May 2005 18:35:59 -0400 [thread overview]
Message-ID: <428BC34F.7000904@netwinder.org> (raw)
In-Reply-To: <1116403535.2682.7.camel@shrek>
Thorsten Haas wrote:
> I have a board equipped with CFI-compatible NOR-flash, which is
> physmapped and detected by the kernel (/dev/mtd0 in /proc/mtd). Now I am
> trying to configure partitions. I read the HOWTO on
> ftp://ftp.uk.linux.org/pub/people/dwmw2/mtd/cvs/mtd/mtd-jffs-HOWTO.txt,
> googled and browsed kernel code (2.6.8.11) and a daily mtd-snapshot
> (2005-05-15). From what i read, I understand:
> a) Command line partition table parsing is not functional with
> physmapped devices
> b) I need to create and fill a 'struct mtd_partition' and call
Hmm, I have used both methods successfully, albeit not with NOR flash...
though I can't see how it would make any difference for partitioning.
I'm using the MTD code "as is" in kernel 2.6.11.3 from kernel.org.
One minor bug with automatic buswidth probing, easily solved though.
> I've seen people writing board-dependent mapping drivers, thus
> clobbering the section "mapping driver for chip access". Is this
> actually the way to go? Well, I am not too lazy to write some code, but
> is there a more genric way?
Unless you have special requirements, such as paging or special unlock
sequences, or multiple (different) kinds of flash chips, you probably do
not need your own mapping driver. Physmap should do fine I'd think.
-R
next prev parent reply other threads:[~2005-05-18 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 8:05 CFI physmap - how to create partitions Thorsten Haas
2005-05-18 22:35 ` Ralph Siemsen [this message]
2005-05-19 8:06 ` Thorsten Haas
2005-05-19 11:54 ` Ralph Siemsen
2005-05-20 7:26 ` Thorsten Haas
2005-05-20 12:58 ` Ralph Siemsen
2005-05-20 13:20 ` Thorsten Haas
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=428BC34F.7000904@netwinder.org \
--to=ralphs@netwinder.org \
--cc=haas@deutaeit.de \
--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