linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jordan <triplesquarednine@gmail.com>
To: Bernardo Barros <bernardobarros2@gmail.com>
Cc: "Ng Oon-Ee" <ngoonee@gmail.com>,
	"Niccolò Belli" <darkbasic4@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Fernando Lopez-Lezcano" <nando@ccrma.stanford.edu>,
	linux-kernel@vger.kernel.org,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	johnstul@us.ibm.com, rostedt@goodmis.org, npiggin@suse.de
Subject: Re: 2.6.3x-rty where x > 3 and y >= 1?
Date: Thu, 11 Nov 2010 19:05:49 -0500	[thread overview]
Message-ID: <AANLkTikX1sVkQtTw_tx8rFapbTrCE3ShTBi5upwOBDOD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik6x=7jewJ-82yEH=6z9dSVevEbKWLtAqpSecEg@mail.gmail.com>

hehehe,

> I'm trying to install the 2.6.36-bfs here, let's see what happens.. :-)

i know what happens at my end. - i can use 2.6.36 for RT type tasks,
as i set that kernel up 2 days ago.
im still holding onto 2.6.35 though, as it is my best kernel, has my
Wacom running, and rgba.
So far though, 2.6.36 seems not too much different from 2.6.35 for my
pro-audio usage.
I may wait for 2.6.37-bfs before i re-install Wacom, rgba, etc.

(or PREEMPT_RT, once i actually here of a patch being available, i hope soonish)

BFS is good enough for now though.

jordan

  reply	other threads:[~2010-11-12  0:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 19:36 2.6.3x-rty where x > 3 and y >= 1? Fernando Lopez-Lezcano
2010-11-10 20:54 ` Thomas Gleixner
2010-11-11 14:56   ` Niccolò Belli
2010-11-11 22:49     ` Ng Oon-Ee
2010-11-11 23:44       ` Bernardo Barros
2010-11-12  0:05         ` jordan [this message]
2010-11-19 21:18       ` Niccolò Belli
2010-11-25  0:29         ` Robin Gareus
2010-11-27 17:20           ` Niccolò Belli
2010-11-25  0:29     ` Robin Gareus
2010-11-25 11:25       ` Niccolò Belli

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=AANLkTikX1sVkQtTw_tx8rFapbTrCE3ShTBi5upwOBDOD@mail.gmail.com \
    --to=triplesquarednine@gmail.com \
    --cc=bernardobarros2@gmail.com \
    --cc=darkbasic4@gmail.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.stanford.edu \
    --cc=ngoonee@gmail.com \
    --cc=npiggin@suse.de \
    --cc=rostedt@goodmis.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).