On Wed, Nov 20, 2019 at 2:17 PM Yusuf Altıparmak <[email protected]> wrote: > > Apologies for the situation, this was my first question to community.
No problem, we've all been there. :) If we continue on the topic - please also avoid top postings. Example: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top > > I didn't know the differences between built-ins and modules. I made a little > research after your answer and corrected the defconfig file as you explained > in last answer. Everything gone well. kernelmodules.tar file is changed with > including the desired drivers. Glad to hear it has solved your issues. > > Andrey Zhizhikin <[email protected]>, 20 Kas 2019 Çar, 16:02 tarihinde şunu > yazdı: >> >> Hey Yusuf, >> >> Please don't take a conversation out from the list (use Reply-To-All) >> unless you really have a question that you would like to ask privately >> from me. By this, other people which might have similar issues might >> get answers by reading mail threads. If you intend to reply to this >> email - please include the list address back. >> >> On Wed, Nov 20, 2019 at 11:26 AM Yusuf Altıparmak >> <[email protected]> wrote: >> > >> > Hello Mr. Andrey, >> > >> > My actual aim is to install 'amdgpu' driver to use 'AMD 9171' product with >> > my embedded boards PCIe slot. 'amdgpu' driver is available after kernel >> > version 4.2. At first, my default bsp kernel was 4.1.xxx and I changed it >> > to 4.9 which I found in qoriq github. Then,in <machine>.conf file, I >> > declared my own defconfig to enable amdpu section. I added the screenshot >> > of menuconfig. amdgpu was selected as '*'. I changed it to 'M' and my diff >> > fragment is like this now. >> > CONFIG_MFD_CORE=m >> > CONFIG_DRM_RADEON=m >> > CONFIG_DRM_AMDGPU=m >> >> That is correct and that is what I would expect to be produced. >> >> The trick here is (and this is what you've solved later and reported >> in another reply) that you created your own defconfig, then did >> menuconfig, and then re-built the kernel. If you would like to >> configure the kernel with your own defconfig, then you should do the >> following: >> 1. bitbake virtual/kernel >> 2. bitbake virtual/kernel -c menuconfig >> 3. change configuration fragment, save the config >> 4. bitbake virtual/kernel -c savedefconfig >> >> After the last step, you would be presented with the path to a new >> defconfig which you can use to overwrite your previous one. In the new >> defconfig file, all your config items would be as you have them >> configured, and also some additional items which might be required by >> your modified config items. This is a preferred way of doing things, >> as in this case you would not have any missing dependencies during >> configuration. >> >> > >> > But result is still same. There is still 13 '.ko' files in my modules.tgz. >> > amdgpu or other modules still does not exist in modules.tgz or >> > rootfs.tar.gz >> >> I believe you then did full virtual/kernel re-build, which flushed >> your modified config items and took the default one. >> >> > >> > Andrey Zhizhikin <[email protected]>, 20 Kas 2019 Çar, 12:18 tarihinde >> > şunu yazdı: >> >> >> >> Hello Yusuf, >> >> >> >> On Wed, Nov 20, 2019 at 9:44 AM Yusuf Altıparmak >> >> <[email protected]> wrote: >> >> > >> >> > Hello, >> >> > First of all, I am using NXP T1042D4RDB-64B board. They have linux sdk >> >> > which is >> >> > https://www.nxp.com/docs/en/supporting-information/QORIQ-SDK-2.0-IC-REV0.pdf >> >> > >> >> > My problem is, >> >> > I am trying to add new modules to linux rootfs generated by yocto. But >> >> > the drivers I selected on "menuconfig" is not compiling as ".ko" file. >> >> > They only got compiled as ".o" file. Here is the details of problem. >> >> > https://stackoverflow.com/questions/58941714/yocto-generated-linux-modules-do-not-contain-all-the-drivers-selected-in-config. >> >> >> >> As you stated on Stackoveflow, some config options are =y and some are >> >> =m. Those with =m are actually be modules, those with =y are >> >> built-ins. It is really hard to tell how you configure the kernel, so >> >> please do: >> >> # bitbake virtual/kernel -c diffconfig >> >> and post your fragment here. >> >> >> >> > >> >> > Can you help me about this situation? >> >> > >> >> > Regards. >> >> > -- >> >> > _______________________________________________ >> >> > meta-freescale mailing list >> >> > [email protected] >> >> > https://lists.yoctoproject.org/listinfo/meta-freescale >> >> >> >> >> >> >> >> -- >> >> Regards, >> >> Andrey. >> >> >> >> -- >> Regards, >> Andrey. -- Regards, Andrey. -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
