Haiku Activity & Contract Report, March 2024 | Haiku Project

This report covers hrev57616 through hrev57679.

apl improved language code handling in HaikuDepot.

This is a companion discussion topic for the original entry at https://www.haiku-os.org/blog/waddlesplash/2024-04-12_haiku_activity_contract_report_march_2024


oh, great!:smiling_face_with_three_hearts::smiling_face_with_three_hearts::smiling_face_with_three_hearts:

Great work to everyone involved.
Very good to have a font-variants show up now, properly!
Special thank to Korli!

The Webcam driver does now connect and can be initialized, do to some work of X512.
But not to be useful for real use, is there some code missing, or is there just no application using it?

Again thanks for all your work!

Once the BT stack refactors are done, what work would be necessary to support integrated BT in Intel wireless adapters (e.g. AX1xx, AX2xx, etc.)?

Ahoy devs,

Thank you for your efforts to fix/improve functions of Haiku and services which can be used on it !..

Get launched!

Kudos !


The bluetooth stack only has drivers for usb bluetooth adapters. Other drivers will be needed for each of these.

And drivers will be needed on the oher side as well, for each type of bluetooth device.

But it’s better to start from solid ground.

Thank you everyone for your hard work.

Actually, so far as I know, Intel WiFi cards pretty much all provide a USB Bluetooth interface (while the WiFi interface is on PCI.) However, in order for the Bluetooth support to work, oftentimes the WiFi driver must configure the WiFi hardware somehow to allow the Bluetooth hardware to share the radios, or something like that. I’m not sure the OpenBSD drivers do this. Some of the FreeBSD drivers at least have code that attempts it.


OpenBSD seems to have previously used the NetBSD BT stack, but has removed it since 2014:

However, it is still possible to send BT audio in a roundabout way on OpenBSD:

That Creative device is just a USB Audio device that then sends Bluetooth internally, I think. So it doesn’t count here.

Looking around a bit, the iwm and iwx drivers do not appear to have “Bluetooth coexistence” configuration code on either FreeBSD or OpenBSD. There are various definitions related to it in the hardware constants definition header, but they’re unused.

(The iwn driver, aka iprowifi4965 on Haiku, does configure Bluetooth coexistence.)

Correct. I suppose it’s a USB2 device like the W3x I tried (and the W5) so it’s not an option atm.


then for me twice the chance would be to have a BT service, as

If I would have such a combo of WiFi / BT in my laptop, but I have a
DELL BT module which was made available via USB by Dell engineers, at least I could find it via
listusb only

~> listusb
0000:0000 /dev/bus/usb/0/hub “HAIKU Inc.” “XHCI RootHub” ver. 0300
046d:c52b /dev/bus/usb/1/0/1/0 “Logitech, Inc.” “Unifying Receiver” ver. 1201
046d:c52b /dev/bus/usb/1/0/1/1 “Logitech, Inc.” “Unifying Receiver” ver. 1201
05e3:0608 /dev/bus/usb/1/0/1/hub “Genesys Logic, Inc.” “Hub” ver. 7764
413c:8197 /dev/bus/usb/1/0/3 “Dell Computer Corp.” “BCM20702A0 Bluetooth Module” ver. 0112
0c45:648b /dev/bus/usb/1/0/4 “Microdia” “Integrated Webcam” ver. 2807
8087:0024 /dev/bus/usb/1/0/hub “Intel Corp.” “Integrated Rate Matching Hub” ver. 0000
0000:0000 /dev/bus/usb/1/hub “HAIKU Inc.” “EHCI RootHub” ver. 0200
0781:a7c1 /dev/bus/usb/2/0/6 “SanDisk Corp.” “Storage device (SD card reader)” ver. 9412
8087:0024 /dev/bus/usb/2/0/hub “Intel Corp.” “Integrated Rate Matching Hub” ver. 0000
0000:0000 /dev/bus/usb/2/hub “HAIKU Inc.” “EHCI RootHub” ver. 0200


I cannot select any BT device …
I know the status of actual BT stack, incomplete, but
this way it is a USB deviceit should be discoverable, shouldn’t it ?