Skip to content

Move Chrome OS devices to community

Administrator requested to merge cros-community into master

These devices are now in good condition, and most of things in #1823 (closed) are implemented

Not moved devices
  • google-spring - poor mainline support for now, shall be improved
  • google-peach-pi - possibly has GPU issues, no active maintainer/tester
  • google-nyan-big, google-nyan-blaze - no active maintainer, my device has wifi/bt broken, I don't work on it anymore unless I get a new device
  • google-x64cros - no active maintainer, sound issues in mainline which may potentially break devices

Some of devices being moved are generic ports, so I suggest to handle it this way:

  1. Move generic ports to community
  2. Advertise tested devices as community supported on wiki, but advrtise others as testing
  3. Start advertising more devices as community supported once they get tested/fixed (without MR and 2 weeks waiting)

This MR includes a lot of packages, and it will be inconvenient for me to work on it here. If I have to do some improvements (e.g. from comments), I will most likely open a separated MR for each change, and then rebase this one when it comes to merge

Merge request reports