Well, at least screen rotation should work without issues on any Intel Baytrail with any Linux, as it has a standard Intel GPU included where drivers exist.
I'm not sure how battery / charging stuff etc. works on x86 PCs, but I thought they have a BIOS which provides all those details as standard API via something like ACPI?
So if properly done, it should work out of the box.
Not if the whole system uses standard APIs like ACPI or similar (is that still used?)
But still, rotation should really work as it uses the standard Intel graphics driver.
Also, audio also doesn't work on current BayTrails, AFAIK.
There isn't an existing driver yet, but without many details about it, no one could code one.
You keep referencing Bay Trail, but isn't the GPD Win Cherry Trail? Not that there should be that much difference.
Work has been done on the audio issues. Several of those drivers exist but have not been pushed up to the kernel yet - and are dependent on what components were put in the individual device.
The "Mele" branded Ubuntu Bay Trail compute stick that I have does HDMI audio fine.
See above:
I would be interested to know if that build is any 'better' on the GPD Win even though it wasn't designed for it specifically. It might be a solid improvement over stock distributions though.
Expecting -any- Linux build to run on -any- highly customized hardware with Bay/Cherry Trail in it regardless of what the supporting hardware is might be asking too much. That would be akin to expecting the Pyra OS to run out of the box on my phone since they're both ARM. However, there are several examples where the driver issues have been overcome to result in pretty solid working products utilizing Ubuntu (not my favorite - but at least it's based on Debian).
Again, I'm not arguing to push for a Cherry Trail Pyra CPU board. That boat has sailed. I'm just trying to squash a few myths regarding Bay/Cherry Trail and Linux. It has come a long ways over the last 2 years to the point where commercial products with fully operational hardware/driver support have shipped with Linux installed. The necessary drivers exist, but are dependent on the 'right' supporting hardware and are not all upstream and into the kernel (they might not ever be). It is highly device dependent based on whatever the manufacturer used for networking and audio.
An example would be USB WiFi dongles for the Pandora. Some worked, some needed additional drivers to work, some simply won't work because there are no Linux drivers for the chipset. The same WiFi chipset roulette applies to all of the Bay/Cherry Trail devices. Some might work, most need drivers, some will never work.
I doubt someone could buy a commercial Windows 10 package and simply install it 'out of the box' on the GPD Win or even the Microsoft Surface without making a round trip for additional device specific drivers.
