From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-wireless@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, dandart@googlemail.com
Subject: Re: [Bugme-new] [Bug 13317] New: No rt2x00 modules in RT kernels.
Date: Thu, 28 May 2009 11:07:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0905281103310.3397@localhost.localdomain> (raw)
In-Reply-To: <20090528000253.c731179c.akpm@linux-foundation.org>
On Thu, 28 May 2009, Andrew Morton wrote:
> > Is there a problem with using rt2x00 kernel modules with realtime kernels?
> > In the info page it says that they need the symbol "BROKEN" which is probably
> > to tell us that we can't use it. I can't compile it into kernels with an RT
> > patch.
> > Why? What's wrong with this mix of module and tree? Is there any way to make
> > them happily coexist?
> >
>
> Good question, but bugzilla isn't a good place to ask it.
>
> Presumably there's some bustage in the rt2x00 driver which makes it not
> work with -rt kernels.
>
> Did the -rt guys tell the wireless guys about this?
There was some build failure which got fixed in meantime, but I forgot
to remove the broken flag.
Will do with the next release.
Thanks,
tglx
prev parent reply other threads:[~2009-05-28 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13317-10286@http.bugzilla.kernel.org/>
2009-05-28 7:02 ` [Bugme-new] [Bug 13317] New: No rt2x00 modules in RT kernels Andrew Morton
2009-05-28 8:40 ` John W. Linville
2009-05-28 9:03 ` Ivo Van Doorn
2009-05-28 9:07 ` Thomas Gleixner [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=alpine.LFD.2.00.0905281103310.3397@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dandart@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rostedt@goodmis.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