From: Sven-Thorsten Dietrich <sdietrich@novell.com>
To: Reagan Thomas <thomasraz@gmail.com>
Cc: Michael Mueller <ss7box@gmail.com>, linux-rt-users@vger.kernel.org
Subject: Re: real time interrupts
Date: Wed, 13 Oct 2010 13:32:36 -0400 [thread overview]
Message-ID: <1286991156.14081.7.camel@sven> (raw)
In-Reply-To: <4CB5D722.1020701@gmail.com>
On Wed, 2010-10-13 at 10:58 -0500, Reagan Thomas wrote:
> On 10/13/2010 7:07 AM, Sven-Thorsten Dietrich wrote:
> > On 10/13/2010 04:50 AM, Michael Mueller wrote:
> >> On Wed, Oct 13, 2010 at 4:37 AM, John Kacur<jkacur@redhat.com> wrote:
> >>> On Wed, Oct 13, 2010 at 10:10 AM, ratheesh
> >>> k<ratheesh.ksz@gmail.com> wrote:
> >>>> I am using 2.6.18 kernel with rt-linux patch.
> >>> I'm afraid that with such an old kernel, you are unlikely to find any
> >>> support here. If it is at all possible for you, please update to
> >>> something newer.
> >>
> >> i tried dropping a new kernel into a distro using 2.6.18 (centos) and
> >> did not succeed; success came after moving to distro with a recent
> >> kernel and toolchain (fedora)
> >>
> >> mike
> >
> > Can you be more specific about the failure you encountered?
> >
> > And the version of the 'new' Kernel.
> >
> > (Oracle didn't seem to have any trouble updating RHEL 5 from 2.6.18 to
> > 2.6.32 -- maybe use their .config)
> >
> > Sven
> > --
>
>
> At a minimum, he should add:
>
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
>
> I'm pretty sure that's all I had to add to get 2.6.33.7-rt29 to work
Nod.
That's what I was fishing for.
The same also applies when trying to get Suse / SLES 10 era systems to
work with RT Kernels later than 2.6.20 or so.
Regards,
Sven
prev parent reply other threads:[~2010-10-13 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 8:10 real time interrupts ratheesh k
2010-10-13 8:37 ` John Kacur
2010-10-13 8:50 ` Michael Mueller
2010-10-13 12:07 ` Sven-Thorsten Dietrich
2010-10-13 15:58 ` Reagan Thomas
2010-10-13 17:32 ` Sven-Thorsten Dietrich [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=1286991156.14081.7.camel@sven \
--to=sdietrich@novell.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=ss7box@gmail.com \
--cc=thomasraz@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).