From: "Thomas Gleixner" <tglx@linutronix.de>
To: Jun Sun <jsun@mvista.com>, Marc Singer <elf@buici.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] MTD Maps driver for Sharp LH7a40x
Date: Sat, 19 Jun 2004 02:16:29 +0200 [thread overview]
Message-ID: <200406190216.29671.tglx@linutronix.de> (raw)
In-Reply-To: <20040618170514.A6101@mvista.com>
Jun,
On Saturday 19 June 2004 02:05, Jun Sun wrote:
>
> How about just using physmap mapping driver and keep all your
> board specific stuff to your board directory? See
> include/linux/mtd/physmap.h for more details.
Thanks for jumping in. That's what I was trying to point out.
In fact most of the board drivers in drivers/mtd/maps could / should go away.
The reason to have one is crappy hardware, unusual chip constellations or
other anomalities.
The common case can just be solved by using the physmap driver and the command
line partition parser. Maybe we should think about an extension to physmap so
the board support code can supply an appropriate partitioning scheme along
with the chip description.
I was thinking about simliar support for the NAND driver too, but there it
turns out that the anomalities are given per design, although it should not
be an unsolvable problem.
--
Thomas
_____________________________________________________________________
From slash dot org
"When customers are visiting, engineers are not allowed to wear ties.
That way the customer can tell who is the engineer and who is the
salesman (and therefore whom to believe.). Ties cut off blood flow
to the brain, making it easier for the salesmen to do their jobs."
_____________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2004-06-19 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 21:43 [PATCH] MTD Maps driver for Sharp LH7a40x Marc Singer
2004-06-14 0:07 ` Thomas Gleixner
2004-06-14 0:54 ` Marc Singer
2004-06-19 0:05 ` Jun Sun
2004-06-19 0:16 ` Thomas Gleixner [this message]
2004-06-19 0:38 ` Marc Singer
2004-06-19 8:19 ` Thomas Gleixner
2004-06-19 9:23 ` Russell King - ARM Linux
2004-06-19 9:51 ` Thomas Gleixner
2004-06-19 11:01 ` Russell King - ARM Linux
[not found] <083AB380E3924D4795740AAE9A27DCAB7B89B3@cgy2000.interalia.ca>
2004-06-19 17:03 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-06-12 16:47 Marc Singer
2004-06-13 19:34 ` Thomas Gleixner
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=200406190216.29671.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=elf@buici.com \
--cc=jsun@mvista.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