In order to make it work properly, the fcc unlock script from MM should
also be enabled... This info will be added to the device's wiki page for
now since upstream MM discourages distros from enabling these unlock
scripts by default...

The fbdev backend was removed with Weston 10 which has been out for a
good while now. As such, it doesn't matter whether Xwayland works or not
since Weston won't work at all --- the DRM backend, which is what would
get used instead of fbdev with this removed, won't work on downstream
kernels like the one used by this device.

[ci:ignore-count]
[ci:skip-build]: Already built successfully in CI.

The fbdev backend was removed with Weston 10 which has been out for a
good while now. As such, it doesn't matter whether Xwayland works or not
since Weston won't work at all --- the DRM backend, which is what would
get used instead of fbdev with this removed, won't work on downstream
kernels like the one used by this device.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

There is no dri-backend.so. I don't know if this ever existed. May have
been a typo where the author meant to type drm-backend.so. The DRM
backend should be the default anyway, so just remove it instead of
fixing what may have been a typo.

The fbdev backend was removed with Weston 10 which has been out for a
good while now. This device should be able to use the DRM backend
anyway given that it uses the A64 SoC which also e.g. the PinePhone
uses.

Additionally, the comment about Xwayland being broken contradicts the
actual configuration file where Xwayland actually is being enabled
(xwayland=true), so this shouldn't be causing any regressions even if it
actually is broken.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

The fbdev backend was removed with Weston 10 which has been out for a
good while now. As such, Weston won't work with the downstream port
anyway which is likely where Xwayland supposedly was broken. As such,
remove this unnecessary configuration file.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

Anton Bambura authored 1 year ago and Newbyte committed 1 year ago

We did set these variables, so it is possible to flash boot and root
partitions separately for booting with stock partition table. This
is useful for U-Boot as secondary bootloader. But it's not good for
U-Boot as primary bootloader because the resulting images have boot
and root partitions separated, so users have to create partitions
themselves and this is very confusing.

I'm suggesting to disable it in favor of doing U-Boot as primary
bootloader, this may be harder for users, but it needs to be done
only once, and this way is more fancy and is supported on more
devices than secondary bootloader.

If someone still wants to use this port with U-Boot as secondary
bootloader they can do "pmbootstrap install --split" and
"pmbootstrap export" to get 2 separate partitions to flash.

[ci:skip-build]: Already built successfully in CI.

mulingLHY authored 1 year ago and Alexey Minnekhanov committed 1 year ago

Package venus firmware to fix:
"subsys-pil-tz 1de0000.qcom,venus: venus: Failed to locate venus-v1.mdt"
causing 30 seconds delay on boot.

Svyatoslav Ryhel authored 1 year ago and Newbyte committed 1 year ago

bcm4330 has 2 wifi sdio firmwares, one with IEEE 802.11а support
and one without. One without was missing which caused some
devices to have wireless network issues.

Additionally Oyua specific bluetooth firmware was found and it
is included as well.

Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>

[ci:skip-build]: Already built successfully in CI.

Arnav Singh authored 1 year ago and Newbyte committed 1 year ago

[ci:skip-build]: Already built successfully in CI.

Fiona Klute authored 1 year ago and Newbyte committed 1 year ago

This fixes the USB networking issue, see:
https://patchwork.kernel.org/project/linux-usb/patch/20231218164532.411125-2-mailingradian@gmail.com/

Thanks to Alexey Min to pointing me at the patch!

[ci:skip-build]: Already built successfully in CI.

Fiona Klute authored 1 year ago and Newbyte committed 1 year ago

Fixes #2349. Patches refreshed because some didn't apply when I built
directly from local repo and tried to import them with "git am".

Known issue: NetworkManager fails to assign IP to usb0, I had to
assign it manually to use USB networking.

Jianhua Lu authored 1 year ago and Newbyte committed 1 year ago

[ci:skip-build]: Already built successfully in CI.

Jakko authored 1 year ago and Alexey Minnekhanov committed 1 year ago

- Hide tooltips by workaround (opacity and font size)
- Enable mouse key buttons on onboard keyboard by default (eases
  right-clicking)

Hagen Fritsch authored 1 year ago and Alexey Minnekhanov committed 1 year ago

