From: Grant Likely <grant.likely@secretlab.ca>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit-2009-discuss@lists.linux-foundation.org,
linux-arch@vger.kernel.org, linux-embedded@vger.kernel.org,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: Representing Embedded Architectures at the Kernel Summit
Date: Thu, 4 Jun 2009 14:15:21 -0600 [thread overview]
Message-ID: <fa686aa40906041315w54b6c9f0n650b09d4d2b8f898@mail.gmail.com> (raw)
In-Reply-To: <4A2596B4.3020309@billgatliff.com>
On Tue, Jun 2, 2009 at 3:16 PM, Bill Gatliff <bgat@billgatliff.com> wrote:
> Russell King wrote:
>>
>> The big problem we have is that the only commonality between different
>> SoCs is that the CPU executes ARM instructions. Everything else is
>> entirely up to the SoC designer - eg location of memory, spacing of
>> memory banks, type of interrupt controller, etc is all highly SoC
>> specific. Nothing outside of the ARM CPU itself is standardized.
>
> And that diversity is precisely because of the diversity in ARM-based
> embedded platforms.
>
> Such diversity means that kernel/driver development is a constant activity,
> which suggests that we shouldn't bother the effort to come up with a
> comprehensive solution because none will exist. Rather, we should maintain
> and improve the ability to rapidly prototype and adapt. Things like
> furthering the deployment of platform_device, clocksource/clockdevice, and
> so on.
No, not comprehensive; just common. It makes sense to spend the
effort on the patterns and devices which are common. It may not cover
everything, but it doesn't have to to be valuable.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-06-04 20:15 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 15:22 Representing Embedded Architectures at the Kernel Summit James Bottomley
2009-06-02 17:29 ` Josh Boyer
2009-06-02 17:42 ` James Bottomley
2009-06-02 17:52 ` David VomLehn
2009-06-02 18:25 ` James Bottomley
2009-06-02 18:51 ` Josh Boyer
2009-06-02 19:30 ` Tim Bird
2009-06-02 20:37 ` [Ksummit-2009-discuss] " James Bottomley
2009-06-02 20:44 ` Bill Gatliff
2009-06-02 21:34 ` Robert Schwebel
2009-06-03 3:35 ` Greg KH
[not found] ` <20090731152617.GW29245@pengutronix.de>
2009-07-31 15:53 ` flicker free booting Robert Schwebel
2009-07-31 18:03 ` David VomLehn
2009-07-31 18:09 ` Robert Schwebel
2009-07-31 18:42 ` Bill Gatliff
2009-08-03 8:19 ` Sascha Hauer
2009-08-03 8:37 ` Geert Uytterhoeven
2009-07-31 18:46 ` Bill Gatliff
2009-07-31 19:48 ` Tim Bird
2009-07-31 19:51 ` Bill Gatliff
2009-07-31 20:05 ` Robert Schwebel
2009-08-01 1:26 ` Tim Bird
2009-07-31 19:25 ` Bill Gatliff
2009-08-01 14:25 ` Jamie Lokier
2009-06-03 0:03 ` [Ksummit-2009-discuss] Representing Embedded Architectures at the Kernel Summit David VomLehn
2009-06-03 0:52 ` Eric W. Biederman
2009-06-03 1:42 ` Steven Rostedt
2009-06-02 22:21 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-03 6:24 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-10 23:13 ` Kumar Gala
2009-06-14 3:48 ` Grant Likely
2009-06-10 23:08 ` Kumar Gala
2009-06-02 17:29 ` Grant Likely
2009-06-02 17:45 ` David VomLehn
2009-06-02 18:46 ` Grant Likely
2009-06-02 17:48 ` James Bottomley
2009-06-03 12:17 ` Mark Brown
2009-06-04 18:18 ` Grant Likely
2009-06-02 21:10 ` Russell King
2009-06-02 21:16 ` Bill Gatliff
2009-06-02 21:18 ` Geert Uytterhoeven
2009-06-02 21:40 ` Robert Schwebel
[not found] ` <20090602214005.GL32630@pengutronix.de>
2009-06-02 21:48 ` Russell King
[not found] ` <10f740e80906021418i1d58f5eer940e7a8ec9fb8b9e@mail.gmail.com>
2009-06-03 7:07 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-04 20:08 ` Grant Likely
[not found] ` <4A2596B4.3020309@billgatliff.com>
2009-06-04 20:15 ` Grant Likely [this message]
[not found] ` <3340601010994331832@unknownmsgid>
2009-06-04 20:24 ` Grant Likely
2009-06-03 6:53 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-03 13:04 ` Catalin Marinas
2009-06-03 13:18 ` Josh Boyer
2009-06-03 13:45 ` Catalin Marinas
2009-06-03 14:11 ` Josh Boyer
2009-06-03 14:06 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-03 16:19 ` James Bottomley
2009-06-03 17:09 ` Russell King
2009-06-03 18:43 ` Andrew Morton
2009-06-03 19:01 ` James Bottomley
2009-06-04 3:11 ` David VomLehn (dvomlehn)
2009-06-04 3:24 ` Mike Frysinger
2009-06-04 9:23 ` Mel Gorman
2009-06-03 19:08 ` Catalin Marinas
2009-06-10 9:42 ` Thomas Petazzoni
2009-06-16 6:42 ` Mike Rapoport
2009-06-16 8:06 ` Mike Frysinger
2009-06-16 12:19 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-17 4:26 ` H. Peter Anvin
2009-06-17 15:04 ` Ralf Baechle
2009-06-17 17:14 ` H. Peter Anvin
2009-06-16 16:06 ` Grant Likely
2009-06-16 18:18 ` Jamie Lokier
2009-06-16 19:28 ` Grant Likely
2009-06-16 20:07 ` Jamie Lokier
2009-06-16 20:10 ` Marcel Holtmann
2009-06-16 21:04 ` Grant Likely
2009-06-18 3:05 ` Paul Mundt
2009-06-17 14:31 ` Kumar Gala
2009-06-18 2:51 ` Paul Mundt
2009-06-19 2:59 ` Kumar Gala
2009-06-19 3:00 ` Paul Mundt
2009-06-19 7:53 ` Kumar Gala
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=fa686aa40906041315w54b6c9f0n650b09d4d2b8f898@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bgat@billgatliff.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=ksummit-2009-discuss@lists.linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=tim.bird@am.sony.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).