Commit graph

4 commits

Author SHA1 Message Date
Minecrell
4724b0f9c1
firmware/*: move community firmware packages to device/community (MR 1362)
Right now we have all firmware packages under firmware/*.
This is problematic for mainly two reasons:

  - It's not immediately clear which firmware packages we need to keep
    when forking a new stable branch. (Where we delete testing devices
    at the moment...) We might end up deleting firmware packages that
    are actually used by one of the devices in community.

  - When backporting devices to the stable we cannot just cherry-pick
    the commit that moved the device to community (since it does not
    contain the firmware package). Instead we need to cherry-pick
    earlier commits as well, which may touch a lot of deleted files
    in the testing directory.

Let's make this consistent by also placing the firmware packages in
the device/* directory. We already have the common firmware- prefix
to distinguish them from device/kernel packages, which are already
both under the device/* directory.
2020-07-07 15:48:57 +02:00
Minecrell
6a2cc8e3db
firmware/firmware-asus-me176c*: fix linter warnings (MR 1362)
It's called !archcheck, not !checkarch, oops! :)
2020-07-07 15:48:57 +02:00
lambdadroid
fe4bd3ab4d
asus-me176c: rework packages (!699)
device/device-asus-me176c:
  - Install me176c-factory to apply correct MAC addresses for
    WiFi and BT
  - Use FAT32 for boot partition. This allows flashing the boot
    partition directly as ESP (EFI System Partition).
  - Overall cleanup

device/linux-asus-me176c:
  - Update kernel fork to 4.19.80
  - Cleanup APKBUILD
  - Stop building patched ACPI DSDT table directly into kernel

firmware/firmware-asus-me176c:
  - Package WiFi firmware

firmware/firmware-asus-me176c-acpi:
  - New package for the patched ACPI DSDT table
  -> Separate from firmware-asus-me176c because it is always required,
     (not optional)

[ci:skip-build]: runs into timeout
2019-11-03 15:58:37 +01:00
Mis012
c28fffa5b3 New device: asus-me176cx (Asus MeMo Pad 7) (!123)
Use upstream Linux with patches, which are needed for a lot of things.
lambdadroid said he will upstream some of them, but the battery driver
would need to be written from scratch, which is apparentely
non-trivial.

[skip ci]: kernel doesn't build under one hour (maybe too many modules
are selected), but it does build eventually
2019-01-03 10:19:45 +01:00