简体繁体 English

Android AOSP 构建映像及其对供应商代码的依赖

[英]Android AOSP build image and its dependency on vendor code

原文 2020-05-08 07:33:01 5 1 linux/ build/ android-source

I have built a Android 10 AOSP image successfully.我已经成功构建了一个 Android 10 AOSP 映像。 I understand that some vendor specific code needs to be integrated with AOSP to make a successful boot.我了解某些供应商特定代码需要与 AOSP 集成才能成功启动。

But, I have no clue to how to integrate it.但是，我不知道如何整合它。 Please some one comment on this or point me to some info link.请对此发表评论或将我指向一些信息链接。

Below are few of my other questions:以下是我的其他几个问题：

Linux uses dtb files which has info about board and SOC how this is handled in android is it same? Linux 使用dtb文件，其中包含有关板和 SOC 的信息如何在 android 中处理是一样的吗？
As different SOC's have different IP implementations related to peripherals ideally kernel also should have specific drivers related to same but how these will be supported in kernel of either android/linux.由于不同的 SOC 具有与外围设备相关的不同 IP 实现，理想情况下，kernel 也应该具有与之相关的特定驱动程序，但如何在 android/linux/的 kernel 中支持这些驱动程序。
On my mobile vendor website i can see source code is available for kernel can I use it along with AOSP the no need of DTB's?在我的移动供应商网站上，我可以看到源代码可用于 kernel 我可以将它与 AOSP 一起使用而无需 DTB 吗？

1 个解决方案

Android only requires your kernel to have a certain set of configurations (eg Binder support). Android 只要求您的 kernel 具有一组特定的配置（例如 Binder 支持）。 Other than that the kernel and the whole boot process that comes before init is started in user-space is considered vendor responsibility, because it is hardware dependent.除此之外，kernel 和在用户空间启动init之前的整个引导过程被认为是供应商责任，因为它依赖于硬件。