YUP! Thank you for the fix (I totally forgot about scripts directory).
Command: make scripts prepare solved it all!
Here is all captured (in order of execution):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/Issues/LKM/prepare_modules.log
These bugzillas will be still nice to have,
On Fri, May 24, 2019 at 8:50 AM Bruce Ashfield
wrote:
>
>
> On Fri, May 24, 2019 at 7:24 AM Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
>
>> As I said, I am a man of experimental try-outs. And here is the try!
>>
>> Now, after setting sources, I tried to compile the example (fro
> I'm going to create two new optional packages for the fall release
> that are simply captured kernel-source and kernel-headers for
> those uses cases where someone really does want the entire
> source tree, or just the headers. The details for that work are in
> bugzilla.
Could you, please, poin
On Fri, May 24, 2019 at 7:24 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> As I said, I am a man of experimental try-outs. And here is the try!
>
> Now, after setting sources, I tried to compile the example (from my Git):
> https://github.com/ZoranStojsavljevic/bbb-yocto/tree/ma
On Thu, May 23, 2019 at 9:00 PM Khem Raj wrote:
>
>
> On 5/23/19 3:32 AM, Zoran Stojsavljevic wrote:
> > After some tests (and I had other problems to take care of, as well),
> > here is the following:
> >
> >> These have all been discussed off an on over the past 5 years.
> >> I can't get at bug
As I said, I am a man of experimental try-outs. And here is the try!
Now, after setting sources, I tried to compile the example (from my Git):
https://github.com/ZoranStojsavljevic/bbb-yocto/tree/master/Issues/LKM
The results are the following (all on the target):
root@beaglebone:~# pwd
/home/roo
On 5/23/19 9:14 PM, Zoran Stojsavljevic wrote:
> I think this is a fair suggestion. Having prebuilt kernel available
> that contains the configuration and header files used in the build is
> all that is required for external modules to build in addition to
> toolchain, so maybe its worth a
> I think this is a fair suggestion. Having prebuilt kernel available
> that contains the configuration and header files used in the build is
> all that is required for external modules to build in addition to
> toolchain, so maybe its worth a try to create such a package and then
> have kernel-sou
On 5/23/19 3:32 AM, Zoran Stojsavljevic wrote:
After some tests (and I had other problems to take care of, as well),
here is the following:
These have all been discussed off an on over the past 5 years.
I can't get at bugzilla right now, but all the details are logged in cases.
A survey of a
On Thu, May 23, 2019 at 6:32 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> After some tests (and I had other problems to take care of, as well),
> here is the following:
>
> > These have all been discussed off an on over the past 5 years.
> > I can't get at bugzilla right now, b
After some tests (and I had other problems to take care of, as well),
here is the following:
> These have all been discussed off an on over the past 5 years.
> I can't get at bugzilla right now, but all the details are logged in cases.
> A survey of all the distros, their kernel package, etc, were
On Wed, May 15, 2019 at 4:09 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> > The core-image-kernel-dev image is how I do all my on target
> > testing when I introduce a new reference kernel for a release.
>
> Maybe you are correct. Maybe I should use/add in my local.conf the
> f
> The core-image-kernel-dev image is how I do all my on target
> testing when I introduce a new reference kernel for a release.
Maybe you are correct. Maybe I should use/add in my local.conf the following:
KERNEL_DEV_TOOLS ?= "packagegroup-core-tools-profile
packagegroup-core-buildessential kerne
On Wed, May 15, 2019 at 3:44 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> > That's correct. That command only adds the kernel source and
> > build infrastructure to the SDK, not to your target image. *You'd still*
> *> need to arrange to have the kernel-devsrc package installed
> That's correct. That command only adds the kernel source and
> build infrastructure to the SDK, not to your target image. *You'd still*
*> need to arrange to have the kernel-devsrc package installed on the*
*> target image if you want it on the board's rootfs.* How you arrange
> to have the packa
On Tue, May 14, 2019 at 1:30 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Hello Chris, Bruce,
>
> I have some additional data to share with you both, since I have tried
> something. And here is my take on the things!
>
> > 1. Build using a bb recipe.
> > Take a look at meta-ske
Hello Chris, Bruce,
I have some additional data to share with you both, since I have tried
something. And here is my take on the things!
> 1. Build using a bb recipe.
> Take a look at meta-skeleton/recipes-kernel/hello-mod for an example.
> You just need to add meta-skeleton to your bblayers.conf
Hello Bruce, Chris,
Thank you both for the replies.
Usually, the kernel header files/kernel source code for the used
kernels are put under: /usr/src/kernels/`uname -r`/
But this, my best guess, is an implementation detail (probably each
distro has its own rule/merit).
Since YOCTO is just one of
Hi Zoran,
There are two ways to do this
1. Build using a bb recipe.
Take a look at meta-skeleton/recipes-kernel/hello-mod for an example.
You just need to add meta-skeleton to your bblaysers.conf and then
bitbake hello-mod
2. Build from the SDK:
First, add the kernel source to the SDK by addi
On Sun, May 12, 2019 at 6:54 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Hello to the YOCTO community,
>
> I am using (to build the target for Beagle Bone Black) the following
> script:
> https://github.com/ZoranStojsavljevic/bbb-yocto
> https://github.com/ZoranStojsavljevic/b
20 matches
Mail list logo
