From: Andrew Morton <akpm@linux-foundation.org>
To: linux-wireless@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Cc: 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 00:02:53 -0700 [thread overview]
Message-ID: <20090528000253.c731179c.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13317-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Fri, 15 May 2009 17:53:46 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13317
>
> Summary: No rt2x00 modules in RT kernels.
> Product: Alternate Trees
> Version: 2.5
> Kernel Version: 2.6.29+
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: rt
> AssignedTo: alt-trees_rt@kernel-bugs.osdl.org
> ReportedBy: dandart@googlemail.com
> Regression: No
>
>
> 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?
next parent reply other threads:[~2009-05-28 7:03 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 ` Andrew Morton [this message]
2009-05-28 8:40 ` [Bugme-new] [Bug 13317] New: No rt2x00 modules in RT kernels John W. Linville
2009-05-28 9:03 ` Ivo Van Doorn
2009-05-28 9:07 ` Thomas Gleixner
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=20090528000253.c731179c.akpm@linux-foundation.org \
--to=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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.