From: Segher Boessenkool <segher@kernel.crashing.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org, Milton Miller <miltonm@bga.com>
Subject: Re: [PATCH] powerpc: Create "rom" (MTD) device prpmc2800
Date: Sun, 3 Jun 2007 21:48:15 +0200 [thread overview]
Message-ID: <bd28eac8eb60db8aaff74f91c76d4196@kernel.crashing.org> (raw)
In-Reply-To: <46630F8F.6080708@ru.mvista.com>
>>> No! It doesn't have anything to do with "ranges" of parent (don't
>>> even know why it would). :-O
>
>> So learn about it please? "ranges" means exactly that:
>> child nodes' address space is direct mapped.
>
> Well, now we certainly need a parent node -- which would be static
> bus controller?
I have no clue what a "static bus controller" is. Your
flash node obviously needs _some_ parent node though --
this is a tree after all.
> But those have multiple chips selects, so we should know which range
> to use. Ugh...
That is described in the "reg" property of the flash
node, just like for any other node.
>> Because that is a) not what you are supposed to do according
>> to the standard (so it might very well not work with a
>> "third-party" device tree that equally conforms to the standard);
>> b) "device_type" describes some other information (namely, the
>> OF programming model for the device node) that is completely
>> unrelated to the process of driver matching; and c) it is wholly
>> redundant to the information in "compatible" *ANYWAY*.
>
> Hm, well. Than changing "compatible" prop would make sense.
Yes.
>>> And why you haven't complained at MPC5200 IDE driver
>
>> Since no one paid me to review the code? Please don't try
>
> Sigh, nobody pays me for that too. :-)
Yeah it's a shame isn't it?
>>> which does the same (well, maybe you have :-) or at PowerMac IDE
>>> driver which matches wither by "name" or "device_type"? Well, quite
>>> a lot of drivers are doing this...
>
>> See before why that may be. Short answer is "history".
>
> Well, at least that's cleared.
Okido, good to hear.
>>> Anyway, reasonable suggestions on how to make MTD nodes more
>>> viable are always welcome. I just haven't seen reasonable enough
>>> yet. ;-)
>
>> I suggest you read, and try to understand, some of the base
>> device tree specifications first.
>
> Read them some months ago -- do you think I would have plunged into
> that not reading anything first? :-/
It seems we really need more howto-style docs...
Segher
next prev parent reply other threads:[~2007-06-03 19:48 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 4:30 [PATCH] powerpc: Create "rom" (MTD) device prpmc2800 Milton Miller
2007-06-02 7:39 ` Benjamin Herrenschmidt
2007-06-03 16:10 ` Sergei Shtylyov
2007-06-03 17:36 ` Segher Boessenkool
2007-06-03 18:03 ` Sergei Shtylyov
2007-06-03 18:25 ` Segher Boessenkool
2007-06-03 18:36 ` Sergei Shtylyov
2007-06-03 18:46 ` Segher Boessenkool
2007-06-03 19:16 ` Sergei Shtylyov
2007-06-03 21:04 ` Benjamin Herrenschmidt
2007-06-04 12:34 ` Sergei Shtylyov
2007-06-04 14:37 ` Segher Boessenkool
2007-06-04 14:49 ` Sergei Shtylyov
2007-06-07 14:53 ` David Woodhouse
2007-06-07 15:49 ` Segher Boessenkool
2007-06-07 14:47 ` David Woodhouse
2007-06-07 15:32 ` Segher Boessenkool
2007-06-02 8:53 ` Segher Boessenkool
2007-06-03 16:22 ` Sergei Shtylyov
2007-06-03 17:40 ` Segher Boessenkool
2007-06-03 18:31 ` Sergei Shtylyov
2007-06-03 18:44 ` Segher Boessenkool
2007-06-03 19:13 ` Sergei Shtylyov
2007-06-03 19:56 ` Segher Boessenkool
2007-06-03 20:26 ` Sergei Shtylyov
2007-06-04 8:07 ` Segher Boessenkool
2007-06-04 13:34 ` Sergei Shtylyov
2007-06-07 15:00 ` David Woodhouse
2007-06-07 15:55 ` Segher Boessenkool
2007-06-07 16:05 ` David Woodhouse
2007-06-07 16:46 ` Segher Boessenkool
2007-06-12 4:44 ` David Gibson
2007-06-12 10:53 ` Segher Boessenkool
2007-06-13 3:16 ` David Gibson
2007-06-13 5:05 ` Segher Boessenkool
2007-06-13 6:11 ` David Gibson
2007-06-13 9:10 ` Segher Boessenkool
2007-06-15 4:12 ` David Gibson
2007-06-15 11:22 ` Segher Boessenkool
2007-06-15 4:14 ` David Gibson
2007-06-15 8:42 ` Segher Boessenkool
2007-06-15 8:47 ` David Woodhouse
2007-06-15 8:59 ` Segher Boessenkool
2007-06-03 21:12 ` Benjamin Herrenschmidt
2007-06-04 8:11 ` Segher Boessenkool
2007-06-04 13:16 ` Sergei Shtylyov
2007-06-04 12:41 ` Sergei Shtylyov
2007-06-04 14:49 ` Segher Boessenkool
2007-06-04 15:54 ` Sergei Shtylyov
2007-06-03 17:29 ` Sergei Shtylyov
2007-06-03 17:45 ` Segher Boessenkool
2007-06-03 18:18 ` Sergei Shtylyov
2007-06-03 18:43 ` Segher Boessenkool
2007-06-03 18:59 ` Sergei Shtylyov
2007-06-03 19:48 ` Segher Boessenkool [this message]
2007-06-03 20:10 ` Sergei Shtylyov
2007-06-04 8:02 ` Segher Boessenkool
2007-06-04 19:40 ` Mark A. Greer
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 23:20 Mark A. Greer
2007-06-02 8:46 ` Segher Boessenkool
2007-06-04 20:56 ` Mark A. Greer
2007-06-05 20:35 ` Sergei Shtylyov
2007-06-05 21:11 ` Mark A. Greer
2007-06-06 12:41 ` Sergei Shtylyov
2007-06-07 15:08 ` David Woodhouse
2007-06-06 2:39 ` David Gibson
2007-06-07 13:30 ` Segher Boessenkool
2007-06-12 4:42 ` David Gibson
2007-06-12 10:50 ` Segher Boessenkool
2007-06-13 6:12 ` David Gibson
2007-06-13 9:13 ` Segher Boessenkool
2007-06-13 9:19 ` David Gibson
2007-06-13 9:37 ` Segher Boessenkool
2007-06-14 4:29 ` David Gibson
2007-06-14 8:00 ` Segher Boessenkool
2007-06-14 12:39 ` Sergei Shtylyov
2007-06-14 13:20 ` Segher Boessenkool
2007-06-14 12:48 ` Sergei Shtylyov
2007-06-14 13:18 ` Segher Boessenkool
2007-06-14 12:50 ` Sergei Shtylyov
2007-06-14 13:43 ` Segher Boessenkool
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=bd28eac8eb60db8aaff74f91c76d4196@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=sshtylyov@ru.mvista.com \
/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).