Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 09/03/2011 12:22 PM, Bastien Nocera wrote:
> On Sat, 2011-09-03 at 10:10 +0200, Hans de Goede wrote:
 >
>> With that said, you're the Fedora bluetooth maintainer, so you are the
>> boss. The easiest way to make this opt-in, and I think also a good one,
>> is to just move the udev-rules and the hid2hci binary to their own
>> bluez-hid2hci sub-package. People who want to have their hid proxying
>> adapters to actually show up as HCI instead of HID can then do
>> yum install bluez-hid2hci
>>
>> We could even have a %post script doing a
>> "udevadm trigger subsys=to-be-figured-out"
>>
>> To avoid people needing to reboot / unplug the adapter after installing
>> the package. If you think this is a good plan, let me know and I'll implement
>> it.
>
> Sounds like a good plan to me. Thanks for looking into it.

Ok, the plan has been executed now and the result works for me :)

Jonathan, can you give bluez-4.96-3.fc17 a spin? It should fix your
mouse + keyboard issue.

For those interested in this, the F-16 update is here:
https://admin.fedoraproject.org/updates/bluez-4.96-3.fc16

Regards,

Hans
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux