* Re: [PATCH 04/57] microblaze_v7: Open firmware files
2009-03-23 18:51 ` [PATCH 04/57] microblaze_v7: Open firmware files Arnd Bergmann
@ 2009-03-23 20:44 ` Michal Simek
2009-03-23 20:53 ` Anton Vorontsov
2009-03-24 11:17 ` Michal Simek
2 siblings, 0 replies; 5+ messages in thread
From: Michal Simek @ 2009-03-23 20:44 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linuxppc-dev, linux-kernel, john.williams
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
Hi Arnd,
nice to hear you.
On Wednesday 18 March 2009, monstr@monstr.eu wrote:
> > From: Michal Simek <monstr@monstr.eu>
> >
> >
> > Signed-off-by: Michal Simek <monstr@monstr.eu>
> > ---
> > arch/microblaze/include/asm/of_device.h | 45 ++
> > arch/microblaze/include/asm/of_platform.h | 64 ++
> > arch/microblaze/include/asm/prom.h | 313 ++++++++
> > arch/microblaze/kernel/of_device.c | 115 +++
> > arch/microblaze/kernel/of_platform.c | 201 +++++
> > arch/microblaze/kernel/prom.c | 1147
> +++++++++++++++++++++++++++++
> > arch/microblaze/kernel/prom_parse.c | 1025
> ++++++++++++++++++++++++++
> > 7 files changed, 2910 insertions(+), 0 deletions(-)
> > create mode 100644 arch/microblaze/include/asm/of_device.h
> > create mode 100644 arch/microblaze/include/asm/of_platform.h
> > create mode 100644 arch/microblaze/include/asm/prom.h
> > create mode 100644 arch/microblaze/kernel/of_device.c
> > create mode 100644 arch/microblaze/kernel/of_platform.c
> > create mode 100644 arch/microblaze/kernel/prom.c
> > create mode 100644 arch/microblaze/kernel/prom_parse.c
>
> Since these files are derived from the powerpc versions, what is the
> plan on them? IIRC, you had them in a common directory in an earlier
> version. Are you planning to merge them at some point in the future
> or do you intend to maintain a fork?
yes, these files are defived from PPC version. Yes, I added them to generic
location and in this version
are in arch folder. It is easier for me to have them in arch folder till
Microblaze will be in linus tree.
And then create patch which will synchronize them.
I prefer to have this code in generic location as much as possible but first
stage should be add microblaze code to tree and
then add it to generic location and remove it from all archs which use it.
Thanks,
Michal
>
>
> Arnd <><
>
[-- Attachment #2: Type: text/html, Size: 2477 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 04/57] microblaze_v7: Open firmware files
2009-03-23 18:51 ` [PATCH 04/57] microblaze_v7: Open firmware files Arnd Bergmann
2009-03-23 20:44 ` Michal Simek
@ 2009-03-23 20:53 ` Anton Vorontsov
2009-03-26 0:01 ` Benjamin Herrenschmidt
2009-03-24 11:17 ` Michal Simek
2 siblings, 1 reply; 5+ messages in thread
From: Anton Vorontsov @ 2009-03-23 20:53 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linuxppc-dev, monstr, linux-kernel, john.williams
On Mon, Mar 23, 2009 at 07:51:23PM +0100, Arnd Bergmann wrote:
> On Wednesday 18 March 2009, monstr@monstr.eu wrote:
> > From: Michal Simek <monstr@monstr.eu>
> >
> >
> > Signed-off-by: Michal Simek <monstr@monstr.eu>
> > ---
> > arch/microblaze/include/asm/of_device.h | 45 ++
> > arch/microblaze/include/asm/of_platform.h | 64 ++
> > arch/microblaze/include/asm/prom.h | 313 ++++++++
> > arch/microblaze/kernel/of_device.c | 115 +++
> > arch/microblaze/kernel/of_platform.c | 201 +++++
> > arch/microblaze/kernel/prom.c | 1147 +++++++++++++++++++++++++++++
> > arch/microblaze/kernel/prom_parse.c | 1025 ++++++++++++++++++++++++++
> > 7 files changed, 2910 insertions(+), 0 deletions(-)
> > create mode 100644 arch/microblaze/include/asm/of_device.h
> > create mode 100644 arch/microblaze/include/asm/of_platform.h
> > create mode 100644 arch/microblaze/include/asm/prom.h
> > create mode 100644 arch/microblaze/kernel/of_device.c
> > create mode 100644 arch/microblaze/kernel/of_platform.c
> > create mode 100644 arch/microblaze/kernel/prom.c
> > create mode 100644 arch/microblaze/kernel/prom_parse.c
>
> Since these files are derived from the powerpc versions, what is the
> plan on them? IIRC, you had them in a common directory in an earlier
> version. Are you planning to merge them at some point in the future
> or do you intend to maintain a fork?
Actually, it's trivial to factor out all the common code out of
arch/powerpc/ to drivers/of/.
It took me approx. 4 hours to factor out the code and make a
proof-of-concept FDT support for a little-endian ARM platform. ;-)
(The device tree was only describing a cpu and a nor flash, though.
No support for interrupt- and gpio-controllers. And no support for
U-Boot, I just built the dtb file into the kernel).
I never got around to clean it up and send though, but for sure,
there is absolutely no reason to duplicate the code across the
platforms.
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 04/57] microblaze_v7: Open firmware files
2009-03-23 20:53 ` Anton Vorontsov
@ 2009-03-26 0:01 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 5+ messages in thread
From: Benjamin Herrenschmidt @ 2009-03-26 0:01 UTC (permalink / raw)
To: avorontsov
Cc: linuxppc-dev, monstr, linux-kernel, Arnd Bergmann, john.williams
On Mon, 2009-03-23 at 23:53 +0300, Anton Vorontsov wrote:
> It took me approx. 4 hours to factor out the code and make a
> proof-of-concept FDT support for a little-endian ARM platform. ;-)
> (The device tree was only describing a cpu and a nor flash, though.
> No support for interrupt- and gpio-controllers. And no support for
> U-Boot, I just built the dtb file into the kernel).
ARM could benefit tremendously I believe from a similar virtualized
interrupt mapping & OF tree to powerpc for their gazillions of weirdly
cascaded interrupt controller setups :-)
Ben.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 04/57] microblaze_v7: Open firmware files
2009-03-23 18:51 ` [PATCH 04/57] microblaze_v7: Open firmware files Arnd Bergmann
2009-03-23 20:44 ` Michal Simek
2009-03-23 20:53 ` Anton Vorontsov
@ 2009-03-24 11:17 ` Michal Simek
2 siblings, 0 replies; 5+ messages in thread
From: Michal Simek @ 2009-03-24 11:17 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linuxppc-dev, linux-kernel, john.williams
Arnd Bergmann wrote:
> On Wednesday 18 March 2009, monstr@monstr.eu wrote:
>> From: Michal Simek <monstr@monstr.eu>
>>
>>
>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>> ---
>> arch/microblaze/include/asm/of_device.h | 45 ++
>> arch/microblaze/include/asm/of_platform.h | 64 ++
>> arch/microblaze/include/asm/prom.h | 313 ++++++++
>> arch/microblaze/kernel/of_device.c | 115 +++
>> arch/microblaze/kernel/of_platform.c | 201 +++++
>> arch/microblaze/kernel/prom.c | 1147 +++++++++++++++++++++++++++++
>> arch/microblaze/kernel/prom_parse.c | 1025 ++++++++++++++++++++++++++
>> 7 files changed, 2910 insertions(+), 0 deletions(-)
>> create mode 100644 arch/microblaze/include/asm/of_device.h
>> create mode 100644 arch/microblaze/include/asm/of_platform.h
>> create mode 100644 arch/microblaze/include/asm/prom.h
>> create mode 100644 arch/microblaze/kernel/of_device.c
>> create mode 100644 arch/microblaze/kernel/of_platform.c
>> create mode 100644 arch/microblaze/kernel/prom.c
>> create mode 100644 arch/microblaze/kernel/prom_parse.c
>
> Since these files are derived from the powerpc versions, what is the
> plan on them? IIRC, you had them in a common directory in an earlier
> version. Are you planning to merge them at some point in the future
> or do you intend to maintain a fork?
yes, these files are defived from PPC version. Yes, I added them to generic
location and in this version are in arch folder. It is easier for me to have
them in arch folder till Microblaze will be in linus tree.
And then create patch which will synchronize them.
I prefer to have this code in generic location as much as possible but first
stage from my perspective should be add microblaze code to tree and then add it
to generic location and remove it from all archs which use it.
Thanks,
Michal
> Arnd <><
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
^ permalink raw reply [flat|nested] 5+ messages in thread