> > By the time MT8183 shows up in more concrete devices, it will, certainly > > in kernel-space and likely in userspace as well. At present, the DDK can > > be modified to run on top of the in-tree Mali drivers, i.e. "Bifrost on > > mainline linux-next (+ page table/compatible patches), with blob > > userspace". > > > > While the open userspace isn't ready here quite yet, I would definitely > > encourage upstream kernel for ChromeOS, since then there's no need to > > maintain the out-of-tree GPU driver. > > That's an interesting idea, I had no idea, thanks for the info! > > Would that work with midgard as well? We have released hardware with > RK3288/3399, so it might be nice to experiment with these first. Yes, the above would work with Midgard as well with no changes needed. Ping Steven about thtat (CC'd). > > More immediately, per Rob's review, it's important that the bindings > > accepted upstream work with the in-tree Bifrost driver. Conceptually, > > once Mesa supports Bifrost, if I install Debian on a MT8183 board, > > everything should just work. I shouldn't need MT-specific changes / need > > to change names for the DT. Regardless of which kernel driver you end up > > using, minimally sharing the DT is good for everyone :-) > > Yes. I'll try to dig further with MTK, but this may take some time. Thank you!
Attachment:
signature.asc
Description: PGP signature
