On Sat, 5 Oct 2013, Arokux X wrote:
Hi all,
first of all thank you all for your help. I now have some news to
report. Using your hint about timing I've inserted a bunch of udelays
around the read/write functions that get called from _rtl92c_write_fw
and got rid of the detected XactErr len
On 10/05/2013 10:01 AM, Alan Stern wrote:
On Sat, 5 Oct 2013, Arokux X wrote:
Hi all,
first of all thank you all for your help. I now have some news to
report. Using your hint about timing I've inserted a bunch of udelays
around the read/write functions that get called from _rtl92c_write_fw
On Sat, 5 Oct 2013, Larry Finger wrote:
I do however have something fishy to report, but this is probably an
off-topic for linux-usb mailing list so I'll just mention it here
briefly for completeness. Fist, I've compared the speed of the
rtl8192cu vs 8192cu in 3.4 kernel. The latter one
On 10/05/2013 02:52 PM, Alan Stern wrote:
On Sat, 5 Oct 2013, Larry Finger wrote:
I do however have something fishy to report, but this is probably an
off-topic for linux-usb mailing list so I'll just mention it here
briefly for completeness. Fist, I've compared the speed of the
rtl8192cu vs
Hi all,
first of all thank you all for your help. I now have some news to
report. Using your hint about timing I've inserted a bunch of udelays
around the read/write functions that get called from _rtl92c_write_fw
and got rid of the detected XactErr len 0/0 retry errors. Then I
just tried to use
Hi Arokux,
Am 29.09.2013 23:16, schrieb Arokux X:
Hi Oleksij,
On Sun, Sep 29, 2013 at 10:01 PM, Oleksij Rempel li...@rempel-privat.de
wrote:
Hi Arokux,
Allan already pointed on timing issue. If you compare bad and working
logs you will see that interval on bad log is match more shorter.
On 29.09.2013 02:50, Arokux X wrote:
Dear Alan,
I don't know. Did you run all these tests on the same computer?
Yes, it is a single board computer, see image here:
http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/A10_device_a1000_inside.jpg
WLAN Adapter is left at the
On 09/28/2013 09:57 PM, Alan Stern wrote:
On Sun, 29 Sep 2013, Arokux X wrote:
What happens if you back-port your glue driver to the vendor's kernel?
I have now 200 lines of code which are (almost) identical. They work
in vendor's kernel and fail in mainline.
This indicates that the
Hi Arokux,
Allan already pointed on timing issue. If you compare bad and working
logs you will see that interval on bad log is match more shorter. On my
expiriance with other wifi adapter it is critical. Beside, it has
nothing todo with wifi at all.
In many cases usb controller insight of adapter
Hi Oleksij,
On Sun, Sep 29, 2013 at 10:01 PM, Oleksij Rempel li...@rempel-privat.de wrote:
Hi Arokux,
Allan already pointed on timing issue. If you compare bad and working
logs you will see that interval on bad log is match more shorter. On my
expiriance with other wifi adapter it is
Dear Alan,
I don't know. Did you run all these tests on the same computer?
Yes, it is a single board computer, see image here:
http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/A10_device_a1000_inside.jpg
WLAN Adapter is left at the bottom.
What happens if you back-port your
On Sun, 29 Sep 2013, Arokux X wrote:
What happens if you back-port your glue driver to the vendor's kernel?
I have now 200 lines of code which are (almost) identical. They work
in vendor's kernel and fail in mainline.
This indicates that the problem isn't in your glue driver, but is
On Mon, 23 Sep 2013, Arokux X wrote:
Hi,
recently I was working on porting EHCI HCD bus glue driver from the
vendors kernel tree to the mainline [1]. I've got the storage (USB
stick and USB external hard drive) working and was happy. However it
does not work completely. Specifically
Hi,
recently I was working on porting EHCI HCD bus glue driver from the
vendors kernel tree to the mainline [1]. I've got the storage (USB
stick and USB external hard drive) working and was happy. However it
does not work completely. Specifically something goes wrong if WiFi
module is talked to.
14 matches
Mail list logo
