From: Stephen Warren <swarren@wwwdotorg.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
"Fernandes, Joel A" <joelagnel@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-kbuild@vger.kernel.org, tony@atomide.com,
Linux@theia.denx.de, Grant Likely <grant.likely@secretlab.ca>,
u-boot@lists.denx.de, Tom Rini <trini@ti.com>,
Grant Likely <glikely@secretlab.ca>,
OMAP List <linux-omap@vger.kernel.org>,
ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [U-Boot] [RFC] Kbuild support for ARM FIT images
Date: Thu, 21 Feb 2013 16:45:37 -0700 [thread overview]
Message-ID: <5126B1A1.2070703@wwwdotorg.org> (raw)
In-Reply-To: <alpine.LFD.2.03.1302211624561.6419@syhkavp.arg>
On 02/21/2013 03:05 PM, Nicolas Pitre wrote:
> On Thu, 21 Feb 2013, Jason Gunthorpe wrote:
...
>> Distros already ship huge kernels with modules for every hardware out
>> there. Shipping all the DTs as well doesn't seem like a problem.
>
> But it is! Even shipping multiple kernels _is_ a problem for them.
> Hence this multi-platform kernel effort. Otherwise why would we bother?
>
> According to your logic, distros could package and distribute BIOS
> updates for all the X86 systems out there. After all, if they did, they
> would guarantee even better support on the hardware they target and not
> have to carry those ACPI quirks in the kernel, no?
>
> Ask them if they find this idea rejoicing. You might be surprised.
Well they ship x86 CPU firmware updates according to the boot log on one
of my systems at least...
next prev parent reply other threads:[~2013-02-21 23:45 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 1:37 [RFC] Kbuild support for ARM FIT images Joel A Fernandes
2013-02-21 4:26 ` Stephen Warren
2013-02-21 7:15 ` Joel A Fernandes
2013-02-21 18:58 ` Stephen Warren
2013-02-21 19:18 ` Tom Rini
2013-02-21 13:29 ` Tom Rini
2013-02-21 19:03 ` Stephen Warren
2013-02-21 10:37 ` Russell King - ARM Linux
2013-02-21 13:20 ` Tom Rini
2013-02-21 13:46 ` Russell King - ARM Linux
2013-02-21 14:08 ` Tom Rini
2013-02-21 14:37 ` Russell King - ARM Linux
2013-02-21 14:46 ` Tom Rini
2013-02-21 17:25 ` [U-Boot] " Nicolas Pitre
2013-02-21 17:40 ` Tom Rini
2013-02-21 19:21 ` Nicolas Pitre
2013-02-21 19:37 ` Stephen Warren
2013-02-21 19:57 ` Wolfgang Denk
2013-02-21 20:05 ` Stephen Warren
2013-02-21 20:18 ` Wolfgang Denk
2013-02-21 21:18 ` Nicolas Pitre
2013-02-22 0:10 ` Stephen Warren
2013-02-22 0:39 ` Russell King - ARM Linux
2013-02-22 20:48 ` Stephen Warren
2013-02-21 18:27 ` Jason Gunthorpe
2013-02-21 19:08 ` Russell King - ARM Linux
2013-02-21 20:15 ` Jason Gunthorpe
2013-02-21 19:57 ` Nicolas Pitre
2013-02-21 21:14 ` Jason Gunthorpe
2013-02-21 22:05 ` Nicolas Pitre
2013-02-21 23:11 ` Jason Gunthorpe
2013-02-21 23:50 ` Stephen Warren
2013-02-22 0:19 ` Scott Wood
2013-02-22 2:39 ` Jason Gunthorpe
2013-02-22 0:27 ` Russell King - ARM Linux
2013-02-22 0:41 ` Russell King - ARM Linux
2013-02-22 2:11 ` Jason Gunthorpe
2013-02-21 23:18 ` Wolfgang Denk
2013-02-21 23:28 ` Jason Gunthorpe
2013-02-22 0:19 ` Rob Herring
2013-02-22 2:22 ` Jason Gunthorpe
2013-02-22 3:32 ` Rob Herring
2013-02-22 7:56 ` Jason Kridner
2013-02-22 17:43 ` Jason Gunthorpe
2013-02-22 6:55 ` Wolfgang Denk
2013-02-21 23:45 ` Stephen Warren [this message]
2013-02-22 0:29 ` Russell King - ARM Linux
2013-02-21 20:56 ` Peter Korsgaard
2013-02-21 17:37 ` Wolfgang Denk
2013-02-21 18:33 ` Russell King - ARM Linux
2013-02-23 8:38 ` Joel A Fernandes
2013-02-22 16:00 ` Olof Johansson
2013-03-18 16:36 ` Pavel Machek
2013-03-18 16:44 ` Russell King - ARM Linux
2013-03-18 17:49 ` Pavel Machek
2013-03-18 17:57 ` Russell King - ARM Linux
2013-03-18 18:04 ` Pavel Machek
2013-03-18 18:14 ` [U-Boot] " Stephen Warren
2013-03-18 19:57 ` Wolfgang Denk
2013-03-18 19:51 ` Wolfgang Denk
2013-03-18 18:29 ` [U-Boot] " Tom Rini
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=5126B1A1.2070703@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Linux@theia.denx.de \
--cc=glikely@secretlab.ca \
--cc=grant.likely@secretlab.ca \
--cc=jgunthorpe@obsidianresearch.com \
--cc=joelagnel@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=tony@atomide.com \
--cc=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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