Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Info] How graphics stack work? #124

Open
hitech95 opened this issue Sep 23, 2019 · 0 comments
Open

[Info] How graphics stack work? #124

hitech95 opened this issue Sep 23, 2019 · 0 comments

Comments

@hitech95
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant