From: Jeremy Jongepier <jeremy@autostatic.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 2.6.33.9-rt31
Date: Wed, 13 Apr 2011 13:02:06 +0200 [thread overview]
Message-ID: <4DA582AE.9020706@autostatic.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104111723020.4501@localhost6.localdomain6>
On 04/11/2011 05:35 PM, Thomas Gleixner wrote:
> We are pleased to announce the next update to our new preempt-rt
> series which is mostly a forward to 2.6.33.9. Thanks Greg !
>
> RT specific patches since 2.6.33.7.2-rt30
>
> 8a97f01: arm: mxc: Add sched_clock to mxc-platform
> a5a2b75: arm: mxc: Add add dummy_get_cycles()
> c1d6834: trace: Add timestamp to maxlatproc data
> cfe9ed2: trace: Add current task to maxlatproc data
> 70fdd17: trace: Add timeroffset to maxlatproc data
> db2aacd: trace: timer offsets histogram consider smp same prio
> 3115eb2: x86, hotplug: Revert 74a6e0fd8 (x86, hotplug: Use mwait to ...)
> 250bf15: ARM: sched_clock: make minsec argument to clocks_calc_mult_shift() zero
> c04f3a8: ARM: sched_clock: allow init_sched_clock() to be called early
> 4d79f92: ARM: sched_clock: provide common infrastructure for sched_clock()
> 7443ac2: asm-generic/percpu: fixup RT mismerge
> 7e1c4f9: rtmutex: Ensure only the top waiter or higher priority task can take the lock
> 47b3309: rtmutex: Fix comment about why new_owner can be NULL in wake_futex_pi()
> 2ce1161: rtmutex: Revert Optimize rt lock wakeup
> 9704792: rtmutex: Try to take lock early in rt_spin_lock_slowlock()
> 5995a44: rtmutex: Only save lock depth once in spin_slowlock
>
> Download locations:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/
>
> Git release branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33
>
> Gitweb:
> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33
>
> Information on the RT patch can be found at:
>
> http://rt.wiki.kernel.org/index.php/Main_Page
>
> to build the 2.6.33.9-rt31 tree, the following patches should be
> applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.9.tar.bz2
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.9-rt31.bz2
>
> Enjoy !
>
> tglx
Thanks for this! Still can't use my two displays with the nouveau kernel
module though :(
Best,
Jeremy
next prev parent reply other threads:[~2011-04-13 11:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 15:35 [ANNOUNCE] 2.6.33.9-rt31 Thomas Gleixner
2011-04-11 15:42 ` Madovsky
2011-04-11 16:06 ` Thomas Gleixner
2011-04-11 16:19 ` Oon-Ee Ng
2011-04-11 16:36 ` Carsten Emde
2011-04-11 16:46 ` Thomas Gleixner
2011-04-13 17:51 ` Madovsky
2011-04-13 18:38 ` jordan
2011-04-13 18:54 ` Jeremy Jongepier
2011-04-13 21:13 ` jordan
2011-04-13 23:38 ` Niccolò Belli
2011-04-14 7:02 ` Jeremy Jongepier
2011-04-14 7:26 ` jordan
2011-04-14 7:42 ` Jeremy Jongepier
2011-04-14 15:58 ` Madovsky
2011-04-14 22:14 ` jordan
2011-04-15 8:22 ` Tracey Hytry
2011-04-17 16:26 ` Niccolò Belli
2011-04-15 15:02 ` dashesy
2011-04-16 8:35 ` Jeremy Jongepier
2011-05-03 23:16 ` dashesy
2011-04-11 16:59 ` Mark Knecht
2011-04-11 19:23 ` Uwe Kleine-König
2011-04-11 22:57 ` Mark Knecht
2011-04-13 11:02 ` Jeremy Jongepier [this message]
2011-04-13 13:39 ` Jan Kiszka
2011-04-13 15:19 ` Jeremy Jongepier
2011-04-18 15:08 ` Clark Williams
2011-04-18 19:14 ` Jan Kiszka
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=4DA582AE.9020706@autostatic.com \
--to=jeremy@autostatic.com \
--cc=linux-rt-users@vger.kernel.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 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).