From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 14 17:41:11 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E695D16A402 for ; Mon, 14 May 2007 17:41:10 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id A11D713C4AD for ; Mon, 14 May 2007 17:41:10 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id d23so422459and for ; Mon, 14 May 2007 10:41:10 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ioho439IvCtG1KwpYs+eHoLlUdWoCMEV8hKVmB6kAAfssac/HnmhhQCTCBgDtp6i8D7XsXEK6gGpAKPds8ZFHn5dMcEJP6NilLiY/jHjv5ctuM7ETFbctfnzRqoyaR0+ZfkhvWfc3IgCG7dU1cUAEy/Ho24YVQHwZR4GZVFU4LM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Oj2CUvEBhxHW9QK8JWdWCX/nopNk3Qh7DFrFX8HWZHv6jl30PD6WNxIe2zDZeTik3vqWSoU1zli2dmfkS47rt3iKa1l8jb2wPqbH3SfG7v3xfL0BbcJjnms9osQrfO+rWdNTZessBY5OVT/yh0GJGlhLiEmePWzXIzyh9HxrT5k= Received: by 10.100.31.2 with SMTP id e2mr4692779ane.1179164469627; Mon, 14 May 2007 10:41:09 -0700 (PDT) Received: by 10.100.111.13 with HTTP; Mon, 14 May 2007 10:41:09 -0700 (PDT) Message-ID: Date: Mon, 14 May 2007 10:41:09 -0700 From: "Maksim Yevmenkin" To: "Stefan `Sec` Zehl" In-Reply-To: <20070514082040.GB24803@ice.42.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070513140148.GA24803@ice.42.org> <20070514082040.GB24803@ice.42.org> Cc: freebsd-bluetooth@freebsd.org Subject: Re: send something TO a hid device X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2007 17:41:11 -0000 [...] > > >The keypad part works ok with bthidd (some special keys don't yet send > > >keycodes, but that should be easily fixable). > > ok. patches are welcome. > > At the moment I am trying to convert the hid report descriptor to see > wether there is a bug in the FreeBSD parser or the descriptor. I have > found only a windows tool which didn't really work, so I am searching > for a spec to do it myself (in perl). From what I've seen, this > shouldn't be too difficult. how about posting descriptor here in hex form, i.e. the same form you put it into bthidd.conf? > > it depends. what are you planning to do with the lcd display? also > > would be nice to have hid descriptor dump (i assume hid reports are > > used to send information to the pad). > > So far not. The information I got was from a Linux patch which just > assembles raw packets (probably gained by sniffing). When I have a text > version of the descriptor, I can tell you more about that. > > If it isn't in that descriptor, I will look into producing an updated > descriptor, but from what I've seen, I'm not sure this will be easy. > > [...] > > local unix or inet (on 127.0.0.1) is the way to go imo. putting stuff > > into vkbd(4) is a bad idea, because one side (keyboard) of vkbd is > > grabbed by the kernel another (device) is grabbed by the bthidd(8) and > > there is no easy way to stuff extra data into vkbd(4). > > > > implementing a "pass-through" type of interface in bthidd(8) makes > > more sense, however, there is aways a risk that someone will use > > "pass-through" interface incorrectly and will, for example, mess with > > keyboard lights or something. > > > > i'm not a really big fan of displays on keyboards, but someone might > > find them useful in an "eye candy" soft of way :) > > > > the "pass-through" interface idea might have some value, though. i'm > > hoping for "smart" hid devices, i.e. keyboards with programmable > > layouts, etc. > > The problem is, I have abolutely no idea how to implement a device, so > thats why I suggested a local socket. The problem with that is, that we > need some kind of "ad hoc" protocol to select which device to talk to > (as bthidd can have multiple connections at once, iirc). I am planning > on a simple linewise text-based thing, but I'm not completely sure on > that yet. again, you do not really need a device. socket will do just fine. local client(s) can connect to the bthidd and identify which hid device it (they) will be taking to, i.e. tell hid device's bd_addr. then client(s) simply sends hid reports to the bthidd via socket and it will relay them the hid device via bluetooth. thanks, max