Hi Johan, >-----Original Message----- >From: Johan Hedberg [mailto:johan.hedberg@xxxxxxxxx] >Sent: Thursday, September 02, 2010 3:51 PM >> I attached slightly updated patches. >Thanks. However, the kernel patch and new ioctl will need >comments at least from Marcel. Once we add an ioctl we're >stuck with it for quite some time and have to maintain it, no >matter what kind of newer/better kernel-userspace interfaces >we come up with. So the choice of accepting a new ioctl isn't so easy. Then, wait for Marcel's comment. >One thing that you'd definitely need to fix in your patches is >to keep at least the same level of support that the current >BlueZ has with kernels that don't have the new ioctl. Right >now your patch would make legacy pairing fail in such cases >which is not acceptable. Only with a major version change >(5.x) would it be possible to consider requiring a newer >kernel version in order to have essential functionality in place. I updated the bluez patch. Now paring will not fail due to not compatible kernel api. Regards, /Waldek
Attachment:
0001-BT_SECURITY_HIGH-requires-16-digit-pin-code.patch
Description: 0001-BT_SECURITY_HIGH-requires-16-digit-pin-code.patch
