From: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Xianghua Xiao <xiaoxianghua@gmail.com>,
"Walzer, Frank" <f-walzer@ti.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.35 RT support roadmap
Date: Thu, 12 Aug 2010 13:11:19 -0700 [thread overview]
Message-ID: <4C645567.2080308@gmail.com> (raw)
In-Reply-To: <1281638311.7093.4.camel@marge.simson.net>
On 08/12/2010 11:38 AM, Mike Galbraith wrote:
> On Thu, 2010-08-12 at 09:38 -0500, Xianghua Xiao wrote:
>> On Tue, Aug 10, 2010 at 2:43 AM, Walzer, Frank<f-walzer@ti.com> wrote:
It should be noted, that TI (Omap) was instrumental in supporting some
of the early serious work on RT in the 2004 time frame.
However, in an example of a severe corporate road-map fail, possibly
caused GPL paranoia, combined probably with a nasty case of
Symbian-leveraged NIH, Nokia didn't pick up what TI was laying down -
and in 2005 squandered a fantastic opportunity to take an early lead in
the linux-phone platfrom space, fizzing out with the 7xx and N800 toys.
Google did Android and even Palm woke up (just long enough to watch its
own demise).
The rest is history.
Except of course putting the RT Kernel in Android.
I am curious what the German TI folks are doing with RT!
Cheers
Sven
>>> Hi Folks,
>>>
>>> What is the plan for kernel 2.6.35 support with the RT patch?
>>>
>>> I know this is a difficult (and unliked) question but I would like at least to get some idea. My management is pushing me for dates when we could run some trials.
>>> If nobody is looking at that we have to come up with some other plan.
>>>
>>> Thanks a lot.
>>>
>>> Frank
>>>
>>>
>>> Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht München HRB 40960. Geschäftsführer: Dr. Wolfram Tietscher. Vorsitzender des Aufsichtsrates: Edgar Frank
>>>
>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>> Yes it would be great if we can know which kernel release will have rt
>> patch for it. So far it seems to like a myth.
> Perhaps people wanting specific events to happen at specific times
> should become more proactive.
>
> -Mike
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-12 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 7:43 2.6.35 RT support roadmap Walzer, Frank
2010-08-12 14:38 ` Xianghua Xiao
2010-08-12 18:38 ` Mike Galbraith
2010-08-12 20:11 ` Sven-Thorsten Dietrich [this message]
2010-08-13 3:17 ` jordan johnston
2010-08-13 6:05 ` Sven-Thorsten Dietrich
2010-08-13 9:32 ` jordan johnston
2010-08-13 6:14 ` Mike Galbraith
2010-08-13 10:51 ` Walzer, Frank
2010-08-17 17:00 ` Clark Williams
2010-08-19 16:09 ` Sven-Thorsten Dietrich
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=4C645567.2080308@gmail.com \
--to=sven@thebigcorporation.com \
--cc=efault@gmx.de \
--cc=f-walzer@ti.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=xiaoxianghua@gmail.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).