Sasano,

recently I bought a pair of pcsensor devices from amazon. Wasn't sure if
uthum supported it yet.

Your diff works for me:

dmesg:
uhidev3 at uhub3 port 1 configuration 1 interface 0 "RDing TEMPerV1.2" rev
2.00/0.01 addr 2
uhidev3: iclass 3/1, 1 report id
uthum0 at uhidev3 reportid 1
uhidev4 at uhub3 port 1 configuration 1 interface 1 "RDing TEMPerV1.2" rev
2.00/0.01 addr 2
uhidev4: iclass 3/1
uthum1 at uhidev4
uthum1: type ds75/12bit (temperature)

sysctl hw:
hw.sensors.uthum1.temp0=29.12 degC (inner)

usbdevs -vd:
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x8086), rev 1.00
  uhub3
 port 1 addr 2: low speed, power 100 mA, config 1, TEMPerV1.2(0x7401),
RDing(0x0c45), rev 0.01
   uhidev3
   uhidev4
 port 2 powered

Im running -current + uthum-wip.diff
OpenBSD 5.3-current (GENERIC.MP) #1: Mon Mar 25 16:26:44 CST 2013
    r...@host.mynetwork.dev:/usr/src/sys/arch/amd64/compile/GENERIC.MP

-luis



On Sat, Mar 16, 2013 at 9:24 AM, SASANO Takayoshi <u...@mx5.nisiq.net> wrote:

> Hi,
>
> I bought a PC Sensor's gold TEMPer
> (http://www.pcsensor.com/index.php?_a=product&product_id=41), but this is
> completely different from TEMPer series which handled by uthum(4) driver.
>
> This is also USB HID device (one keyboard and one mouse) but temperature
> data comes from interrupt pipe, not control pipe.
>
> Details are described in TEMPered's wiki page [1]. And I hope my lsusb
> log [2] and USB analyzer log (attached to Windows) [3] helps.
>
> I wrote a patch (work-in-progress, and for OpenBSD 5.2) for uthum(4) to
> test my device [4]. But I have a question, which is better to expand
> uthum(4) driver or write a new one?
>
> [1] https://github.com/edorfaus/TEMPered/wiki/0C45%3A7401
> [2] http://www2192ue.sakura.ne.jp/~uaa/gomitext/2013/20130224/temp.txt
> [3] http://www2192ue.sakura.ne.jp/~uaa/gomitext/2013/20130307/temper.txt
> [4]
> http://www2192ue.sakura.ne.jp/~uaa/gomitext/2013/20130315/uthum-wip.diff
>
> Thanks,
> ----
> SASANO Takayoshi <u...@mx5.nisiq.net>
>
>

Reply via email to