| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Add only to x86 and Jetson-tk1 kernels, given that these are the BSP
used on systems with audio-bluetooth (bluez)
Change-Id: Iff16d49079a55f00377ad0ee5831eb8aa657762c
|
|
|
|
|
|
|
| |
This will allow 3D acceleration with the virgl mesa driver running in
a host with qemu >= 2.5
Change-Id: I719ce9da94361b4bc2fa96aaefe71d5f890a8028
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was broken by changes in c4bf91813c787b503eaeaa1d372f271d4638a16d
which expected 'depmod' to be present in all systems.
It would be annoying to prevent anyone from using modules, but it also
defeats the point of minimal-system to start adding bits of the
'foundation' stratum.
This hack to only run 'depmod' if it is present in the system seems like
a reasonable compromise, until we have a nice way of customising the
Linux config for different systems.
Change-Id: Ida083b51353cab78f8d3f6a72af711a00d0fcfd8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch add KMS DRM kernel drivers for:
- cirrus, wich is the default adapter in qemu < 2.2
- std, wicht is the default in qemu >= 2.2
With this, weston will use its native DRM backend under qemu, so it's not
needed to use the fbdev-backend anymore
This also make possible to run the GNOME wayland session in qemu, simply
run from a terminal:
gnome-session --session=gnome-wayland
Change-Id: I1318bbaff462a62c0dfde06588aecf689436857d
|
|
|
|
|
|
|
|
| |
This is a pretty generic intel driver which supports a few intel
audio chipsets, including the default audio chipset provided in
VirtualBox.
Change-Id: I0af8fe8d87801850111b8dc0dc63e29acc7746c7
|
|
|
|
|
|
|
|
| |
This makes system containers work better.
Now it is possible to log in with ssh or `machinectl login`
to any containers started by systemd-nspawn.
Change-Id: Ia038355b48e13fe67996a488660fecdfc5ae1215
|
|
|
|
| |
Change-Id: Ic51480a7f1e3083bb245393336ecd2fad57fba67
|
|
|
|
| |
Change-Id: Iec8bb1d659b037b45b8733f46d3f4af2413631a7
|
|
|
|
|
|
|
|
|
| |
This works for a few commonly available USB Ethernet devices; and while
other architectures may make use of such devices, I don't believe we
currently have a use-case that requires us to be able to support extra
interfaces on those devices.
Change-Id: Ib8974207c04f34cff4f6884409c70aeb116935d5
|
|
|
|
|
| |
E1000E is not in the standard x86_64 defconfig, but it is in the i386 defconfig, and it's necessary to support commonly available hardware.
Change-Id: Ia0f97ffaba190901bd1ae563690b6ebc9d108e66
|
|
|
|
| |
Change-Id: Ia45fd5e8bc53b6b8ebe3cc35aa52cb524a992100
|
|
|
|
| |
Change-Id: Ib98d024f34b6dd0d821335bdf24cb59278977a17
|
|
|
|
| |
Change-Id: I2ecb0ac435aa6f364b41c0e680c5792dcbe02f50
|
|
|
|
| |
Change-Id: I864631f70fa7feb650d924cc2bb91d787270c27d
|
|
|
|
| |
Change-Id: I113e08474cc4a1c3a60c9a683725d7fdc13ffe08
|
|
|
|
| |
Change-Id: I1b65a1b3add4f8da11f6403bceb1063797a99b5d
|
|
|
|
| |
Change-Id: I87f44ebc26b44a024b39149bfce1e29e4e204051
|
|
|
|
| |
Change-Id: I0f426296df43d6f0bb37b23293fd5268f1461fe3
|
|
|
|
| |
Change-Id: I939022e819a386c45e900e2df23dc3809f4a1a45
|
|
|
|
|
|
| |
These modules are needed for ebtables and netfilter.
Change-Id: I36c0fc69c3167de556fd2d0242c4aada1441c55c
|
|
|
|
| |
Change-Id: I066f7dcf30452945d973fa8eedb3393975badd1f
|
|
|
|
| |
Change-Id: Icc538974fcbf565ad70454a19281802b232d6c08
|
|
|
|
|
|
| |
CONFIG_NF_NAT_IPV4 is known as CONFIG_IP_NF_NAT in 3.17 kernels onwards.
Change-Id: I4c41eb01c62de37f0c16aedaec01d404de50a2e1
|
|
|
|
|
|
|
| |
I want to use LVM snapshots for taking backups of data volumes in our
infrastructure systems.
Change-Id: I665a3ec2e53fb57f529089b5f6e59deddf61dc73
|
|
|
|
|
|
|
| |
It puts headers for building com32 binaries in a different path,
presumably because they're not for building normal libraries, so putting
them in the search paths for normal libraries would just cause
conflicts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the GCC compiler to the 4.9.2 version. It turns out that a C++
compiler is required to build the latest GCC releases, so build one in
stages 1 and 2 as well.
The updated list of GCC configuration options that either don't work in
a cross compiler or are not needed in a temporary compiler, were based
on the latest instructions from Linux From Scratch.
The inclusion of /lib64 in the lib path for the stage 1 linker is an
attempt to turn things more robust rather than to just symlink in /lib
stuff that ends up installed in /lib64 (as it is already being done for
libgcc_s.so). Ideally, we should configure every chunk to install to
/lib, however GCC seems to not honour the `--with-libdir` configuration
flag.
With this version of GCC, it looks like a sysroot needs to be given at
configure time so that `--with-native-system-header-dir` does what it
claims to do. Unfortunately, this has the side effect of making GCC not
passing to the linker the linker sysroot flag: `-Wl,--sysroot=$SYSROOT`.
The workaround is to modify LDFLAGS to give a sysroot directly to GCC,
`--sysroot=$SYSROOT`, which will then be further passed down to the
linker.
As the newest version of GCC finds more warnings than the previous one,
`-Werror` was disabled for the coreutils, GDB and Syslinux projects.
Syslinux's Makefile had to be patched, as it is not possible to disable
`-Werror` for all targets through the NO_WERROR variable.
The hack to handle libgcc_eh being required during eglibc's build was
removed, as it doesn't seem to be the case anymore.
|
|
|
|
|
|
| |
With VLANs it's possible to PXE boot hardware without needing to fiddle
with the DHCP server, by starting your own PXE server on a VLAN, and
configure the NIC of the target to start in that VLAN.
|
|
|
|
|
|
|
| |
To enable Hotplug support this patch enables the following in
the kernel:
- HOTPLUG_PCI
- HOTPLUG_PCI_ACPI
|
|
|