55503f0e52
There is already samsung-a3ulte in community, and the devices actually share the same kernel, device tree, and basically everything except firmware. We just need separate firmware packages because Samsung uses different secure boot certificates on a3lte and a3ulte. They also share the same wiki page which suggests installation using the pre-built images now, so having pre-built images only for samsung-a3ulte is quite confusing for users. The situation is similar as for samsung-a5ulte and samsung-a5lte which also are both in community already.
20 lines
1 KiB
Text
20 lines
1 KiB
Text
#
|
|
# There is a weird probe issue if both MSM DRM and the panel driver are built
|
|
# as modules: When MSM DRM is loaded it registers the DSI bus for the panel.
|
|
# At this point the panel is not loaded yet, so the kernel sends an uevent
|
|
# to userspace to load the necessary panel module.
|
|
#
|
|
# This causes some delay until the panel module is loaded, so MSM DRM fails to
|
|
# probe temporarily and returns -EPROBE_DEFER (to request probing again later).
|
|
# Unfortunately this will also unregister the DSI bus for the panel, and the
|
|
# kernel will not try probing MSM DRM + panel again until some other (slow)
|
|
# driver loads after MSM DRM.
|
|
#
|
|
# Usually WCNSS (WiFi/BT) fits that criteria, allowing the display to work.
|
|
# But this does not work if the user decides to exclude proprietary firmware.
|
|
#
|
|
# To avoid this problem we add an explicit soft dependency for MSM DRM
|
|
# on the panel module, so modprobe loads the panel module first and MSM DRM
|
|
# will immediately find the panel it is looking for.
|
|
#
|
|
softdep msm pre: panel-samsung-s6e88a0-ams452ef01
|