linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: alupu@verizon.net
To: Larry.Finger@lwfinger.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: r8712u staging in kernel 3.2.9
Date: Fri, 09 Mar 2012 22:53:40 -0600 (CST)	[thread overview]
Message-ID: <12012339.37222.1331355220163.JavaMail.root@vznit170060> (raw)

> On 03/09/12, 09:17 PM, Larry Finger wrote:
> I was surprised to see you using my
> ESSID of "radius", and my WEP key ...

Hi Larry,

You don't need to be. It has always been our intention to
come as close as possible to comparing apples to apples.
You were gracious enough to install wireless tools _v29_
to accommodate me. I tried to reciprocate by using _exactly_ the
values for essis and key you did. Just for argument's sake,
any other values I could've used (practically an infinite array
- the complimentary set) would've raised the suspicion that 
that "unfortunate" choice might be responsible for the problem.
And we'd hate that, wouldn't we?

> I have no idea what is going wrong on your system ...

In general, I wouldn't be so hasty in blaming my system.
It's _very_ possible, but not proven yet. There's nothing
to gain in finger pointing. The object of the game is
to see what and where the problem is. We'll both come
out heads up high if we deal with the situation
professionally, as we are.

Speaking of this, I've been wondering if there's a possibility
that the firmware is somewhat bad (corrupted, wrong, etc)
I did "describe" it in my Mar 6 07:15 PM post,
for convenience, I repeat it here:

[~]$ ls -l /lib/firmware/rtlwifi
-rw-r--r-- 1 alex users 129304 2012-03-04 15:42 rtl8712u.bin

I assumed, your original acceptance of this file (size, etc.)
was an implicit assuaging of my above concern, but one never knows,
do one?

There's another possibility that the Rosewill Wireless Adapter,
RNX-N180UBE, uses a non-"standard" chip, design, etc..
Have you tested your driver with this particular device?
What other devices and/or systems have you validated your
driver with?
Etc., etc.
Anyway, the point is to troubleshoot the problem and not to
speculate about it. Any suggestions, help are welcome as always.

Regards,
-- Alex

             reply	other threads:[~2012-03-10  4:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10  4:53 alupu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-13  4:13 r8712u staging in kernel 3.2.9 alupu
2012-03-12 23:02 alupu
2012-03-13  0:54 ` Larry Finger
2012-03-12  1:46 alupu
2012-03-12  2:54 ` Larry Finger
2012-03-11 22:36 alupu
2012-03-12  0:19 ` Larry Finger
2012-03-11 19:57 alupu
2012-03-11 19:57 alupu
2012-03-10 18:10 alupu
2012-03-11  4:23 ` Larry Finger
2012-03-09 19:06 alupu
2012-03-10  2:17 ` Larry Finger
2012-03-07  5:31 alupu
2012-03-07 16:15 ` Larry Finger
     [not found] <31991817.2926129.1331079358141.JavaMail.root@vznit170116>
2012-03-07  3:22 ` Larry Finger
2012-03-07  1:44 alupu
2012-03-06  2:22 alupu
2012-03-06 20:21 ` Larry Finger
2012-03-05 17:07 alupu
2012-03-05 19:10 ` Larry Finger

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=12012339.37222.1331355220163.JavaMail.root@vznit170060 \
    --to=alupu@verizon.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).