as it causes connection issues with different gamepads, it is safer to
remove it and the user can add this on need basis via
```
echo options bluetooth disable_ertm=1 > /storage/.config/modprobe.d/disable_ertm.conf
```
fixes#1528
* add xpadneo driver for Xbox One wireless gamepad
* xpadneo: add kernel patches
should prevent generic hid module to claim the gamepad
* xpadneo: add additional settings to modprobe conf
* rpi4-aarch64: Add rpi4 aarch64 kernel config
This was created by copying the arm config and looking at the diff between:
https://github.com/raspberrypi/linux/blob/rpi-5.4.y/arch/arm/configs/bcm2711_defconfig
and
https://github.com/raspberrypi/linux/blob/rpi-5.4.y/arch/arm64/configs/bcm2711_defconfig
* rpi4-aarch64: Don't pass --enable-neon to retroarch as it makes the build fail
* rpi4-aarch64: Raspberry Pi dtb files are created in a different place for aarch64
* rpi4-aarch64: Build some rpi specific packages for aarch64 as well as arm
* rpi4-aarch64: RPi4 64-bit needs fixup4.dat to boot
I don't think this harms anything else
* rpi4-aarch64: Enable 64-bit mode and specify kernel filename in config.txt
This is a bit hacky.
We need to specify the kernel filename otherwise it expects it to be kernel8.img
* rpi4-aarch64: Fix RPi options for RPi4 aarch64
* rpi4-aarch64: update mupen64plus to aarch64 compatible version
* rpi4-aarch64: exclude cores that don't compile only for rpi-aarch64
* rpi4-aarch64: Update alsa-utils to overcome https://github.com/alsa-project/alsa-utils/issues/33
* rpi4-aarch64: Remove extra $ARCH arg from mk_arcade_joystick_rpi
* rpi4-aarch64: Fix ffmpeg compilation
* rpi4-aarch64: add new kernel conf
Created by copying the existing linux.arm.conf and applying the diffs between the official 32bit rpi kernel config and the official 64bit rpi kernel config
* rpi4-aarch64: improve kernel config
* rpi4: don't configure non-default audio_device
* Update mupen64plus_next
* rpi4-aarch64: turn off a load of debugging in the kernel
When setting a custom build script (which must be relative to $PKG_BUILD), the
value should be set in configure_package() so that $PKG_BUILD is known, and also
because the path to the script will be validated prior to calling
pre_configure_$TARGET(), so the script variable must be configured once the pacakge
is sourced.
Move variable assignments into configure_package() if the assignments
depend on variables initialised after the package is sourced, ie.
$PKG_BUILD, $PKG_SOURCE_NAME etc.
