From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Frank Neuber <neuber@convergence.de>, linux-mtd@lists.infradead.org
Subject: Re: parse_cmdline_partitions equivalent for map_info
Date: Sat, 19 Oct 2002 18:44:45 +0200 [thread overview]
Message-ID: <20021019164445.GA9364@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <26791.1034943288@passion.cambridge.redhat.com>
On Fri, 18 October 2002 13:14:48 +0100, David Woodhouse wrote:
> neuber@convergence.de said:
> > Now I'm looking for the same feature to pass the physically
> > informations to the kernel (struct map_info). I could add this simply
> > to the cmdline.c file based on the parse_cmdline_partitions function.
>
> That seems like a relatively sensible addition to physmap.c. You could make
> it take the probe type that way too...
>
> 'physmap=0xe0000000,0x100000,16,cfi'
Hmm, somewhere in my collection of yet-to-be-committed patches, I have
a variant of the physmap driver that does exactly this and is capable
of mapping up to eight independent devices. Interested?
Jörn
--
Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface.
-- Doug MacIlroy
next prev parent reply other threads:[~2002-10-19 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 10:49 parse_cmdline_partitions equivalent for map_info Frank Neuber
2002-10-18 12:14 ` David Woodhouse
2002-10-19 16:44 ` Jörn Engel [this message]
2002-10-22 10:39 ` Frank Neuber
2002-10-22 17:29 ` Jörn Engel
2002-10-23 13:25 ` Robert Kaiser
2002-10-23 13:33 ` Jörn Engel
[not found] ` <20021022170803.GA9161@wohnheim.fh-wedel.de>
2002-10-23 9:49 ` Frank Neuber
2002-10-23 10:06 ` Jörn Engel
2002-10-23 10:27 ` Frank Neuber
2002-10-23 12:07 ` Jörn Engel
2002-10-23 14:01 ` Robert Kaiser
2002-10-23 14:35 ` Jörn Engel
2002-10-23 16:22 ` Robert Kaiser
2002-10-27 18:00 ` Jörn Engel
2002-10-28 10:56 ` Robert Kaiser
2002-10-28 15:30 ` Jörn Engel
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=20021019164445.GA9364@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=neuber@convergence.de \
/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