Thanks. Using some (maybe flawed) logic I deducted that bluetooth
devices should all have product='a12/1/*' so I'll match with that.
Hope this info helps also others reading this later...
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http
On 27 December 2013 09:49, valent.turko...@gmail.com
wrote:
> After adding hotplug troubleshooting on wiki [1] and creating hotplug
> debug script I saw this for two different bluetooth dongles:
>
>
> action='add' product='a12/1/1915' type='224/1/1' interface=''
> action='add' product='a12/1/1915'
sorry for the missing link:
[1] http://wiki.openwrt.org/doc/techref/hotplug#troubleshoot
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
On Fri, Dec 27, 2013 at 12:44 AM, valent.turko...@gmail.com
wrote:
> On Mon, Dec 23, 2013 at 11:48 AM, Yousong Zhou wrote:
>> On 23 December 2013 04:26, valent.turko...@gmail.com
>> wrote:
>>> Hi,
>>> I see that procd is being used by OpenWrt but wiki documentation is
>>> lacking some basic exam
On Mon, Dec 23, 2013 at 11:48 AM, Yousong Zhou wrote:
> On 23 December 2013 04:26, valent.turko...@gmail.com
> wrote:
>> Hi,
>> I see that procd is being used by OpenWrt but wiki documentation is
>> lacking some basic examples how could it be used further by advanced
>> users (not developers).
>>
On 23 December 2013 04:26, valent.turko...@gmail.com
wrote:
> Hi,
> I see that procd is being used by OpenWrt but wiki documentation is
> lacking some basic examples how could it be used further by advanced
> users (not developers).
>
> One use case would be to trigger some action when some usb de
