From: Jonas Larsson <jonas.larsson@netinsight.net>
To: linux-mtd@lists.infradead.org
Subject: Cmdline partitions
Date: 11 Aug 2003 09:31:59 +0200 [thread overview]
Message-ID: <1060587118.28472.66.camel@doris> (raw)
Hi all. I've had some trouble creating my mtd partitions
with the 2.6.0-test2 kernel and I need some advice. I have
my own mapping driver for our board (not submitted yet) which
is based on the dc21285 map driver.
In the 2.5.70-rmk1 kernel I call parse_cmdline_partitions with
mtd_id="mymapdriver", and specify mtdparts=mymapdriver:<partitions>
to the kernel. In 2.6.0-test2-rmk1 I have to call parse_mtd_partitions
to parse the cmdline. However I cannot specify my mtd_id from the map
driver (except setting the .name member of my map_info struct) as I
could with 2.5.70. This makes the line
if ((!mtd_id) || (!strcmp(part->mtd_id, mtd_id)))
in cmdlinepart.c:parse_cmdline_partitions() to fail.
The edb7312 map driver calls parse_mtd_partitions like this:
mtd_parts_nb = parse_mtd_partitions(mymtd, probes, &mtd_parts,
"edb7312-nor");
But the 4th arg (origin) is a unsigned long and as I can see
is not used by the implementation of the function. Is this
really the way it is supposed to be?
Comments?
/ Jonas
reply other threads:[~2003-08-11 7:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1060587118.28472.66.camel@doris \
--to=jonas.larsson@netinsight.net \
--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