From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/06] ARM: shmobile: Introduce SHMOBILE_FIXUP() helper
Date: Thu, 06 Jun 2013 16:53:43 +0000 [thread overview]
Message-ID: <201306061853.44135.arnd@arndb.de> (raw)
In-Reply-To: <20130605192019.GG18614@n2100.arm.linux.org.uk>
On Wednesday 05 June 2013, Russell King - ARM Linux wrote:
> On Wed, Jun 05, 2013 at 04:34:18PM +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@opensource.se>
> >
> > Introduce SHMOBILE_FIXUP() as a helper function to
> > allow boards to specify their memory base and size.
>
> No. I really don't like this idea (we've had people doing this in the
> past and I went around removing all that crap, and adding command line
> options into the defconfig files for those boards.)
>
> I also fail to understand why in 2013, some 11 years after ATAG stuff
> was created, people still can't get pass correct information into
> the kernel.
>
> It's exactly this kind of issue which makes me believe that stuff like
> ACPI, UEFI and DT are doomed to fail on ARM because this kind of problem
> constantly crops up time and time again. People have seem to have this
> total inability to get the pre-kernel environment right.
I think the problem in this case is that the pre-boot environment is
essentially nothing but mask rom jumping into head-shmobile.S, which
is something nobody else does.
My understanding is that you can also put a regular u-boot, kexec or
some other boot loader into the same place and get a running system with
correct ATAGS or DT information.
It's debatable whether booting the kernel directly without an upgradable
boot loader is a good idea, but since Renesas have come to depend on
this and it's been supported by Linux for ages (both on ARM and SH),
I would certainly not ask them to remove support for that.
What I think we can do however is move all that configuration into
one place of the kernel that is fairly separate from everything else.
head-shmobile.S already contains most of the special case, so
how about adding a configuration option that enables both the
head-shmobile.S code and contains the configuration for that in
a submenu?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/06] ARM: shmobile: Introduce SHMOBILE_FIXUP() helper
Date: Thu, 6 Jun 2013 18:53:43 +0200 [thread overview]
Message-ID: <201306061853.44135.arnd@arndb.de> (raw)
In-Reply-To: <20130605192019.GG18614@n2100.arm.linux.org.uk>
On Wednesday 05 June 2013, Russell King - ARM Linux wrote:
> On Wed, Jun 05, 2013 at 04:34:18PM +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@opensource.se>
> >
> > Introduce SHMOBILE_FIXUP() as a helper function to
> > allow boards to specify their memory base and size.
>
> No. I really don't like this idea (we've had people doing this in the
> past and I went around removing all that crap, and adding command line
> options into the defconfig files for those boards.)
>
> I also fail to understand why in 2013, some 11 years after ATAG stuff
> was created, people still can't get pass correct information into
> the kernel.
>
> It's exactly this kind of issue which makes me believe that stuff like
> ACPI, UEFI and DT are doomed to fail on ARM because this kind of problem
> constantly crops up time and time again. People have seem to have this
> total inability to get the pre-kernel environment right.
I think the problem in this case is that the pre-boot environment is
essentially nothing but mask rom jumping into head-shmobile.S, which
is something nobody else does.
My understanding is that you can also put a regular u-boot, kexec or
some other boot loader into the same place and get a running system with
correct ATAGS or DT information.
It's debatable whether booting the kernel directly without an upgradable
boot loader is a good idea, but since Renesas have come to depend on
this and it's been supported by Linux for ages (both on ARM and SH),
I would certainly not ask them to remove support for that.
What I think we can do however is move all that configuration into
one place of the kernel that is fairly separate from everything else.
head-shmobile.S already contains most of the special case, so
how about adding a configuration option that enables both the
head-shmobile.S code and contains the configuration for that in
a submenu?
Arnd
next prev parent reply other threads:[~2013-06-06 16:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 7:34 [PATCH 00/06] ARM: shmobile: Per-board memory size fixups Magnus Damm
2013-06-05 7:34 ` Magnus Damm
2013-06-05 7:31 ` Magnus Damm
2013-06-05 7:31 ` Magnus Damm
2013-06-05 7:34 ` [PATCH 01/06] ARM: shmobile: Introduce SHMOBILE_FIXUP() helper Magnus Damm
2013-06-05 7:34 ` Magnus Damm
2013-06-05 19:20 ` Russell King - ARM Linux
2013-06-05 19:20 ` Russell King - ARM Linux
2013-06-05 23:47 ` Magnus Damm
2013-06-05 23:47 ` Magnus Damm
2013-06-06 17:17 ` Arnd Bergmann
2013-06-06 17:17 ` Arnd Bergmann
2013-06-10 7:22 ` Magnus Damm
2013-06-10 7:22 ` Magnus Damm
2013-06-10 15:27 ` Arnd Bergmann
2013-06-10 15:27 ` Arnd Bergmann
2013-06-06 16:53 ` Arnd Bergmann [this message]
2013-06-06 16:53 ` Arnd Bergmann
2013-06-05 7:34 ` [PATCH 02/06] ARM: shmobile: AG5EVM memory size fixup Magnus Damm
2013-06-05 7:34 ` Magnus Damm
2013-06-05 7:34 ` [PATCH 03/06] ARM: shmobile: AP4EVB " Magnus Damm
2013-06-05 7:34 ` Magnus Damm
2013-06-05 7:34 ` [PATCH 04/06] ARM: shmobile: Bonito " Magnus Damm
2013-06-05 7:34 ` Magnus Damm
2013-06-05 7:34 ` [PATCH 05/06] ARM: shmobile: Kota2 " Magnus Damm
2013-06-05 7:34 ` Magnus Damm
2013-06-05 7:34 ` [PATCH 06/06] ARM: shmobile: Marzen " Magnus Damm
2013-06-05 7:34 ` Magnus Damm
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=201306061853.44135.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.