What is kernel 'make menuconfig' in android AOSP
I tried make kernel from AOSP. it could build kernel only.
But how about if I want to customize kernel config from menuconfig
Regards
Peter
There's a config.sh script for menuconfig in android kernel source.
Here's the step:
download android kernel source code
repo init -u https://android.googlesource.com/kernel/manifest -b BRANCH
repo sync
run menuconfig
BUILD_CONFIG=common/build.config.gki.aarch64 build/config.sh menuconfig
modify menuconfigs and save .config
build kernel
BUILD_CONFIG=common/build.config.gki.aarch64 build/build.sh
Reference: https://source.android.com/docs/setup/build/building-kernels
Building Android kernels for various devices is documented on source.android.com. It covers the Android Common Kernels as well as some widely used devices that can be built directly from AOSP. While there are no specific instructions for make menuconfig, it contains a section on how to customize the kernel build with specific kernel configuration options.
Such kernel options can of course be discovered through make menuconfig as usual.
Related
I build a yocto OS image, the image is done, but I can't find the kernel source.
I want to modify some files in the kernel source.
I see no any kernel source file in build/
i built for Yocto dunfell , core-image-minimal image for qemuarm machine
You can find kernel source in
build/tmp/work-shared/qemuarm/kernel-source
I have a custom board with imx6dl chip and peripherals. I have compiled u-boot, zImage and rootfs from examples provided by manufacturer. But when i try to build yocto from git repo with latests releases, it fails to run (some drivers not working, board is loading and display interface, but touchscreen is not working for ex.),
Is there any way to include precompiled binaries zImage, u-boot and device table to bitbake recipes? I'm very new to yocto project, and only need to get bootable image with working drivers and qt5.
If you have a working boot chain (e.g. u-boot, kernel and device tree) that you have built out-of-yocto, then you might try building a rootfs only. This requires two main settings, to be made in your local.conf to get started. Please don't firget that this is just a starting point, and it is highly advised to get the kernel/bootloader build sorted out really soon.
PREFERRED_PROVIDER_virtual/kernel = "linux-dummy to have no kernel being built, and something like MACHINE="qemuarm" to set up an armv7 build on poky later than version 3.0. The core-image-minimal target should at least be enough to drop you in a shell for starters, and then you can proceed from there.
Additionally, it might be qorth asking the board vendor or the yocto community (#yocto on the freenode server) if they know about a proper BSP layer. FSL things are quite nicely supported these days, and if your board is closely related to one of the well-known ones, you've got a high chance that meta-freescale just does the trick nicely.
Addition:
#Martin pointed out the mention of Qemu is misleading. This is just the easiest way to make Yocto build a userland for the armv7-architecture which the imx6dl is based on. The resulting root filesystem should be sufficiently compatible to get started, before moving on to more tuned MACHINE configuration.
I want to build v4l2-ctl tool in buildroot (from 2019.02.4) linux system.
But v4l2-ctl is legacy (has been deprecated and replaced by a single option to build all the libv4l utilities).
I try to setup BR2_PACKAGE_LIBV4L_UTILS, to get v4l2-ctl, but after make, in linux system there is no v4l2-clt tool.
Do not understand: where is v4l2-ctl? How to build v4l2-ctl?
I got it:
It is need to rebuild buildroot's packet again:
make libv4l-dirclean
then
make libv4l-rebuild
then
make
and v4l2-ctl will appear in target usr/bin directory
I have AOSP sources checked out on a Linux system using the repo command as follows:
repo init -u https://android.googlesource.com/platform/manifest -b android-9.0.0_r30
I've successfully cross-compiled the SDK for Windows but I am having trouble with compilation of the emulator. The prebuilt packages in prebuilts/android-emulator/ are available only for linux and darwin platforms. I tried to add the needed repo by adding the following line to .repo/default.xml:
<project path="external/qemu-android" name="platform/external/qemu-android" groups="pdk" />
but repo sync responded with error:
fatal: couldn't find remote ref refs/tags/android-9.0.0_r30
which is understandable, because this tag indeed doesn't exist. In conclusion, I'd like to have the newest awailable emulator (from master) built for Windows, but without the need for creation of the whole new AOSP source tree (I don't have that much space).
I'm trying to build a rootfs for an blackfin target, However I can't figure out how I configure the kernel that buildroot produces. The first run through came up with menuconfig, but it's cached the .config since then and I can't see where to change it.
regards
santhosh babu
You need to run make linux-menuconfig to ask Buildroot to start the menuconfig interface of the Linux kernel.