So you might want think about a common approach that handles those as well. This way you have your own defconfig that could be used to configure the kernel in the step 1:my question is about this step 2 : suppose I do change some kernel config settings using xconfig -> these changes are saved to the .config file (which is hidden and gitignored)- manage patches in your source control system.The xilinx_zynq_defconfig can best be viewed as a starting point. The Xilinx toolchain is recommended, but the Linaro toolchain can also be used.
If the problem persists, contact Atlassian Support or your space admin with the following details so they can locate and troubleshoot the issue:. Recompile the devicetree file. This code: 984f13 The URL of … This page is intended to give more details on the Xilinx drivers for Linux, such as testing, how to use the drivers, known issues, etc. In the first step, this file (essentially) is copied into .config. Make sure the boot partition is mounted. Try refreshing the page. Try refreshing the page. This way allows me avoid generating and maintaining patches which I have learned is a major hassle. So I find keeping a private repo and using git to manage things much, much easier.Or is this 'manual work', meaning I have to figure out the diff in the .config file before and after my 'xconfig' changes, and apply this manually to the 'xilinx_zynq_defconfig' file (or save to another config file)? Or do people just generate the .config once from the 'xilinx_zynq_defconfig', and then keep on working on the .config file (so doing once the 'step 1', and then only 'step 2' on subsequent kernel modifications? I have a my own kernel repo and then push the xilinx branches to that repo. In this repo I make as many kernel configs(and devicetrees) as I need. To create new config you just have to copy back the .config into arm/arm/configs giving any name you want.-> starting from the 'xilinx_zynq_defconfig' file, this creates a .config fileThis can be handled in a number of ways.
Note that this is not specific to Zynq or Xilinx, the same answer applies to Linux kernels in general.- keep a patch file and apply it manually Also any drivers I write or modify go into that private repo. So when I want to use a new xilinx branch I just push that branch to my private repo and then cherry-pick or rebase my changes onto the new branch. Note that you will likely also be changing other files, such as the device tree (arch/arm/boot/dts/zynq-*). If the problem persists, contact Atlassian Support or your space admin with the following details so they can locate and troubleshoot the issue:. On new images, this can be done by right-clicking the boot icon on the desktop and selecting the “Mount Volume” option.