android-rpi/device_brcm_rpi3

[Info] How graphics stack work?

hitech95 opened this issue · 0 comments

Hi,
sorry if this is not a bug, but I tied with the google mailing list but no one replied.

I would like to build a custom image for the RPI but I'm quite a newbie with android AOSP sources and development but I was a Android/Java developer so I have some experience with it.

Anyway I would like to know why you use the kms instead of the fkms module device tree overlay.
As far I know you are not using the binary blob of the vpu, so both the ISP and the encoding/decoding is not working. I would like to better understand if this choice is due to a limitation if the fkms mode or else.

BTW I'm still trying to build an AOSP image but even the emulator keep crashing. I thing that there is something wrong on that i do!