this post was submitted on 24 Jun 2024
42 points (100.0% liked)

Linux

5237 readers
231 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
 

cross-posted from: https://lemmy.world/post/16873587

A lot of people here seemed excited for these chips. It'll be very interesting to see the gaming performance as this could bring in an entire new segment of portable devices running Linux if powerful enough to deliver solid battery life and CPU performance.

you are viewing a single comment's thread
view the rest of the comments
[–] PenisWenisGenius@lemmynsfw.com 2 points 4 months ago* (last edited 4 months ago)

Another part of it is the gpu bios. The gpu bios contains x86 opcodes that it expects the host system to run for gpu-specific functions like video mode switching and probably lots of other stuff. I know that Vesa bios extensions mode switching requires a pointer to the functions in the gpu bios which the cpu runs. I tried to make a platform independent Vesa driver one time and couldn't figure out how to circumvent using the gpu bios for it since the functions you're supposed to call are compiled for x86. Even the well-refined projects like Seabios still rely on the VBE pointers for non-legacy video modes.

Legacy vga does also has a bios but it's relatively not that difficult to circumvent using the bios on legacy vga cards, only issue is that legacy vga modes are mostly useless.

I think there's a newish way of doing this stuff that doesn't involve Vesa or legacy vga but I don't know what it is. This I'm sure is only one of the many problems that have to be overcome if someone wanted to hack a 1080ti onto a raspberry pi or something.