| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
The upstream repository now has support for kernel 4.x, so we no longer
need the patch.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
These flags are applied via the kernel config, so if we add it using our
compiler wrapper the kernel build process is unable to detect these
flags and the build will fail.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using xset for DPMS control only works as soon as we have an X session,
but we want to work around the issue as early as possible so let's set
it in preDeviceCommands.
The program here directly uses the ioctls to blank/unblank the current
console without enums/constants (14 is blank and 4 is unblank) because
it's just a workaround and supposed to go away in the near future.
If we'd wanted to use the constants from tiocl.h, we'd have to add
dependencies on Linux headers, but I'm lazy right now ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
This reverts commit bafb5933654cdb7e35f0c54418bdd0dcb999f98c.
We can finally drop that patch, because the issue has been fixed
upstream already.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
This was a copy & paste error by me, because I copied the options out of
an existing configuration, which contained the CONFIG_ prefixes. Within
extraConfig of the generic kernel builder, we only use the names without
prefixes.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9d4575855bf1ae2136d85a2d0aa7b5ede50cfc67.
The upstream issue systemd/systemd#3735 has been fixed and it got
included in systemd version 331.
Since NixOS/nixpkgs@51871dfb3777 we're also on version 331, so we
no longer need this patch in Vuizvui.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
| |
Let's enable the options that *should* work with this kind of hardware
regardless whether it's currently working in mainline. It doesn't make a
huge difference to the kernel configuration prior to this change, but
let's better compile in these options rather than wondering why some
hardware isn't working.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I didn't use -rc6 directly but a few commits after the tag.
Within the mainline merges there was torvalds/linux@45209046c47b93fad.
I didn't investigate further why this exactly is a problem other than
freezing the machine shortly after the bootloader hands over control to
the kernel.
Reverting this commit fixes this issue for now until I have time to look
into it.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
Not that this improves anything significant in terms of hardware
support, but I'm debugging on the basis of the -next kernels, so it's
better to stay on latest mainline for the vuizvui builds (current -next
kernels for the last few weeks make the situation even worse).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
This one is tracked upstream at systemd/systemd#3632.
I've implemented the workaround proposed by @medhefgo as a patch.
As this module is only for a particular hardware, we won't cause
troubles for other hardware.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
| |
This adds a few #ifdefs for Atom platforms, however I don't remember
what exactly it fixed/changed for the T100HA.
Nevertheless it's probably a good idea to optimize for that architecture
because we're going to compile our custom kernel anyway.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 0182e0ca12760da2aecd65de98c85a76ecdcedc6.
With the latest testing kernel, the machine still gets random GPU
lockups which are already fixed in linux-next, so let's get back to
linux-next even though things break from time to time.
We can still pin a specific next version to base our patches on once we
have a base version that's stable enough.
I've also fixed the backlight patch to compile against the latest next
version.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
This fix is more or less because of GCC 5 rather than just against
kernel 4.x, because the number of arguments for rtw_select_queue() have
been changed since 4.0 already.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
This is to not clutter up the hardware/ namespace with patches (we're
going to add one).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, linux-next-20160408 introduces a few unrelated bugs to the
hardware, so instead of updating to the latest -next version, we're
going for the latest -rc instead.
This should also help a lot in development to focus on the important
parts instead of dealing with completely unrelated bugs/issues.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
This really is specific to the RTL8192CX chipset and I originally was
using this for tyree along with the mainline kernel modules.
Unfortunately, I had connection drop outs so I switched to the original
Realtek driver, which is now vuizvui.hardware.rtl8192cu, so the firmware
is used and should be enabled there as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
It's actually a backport of Realtek's own USB WiFi driver that is not
(yet?) in mainline. I'm using this for tyree (the T100HA) because the
internal WiFi card isn't recognized by SDHCI yet.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
| |
Essentially forcing DPMS standby and bringing it on again for now
mitigates the vblank issue with the I915 driver.
Of course in the long term I need to debug this properly, but for now
this works consistently so I'll leave it that way.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both of these patches are from the following Google Drive:
https://drive.google.com/folderview?id=0B4DiU2o72FbuejQ1S2VZZW5xV2c
The meta-keys-asus.patch (which is called just meta-keys.patch in this
repository) is used verbatim.
However, the baytrail-backlight.4.4.patch (here just backlight.patch) is
a rebased version of the patch from the Google Drive with a few
modifications by me, which boils down to:
* Remove the module parameter force_backlight_pmic, because this module
is hardware-specific so we don't actually need to do that (and *if*
we want to do that we'd compile it in directly).
* Add an unused pipe function argument to vlv_pmic_setup_backlight().
As the backlight patch introduces the functions intel_soc_pmic_readb()
and intel_soc_pmic_writeb() which are not available at module link time,
I have also added DRM_I915 to be compiled into the kernel.
In addition I needed to disable VIDEO_EM28XX and RAPIDIO, because they
do not compile with linux-next-20160226 and I didn't bother to provide
fixes because it's for hardware that is not existing on the T100HA.
Note that I'm using linux-next-20160226 here instead of 20160229 because
the latter has some networking I/O issues right now.
This makes the backlight, battery status and charging usable on the
T100HA and the fixes from the drm-intel-fixes branch are no longer
needed because they're already in linux-next-20160229.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
So far INTEL_SOC_PMIC hasn't been enabled *at* *all* so there wasn't any
battery status available nor did it charge while the system was running.
Enabling INTEL_SOC_PMIC now solves this issue.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We already have a directory just for hardware-specific configuration
options and the module option already says "vuizvui.hardware", so it
should better be consistent with the directory layout.
Tested using:
nix-instantiate release.nix -A machines.profpatsch.katara
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The custom kernel has built in modules for the MMC storage and a small
patch which is essentially diff of the merge of the "drm-intel-fixes"
branch from git://anongit.freedesktop.org/drm-intel against 4.5-rc5.
This is the HEAD of what I have merged:
https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=9b18572e83bfd5378b3fcff3acf123f7bddf558a
Eventually these fixes will hit mainline so we can drop them very soon.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
This may need some calibration as well, but I don't have a stylus to do
it very precisely so I'm leaving this to the defaults because I tried to
calibrate it using my monstrous fingers and it got worse than the
defaults.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
We already know the display device for this particular type of hardware,
so there is no need to probe different video drivers.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
We already rotate the fbcon display, but we need to make sure we also
apply the rotation to the X server.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
This module is for declaratively specifying SDL_GAMECONTROLLERCONFIG, an
environment variable used by SDL 2 to map arbitrary controllers to that
of an XBox reference controller.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
This should go into its own hardware module, so it might be helpful for
others as well (especially if we're going to put it into upstream
<nixpkgs>).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
