(added CC'ed to the correct mailing list). No, what you did was wrong - unless you are recruiting for private consultants and want to pay for one-to-one consultation, the appropriate way of contacting is via/Cc'ing one of the mailing lists. (and go by the usual rules, like no html-styled e-mail, etc, which you also broke). That said - you have not mentioned any debugging information or any method you tried; nor code snipplets of your work. There is nothing to work on, other than "read my mind". So until you can do that, there is nothing to say. --- On Thu, 26/1/12, Nikola Gacic <empnik@xxxxxxxxx> wrote: From: Nikola Gacic <empnik@xxxxxxxxx> Subject: Fwd: Question regarding Linux RTL driver To: htl10@xxxxxxxxxxxxxxxxxxxxx Date: Thursday, 26 January, 2012, 17:36 Hello Mr. Leung, 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. Kind regards, Nikola Gacić -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
