Re: some issues with the USB tree

2007-01-19 Thread Hans Petter Selasky
On Friday 19 January 2007 06:28, Kip Macy wrote: Could you connect a umass device in console mode, and do some dd benchmarking? I'll have to dig out a USB hard drive to make any meaningful measurements, the write speed on my flash drive is the same as in HEAD - a fairly paltry

Re: no data from USB wireless mouse

2007-01-19 Thread Hans Petter Selasky
On Friday 19 January 2007 07:55, Andrew Tamm wrote: I am having no success at all in getting a Microsoft Optical Wireless Desktop Pro mouse to work in FreeBSD 6.2-RC2. The kernel sees it as: ums0: Microsoft Microsoft Wireless Optical Desktop ums0: 5 buttons and Z dir and a TILT dir. cat

Re: usb/108097: [usbgen] [patch] ADMtek 851X USB-to-LAN adapter

2007-01-19 Thread Volker
Hans Petter, On 01/19/07 15:34, Hans Petter Selasky wrote: Could you get the revision number for this chip. For example what does usbdevs -v output? usbdevs -v says: port 4 addr 8: full speed, power 144 mA, config 1, ADM8515 USB To LAN NIC(0x8515), ADMTEK(0x0a46), rev 1.01 PS: I have

Re: no data from USB wireless mouse

2007-01-19 Thread Aleksey Salow
On 1/19/07, Andrew Tamm [EMAIL PROTECTED] wrote: Done, now i'm not getting the status=6 when I cat the usm1, and the mouse still does not work. ''ums_open'' appears when you cat the usm1, but nothing else on mouse move or click. The other wired mouse ( also an Intellimouse ) giving a copius

Re: no data from USB wireless mouse

2007-01-19 Thread Andrew Tamm
Hans Petter Selasky wrote: On Friday 19 January 2007 16:53, Andrew Tamm wrote: Hans Petter Selasky wrote: I am having no success at all in getting a Microsoft Optical Wireless Desktop Pro mouse to work in FreeBSD 6.2-RC2. The kernel sees it as: ums0: Microsoft Microsoft Wireless Optical

Re: usb/93408

2007-01-19 Thread Joerg Wunsch
The following reply was made to PR usb/93408; it has been noted by GNATS. From: Joerg Wunsch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: Re: usb/93408 Date: Fri, 19 Jan 2007 23:32:51 +0100 Is this perhaps a duplicate for i386/104678? See the audit trail there. -- cheers, Jorg