@iska@mstdn.starnix.network @safiuddinkhan@fosstodon.org @hacknorris @2T2@mstdn.starnix.network Oh, now I get the question 😂
Why Windows and not Linux? Because the community port of Windows is great, everything works, including HW video decoding. It can boot linux — but that's it. It has some framebuffer support and the networking might work if stars align properly. A device like this is hardly useful.
@Suiseiseki I still think it's acceptable in this rare case. Only the kernel boots on this device, the userspace doesn't matter at this point 😆
@Suiseiseki I insist that it is acceptable. Sure the kernel won't work by itself, but that is not what my point was. This device is not usable because there is no support for the hardware it has *in the kernel*. No init can change that.
@Suiseiseki I didn't mention any login prompt. The fact that framebuffer works doesn't imply login prompt, it doesn't even imply you can access built-in storage and mount the root partition, right?
I get it, you just want to push some agenda, but this doesn't look like a perfect occasion to do it.
You just claimed it booted up into a framebuffer.
If Linux doesn't have drivers for the hardware you're trying it with, it simply won't boot (although generic drivers leave much to be desired).
If you got into a framebuffer login prompt, that is perfectly usable, as you can use emacs (rms prefers framebuffer emacs), nano and a bunch of other GNU tools just fine.
The only reason why I use Xorg, is because Xorg lets me use lots of terminals on multiple monitors, and it can display UTF-8 (for です).