From: "Vladimir G. Ivanovic" <vgivanovic@comcast.net>
To: gentoo-amd64 <gentoo-amd64@lists.gentoo.org>
Subject: [gentoo-amd64] 2.6.22 and the rt2500/rt2x00 wireless drivers
Date: Fri, 13 Jul 2007 09:01:41 -0700 [thread overview]
Message-ID: <4697A1E5.60400@comcast.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kernels before 2.6.22 could be configured with "CONFIG_NET_RADIO=y"
which would allow the rt2500 legacy driver for the Ralink wireless
chipset to compile. I've had this combination working now for over a year.
Starting with kernel 2.6.22, NET_RADIO is apparently no longer a
configuration parameter, so I can't compile the rt2500 legacy driver,
nor can I compile the newer rt2x00 driver which also depends on NET_RADIO.
Has anyone gotten a rt2500/rtx00 driver to compile with 2.6.22? What
patches are needed? Is there a HOWTO somewhere? (The Gentoo Wiki
articles "rt2500 on AMD64" and "rt2x00" don't seem to address my
issue. In any case, neither the latest CVS of rt2500 (2007051606) nor
the latest ebuild (net-wireless/rt2500-1.1.0_pre2007020911) compile
with KERNDIR=/usr/src/linux-.6.22-gentoo-r1. The latest ebuild
compiled just fine with kernels before 2.6.22.)
Any help would be appreciated. Thanks.
- --- Vladimir
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.5 (GNU/Linux)
iD8DBQFGl6HlEo/yvZUwubMRAkCGAJwMpHhYUd9Y+T8gjZKOyliZz7vsCACeLSjJ
D3vyqbszeYiA8s+DtCN28KQ=
=q6ne
-----END PGP SIGNATURE-----
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2007-07-13 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 16:01 Vladimir G. Ivanovic [this message]
2007-07-13 20:17 ` [gentoo-amd64] 2.6.22 and the rt2500/rt2x00 wireless drivers Marc Redmann
2007-07-15 9:53 ` Rodolphe Rocca
2007-07-15 9:55 ` Rodolphe Rocca
2007-07-15 10:02 ` Rodolphe Rocca
2007-07-15 10:16 ` Rodolphe Rocca
2007-07-17 11:52 ` Vladimir G. Ivanovic
2007-07-18 9:57 ` Rodolphe Rocca
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=4697A1E5.60400@comcast.net \
--to=vgivanovic@comcast.net \
--cc=gentoo-amd64@lists.gentoo.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