On April 30, 2018 5:23 PM, Mark Kettenis <mark.kette...@xs4all.nl> wrote: > > On April 30, 2018 3:21 PM, Mark Kettenis mark.kette...@xs4all.nl wrote: > > > OpenBSD will be able to use a framebuffer set up by the firmware. I > > > believe this works on the Raspberry Pi although it may depend somewhat > > > on the firmware version and/or device tree you use. You'll need to > > > boot the board with the monitor connected and turned on for this to > > > work. There is no acceleration for the framebuffer. > > > > Should this apply for RockChip RK3399 also? > In principle yes, as long as support for it is enabled in U-Boot.
Wow! > Currently that's only the case for the TheoBroma Systems "puma" > RK3399-Q7 board. I think the driver only supports HDMI output right > now. Do you know why, did they extend manufacturer firmware? > > What resolution would the display apply? > Not sure if there are any limits; 1920x1280 defenitely works on sunxi > boards, so that probably would work for RK3399 as well. Sometimes there are more displays, e.g. the Theobroma has both HDMI and DP. The Samsung Chromebook Plus has a built-in display and also HDMI via USB-C [1]. Resolution and port switching logics would be all in the firmware then, right? Do you have any guess if the Chromebook Plus RK3399 would have a firmware framebuffer? Should you be able to run X using the wsfb driver on the firmware framebuffer? [1] https://www.samsung.com/us/support/answer/ANS00061883/
