Date: Thu, 12 Jul 2007 19:30:39 +0100 From: Rui Paulo <rpaulo@fnop.net> To: Anish Mistry <amistry@am-productions.biz> Cc: freebsd-bluetooth@freebsd.org Subject: Re: HCI - HID proxy Message-ID: <4696734F.4040201@fnop.net> In-Reply-To: <200707121347.29676.amistry@am-productions.biz> References: <469593F2.1040703@fnop.net> <200707121307.38442.amistry@am-productions.biz> <46966301.7060004@fnop.net> <200707121347.29676.amistry@am-productions.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
Anish Mistry wrote:
>> Anyway, if you want to use devd it would be something like:
>>
>> attach 100 {
>> match "vendor" "0x05ac";
>> match "product" "0x1000";
>> action "/usr/bin/ubthid2hci -m 0 $device-name";
>> };
>>
>> And then repeat this for every device that needs to be switched to
>> HCI mode. This has the problem of not being able to switch the
>> device to HID mode because when you try to do that, devd will
>> automatically switch it back to HCI mode if this attach rule is
>> present. I don't think this is a serious issue because the HID mode
>> is normally only needed before the operating system has booted.
>
> Right. Actually that brings up a good point. Is there a way (API)
> that allows us to enable/disable certain devd entries at runtime? If
> not I think that this might be a useful feature. If this was
> available we'd then be able to programmatically disable an entry when
> we want to switch back to HID mode without having to change the
> devd.conf file.
AFAIK, no.
--
Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4696734F.4040201>