It's more convenient to refer to a pin by the name that's printed right
on the header itself instead of having to count the pin number.
Signed-off-by: Hrishikesh Tapaswi <hrishikesh195@yahoo.com>
In the sysfs i2cDevice implementation, use an ioctl to get the adapter
functionality mask. Prefer SMBus block I/O but if it's not available,
perform read/write calls directly on the file descriptor.
Improve Wiichuck error handling. Add a 1 ms delay between I/O operations
to the Wiichuck; this dramatically improves reliability.
Signed-off-by: Hrishikesh Tapaswi <hrishikesh195@yahoo.com>
If this is anything like the Bebop, then taking off immediately fires the "flying" event, but these events aren't buffered so attaching an event handler afterwards achieves nothing. When I ran the same code for the Bebop (as suggested on the site) it never landed, prompting an emergency connect-with-phone-hammer-buttons scramble. Swapping the event registration with the takeoff method call fixed the problem immediately.
It's more convenient to refer to a pin by the name that's printed right
on the header itself instead of having to count the pin number.
Signed-off-by: Hrishikesh Tapaswi <hrishikesh195@yahoo.com>
In the sysfs i2cDevice implementation, use an ioctl to get the adapter
functionality mask. Prefer SMBus block I/O but if it's not available,
perform read/write calls directly on the file descriptor.
Improve Wiichuck error handling. Add a 1 ms delay between I/O operations
to the Wiichuck; this dramatically improves reliability.
Signed-off-by: Hrishikesh Tapaswi <hrishikesh195@yahoo.com>
If this is anything like the Bebop, then taking off immediately fires the "flying" event, but these events aren't buffered so attaching an event handler afterwards achieves nothing. When I ran the same code for the Bebop (as suggested on the site) it never landed, prompting an emergency connect-with-phone-hammer-buttons scramble. Swapping the event registration with the takeoff method call fixed the problem immediately.
I noticed that the grove LCD screen only has an ASCII/Japanese font table. I need to be able to display accented characters
looking at the data sheet the screen supports up to 8 custom CGRAM characters. I added an API to set those CGRAM characters
as well as a map of common latin 1 characters + emoticons
