Bekijk de volledige versie : PL2303 module backport from 2.6.8 to 2.4.20
Hi. I've got a PL2303(X) adaptor which didn't work with any 2.4.X kernels.
(There seem to be different chipsets under this name which are nonetheless incompatible to one another - the 2.4.X kernel holds support for just one of them)
However the 2.6.X kernel modules worked just fine so I backported the driver from 2.6.8 to 2.4.20 and wonder if there's anybody else with the same problem interested in the patch/modified driver files.
yes, everybody is interested. Post it.
Well then:
http://graphics.cs.uni-sb.de/~grsch/pl2303.patch
Have fun :)
Hi Folks.
It seems that the device that's perfectly working on a wl500g doesn't cooperate with my new wl500g deluxe. In fact, I get a "unable to get device descriptor" when I plug it and the green LED on my hub only flashes shortly before staying dark. (usually lit up even without the driver loaded ;) )
I suspect that the incompatibility has got something to do with the fact that the deluxe has got USB2.0 while the wl500g only has got USB1.1 .
I gave my adaptre away along with the wl500g since a friend of mine needed it but I lacked another machine with USB2.0 to verify... so - just out of curiosity: can anyone confirm this incompatibility with either ehci-hcd or USB2.0 as such and has anyone succeeded plugging adaptres with different chipsets to the deluxe he'd recommend?
kodomo, small question regarding your patch - which sources you've used to perform diff? This is not against 1.9.2.7 kernel...
As for your problem - please try using it without a hub. Also, usb 1.1 devices are handled by uhci, so you could try compiling alternate driver (as there are two in the kernel).
Well then:
http://graphics.cs.uni-sb.de/~grsch/pl2303.patch
Have fun :)
Can you post the full files? I can't find a suitable base version for you patch to apply cleanly to.
-- Rod
kodomo, small question regarding your patch - which sources you've used to perform diff? This is not against 1.9.2.7 kernel...
As for your problem - please try using it without a hub. Also, usb 1.1 devices are handled by uhci, so you could try compiling alternate driver (as there are two in the kernel).
The patches are against linux kernel 2.4.20 (worked against vanilla as well as the one in openwrt stable)
- I don't think that the hub's the problem, as it worked with the hub though I could try (have to ask the person I gave it to though and he's gone for about 2 weeks - so this could take a while ;) )
- it was working perfectly on my /wl500g/ but is not on the /wl500g deluxe/, which has usb 2.0 (as to my knowledge there's only ehci for usb 2.0)
- I don't think that the problem's with the driver itself as the usb system fails to get the device identified and rejects it way before the driver could be loaded.
Here are the patches again together with the plain files. :)
The patches are against linux kernel 2.4.20 (worked against vanilla as well as the one in openwrt stable)
- I don't think that the hub's the problem, as it worked with the hub though I could try (have to ask the person I gave it to though and he's gone for about 2 weeks - so this could take a while ;) )
Try using it wthout hub, as hubs are often causing problems. This could be just hub incompatibility of some kind. wl500g uses ohci for usb 1.1, wl500gx - uhci.
- it was working perfectly on my /wl500g/ but is not on the /wl500g deluxe/, which has usb 2.0 (as to my knowledge there's only ehci for usb 2.0)
ehci handles usb 2.0 devices only, 1.1 devices are handled by uhci. Internally usb 2.0 controllers have 2 usb hosts (2.0 and 1.1) and MUX which connects ports to the correct host.
ehci handles usb 2.0 devices only, 1.1 devices are handled by uhci. Internally usb 2.0 controllers have 2 usb hosts (2.0 and 1.1) and MUX which connects ports to the correct host.
Now this would be a /very/ good reason for it not to work, since I didn't compile uhci support into my deluxe kernel *g* Thus all other devices connected to the hub were (by coincidence) USB2.0 compatible, while the said adaptre only supported 1.1. Thanks :) . This should solve my problem.
Oleg,
Here is the patch in the right format for your firmware build.
-- Rod
Hi.
If anyone's interested, I've re-ported the driver from 2.6.12.3 to 2.4.30 (the old port was hackish and lacking some functionality. The 2.6.12.3 version seems to be working out fine.
Randale91
24-10-2005, 10:33
Does anybody have a port for kernel 2.4.20 ?
Thanks a lot.
Gabriel
@kodomo
I am using your driver with a Kernel 2.4.33 pre1. I attached a Digitus USB1.1 Adapter and everything works great.
I have this messages in my dmesg file:
host/usb-uhci.c: ENXIO 40408280, flags 0, urb 810e2ee0, burb 810e2ee0
pl2303.c: pl2303_read_int_callback - usb_submit_urb failed with result -6
Any serious problem? I am using the normal UHCI driver in the kernel. Should I use the UHCI JE Driver?
Thanks,
Madman
When I use the UHCI JE Driver I get the following error, but it works...
pl2303.c: pl2303_read_int_callback - usb_submit_urb failed with result -19
Any ideas? Is it because of USB2.0 and USB1.1 mix?
Nobody knows, what could be the problem?
-Madman
puppinoo
21-05-2006, 12:52
hi,
I have a Asus wl-500g DLX with OpenWRT RC5 installed. I bought a pl2303 based Serial to USB adapter to use with a rs232 smart card reader.
I installed all needed pkgs from ipkg repository. Here are the intersted modules loaded:
pl2303 12552 0
usbserial 23868 0 [pl2303]
usb-ohci 19204 0 (unused)
printer 9788 0 (unused)
usb-storage 65328 1
scsi_mod 70488 3 [usb-storage sg sd_mod]
uhci 30164 0 (unused)
usbcore 74792 1 [pl2303 usbserial usb-ohci printer usb-storage uhci]
Here's my lsusb
lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0c76:0005 JMTek, LLC. USBdisk
Bus 001 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
It seems to be seen correctly but when i try it to use with my reader my dmesg gives:
pl2303.c: pl2303_read_int_callback - usb_submit_urb failed with result -19
pl2303.c: pl2303_read_int_callback - usb_submit_urb failed with result -19
pl2303.c: pl2303_read_int_callback - usb_submit_urb failed with result -19
...etc...
...and the smart card reader soft gives me a Bind error: port already in use error. (tried with and withoput other usb devices plugged on the second port)
Tried with and without USB2..but always the same result.
Can anyuone help me?
Thanks and bye all.
Pino.
dreamlayers
24-07-2009, 19:04
The pl2303 driver has been backported from 2.6.24.1 to 2.4.36.3. I got pl2303.c and pl2303.h from the latest 2.4 kernel (2.4.37.3 (http://www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.37.3.tar.bz2)), and I simply replaced the files in the kernel source with those. The resulting pl2303 module seems to work perfectly. The onlcr stty option works, and I can perform an interactive login via the port. I don't see any errors in dmesg output.
I'm using Oleg's firmware 1.9.2.7-10
Edit: You can download that module I compiled (http://drop.io/dreamlayers/asset/pl2303-2-6-24-1-for-oleg-1-9-2-7-10-gz).
theMIROn
24-07-2009, 19:20
Take a look at 1.9.2.7-d (http://wl500g.googlecode.com) firmware, based on Oleg's 1.9.2.7-10 with kernel 2.4.37.3, busybox, drivers, etc updated and improved