On Thu, Mar 19, 2015 at 8:53 AM, Maksim Yevmenkin
<[email protected]> wrote:
> Hello,
>
>> maybe getting closer. bthidd connects and opens control and interrupt
>> channels, and i can see data on the interrupt line.
>
> [...]
>
>> send characters to FIFO
>> # echo "ABEF010231" >> /tmp/ain
>>
>> ...
>> sent data 3
>> sent data 4
>> sent data 7
>> sent data 8
>> sent data 38
>> sent data 29
>> sent data 38
>> sent data 30
>> sent data 31
>> sent data 29
>>
>> this shows up on the client .. simple syslog(LOG_ERR,"%s",data.b);
>>
>> Mar 18 21:23:32 rpidev bthidd[4948]: Opening outbound session for
>> 00:1b:dc:06:94:d3 (new_device=0, reconnect_initiate=0)
>> Mar 18 21:23:32 rpidev kernel: kbd2 at vkbd16
>> Mar 18 21:23:35 rpidev bthidd[4948]:
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^C
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^D
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^G
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^H
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- &
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^]
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- &
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^^
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^_
>> Mar 18 21:23:51 rpidev bthidd[4948]: ¡^BM- ^]
>>
>> I'm guessing I'll have to hook up a display to that machine to see if
>> the virtual keyboard device is working right.
>
> ok. so seems like your data are making it all the way to bthidd(8).
> its good. a couple things
>
> (1) please make sure your hid report is correctly encoded. i don't
> recall all the specifics at this time, but, i'm fairly certain you
> need to actually send two hid reports for each character, i.e. one for
> key being pressed and one for key being released;
>
> (2) with respect to virtual keyboard working, please make sure that
> machine that runs bthidd(8) also has kbdmux(4) loaded. kbdmux(4)
> should be enabled by default in GENERIC, but please double check. if
> its not, please make sure to either kldload kbdmux (you can do it from
> loader.conf), or, compile it into the kernel.
>
>> modified bthidd https://github.com/waitman/bthidd
>
> can you please point me to your modifications?
Hi,
It's not for production use, but if someone comes across this post in
the future maybe save a few minutes when tinkering and
troubleshooting.
I changed the Makefile so it will 'more easily' build as a standalone
outside /usr/src
I added the syslog line around ln 324 in server.c - just wanted to see
that data was coming in.
do {
len = read(fd, &data, to_read);
syslog(LOG_ERR,"%s",data.b);
} while (len < 0 && errno == EINTR);
>
> [...]
>
>> I'm going to have to go through everything from the beginning and make
>> sure everything is correct.
>
> i suspect that your hid reports are not quite correct.
>
>> Here's what I did to generate bthidd.conf - maybe I can make a man
>> page for bthidd.conf? There's a note on the bthidd man page about
>> needing a bthidd.conf man page. (but maybe there's a better way than
>> the way I did it?)
>
> i think the way you did it is correct. bthidd.conf contains entries
> produced by "bthidcontrol query" command. normally it is not needed to
> do modify entries in any way.
Ok great i'll create a man page for bthidd.conf
>
>> also, I'll try the manual restart of bluetooth stack and let you know
>> if that works.
>
> you really should not need to do anything manually. everything should
> be started automatically (from devd.conf) when ng_ubt(4) device
> attaches.
>
Sorry, I was referring to your previous message about trying to
restart bluetooth 'manually' to see if it works.
> thanks,
> max
--
Waitman Gobble
Los Altos California USA
510-830-7975
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "[email protected]"
