14:00 <rah> are any binary blobs required in the bootloader for rk3399?

14:00 <rah> or anywhere else?

14:18 <jakllsch> there's the maskrom in the SoC

14:27 <sigmaris> beyond the boot code in maskrom, there's no blobs required for booting. there are blobs included in TF-A and in linux's firmware for the displayport controller, only required if you want to use displayport.

14:33 <rah> OK, thanks

14:51 <rah> when you say "displayport", is that distinct from the HDMI outputs on various SBCs, or should one expect that the HDMI comes from a displayport output requiring the binary blob?

14:51 <rah> ^ sigmaris

14:52 <jakllsch> istr the blob DP controller is the one for the Type C

14:52 <jakllsch> there's also a eDP controller that just works

14:57 <robmur01> IIRC the DP firmware is supposedly only needed for higher resolutions and HDCP to work

14:58 <rah> robmur01: higher resolutions on a DP output or on an HDMI output?

14:58 <jakllsch> in any case, last i checked, upstream linux doesn't really support the DP on Type C on 3399

14:59 <robmur01> on displayport; HDMI is a completely separate IP from a different vendor

14:59 <jakllsch> yup

15:01 <robmur01> indeed the mainline status of Type C is that it only works on Chromebooks, for reasons

15:01 <jakllsch> oh is that the catch

15:01 <jakllsch> in any case it hasn't been working on Pinebook Pro so *shrug*

15:04 <robmur01> basically the phy driver only does magic extcon stuff with cros-ec and doesn't use the upstream typec framework that other controller drivers (usually fusb302) now expect

15:05 <jakllsch> ah

15:06 <robmur01> just needs someone with time, sufficient expertise, and motivation to update it, but as always those are in short supply :)

15:07 <robmur01> (I have almost enough of the third, but not of the first two...)

15:35 <rah> robmur01: thanks, HDMI being separate is what I needed

15:35 <rah> RK3399 it is

15:35 <rah> now, to find a cheap board..