* When 'jack' is selected using the property, first PCM card that has name
'Headphones' is used.
When 'dac' is selected, first PCM card that is not named 'Headphones',
'vc4hdmi0', or 'vc4hdmi1' is used.
* It's always been intended that changing audio output devices requires
a reboot. Get the PCM card and device once when the HAL is initialized.
Might save a few ms on start_output_stream.
* It's always been intended that changing audio output devices requires
a reboot. Get the ALSA device once when the HAL is initialized.
Might save a few ms on start_output_stream.
* Pi 5 has independent cards for DSI-0, DSI-1, DPI, and VEC.
In theory we could have two DSI displays so add two more entries.
avc: denied { ioctl } for path="/dev/dri/card2" dev="tmpfs" ino=749 ioctlcmd=0x64bc scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
* Doesn't do anything if BOARD_HAVE_BLUETOOTH_BCM is not set.
* Bluetooth device name is parsed from 'ro.product.model' if no default
is provided using 'bluetooth.device.default_name' property.
* Drop Raspberry from model as some hardware information applications
display it after the manufacturer/brand and we'll end up with duplicate
Raspberry in the device name.
* PRODUCT_RELEASE_NAME is long gone.
* Some hardware information applications use this so set actual hardware
platform name.
* Historic reason why this was set to rpi is that this allowed to use same
HALs on rpi3/rpi4 when they were commonized. 'ro.board.platform' this sets
is used in the legacy module load order.
https://android.googlesource.com/platform/hardware/libhardware/+/refs/tags/android-15.0.0_r20/modules/README.android
This has no use with modern HIDL/AIDL/APEX HALs. For legacy HALs name can
be implicitly set using system properties (e.g. 'ro.hardware.audio.primary'
that's still relevant).
* PRODUCT_FULL_TREBLE gets set on PRODUCT_SHIPPING_API_LEVEL >= 26.
There's no need to override it.
2b32469c47
* BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED gets set with PRODUCT_FULL_TREBLE.
c227ce7c25
* This will create a flashable image that is 15569256448 bytes.
* I checked several 16GB sdcards and USB storage devices and the
actual byte size ranged from 15646851072 to 16008609792.
* This gets built as a dependency to minigbm gbm_mesa_driver's
libgbm_mesa_wrapper but add it here for completeness.
* Move Mesa gbm libraries under separate section.
