From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] [RFC] ARM: multiplatform: rename all mach headers
Date: Wed, 22 Aug 2012 15:31:42 +0000 [thread overview]
Message-ID: <201208221531.42845.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1208221106010.1754@xanadu.home>
On Wednesday 22 August 2012, Nicolas Pitre wrote:
> On Wed, 22 Aug 2012, Arnd Bergmann wrote:
> > There are two branches available in the arm-soc tree:
> >
> > 1. This series,
> > http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=shortlog;h=refs/heads/testing/mach-headers
> > This just moves header files around and changes most of the
> > files including them. There are a few remaining drivers
> > and platform files that keep including a generic file name
> > like <mach/uncompress.h>. It remains possible to do that,
> > and I've run extensive tests to ensure I did not break
> > anything with this. However, each of these instances means
> > that there is something that stops working when you get to
> > the real multiplatform kernel and we still need to deal
> > with them one by one.
>
> The content of <mach/uncompress.h> is fundamentally machine or SOC
> specific. We already know it is generally incompatible with a multi
> platform kernel. So the best way to deal with this at the moment is
> probably to just provide a dummy uncompress.h with empty stubs whenever
> CONFIG_ARCH_MULTIPLATFORM is selected. The effect from this is that
> there wouldn't be any "Uncompressing the kernel... Done" output anymore,
> which should be an acceptable compromise until a better solution is
> found.
Yes, that is what I do in the second series.
> One problem is that some (very few) machines define a method in that
> file to keep a hardware watchdog alive. This might not be the case for
> all the intended targets to gather in a single kernel binary image
> though.
Ok. I think we have a list of known issues somewhere, we should add this
one. I just can't remember where that list is located.
> Another issue is the fact that some platforms do very ugly
> layer-violating hacks where the decompressor selects a serial port for
> early output and then store that selection in some arbitrary memory
> location for the main kernel to blindly use, making the decompressor
> mandatory. OMAP and Davinci are prime example of such "abuse" which
> would need to be fixed.
Same thing here I guess.
Thanks for the input!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] [RFC] ARM: multiplatform: rename all mach headers
Date: Wed, 22 Aug 2012 15:31:42 +0000 [thread overview]
Message-ID: <201208221531.42845.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1208221106010.1754@xanadu.home>
On Wednesday 22 August 2012, Nicolas Pitre wrote:
> On Wed, 22 Aug 2012, Arnd Bergmann wrote:
> > There are two branches available in the arm-soc tree:
> >
> > 1. This series,
> > http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=shortlog;h=refs/heads/testing/mach-headers
> > This just moves header files around and changes most of the
> > files including them. There are a few remaining drivers
> > and platform files that keep including a generic file name
> > like <mach/uncompress.h>. It remains possible to do that,
> > and I've run extensive tests to ensure I did not break
> > anything with this. However, each of these instances means
> > that there is something that stops working when you get to
> > the real multiplatform kernel and we still need to deal
> > with them one by one.
>
> The content of <mach/uncompress.h> is fundamentally machine or SOC
> specific. We already know it is generally incompatible with a multi
> platform kernel. So the best way to deal with this at the moment is
> probably to just provide a dummy uncompress.h with empty stubs whenever
> CONFIG_ARCH_MULTIPLATFORM is selected. The effect from this is that
> there wouldn't be any "Uncompressing the kernel... Done" output anymore,
> which should be an acceptable compromise until a better solution is
> found.
Yes, that is what I do in the second series.
> One problem is that some (very few) machines define a method in that
> file to keep a hardware watchdog alive. This might not be the case for
> all the intended targets to gather in a single kernel binary image
> though.
Ok. I think we have a list of known issues somewhere, we should add this
one. I just can't remember where that list is located.
> Another issue is the fact that some platforms do very ugly
> layer-violating hacks where the decompressor selects a serial port for
> early output and then store that selection in some arbitrary memory
> location for the main kernel to blindly use, making the decompressor
> mandatory. OMAP and Davinci are prime example of such "abuse" which
> would need to be fixed.
Same thing here I guess.
Thanks for the input!
Arnd
next prev parent reply other threads:[~2012-08-22 15:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 12:53 [PATCH 0/4] [RFC] ARM: multiplatform: rename all mach headers Arnd Bergmann
2012-08-22 12:53 ` Arnd Bergmann
2012-08-22 12:54 ` [PATCH 1/4] [RFC] ARM: autogenerate mach-foo/* and plat-foo/* header redirects Arnd Bergmann
2012-08-22 12:54 ` Arnd Bergmann
2012-08-22 15:24 ` Nicolas Pitre
2012-08-22 15:24 ` Nicolas Pitre
2012-08-24 13:44 ` Rob Herring
2012-08-24 13:44 ` Rob Herring
2012-08-22 12:56 ` [PATCH 2/4] [RFC] ARM: mass move of mach-*/plat-* header files Arnd Bergmann
2012-08-22 12:56 ` Arnd Bergmann
2012-08-22 15:28 ` Nicolas Pitre
2012-08-22 15:28 ` Nicolas Pitre
2012-08-22 15:37 ` Arnd Bergmann
2012-08-22 15:37 ` Arnd Bergmann
2012-08-22 13:00 ` [PATCH 3/4] [RFC] ARM: multiplatform: rename all mach headers Arnd Bergmann
2012-08-22 13:00 ` Arnd Bergmann
2012-08-22 15:31 ` Nicolas Pitre
2012-08-22 15:31 ` Nicolas Pitre
2012-08-22 13:01 ` [PATCH 4/4] [RFC] ARM: treewide: manually change more mach-*/*.h includes Arnd Bergmann
2012-08-22 13:01 ` Arnd Bergmann
2012-08-22 15:33 ` Nicolas Pitre
2012-08-22 15:33 ` Nicolas Pitre
2012-08-22 21:43 ` Russell King - ARM Linux
2012-08-22 21:43 ` Russell King - ARM Linux
2012-08-23 11:35 ` Arnd Bergmann
2012-08-23 11:35 ` Arnd Bergmann
2012-08-23 12:37 ` Nicolas Ferre
2012-08-23 12:37 ` Nicolas Ferre
2012-08-23 13:31 ` Arnd Bergmann
2012-08-23 13:31 ` Arnd Bergmann
2012-08-23 17:26 ` Arnd Bergmann
2012-08-23 17:26 ` Arnd Bergmann
2012-08-24 20:36 ` Tony Lindgren
2012-08-24 20:36 ` Tony Lindgren
2012-08-30 19:04 ` Tony Lindgren
2012-08-30 19:04 ` Tony Lindgren
2012-09-05 0:36 ` Tony Lindgren
2012-09-05 0:36 ` Tony Lindgren
2012-08-24 20:47 ` Russell King - ARM Linux
2012-08-24 20:47 ` Russell King - ARM Linux
2012-08-24 20:52 ` Russell King - ARM Linux
2012-08-24 20:52 ` Russell King - ARM Linux
2012-08-27 22:16 ` Haojian Zhuang
2012-08-27 22:16 ` Haojian Zhuang
2012-08-22 15:23 ` [PATCH 0/4] [RFC] ARM: multiplatform: rename all mach headers Nicolas Pitre
2012-08-22 15:23 ` Nicolas Pitre
2012-08-22 15:31 ` Arnd Bergmann [this message]
2012-08-22 15:31 ` Arnd Bergmann
2012-08-22 19:44 ` Stephen Warren
2012-08-22 19:44 ` Stephen Warren
2012-08-22 20:04 ` Arnd Bergmann
2012-08-22 20:04 ` Arnd Bergmann
2012-08-24 13:19 ` Shawn Guo
2012-08-24 13:19 ` Shawn Guo
2012-08-24 13:55 ` Rob Herring
2012-08-24 13:55 ` Rob Herring
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=201208221531.42845.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.