| Summary: | net-wireless/bluez - add USE=hidd | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Another Mortal <a.m> |
| Component: | Current packages | Assignee: | Pacho Ramos <pacho> |
| Status: | VERIFIED WONTFIX | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Add hidd USE flag and optionally --enable-hidd | ||
hidd option has been completely dropped by upstream since bluez-4.101, then, I wouldn't add an option that, in next bump, people will lose again Facts:
(1) --enable-hidd *is* available in 4.101
[in other words, the comment on this being dropped "since" 4.101
feels misleading; although you probably meant _after_ not since]
(2) 4.101 is the only version available in portage
Questions:
(1) when is the next bump expected?
(Upstream is already at 5.3)
(2) what's your suggestion for using a bluetooth keyboard
for entering a passphrase in initramfs?
(In reply to comment #2) > (1) when is the next bump expected? > (Upstream is already at 5.3) > It's handled in bug 452162 > (2) what's your suggestion for using a bluetooth keyboard > for entering a passphrase in initramfs? Would be better if you could ask to upstream (probably in upstream mailing list) about how is this handled now in bluez-5 |
Created attachment 338886 [details] Add hidd USE flag and optionally --enable-hidd I want to be able to use my bluetooth keyboard in early boot (i.e. to enter a disk encryption password in initramfs), and I really don't want to start dbus and bluetoothd just for this, when hidd (with a little help from hciconfig and hcitool) is fully adequate to handle the situation. I'm attaching a patch with the rather minimal changes to make this happen. (I realize that hidd is deemed obsolate, but I'm seriously considering to make a hidd-only build of bluez, since that's the _only_ bluetooth profile I regularly use. Then, I'll be finally be able to ditch dbus altogether. When, I have some time over, that is... ;-))) Thanks for you kind consideration!