Re: usb/92403: [uplcom] [patch] uplcom.c needs new entry for 4.00 revision of Prolific chipset
Synopsis: [uplcom] [patch] uplcom.c needs new entry for 4.00 revision of Prolific chipset State-Changed-From-To: open-patched State-Changed-By: imp State-Changed-When: Sun Jul 1 23:13:12 MDT 2007 State-Changed-Why: This seems to work well, and was committed a long time ago. I'll MFC it in my planned mega MFC. Linux uses a better size detection algorithm, but that hasn't been implemented. http://www.freebsd.org/cgi/query-pr.cgi?pr=92403 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: uplcom.c
On Tuesday 13 June 2006 18:06, Ulrich Spoerlein wrote: Hans Petter Selasky wrote: On Monday 12 June 2006 21:39, Ulrich Spoerlein wrote: Hans Petter Selasky wrote: UPLCOM_INTR_INTERVAL I have such a device and am using it. The question is, what is that option supposed to do? It sets how often the USB host controller should query the USB device for an interrupt packet. I might be making a fool out of myself, but how come you have to query for an interrupt? Shouldn't and interrupt fire itself? Besides, since this is used for serial devices (=115200 bit/s) where's the point in tuning? That is what I thought too. The USB descriptors provided with the device already give the default interrupt interval, so there should not be any need for tuning. Could you have done some testing of the new driver? Maybe not right now, but in one or two weeks. I will provide you with a nice tarball, that you can install on FreeBSD 6/7. Sure thing, just post patches to the usual mailing lists or email me directly. Btw, do you know if the NetBSD folks are interested in your USB stack? I think it's a shame if we get three (four) BSDs with three different USB stacks. There are already too few people working on it ... I don't know. We'll see when my work is finished. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: uplcom.c
On Monday 12 June 2006 21:39, Ulrich Spoerlein wrote: Hans Petter Selasky wrote: Hi, I am currently working on converting uplcom.c to my new USB API. In that regard I have a question: Is anyone using option UPLCOM_INTR_INTERVAL or sysctl hw.usb.uplcom.interval, or can this be left to the default interrupt interval? /* * The uplcom.c driver supports several USB-to-RS232 serial adapters * driven by Prolific PL-2303, PL-2303X and probably PL-2303HX USB-to-RS232 * bridge chip. The adapters are sold under many different brand * names. */ I have such a device and am using it. The question is, what is that option supposed to do? It sets how often the USB host controller should query the USB device for an interrupt packet. Could you have done some testing of the new driver? Maybe not right now, but in one or two weeks. I will provide you with a nice tarball, that you can install on FreeBSD 6/7. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
uplcom.c
Hi, I am currently working on converting uplcom.c to my new USB API. In that regard I have a question: Is anyone using option UPLCOM_INTR_INTERVAL or sysctl hw.usb.uplcom.interval, or can this be left to the default interrupt interval? /* * The uplcom.c driver supports several USB-to-RS232 serial adapters * driven by Prolific PL-2303, PL-2303X and probably PL-2303HX USB-to-RS232 * bridge chip. The adapters are sold under many different brand * names. */ --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/92403: uplcom.c needs new entry for 4.00 revision of Prolific chipset
The following reply was made to PR usb/92403; it has been noted by GNATS. From: Marcin Gryszkalis [EMAIL PROTECTED] To: M. Warner Losh [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: usb/92403: uplcom.c needs new entry for 4.00 revision of Prolific chipset Date: Fri, 27 Jan 2006 16:12:40 +0100 I tested the patch and it works well. I think I found somewhere that chip version can ve recognized from some other internal parameter (buffer size o something) - but this solution seems to be sufficient. Is there any chance to have that MFCed to 6-stable? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/92403: uplcom.c needs new entry for 4.00 revision of Prolific chipset
The following reply was made to PR usb/92403; it has been noted by GNATS.
From: M. Warner Losh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: usb/92403: uplcom.c needs new entry for 4.00 revision of
Prolific chipset
Date: Thu, 26 Jan 2006 22:27:53 -0700 (MST)
Does this work for you?
Warner
Index: uplcom.c
===
RCS file: /home/ncvs/src/sys/dev/usb/uplcom.c,v
retrieving revision 1.30
diff -u -r1.30 uplcom.c
--- uplcom.c 4 Dec 2005 10:06:04 - 1.30
+++ uplcom.c 27 Jan 2006 05:27:12 -
@@ -224,6 +224,9 @@
uint16_tproduct;
int32_t release; /* release is a 16bit entity,
* if -1 is specified we don't care
+* This is a floor value. The table
+* must have newer revs before older
+* revs (and -1 last).
*/
charchiptype;
} uplcom_products [] = {
@@ -320,7 +323,7 @@
for (i = 0; uplcom_products[i].vendor != 0; i++) {
if (uplcom_products[i].vendor == uaa-vendor
uplcom_products[i].product == uaa-product
- (uplcom_products[i].release == uaa-release ||
+ (uplcom_products[i].release = uaa-release ||
uplcom_products[i].release == -1)) {
return (UMATCH_VENDOR_PRODUCT);
}
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
