I am currently working with creating an alternative BSP using Yocto to replace the existing BSP. I am new to Yocto and I need to know how I can add libusb support to Yocto to detect the bluetooth dongle when attached.
Regards,
Pavan
You could use OpenEmbedded Layer Index to search for recipes available in Yocto. libusb1 recipe is here.
Then, to add that recipe to your Image, in /build/conf/local.conf, add IMAGE_INSTALL_append = " libusb1 "
Another option is to create core-image-full-cmdline for a console-only image with more full-featured Linux system
functionality installed.
Related
when we are using the kdump tool, we need to install the according kernel-debug*.rpm at first.
My questions is , the linux I am using is compiled by myself with lots of modifications. When could I find the kernel-debug*.rpm related to my customized kernel version?
Thanks
Not certain if you are using Fedora, RHEL or CentOS to create your kernel. For Fedora, a custom kernel-debug*.rpm is built from your source with the instructions given here:
https://fedoraproject.org/wiki/Building_a_non-debugging_kernel#Building_a_non-debugging_kernel
using the make release target.
We want to build a embedded Linux device using Yocto which is SELinux Enabled.
I was looking at meta-selinux layer Dependencies.
Dependencies
This layer depends on the openembedded-core metadata and the
meta-python and meta-oe layers from the meta-openembedded repository.
When it is referring to 'openembedded-core' does it mean poky
git://git.yoctoproject.org/poky
or
https://github.com/openembedded/openembedded-core
What are the differences between poky and openembedded-core, i don't see bitbake in openembedded-core
OpenEmbedded/Yocto Project is a superset project, from this superset, a subset (poky) is created so people can get a taste of OE.
Poky distribution is made using components from OE, demo BSPs, helper scripts to easily setup build environment, QEMU emulator to test the image, and the bitbake task scheduler. This make poky a ready-to-cook subset of OpenEmbedded (OE) that helps users to understand the build system and to create their own Linux distribution possibly based on Poky distro.
Poky is a reference distribution of the Yocto Project. It contains the OpenEmbedded Build System (BitBake and OpenEmbedded Core) as well as a set of metadata to get you started building your own distro. See https://www.yoctoproject.org/software-item/poky/
We are planning to release our Embedded Linux product using Yocto.
Currently, I see 'Warrior' is the stable release version.
https://wiki.yoctoproject.org/wiki/Releases
Looking at the poky source code, I find lot of tags.
https://git.yoctoproject.org/cgit/cgit.cgi/poky/refs/tags
How to decide on choosing the tag. I see poky-yocto tag, poky-warrior tag
Unless your hardware supplier provides you with a customized Yocto version (usually a Linux kernel, related patches and some recipes to setup specific hardware), you should always start with the latest stable version available at the moment, because it will contain the latest fixes from the community, and probably you are interested on them.
I need realtek-8192cu driver in my linux version.
The default driver shipped with kernel is not suitable for me.
I want to use a custom version of driver like https://github.com/desflynn/realtek-8192cu-concurrent-softAP.
How to create a recipe for that job.
Thanks,
one possibility is to use the bitbake recipe hello-mod_0.1.bb as starting point to build a recipe for external kernel modules. It can be found at openembedded-core/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
The Reference to Incorporating Out-of-Tree Modules: https://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-manual.html#incorporating-out-of-tree-modules
I am working on Qt application in the linux Desktop enviromet. Most desktop Linux uses xwindows to display onto the screen.
But now I want to try my hands on DirectFB on my desktop. Related to which i have some questions :---
1> Can i make my desktop QT application to make use of DirectFB to run my QT application .
2> If yes then do i have to disable xwindow server on my desktop first Or directfb can run simultaneously.
3> Also is it the right way to configure QT for using directFB .
http://qt-project.org/doc/qt-4.8/qt-embeddedlinux-directfb.html
http://qt-project.org/wiki/DirectFBAndQt
4> How does Qt and directFB & openGL works together. Is this how communication flow occurs :---
Qt ----> OpenGL ----> DirectFB --> screen
5> Also if i install Directfb library then will it automatically come to know how to communicate with video h/w driver ?
http://en.wikipedia.org/wiki/DirectFB
Please suggest on these points.
try to inform the display plugin your Qt application should use
./qt-app -display directfb
DirectFB can create windows over X, but you need to configure it to do so (XNest or something like it)
Probably yes
Don't know
Nope, you need a plugin backend for your platform. When dealing with custom boards, usually the vendor ships the code needed to build such component
The Qt library is able to draw either on X11 or on the framebuffer without the need of the (additional) DirectFB layer. Recent versions of the library also have OpenGL support. Adding such a layer would just be a waste of time/memory/cpu.