Re: usb/92403: [uplcom] [patch] uplcom.c needs new entry for 4.00 revision of Prolific chipset

2007-07-06 Thread Mark Linimon
Synopsis: [uplcom] [patch] uplcom.c needs new entry for 4.00 revision of Prolific chipset Responsible-Changed-From-To: freebsd-usb->imp Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jul 6 08:24:22 UTC 2007 Responsible-Changed-Why: imp committed the patch. http://www.freebsd.

Re: usb/92403: [uplcom] [patch] uplcom.c needs new entry for 4.00 revision of Prolific chipset

2007-07-01 Thread Warner Losh
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

Re: uplcom.c

2006-06-14 Thread Ulrich Spoerlein
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 th

Re: uplcom.c

2006-06-13 Thread Hans Petter Selasky
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 su

Re: uplcom.c

2006-06-12 Thread Hans Petter Selasky
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_INTE

Re: uplcom.c

2006-06-12 Thread Ulrich Spoerlein
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

uplcom.c

2006-06-11 Thread Hans Petter Selasky
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 "uplco

Re: usb/92403: uplcom.c needs new entry for 4.00 revision of Prolific chipset

2006-01-27 Thread Marcin Gryszkalis
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:

Re: usb/92403: uplcom.c needs new entry for 4.00 revision of Prolific chipset

2006-01-26 Thread M. Warner Losh
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:

usb/92403: uplcom.c needs new entry for 4.00 revision of Prolific chipset

2006-01-26 Thread Marcin Gryszkalis
>Number: 92403 >Category: usb >Synopsis: uplcom.c needs new entry for 4.00 revision of Prolific chipset >Confidential: no >Severity: non-critical >Priority: medium >Responsible:freebsd-usb >State: open >Quarter: