From: Walter Goldens <goldenstranger@yahoo.com>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00] rt3070 fails to initialize with rt2800usb
Date: Fri, 23 Apr 2010 01:46:44 -0700 (PDT) [thread overview]
Message-ID: <260332.71011.qm@web56802.mail.re3.yahoo.com> (raw)
In-Reply-To: <4BD0B6BD.50509@gmail.com>
> > The problem as I recall first occurred in late January
> or some time in February when someone decided to
> remove large portion of the VIDs from the code because of
> driver collisions and I suppose the purpose of it was to
> reshuffle VID tables and insert some sort of order. Since
> then, compat-wireless does not automatically provide drivers
> for the rt307x via rt2800usb. To this point, only manual
> modification and inserting of the VIDs above solves the
> problem.
> >
> > I'm a 100% certain of this. Even if your cards have
> different VIDs /not 148f:3070/, just install compat-wireless
> with enabled rt307X support and see if "modinfo rt2800usb
> |grep 3070" returns something. Then you'll be able to verify
> my reports.
> >
>
> As I mentioned, I am not experiencing this. See attached
> the modinfo output for the modules that I built with a clean
> compat-wireless package.
>
> The only way I can explain this is that on your system, for
> some reason, changes to config.mk are not picked up by the
> build system.
>
> Can you try removing the include/linux/compat_autoconf.h
> file (from the root of the compat-wireless tree), and then
> run a make clean, followed by a make.
>
> ---
> Gertjan.
Unfortunately, removing this file changes nothing. The rt2800usb still doesn't pick up the 148f:3070 VID as modinfo would show. That is with enabled rt307x support in config.mk and removed compat_autoconf.h in the compat directory. I'm on a Ubuntu 9.10 / 2.6.31-20 kernel. The problem appears to be deeper that I thought.
I don't mind manually modifying VID table to enable support for my devices, but this would mean a large number of users won't be able to take advantage of the new code via compat-wireless. I'm puzzled how results differ, you appear to be testing it on Fedora system with .2.6.32 and Ubuntu 2.6.31 fails. I'm running out of explanations.
Walter.
next prev parent reply other threads:[~2010-04-23 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 16:13 [rt2x00] rt3070 fails to initialize with rt2800usb Walter
2010-04-19 16:25 ` Ivo van Doorn
2010-04-21 8:17 ` Walter Goldens
2010-04-21 21:10 ` Gertjan van Wingerde
2010-04-22 9:05 ` Walter Goldens
2010-04-22 20:51 ` Gertjan van Wingerde
2010-04-23 8:46 ` Walter Goldens [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-17 12:26 Walter
2010-04-17 12:45 ` Ivo van Doorn
2010-04-17 13:09 ` Walter
2010-04-17 13:16 ` Ivo van Doorn
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=260332.71011.qm@web56802.mail.re3.yahoo.com \
--to=goldenstranger@yahoo.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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).