USB Driver for PL2303 serial adpater

@MigthyMax

Quote:Inside the file itself. It has a huge commented section at the top with very thorough documentation.

Best regards,

Niels

What term program works with OS 4?

@tekmageQuote:

I don't have a list but about 10 years ago i tested alot of them and the one i wanted to work did not.
That was Ncomm.
I found surprisingly few alternatives that works that was not crap.

I settled with "term" in the end https://aminet.net/package/comm/term/Term

It was good but for unknown reasons for me the fonts supplied in that archive did not work with os4 and leads to a crash. (atleast 10 years ago)
Someone fixed the fonts with https://aminet.net/package/text/font/Typeface124 and gave a copy to me but it was also possible to run term if the fonts directory in the archive is renamed/deleted.(or possibly change used fonts in the prefs file)

I grabbed term 4.8, renamed the fonts due and I get the upload icon but no window.

Any have tips to get it working?

I did notice that version 4.7 is on Aminet with full source....

Cheers,
Bill

@tekmage

For me it was the same, I think Term was hiding on its own Screen in background. So just toggle through the screens.

You can change the behavior of Term in the setting to let it open its window on a public screen, like the workbench.

I found one of my devices is:

- Class 0x00/0x00 device (UsbRawFunction: 0x53B60020)
Hub : 0x6ff90dc0 port 3 (port path 1/1/3)
Speed : Full (12Mb/s) [1]
Status : available / active
Locks : 1/2 (Usr/Sys)
Device Descriptor:
.dd_USBVer: 0x0110
.dd_Class: 0x00
.dd_Subclass: 0x00
.dd_Protocol: 0x00
.dd_MaxPacketSize0: 0x40
.dd_VendorID: 0x0557
.dd_Product: 0x2008
.dd_DevVer: 0x0300
.dd_ManufacturerStr: 0x01 ("Prolific Technology Inc. ")
.dd_ProductStr: 0x02 ("USB-Serial Controller D")
.dd_SerialStr: 0x00 ("")
.dd_NumConfigs: 1

The previously published beta is not binding to this device.

Cheers,
Bill

@tekmage

If you can access dropbox try download this fonts archive
Term Fonts

@tekmage

A class 0x00/0x00 device has its class type specified at an Interface level. So you should probably also include the Interfaces listed under the device in the output where you took the device information from.

@tekmage

For that device you need an adopted pl2303.fdclass (It's a text file)

Just change the VENDOR and PRODUCT entries os that the file content looks like this:



With that file the driver should pick up your device and the than everything
works as expected/hoped a device will be register in os with the name "pl2303.device".

@graff

Hi Thomas Graff, I'm assume you are the author of the USB stack?

If so you might answer me the following question:

The driver is heavily bases/inspired on the linux driver, which supports a variety of usb device (product/vendor) combinations.

As long I understand it I need for each product/vendor combination a fdclass file? Is there a way to group them within a sub drawer or can a fdclass file contain multiples entries?

Max

@MigthyMax
Yup, that I am.

Yeah, its a use case I've not had in mind with the fdclass files, so there's no such feature currently.
I definitely should add that as an alternative to the VENDOR and PRODUCT properties so a list of vendor/product pairs can be specified. I am, however, currently out of spare time until end of June, so unfortunately I can't jump in with a quick fix right now.

@graff

Even a solution for end of June, would be in Amiga time measurement an immeasurable of warp 20

Would it make sense to allow an override of VENDOR and PRODUCT fields via ENV at the stack level? I'm thinking of the future, so users can try to connect existing drivers to new HW if the code is not open.

Thanks,
Bill Borsari