From: Larry Finger <Larry.Finger@lwfinger.net>
To: Nikola Gacic <empnik@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Question regarding Linux RTL driver
Date: Thu, 26 Jan 2012 12:49:02 -0600 [thread overview]
Message-ID: <4F21A01E.20105@lwfinger.net> (raw)
In-Reply-To: <CAOVbLLFcja-DV1bEq9C2U8q5eohc7O0AE=oymfjMMBOBi4D52g@mail.gmail.com>
On 01/26/2012 11:37 AM, Nikola Gacic wrote:
> Hello Mr. Finger,
>
> I don't know if this is the right way for contacting you but I couldn't
> find the other way.
> Firstly, I want to say that I am student at School of electrical
> Engineering in Belgrade and I am working on some embedded project where I tried
> to use you RTL8187 Linux driver to communicate with PIC32 microcontroller over USB.
> I would appreciate any help with my problem. If you could spare some time
> to read this it would be great. I have several questions. Initialization worked
> fine I think (I get ACK packets), but when I try to finally send IN packet to
> endpoint 0x81 I get NAK packets all the time!
> I checked code in microcontroller several times and, of course, maybe error
> could be somewhere in initialization, but would that block my IN packets to
> device? I know that PIC32 cannot work in high-speed mode, only in full-speed,
> but in the datasheet for this dongle it says it can work in full-speed. So I
> want to know does USB card set its speed to full-speed automatically?
> I think my understanding of driver code is good so you can give me some
> general guidelines regarding initialization if you don't want to go to
> details.Thank you in advance.
Contacting me is OK, but all communication should also be Cc'd to the
linux-wireless mailing list.
Could you please give me some more details? Is this setup as an ad-hoc wireless
connection? I know that rtl8187 does not work in AP mode, but I'm not sure about
ad-hoc mode, and I am unable to test that at the moment.
Which device are you using - RTL8187L, or RTL8187B? The USB ID should tell that.
Yes, the device will work with USB1.1 hardware, and it might even work with
USB1.0, but I have never tested that.
Larry
next parent reply other threads:[~2012-01-26 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOVbLLHPdC3XkuTs6OapNMFkSbWaRq54D5U3RDY=N4ugZfEKKQ@mail.gmail.com>
[not found] ` <CAOVbLLHK=3K5KfYs7V+9PyE2joWTewuXvpS7RzU63GJS0C2=ug@mail.gmail.com>
[not found] ` <CAOVbLLH_RXSzXeQ-g7--6QrUBGD63o-9-7a7NjKc=LM8UL2+GA@mail.gmail.com>
[not found] ` <CAOVbLLEzuyBkQv0a238SfDrNXi3hf72Kzyjv8L=m9hokhGjx5A@mail.gmail.com>
[not found] ` <CAOVbLLFcja-DV1bEq9C2U8q5eohc7O0AE=oymfjMMBOBi4D52g@mail.gmail.com>
2012-01-26 18:49 ` Larry Finger [this message]
[not found] ` <CAOVbLLHirAKiDehW=79dv1ku1pB0JdpA9SfFkLTcLk5NZctX7A@mail.gmail.com>
2012-01-26 22:51 ` Question regarding Linux RTL driver Nikola Gacic
2012-01-26 23:29 ` Larry Finger
2012-01-26 23:58 ` Nikola Gacic
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=4F21A01E.20105@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=empnik@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.