On 9/28/19, JH wrote:
> On 9/28/19, JH wrote:
>> On 9/28/19, JH wrote:
>>> On 9/27/19, Maciej Pijanowski wrote:
On 27.09.2019 14:01, JH wrote:
> Hi,
>
> I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers
> and kernel modules in emmy-w1-driver-sdiosd
On 9/28/19, JH wrote:
> On 9/28/19, JH wrote:
>> On 9/27/19, Maciej Pijanowski wrote:
>>>
>>> On 27.09.2019 14:01, JH wrote:
Hi,
I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers
and kernel modules in emmy-w1-driver-sdiosdio are missing in the
deploy
On 9/28/19, JH wrote:
> On 9/27/19, Maciej Pijanowski wrote:
>>
>> On 27.09.2019 14:01, JH wrote:
>>> Hi,
>>>
>>> I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers
>>> and kernel modules in emmy-w1-driver-sdiosdio are missing in the
>>> deploy image, any clues why, how to deb
On 9/27/19, Maciej Pijanowski wrote:
>
> On 27.09.2019 14:01, JH wrote:
>> Hi,
>>
>> I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers
>> and kernel modules in emmy-w1-driver-sdiosdio are missing in the
>> deploy image, any clues why, how to debug it, how to fix it?
> It is no
On 27.09.2019 14:01, JH wrote:
> Hi,
>
> I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers
> and kernel modules in emmy-w1-driver-sdiosdio are missing in the
> deploy image, any clues why, how to debug it, how to fix it?
It is not clear to me what do you mean by including it i
Hi,
I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers
and kernel modules in emmy-w1-driver-sdiosdio are missing in the
deploy image, any clues why, how to debug it, how to fix it?
Thank you.
Kind regards,
- jh
--
___
yocto mailin
> 17 feb. 2019 kl. 14:57 skrev Russell Peterson :
>
> Hello,
>
> I have what I would think is an unusual requirement regarding a kernel module
> and could use some advice.
>
> I have a kernel module that has been heavily modified... to the point where
> we have a separate recipe for it and
Hello,
I have what I would think is an unusual requirement regarding a kernel
module and could use some advice.
I have a kernel module that has been heavily modified... to the point where
we have a separate recipe for it and treat it as an out-of-tree module.
This works by not setting the kernel
Hallo Yocto developpers,
I have been struggling a little to write recipe with kernel modules
depedency. It seems that this is not well documented and picked up some
solution across the mailing list and by reading the source. That is why
I'm wondering if my approach is correct or hopefully will
Thanks!!
Em 09/10/2015 04:25, "Khem Raj" escreveu:
>
> > On Oct 8, 2015, at 1:29 PM, Daniel. wrote:
> >
> > Hi all,
> >
> > Is the kernel-module- prefix mandatory for out-of-tree modules
> > compiled inside Yocto? And, This prefix applies to package names or
> > recipe names? Should I rename my
> On Oct 8, 2015, at 1:29 PM, Daniel. wrote:
>
> Hi all,
>
> Is the kernel-module- prefix mandatory for out-of-tree modules
> compiled inside Yocto? And, This prefix applies to package names or
> recipe names? Should I rename my recipe file with this prefix or setup
> PN stuff?
if you inherit
Hi all,
Is the kernel-module- prefix mandatory for out-of-tree modules
compiled inside Yocto? And, This prefix applies to package names or
recipe names? Should I rename my recipe file with this prefix or setup
PN stuff?
Cheers,
--
"Do or do not. There is no try"
Yoda Master
--
__
> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: June 03, 2015 3:42 AM
>
> On Tuesday 02 June 2015 19:58:50 Vuille, Martin wrote:
> > Yocto 1.6.1
> >
> > I have added a module to my kernel.
> >
> > The module is getting built, I see a kernel-module-
On Tuesday 02 June 2015 19:58:50 Vuille, Martin wrote:
> Yocto 1.6.1
>
> I have added a module to my kernel.
>
> The module is getting built, I see a kernel-module-blah-blah RPM
> and it contains the .ko
>
> I add kernel-module-blah-blah to one of the packagegroups
> contained in my image, I see
Yocto 1.6.1
I have added a module to my kernel.
The module is getting built, I see a kernel-module-blah-blah RPM
and it contains the .ko
I add kernel-module-blah-blah to one of the packagegroups
contained in my image, I see do_rootfs task run, but the module
is not in the image. In log.do_rootfs
On 15-01-15 22:51, Glenn Schmottlach wrote:
I am developing a codec kernel driver/module for the BeagleBone Black
and have a question about the recommended work-flow for developing
this module in the context of the Yocto/poky environment. Currently
I'm working with the Daisy release using the me
I am developing a codec kernel driver/module for the BeagleBone Black
and have a question about the recommended work-flow for developing
this module in the context of the Yocto/poky environment. Currently
I'm working with the Daisy release using the meta-ti layer and the
linux-ti-staging_3.14 kerne
Dilip,
You can take a look at this example :
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod
--
*dS
Diego Sueiro
sent from my droid tablet.
On Oct 11, 2013 11:17 PM, "Dilip Kumar" <008di...@gmail.com> wrote:
> Hi,
> What all the modifications has to
Hi,
What all the modifications has to be done and steps to follow for adding
external kernel module into the linux-yocto and checking that in qemulator.
regards
dilip
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/y
Hi,
I have an application recipe wich RDEPENDS on a couple of kernel modules
and is installed in my initramfs image. The dependency on the kernel
modules is expressed by:
RDEPENDS_${PN}_mymachine += "kernel-module-abc kernel-module-def"
This seems to work fine, expect that I now have a copy of t
20 matches
Mail list logo
