linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogerio Luz Coelho <rogluz.news@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
	Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Subject: Re: RTL 8187b - naughty behaviour
Date: Sat, 3 Apr 2010 14:04:17 -0300	[thread overview]
Message-ID: <r2n917a57cb1004031004l392de507x6e655440d2509d0@mail.gmail.com> (raw)
In-Reply-To: <n2n917a57cb1004031000h9910230ew50c6380788a64b1c@mail.gmail.com>

2010/4/3 Rogerio Luz Coelho <rogluz.news@gmail.com>:
> 2010/4/3 Larry Finger <Larry.Finger@lwfinger.net>:
>> On 04/03/2010 11:49 AM, Rogerio Luz Coelho wrote:
>>>
>>> I have a MS-Win7 instalation on this Laptop and it works 100% even at
>>> longer distances than you report,even with walls in between.
>>>
>>> Will do the tcpperf test as soon as I get home. There are other with
>>> the same problem with my exact chip here in Brasil , that is because
>>> one of our leading Laptop vendors uses this config.
>>
>> What is the exact make and model of the device? It might be difficult
>> for me to get one in the US, but one of the rtl8187 developers lives in
>> Brazil. He should be able to find one.
>>
>
> It´s a POSITIVO R430L - Core 2 Duo 4GB RAM
>
>
>>> Does it matter that the USB port used in this setting is a connected
>>> to a USB HUB and then to the mother board?
>>
>> Is the hub passive, or is it powered? If the hub is good and not
>> underpowered, it should be OK.

Have no idea ... how do I find this out?

Rogerio

  reply	other threads:[~2010-04-03 17:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 13:56 RTL 8187b - naughty behaviour Rogerio Luz Coelho
2010-04-03 16:00 ` Larry Finger
2010-04-03 16:49   ` Rogerio Luz Coelho
2010-04-03 16:58     ` Larry Finger
2010-04-03 17:00       ` Rogerio Luz Coelho
2010-04-03 17:04         ` Rogerio Luz Coelho [this message]
2010-04-03 17:33           ` Larry Finger
2010-04-03 17:52             ` Rogerio Luz Coelho
2010-04-10 12:07         ` Rogerio Luz Coelho
2010-04-10 18:50           ` Gábor Stefanik
2010-04-10 19:40             ` Rogerio Luz Coelho
2010-04-11 13:35               ` Gábor Stefanik
2010-04-22 20:45                 ` Rogerio Luz Coelho
2010-04-23 20:16                   ` Gábor Stefanik
2010-04-24 10:47                     ` Rogerio Luz Coelho
2010-04-24 13:59                       ` Larry Finger
2010-06-03 15:40                 ` Rogerio Luz Coelho
2010-08-08 22:22                   ` Rogerio Luz Coelho
2010-08-09  1:43                     ` Larry Finger
2010-08-11  0:03                       ` Rogerio Luz Coelho
2010-08-11  0:23                         ` Thadeu Lima de Souza Cascardo
2010-08-11  2:51                           ` Larry Finger
2010-04-04  0:20       ` Hin-Tak Leung
2010-04-05  0:53         ` Rogerio Luz Coelho
2010-04-05  1:50           ` Gábor Stefanik
2010-04-05  3:12             ` Rogerio Luz Coelho
2010-04-05  3:43               ` Gábor Stefanik
2010-04-03 20:03   ` Gus Wirth
2010-04-03 21:40     ` Larry Finger
2010-05-06 17:36   ` seno
2010-05-06 18:20     ` Larry Finger
2010-05-14 20:12       ` seno
2010-05-14 20:20       ` seno

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=r2n917a57cb1004031004l392de507x6e655440d2509d0@mail.gmail.com \
    --to=rogluz.news@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --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).