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: "Gábor Stefanik" <netrolller.3d@gmail.com>,
	linux-wireless@vger.kernel.org,
	"Herton Ronaldo Krzesinski" <herton@mandriva.com.br>
Subject: Re: RTL 8187b - naughty behaviour
Date: Tue, 10 Aug 2010 21:03:46 -0300	[thread overview]
Message-ID: <AANLkTimQtAOSjfpCx8H3RXu0O+gPbvMQQ3P3-tLmpaiV@mail.gmail.com> (raw)
In-Reply-To: <4C5F5D5C.9040709@lwfinger.net>

lem
2010/8/8 Larry Finger <Larry.Finger@lwfinger.net>:
> On 08/08/2010 05:22 PM, Rogerio Luz Coelho wrote:
>> SNIP ...
>>
>> So no luck with the Realtek driver yet?
>
> We are not doing anything with the Realtek driver. My RTL8187B device works
> perfectly fine.
>
> If you were to study a vendor driver and come up with some patches to rtl8187
> that made your device function better, then I would consider them, but at this
> point, I am not looking at any changes to rtl8187.
>
> Larry
>

Ok, but have you seen the amount of people on the Ubuntu bug list with
the same problem?

I am just saying it seems it is quite widespread problem, not just my case ...

I tried to post all information asked, I have no idea even if  I did
the mmio trace right since I had no response.

:)

Hey, I am not trolling here, it´s just I thought you guys would
**magically** find the issue after my post (hey wishfull thinking is
STILL thinking right?)

Rogerio

  reply	other threads:[~2010-08-11  0:03 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
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 [this message]
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=AANLkTimQtAOSjfpCx8H3RXu0O+gPbvMQQ3P3-tLmpaiV@mail.gmail.com \
    --to=rogluz.news@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.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).