linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	LKML <linux-kernel@vger.kernel.org>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 2.6.33.7-rt29
Date: Fri, 31 Dec 2010 11:56:34 -0800	[thread overview]
Message-ID: <4D1E3572.20505@localhost> (raw)
In-Reply-To: <4D152086.1070909@localhost>

On 12/24/2010 02:36 PM, Fernando Lopez-Lezcano wrote:
> On 12/21/2010 05:52 AM, Thomas Gleixner wrote:
>> We are pleased to announce the next update to our new preempt-rt
>> series.
>> ...
>> Information on the RT patch can be found at:
>>
>> http://rt.wiki.kernel.org/index.php/Main_Page
>>
>> To build the 2.6.33.7.2-rt30 tree, the following patches should be
>> applied:
>>
>> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2
>> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2
>>
>>
>> Enjoy !
>
> I'm testing it right now and it does seem to have fixed some stuff, for
> example I don't see any more errors when waking up from a sleep state.
> Anyway, I'll let you know of any problems...

So far so good...

> Thanks a lot! (and also good to know about the plans for 2.6.37.x rt!)

A question: I need to find out the pid of the irq process that handles a 
particular audio device from the information available from udev (to 
dynamically change its rt priority).

AFAICT that is not really possible. I can find the irq number easily but 
if there is more than one device using that number then I'm sort of 
stuck. The naming of the irq processes for each card appear to be 
hardwired strings in the driver code that do not necessarily correspond 
to any other name in the driver itself.

Is there a connection between the two somewhere in /sys, /proc or 
anywhere else that I'm missing? (ie: which interrupt process corresponds 
to which driver?)

-- Fernando

      reply	other threads:[~2010-12-31 19:56 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner
2010-02-24 22:38 ` Peter Zijlstra
2010-02-25 22:56   ` Peter Zijlstra
2010-02-26 19:44 ` Dan Carpenter
2010-02-27  8:10   ` Thomas Gleixner
2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner
2010-02-27  9:25   ` Xavier Miller
2010-02-27 10:10     ` GeunSik Lim
2010-02-27 11:53     ` Thomas Gleixner
2010-03-02 21:25       ` Fernando Lopez-Lezcano
2010-03-02 21:53         ` Thomas Gleixner
2010-02-27  9:50   ` GeunSik Lim
2010-03-12 10:44   ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner
2010-03-12 12:17     ` 2.6.33-rt6 on Beagle Chatterjee, Amit
2010-03-15  9:20       ` Uwe Kleine-König
2010-03-15 11:23         ` What's the best way to create an embedded version of PREEMPT_RT Linux ? Armin Steinhoff
2010-03-21 11:06     ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner
2010-04-07 14:24       ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner
2010-04-27 15:52         ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner
2010-04-30 10:00           ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner
2010-05-02 19:18             ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner
2010-06-09 16:44               ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner
2010-06-09 21:31                 ` Will Schmidt
2010-06-10  6:07                   ` Thomas Gleixner
2010-06-10 15:56                     ` Will Schmidt
2010-06-10 16:05                       ` Darcy L. Watkins
2010-06-14 13:33                         ` Thomas Gleixner
2010-06-14 13:34                       ` Thomas Gleixner
2010-06-14 15:35                         ` Will Schmidt
2010-07-13 15:54                 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner
2010-07-13 16:52                   ` Dhaval Giani
2010-07-13 18:04                   ` Philipp Überbacher
2010-07-13 19:13                     ` Darcy L. Watkins
2010-07-13 19:23                       ` Philipp Überbacher
2010-07-14 13:47                         ` Thomas Gleixner
2010-07-14 13:57                           ` Ng Oon-Ee
2010-07-14 14:27                             ` John Kacur
     [not found]                               ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com>
2010-07-15  5:25                                 ` Yang Jian
2010-07-15 11:45                           ` Philipp Überbacher
2010-07-19  6:37                   ` Barry Song
2010-07-31 13:33                   ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner
2010-08-03  9:23                     ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner
2010-12-21 13:52                       ` Thomas Gleixner
2010-12-21 15:01                         ` Mark Knecht
2010-12-21 15:48                         ` Madovsky
2010-12-21 16:39                         ` Dennis Borgmann
2010-12-22 16:38                         ` Madovsky
2010-12-22 20:20                         ` Remy Bohmer
2010-12-24 22:36                         ` Fernando Lopez-Lezcano
2010-12-31 19:56                           ` Fernando Lopez-Lezcano [this message]

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=4D1E3572.20505@localhost \
    --to=nando@ccrma.stanford.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).