In the mainline ds2482 onewire kernel driver, active_pullup defaults to
1 which is setting the APU register. This caused the connection to the
ds2784_battery slave to be unstable and flaky. In the AOSP manta project
this flag is set to 0 as well.

This is a device-specific package. The only device that depends on
this, device-nokia-n900, is in community, so let's move it there too.

[ci:skip-build]: already built successfully in CI

This is a device-specific package. No need to keep it in main where it
gets included in stable releases unnecessarily. The only device that
depends on this, device-inet-a33, is in testing, so let's move it there
too.

[ci:skip-build]: already built successfully in CI

Luca Weiss authored 1 year ago and Newbyte committed 1 year ago

Also start squashing the .mdt files into .mbn and provide compatibility
symlinks so old kernels that look for .mdt still find it.

Also move the zap firmware into a device-specific subdirectory.

Symlinks for venus are skipped since that one's not used in any
production branch yet for sm7225.

[ci:skip-build]: Already built successfully in CI.

Jakko authored 1 year ago and Newbyte committed 1 year ago

Dependencies:
- Add dependency "xfce4-screensaver" to provide virtual keyboard at screen
  unlock. As a dependency because several settings need to be implemented to
  integrate it well in LXQt.
- Add dependency "setxkbmap" to make keyboard layout settings work
- Add dependency "upower" to make battery icon in panel work

Recommends:
- Add recommend "pulseaudio" to make sound work
- Add recommend "adwaita-icon-theme" because that's used by xfce4-screensaver
- Remove recommend "pavucontrol" because there is already "pavucontrol-qt"

Sources:
- Add autostart desktop file for xfce4-screensaver
- Add autostart desktop file to override lxqt-xscreensaver-autostart
- Modify autostart desktop file for onboard, a startup delay mitigates
  an issue with the onboard panel icon not showing up at the first boot
- Modify lxqt-tablet.sh to include custom XDG_DATA_DIRS
- Add application desktop file to override xfce4-screensaver-preferences,
  adding it to the menu
- Add application desktop file to override xscreensaver-settings, removing it
  from the menu
- Change install location of "lxqt-tablet" repository configs from
  /etc/skel/.config to /etc/xdg/lxqt-tablet. That way they are handled as
  distribution-specific configs and are separated from the user configs in
  ~/.config.
- Upgrade to version 0.3 of "lxqt-tablet" repository:
  - Change theme to "Dark" to fix panel look
  - Increase panel size
  - Change wallpaper mode to "zoom" to avoid deforming the picture
  - Disable global single click to not interfere with PCManFM
  - Add terminal and file manager launchers to panel
  - Rename openbox xml file to apply the configs
  - Set lock command to xfce4-screensaver
  - Add xfconf files to configure xfce4-screensaver
  - Clean up configs by removing default values

[ci:skip-build]: Already built successfully in CI.

Jakko authored 1 year ago and Newbyte committed 1 year ago

It was disabled because Alpine riscv64 builder was behind. But now it's
fine again.

[ci:skip-build] already built successfully in CI

These cmdline params are not needed because the issues they worked
around were fixed in 6.7 or in this kernel branch we are using.

Additional modules are included in the initramfs since they may not be
builtin in the future, and not having them loaded in the initfs can break booting

kconfig changes:
- Most are due to running 'pmb kconfig migrate'
- Enable USB_F_FS
- Build ath11k as a module + enable debug, to help with debugging
  pma#2361
- Enable support for BT BR/EDR stuff (like HFP)
- Enable CRYPTO_MD4 for EAP_MSCHAPv2

This uses oem-specific packages for configuring Intel and AMD systems,
and installs them all by default for new images using pmbootstrap's
pmb_recommends feature.

The intention is to provide pre-built images with support for Intel and
AMD already enabled/configured, and users can remove an unwanted set of
packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD
system) if they want to.

Upgrading existing systems should work, in that I haven't observed any
apk conflicts with it. But you do need to manually install the new
oem-specific package if you need it (e.g. `oem-intel`)

fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484

[ci:skip-build]: already built successfully in CI

Gianluca Boiano authored 1 year ago and Newbyte committed 1 year ago

[ci:skip-build]: Already built successfully in CI.