Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Khem Raj]

On Sat, Feb 2, 2019 at 7:17 PM Ken Sloat 
wrote:

> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
>  wrote:
> >
> > On 2019-02-02 9:59 p.m., Ken Sloat wrote:
> > > Hello,
> > >
> > > I have an out of tree kernel module which I want autoloaded at startup
> > > on my system. Looking at the Yocto project manual, I see that one way
> > > I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
> > > variable within my custom module recipe.
> > >
> > > What I have found is that the module-split class is indeed generating
> > > the "/etc/modules-load.d/mymodule.conf" file, however this file is not
> > > actually being installed. To be more precise it is appearing in the
> > > "package" directory (i.e.
> > > tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
> > > within the "image" directory (nor in my final rootfs).
> > >
> > > Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
> > > Is the intention for this variable I add extra steps to manually
> > > install this file in my recipe? FYI I'm using Morty.
> >
> > Can you provide your recipe ? It would make suggestions easier. For
> > example, my first question is: Is the module being installed to your
> > image via IMAGE_INSTALL, or some other similar variable ?
> >
> > Bruce
> >
> > >
> > > Thanks,
> > > Ken Sloat
> > >
> >
>
> Hi Bruce,
>
> Thanks for your quick reply. Yes the module is being installed via
> image_install. Module is installed but generated conf file is not. See
> recipe below:
>
> require mymodule.inc
>
> inherit module kernel-module-split
>
> DEPENDS = "virtual/kernel"
>
> EXTRA_OEMAKE_append = " \
> KERNELDIR=${STAGING_KERNEL_DIR} \
> "
>
> MAKE_TARGETS = "module"
>
> MODULE_NAME = "mymodule"
>
> PKG_${PN} = "kernel-module-${MODULE_NAME}"
>
> module_do_install() {
> install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
> install -m 0644 ${MODULE_NAME}.ko \
>
> ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
> }
>
> FILES_${PN} = " \
> /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
> "


Your recipe is overwriting common stuff which otherwise should be provided
by module bbclass
I would suggest that you append to the variables instead of over writing
them above and try to reuse
The primitives from bbclass as much as you can for best results

>
>
> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ken Sloat]

On Mon, Feb 4, 2019 at 10:50 AM Robert Berger
 wrote:
>
> Hi Ken,
>
> Is there any particular reason you don't use the sample[1] for an out of
> tree kernel module?
>
> [1]
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod
>
> Regards,
>
> Robert

Hi Robert,

We are running an older version of Yocto (Morty) for a customer. I
redacted the recipe name for the example I posted, but the recipe is
basically an identical copy of another recipe from newer versions of
Poky not present in Morty.

I might try to debug this more at some point, but the FILES statement
seems to make it work. Thanks for all the help everyone, I really
appreciate it.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] YPTM minutes

[Scott Rifenbark]

On Tue, Feb 5, 2019 at 1:05 PM akuster808  wrote:

>
>
> On 2/5/19 10:24 AM, Joshua Watt wrote:
>
> On Tue, 2019-02-05 at 10:11 -0800, Scott Rifenbark wrote:
>
>
>
> On Tue, Feb 5, 2019 at 8:37 AM  wrote:
>
> *Yocto Technical Team Minutes for Feb. 5, 2019.*
>
>
>
> Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen,
> Jan-Simon, Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate, Michael,
>
>
>
> YP 2.6.1 was released on Feb. 4, 2019.
>
> YP 2.7 M2 was built and is in QA and is 79% done.  See:
> https://wiki.yoctoproject.org/wiki/2.7_QA_Status
>
>
>
> Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in for YP
> 2.7
>
> We discussed that the YP 2.6 manual doesn’t have an upgrading to YP 2.6.
> Tracey will look into this.
>
>
> Can I get some clarification on this.  Ubuntu 18.04 seems to be an LTS.  I
> don't have "LTS" listed in the 2.6 ref-manual (
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros)
> but do have Ubuntu 18.04 listed as a supported distro.  What is meant by
> "... the YP 2.6 manual doesn't have an upgrading to YP 2.6."?  - Thanks
> Scott
>
>
> I think there is a little confusion here. There are actually 2 issues:
>
> 1) The Yocto 2.6 manual doesn't have the "Moving to the Yocto Project 2.6
> Release" section to describe the changes that have been made from 2.5 ->
> 2.6 (
> https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.5-release).
> Oddly, this section *is* present in the "latest" mega manual.
>
> 2) The second (unrelated) issue has to do with reporting 18.04 as a
> supported host distro. I'm not as familiar with this one, so I'll let
> someone else chime in.
>
>
> This is in thud-next:
>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta-poky/conf/distro/poky.conf?h=thud-next=263cf203bd363a6b9d58524ff5862d23c76e6390
>
> Once I get sumo stabilized, the same will be validated and back ported.
>

Once poky.conf is legit for a release, I have a script that extracts these
repos out and that is what I use for the manuals.
Thanks


> - armin
>
>
>
>
>
> We discussed the status of YP 2.7 upgrades and we are doing OK there.  We
> are struggling on new features YP 2.7.  Richard is primarily working to
> stabilize the autobuilder to produce an automated QA report to allow QA to
> transition from Intel.
>
>
>
> Richard discussed maintainers of OE-Core.  AUH is sending requests but not
> getting feedback.
>
>
>
> Richard discussed that we have issues with some products and need support
> from the community to fix.
>
>
>
> Tim discussed ptest issues Richard has identified.
>
>
>
> Richard asked if there were ideas about how to better communicate with the
> community. No specific suggestions.
>
>
>
> Thanks,
>
>
>
> *Stephen K. Jolley*
>
> *Yocto Project Project Manager*
>
> (*Cell*:(208) 244-4460
>
> * *Email*:  *sjolley.yp...@gmail.com
> *
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
> --
>
> Joshua Watt 
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] YPTM minutes

[akuster808]

On 2/5/19 10:24 AM, Joshua Watt wrote:
> On Tue, 2019-02-05 at 10:11 -0800, Scott Rifenbark wrote:
>>
>>
>> On Tue, Feb 5, 2019 at 8:37 AM > > wrote:
>>>
>>> *Yocto Technical Team Minutes for Feb. 5, 2019.*
>>>
>>>  
>>>
>>> Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen,
>>> Jan-Simon, Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate,
>>> Michael,
>>>
>>>  
>>>
>>> YP 2.6.1 was released on Feb. 4, 2019.
>>>
>>> YP 2.7 M2 was built and is in QA and is 79% done.  See:
>>> https://wiki.yoctoproject.org/wiki/2.7_QA_Status
>>>
>>>  
>>>
>>> Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in
>>> for YP 2.7
>>>
>>> We discussed that the YP 2.6 manual doesn’t have an upgrading to YP
>>> 2.6.  Tracey will look into this.
>>>
>>>
>>
>> Can I get some clarification on this.  Ubuntu 18.04 seems to be an
>> LTS.  I don't have "LTS" listed in the 2.6 ref-manual
>> (https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros)
>> but do have Ubuntu 18.04 listed as a supported distro.  What is meant
>> by "... the YP 2.6 manual doesn't have an upgrading to YP 2.6."?  -
>> Thanks Scott
>
> I think there is a little confusion here. There are actually 2 issues:
>
> 1) The Yocto 2.6 manual doesn't have the "Moving to the Yocto Project
> 2.6 Release" section to describe the changes that have been made from
> 2.5 -> 2.6
> (https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.5-release).
> Oddly, this section *is* present in the "latest" mega manual.
>
> 2) The second (unrelated) issue has to do with reporting 18.04 as a
> supported host distro. I'm not as familiar with this one, so I'll let
> someone else chime in.

This is in thud-next:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta-poky/conf/distro/poky.conf?h=thud-next=263cf203bd363a6b9d58524ff5862d23c76e6390

Once I get sumo stabilized, the same will be validated and back ported.

- armin
>
>>
>>>  
>>>
>>> We discussed the status of YP 2.7 upgrades and we are doing OK
>>> there.  We are struggling on new features YP 2.7.  Richard is
>>> primarily working to stabilize the autobuilder to produce an
>>> automated QA report to allow QA to transition from Intel.
>>>
>>>  
>>>
>>> Richard discussed maintainers of OE-Core.  AUH is sending requests
>>> but not getting feedback.
>>>
>>>  
>>>
>>> Richard discussed that we have issues with some products and need
>>> support from the community to fix.
>>>
>>>  
>>>
>>> Tim discussed ptest issues Richard has identified.
>>>
>>>  
>>>
>>> Richard asked if there were ideas about how to better communicate
>>> with the community. No specific suggestions.
>>>
>>>  
>>>
>>> Thanks,
>>>
>>>  
>>>
>>> */Stephen K. Jolley/**//*
>>>
>>> *Yocto Project Project Manager*
>>>
>>> (    *Cell*:    (208) 244-4460
>>>
>>> * *Email*:  _sjolley.yp...@gmail.com
>>> _
>>>
>>>  
>>>
>>> -- 
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org 
>>> https://lists.yoctoproject.org/listinfo/yocto
> -- 
> Joshua Watt mailto:jpewhac...@gmail.com>>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] YPTM minutes

[Scott Rifenbark]

On Tue, Feb 5, 2019 at 10:24 AM Joshua Watt  wrote:

> On Tue, 2019-02-05 at 10:11 -0800, Scott Rifenbark wrote:
>
>
>
> On Tue, Feb 5, 2019 at 8:37 AM  wrote:
>
> *Yocto Technical Team Minutes for Feb. 5, 2019.*
>
>
>
> Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen,
> Jan-Simon, Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate, Michael,
>
>
>
> YP 2.6.1 was released on Feb. 4, 2019.
>
> YP 2.7 M2 was built and is in QA and is 79% done.  See:
> https://wiki.yoctoproject.org/wiki/2.7_QA_Status
>
>
>
> Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in for YP
> 2.7
>
> We discussed that the YP 2.6 manual doesn’t have an upgrading to YP 2.6.
> Tracey will look into this.
>
>
> Can I get some clarification on this.  Ubuntu 18.04 seems to be an LTS.  I
> don't have "LTS" listed in the 2.6 ref-manual (
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros)
> but do have Ubuntu 18.04 listed as a supported distro.  What is meant by
> "... the YP 2.6 manual doesn't have an upgrading to YP 2.6."?  - Thanks
> Scott
>
>
> I think there is a little confusion here. There are actually 2 issues:
>
> 1) The Yocto 2.6 manual doesn't have the "Moving to the Yocto Project 2.6
> Release" section to describe the changes that have been made from 2.5 ->
> 2.6 (
> https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.5-release).
> Oddly, this section *is* present in the "latest" mega manual.
>

I think I know what happened here.  The tip of "thud" has the section on
migrating to YP 2.6.  However, as pointed out, the published 2.6 manual
does not have it.  During a release, docs lag behind software and
everything else that gets locked down.  I wrote that section for the 2.6
release of the manuals.  Likely, some important fix had to be back-ported
to the manuals post-release and I probably was working from a cloned thud
repo that was checked out on the tag "Yocto-2.6", which is earlier than the
commits for that section.  So, when I rebuilt manuals post-release for
various reasons, it was not included.  I can fix that for the 2.6 version
of the manual.  It is already present in the newly released 2.6.1 version
of the manual.  This problem is ongoing with the docs.  I just recently
have come up with a work-around for these types of situations.  I am now
keeping a local area of changed doc source files per-release for released
manuals.  That way, in the future, I can checkout a release by tag, make
any special changes, and then populate the local repo with the previously
changed files.  Rebuilding then produces manuals with all the one-off
changes that have occurred. - Thanks for the clarification Joshua.


> 2) The second (unrelated) issue has to do with reporting 18.04 as a
> supported host distro. I'm not as familiar with this one, so I'll let
> someone else chime in.
>
>
>
>
> We discussed the status of YP 2.7 upgrades and we are doing OK there.  We
> are struggling on new features YP 2.7.  Richard is primarily working to
> stabilize the autobuilder to produce an automated QA report to allow QA to
> transition from Intel.
>
>
>
> Richard discussed maintainers of OE-Core.  AUH is sending requests but not
> getting feedback.
>
>
>
> Richard discussed that we have issues with some products and need support
> from the community to fix.
>
>
>
> Tim discussed ptest issues Richard has identified.
>
>
>
> Richard asked if there were ideas about how to better communicate with the
> community. No specific suggestions.
>
>
>
> Thanks,
>
>
>
> *Stephen K. Jolley*
>
> *Yocto Project Project Manager*
>
> (*Cell*:(208) 244-4460
>
> * *Email*:  *sjolley.yp...@gmail.com
> *
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
> --
>
> Joshua Watt 
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto doc typo

[Scott Rifenbark]

Ahh... The elusive "eSDSK"... :)

Thanks Brian.  I will fix that right away.

Here is the section in the 2.6.1 manual -
https://yoctoproject.org/docs/2.6.1/overview-manual/overview-manual.html#openembedded-build-system-workflow
.
Here is the section in the "latest" (2.7) manual -
https://yoctoproject.org/docs/2.7/overview-manual/overview-manual.html#openembedded-build-system-workflow

Scott.

On Tue, Feb 5, 2019 at 10:09 AM Brian Silverman 
wrote:

> Minor typo at (eSDSK -> eSDK):
>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/tree/documentation/overview-manual/overview-manual-yp-intro.xml#n1160
>
>
>
>
> --
> Brian Silverman
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] YPTM minutes

[Joshua Watt]

On Tue, 2019-02-05 at 10:11 -0800, Scott Rifenbark wrote:
> On Tue, Feb 5, 2019 at 8:37 AM  wrote:
> > Yocto Technical Team Minutes for Feb. 5, 2019.
> >  
> > Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen,
> > Jan-Simon, Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate,
> > Michael, 
> >  
> > YP 2.6.1 was released on Feb. 4, 2019.
> > YP 2.7 M2 was built and is in QA and is 79% done.  See: 
> > https://wiki.yoctoproject.org/wiki/2.7_QA_Status
> >  
> > Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in
> > for YP 2.7 
> > We discussed that the YP 2.6 manual doesn’t have an upgrading to YP
> > 2.6.  Tracey will look into this.
> 
> Can I get some clarification on this.  Ubuntu 18.04 seems to be an
> LTS.  I don't have "LTS" listed in the 2.6 ref-manual (
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros
> ) but do have Ubuntu 18.04 listed as a supported distro.  What is
> meant by "... the YP 2.6 manual doesn't have an upgrading to YP
> 2.6."?  - Thanks Scott

I think there is a little confusion here. There are actually 2 issues:
 1) The Yocto 2.6 manual doesn't have the "Moving to the Yocto Project
2.6 Release" section to describe the changes that have been made from
2.5 -> 2.6 (
https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.5-release
). Oddly, this section *is* present in the "latest" mega manual.
 2) The second (unrelated) issue has to do with reporting 18.04 as a
supported host distro. I'm not as familiar with this one, so I'll let
someone else chime in.
>  
> >  
> > We discussed the status of YP 2.7 upgrades and we are doing OK
> > there.  We are struggling on new features YP 2.7.  Richard is
> > primarily working to stabilize the autobuilder to produce an
> > automated QA report to allow QA to transition from Intel. 
> >  
> > Richard discussed maintainers of OE-Core.  AUH is sending requests
> > but not getting feedback. 
> >  
> > Richard discussed that we have issues with some products and need
> > support from the community to fix.
> >  
> > Tim discussed ptest issues Richard has identified.
> >  
> > Richard asked if there were ideas about how to better communicate
> > with the community. No specific suggestions.
> >  
> > Thanks,
> >  
> > Stephen K. Jolley
> > Yocto Project Project Manager
> > (Cell:(208) 244-4460
> > * Email:  sjolley.yp...@gmail.com
> >  -- 
> > 
> > ___
> > 
> > yocto mailing list
> > 
> > yocto@yoctoproject.org
> > 
> > https://lists.yoctoproject.org/listinfo/yocto
> > 
-- 
Joshua Watt 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto touchscreen

[Zoran Stojsavljevic]

Hello Nikola,

Let us try to cut to the chase!

After reading what Marc Ferland says/writes, and looking into the following:
https://bugzilla.redhat.com/show_bug.cgi?id=1650634

I have spotted the following:
*Pat Riehecky ** 2018-11-20 14:28:22 UTC *


*the bug remains with the elrepo
kernels:kernel-ml-4.19.2-1.el7.elrepo.x86_64kernel-lt-4.4.163-1.el7.elrepo.x86_64*

I never had this problem since I do not use Xorg (GFX), rather I only
use serial console from VBox VM from my BBB (pass-through).

Thus, my suggestion for you, to skip the whole mess is to rebuild your
distro *in the light of YOCTO Project 2.6.1 (thud 20.0.0.1).*

My best guess (then you'll inherit YOCTO kernel 4.20.x with fixed Xorg -
X11).

I am using Fedora 29 on my laptop. Also from the bugzilla:
*Pat Riehecky ** 2018-11-20 15:46:11 UTC *

*Bug resolved by rebuilding xorg-x11-server-1.20.3-1.fc29 [1] for 7.6.*
*With this in mind it appears to be an Xorg server bug rather than fbdev.*

>From my HP EliteBook 840 G1 Fedora 29, Xorg.0.log - February 5th, 2019.,
I have the following:

[26.955] Kernel command line: BOOT_IMAGE=/
*vmlinuz-4.20.6-200.fc29.x86_64*
root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap
rhgb
quiet LANG=en_US.UTF-8
[26.955] Build Date: 11 January 2019  12:47:38PM
*[26.955] Build ID: xorg-x11-se**rver 1.20.3-3.fc29*
[26.955] Current version of pixman: 0.34.0

Best Regards,
Zoran
___

On Tue, Feb 5, 2019 at 2:49 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
>
> Hello Nikola,
>
> > I created a kernel recipe with a bbappend file, and, I added
> > the same defconfig that I used for krogoth version.
> > The bbappend for kernel recipe concern meta-ti layer.
> > I didn't edited defconfig file in other layers which contain a
> > kernel recipe.
>
> It could be some problem that Sumo does not take your bbappend file into
the
> consideration as placed.
>
> It could be something else, as well.
>
> I have the same issue with my defconfig file for my Thud Beagle Bone
Black (BBB)
> standard board. Every time I recompile my YOCTO for it for different
releases, I need
> to import my specific defconfig. But I use complete different repos for
my standard
> Beagle Bone Black than YOCTO BBB Poky reference distro.
>
> Here is what I use in Thud (my bblayers.conf):
>
> POKY_BBLAYERS_CONF_VERSION = "2"
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /home/user/projects2/beaglebone-black/yocto-thud/meta-bbb \
>
/home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-networking
\
>
/home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-oe \
>
/home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-python
\
> /home/user/projects2/beaglebone-black/yocto-thud/meta-qt5 \
> /home/user/projects2/beaglebone-black/yocto-thud/poky/meta \
> /home/user/projects2/beaglebone-black/yocto-thud/poky/meta-poky"
>
> There, I replace defconfig in this layer:
/home/user/projects2/beaglebone-black/yocto-thud/meta-bbb
> with my own defconfig.
>
> In the directory:
>
/home/user/projects2/beaglebone-black/yocto-thud/meta-bbb/recipes-kernel/linux/linux-stable-4.19/beaglebone
>
> If you use only Poky repository, then you need to read the following
paragraph (how to use
> your defconfig with Poky):
>
> [2.3.3. Changing the Configuration] YOCTO Project Linux Development Manual
>
https://www.yoctoproject.org/docs/2.5/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
> 2.3.3. Changing the Configuration
>
> I hope this will help. Please, keep us posted!
>
> Zoran
> ___
>
>
> On Tue, Feb 5, 2019 at 10:54 AM Stanisavljevic <
n.stanisavlje...@polycaptil.fr> wrote:
>>
>> Hy Zoran
>>
>> Thank's to take time to answer
>>
>> I created a kernel recipe with a bbappend file, and, I added the same
defconfig that I used for krogoth version.
>> The bbappend for kernel recipe concern meta-ti layer.
>> I didn't edited defconfig file in other layers which contain a kernel
recipe.
>>
>> I think it's a problem which concern the screen resolution, screen
frequency and adc touchscreen.
>> Something is different between the krogoth and sumo version, but I
didn't find what is changed...
>>
>> Xrandr show that problem is maybe around the screen resolution.
>> It's show the next message : "Size 1024x768 not found in available modes"
>> Maybe it was changed between krogoth and sumo version...but I don't know
where it is indicated if sources files...
>>
>> What do you think ? problem can be around the screen resolution, screen
frequency and adc touchscreen ?
>>
>> Nikola
>>
>> -Message d'origine-
>> De : Zoran Stojsavljevic 
>> Envoyé : lundi 4 février 2019 17:08
>> À : Stanisavljevic 
>> Cc : Yocto Project 
>> Objet : Re: [yocto] yocto touchscreen
>>
>> > I built a first version of this os with version krogoth and it works
fine.
>> >
>> > Now I build a second version of this os with version sumo and the
>> > touch screen works fine during boot 

Re: [yocto] YPTM minutes

[Scott Rifenbark]

On Tue, Feb 5, 2019 at 8:37 AM  wrote:

> *Yocto Technical Team Minutes for Feb. 5, 2019.*
>
>
>
> Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen,
> Jan-Simon, Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate, Michael,
>
>
>
> YP 2.6.1 was released on Feb. 4, 2019.
>
> YP 2.7 M2 was built and is in QA and is 79% done.  See:
> https://wiki.yoctoproject.org/wiki/2.7_QA_Status
>
>
>
> Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in for YP
> 2.7
>
> We discussed that the YP 2.6 manual doesn’t have an upgrading to YP 2.6.
> Tracey will look into this.
>

Can I get some clarification on this.  Ubuntu 18.04 seems to be an LTS.  I
don't have "LTS" listed in the 2.6 ref-manual (
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros)
but do have Ubuntu 18.04 listed as a supported distro.  What is meant by
"... the YP 2.6 manual doesn't have an upgrading to YP 2.6."?  - Thanks
Scott


>
> We discussed the status of YP 2.7 upgrades and we are doing OK there.  We
> are struggling on new features YP 2.7.  Richard is primarily working to
> stabilize the autobuilder to produce an automated QA report to allow QA to
> transition from Intel.
>
>
>
> Richard discussed maintainers of OE-Core.  AUH is sending requests but not
> getting feedback.
>
>
>
> Richard discussed that we have issues with some products and need support
> from the community to fix.
>
>
>
> Tim discussed ptest issues Richard has identified.
>
>
>
> Richard asked if there were ideas about how to better communicate with the
> community. No specific suggestions.
>
>
>
> Thanks,
>
>
>
> *Stephen K. Jolley*
>
> *Yocto Project Project Manager*
>
> (*Cell*:(208) 244-4460
>
> * *Email*:  *sjolley.yp...@gmail.com
> *
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto touchscreen

[Marc Ferland]

Looks like: https://bugzilla.redhat.com/show_bug.cgi?id=1650634

Good luck!

On Tue, Feb 5, 2019 at 10:30 AM Stanisavljevic <
n.stanisavlje...@polycaptil.fr> wrote:

> Hy Marc,
>
>
>
> Here is the log file attached in this mail.
>
>
>
> Nikola
>
> *De :* Marc Ferland 
> *Envoyé :* mardi 5 février 2019 16:10
> *À :* Stanisavljevic 
> *Cc :* Yocto discussion list 
> *Objet :* Re: [yocto] yocto touchscreen
>
>
>
> On Mon, Feb 4, 2019 at 6:17 AM Stanisavljevic <
> n.stanisavlje...@polycaptil.fr> wrote:
>
> Hy Team,
>
>
>
> I have a problem
>
>
>
> I buid a custom os for AM335x processor and I used yocto to do it.
>
>
>
> I build a first version of this os with version krogoth and it work fine.
>
>
>
> Now I build a second version of this os with version sumo and the
> touchscreen work fine during boot process but when kernel is loaded,
> touchscreen freeze / lock and impossible to use it.
>
> The terminal is printed on the touchscreen but the screen is locked,
> impossible to write a command or to move the mouse to select, ….
>
>
>
> Here is the log of boot to the user session (log got with serial
> communication between PC and board) :
>
>
>
> ...
>
> X.Org X Server 1.19.6
>
> Release Date: 2017-12-20
>
> X Protocol Version 11, Revision 0
>
> Build Operating System: Linux 4.15.0-38-generic x86_64
>
> Current Operating System: Linux polycaptil-machine-am335x-evmsk
> 4.4.19-ge581bb1cac #1 PREEMPT Thu May 24 11:42:17 CEST 2018 armv7l
>
> Kernel command line: console=ttyO0,115200 root=/dev/mmcblk0p3 rw
>
> Build Date: 05 November 2018  09:33:21PM
>
>
>
> Current version of pixman: 0.34.0
>
> Before reporting problems, check http://wiki.x.org
>
> to make sure that you have the latest version.
>
> Markers: (--) probed, (**) from config file, (==) default setting,
>
> (++) from command line, (!!) notice, (II) informational,
>
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb  1 20:08:02 2019
>
> (==) Using config file: "/etc/X11/xorg.conf"
>
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>
> done.
>
>
>
> Please post the full /var/log/Xorg.log.
>
>
>
> Marc
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] New e-mail address

[sjolley.yp.pm]

All,

 

I have moved from stephen.k.jol...@intel.com
  to sjolley.yp...@gmail.com
  for my e-mail address I am using for the
Yocto Project PM work.   Please use the new e-mail address if you wish to
communicate with me going forward.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] YPTM minutes

[sjolley.yp.pm]

Yocto Technical Team Minutes for Feb. 5, 2019.

 

Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen, Jan-Simon,
Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate, Michael, 

 

YP 2.6.1 was released on Feb. 4, 2019.

YP 2.7 M2 was built and is in QA and is 79% done.  See:

https://wiki.yoctoproject.org/wiki/2.7_QA_Status

 

Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in for YP
2.7 

We discussed that the YP 2.6 manual doesn't have an upgrading to YP 2.6.
Tracey will look into this.

 

We discussed the status of YP 2.7 upgrades and we are doing OK there.  We
are struggling on new features YP 2.7.  Richard is primarily working to
stabilize the autobuilder to produce an automated QA report to allow QA to
transition from Intel. 

 

Richard discussed maintainers of OE-Core.  AUH is sending requests but not
getting feedback. 

 

Richard discussed that we have issues with some products and need support
from the community to fix.

 

Tim discussed ptest issues Richard has identified.

 

Richard asked if there were ideas about how to better communicate with the
community. No specific suggestions.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Happy to be hear.

[Nicolas Dechesne]

hey Mbha,

On Tue, Feb 5, 2019 at 3:00 PM Matt-Klaus Mushi
 wrote:
>
> Greetings, to the brains behind the YoctoProject.
>
> My name is Mbah Matt-Klaus, an undergrad student from Cameroon.
> Our community here encourages contributing to OpenSource, and there have been 
> a lot going on.

welcome to this mailing list, and thanks for your message!

>
> So, I went through a list of OS communities, and my greatest interest was in 
> this community (due to my love for electronics and embedded systems). My 
> excitement led me to watch a few videos, read from YoctoProject and 
> consequently subscribe. Despite this, I am new to Yocto and Linux (I 
> basically use Linux Mint on my dual-booted PC). I would appreciate any 
> materials to get me up to speed (I program in Python and C++).
>

You've probably found by now the Yocto Project online documentation,
if you need help with that, please let me know.

A Linux PC is all you need to get started. You probably should try to
build your first images for QEMU and run them on your PC. The entire
project is extensively developed and tested using QEMU, so you don't
really need any additional hardware to get started. Once you are
familiar with building and running your images, you could have a look
at Bugzilla and browse through the open issues, and try to pick one of
them. That's a good way to start with something concrete.

> Thanks in advance.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW06'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3

Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Anuj 
*   SWAT team rotation: Anuj -> Paul on Feb. 8, 2019
*   SWAT team rotation: Paul -> Ross on Feb. 15, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP 2.6.1 was released on Feb. 4, 2019.
*   YP 2.7 M2 was built and is in QA and is 79% done.  See:

https://wiki.yoctoproject.org/wiki/2.7_QA_Status
*   Some major recipe upgrades merged (glibc, binutils, llvm)
*   Some "prework" patches for various series merged (util-linux,
virtgl) but the main series are still pending development or review
*   Various ptest-runner and ptest runtime testing integration fixes
merged but many problems with the tests remain no volunteers to help resolve
issues.
*   We're seeing test failures which highlight major problems with the
archiver class, in particular the src.rpm component of it. I've proposed we
remove it, if you do care about it please step up and help fix it else it
will be removed. The src.rpm support is limited anyhow and likely to mislead
user expectations so removing it may be a good thing.
*   The recipe reporting system integration with the layer index is now
complete and available at:

https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/. Historical data
has not yet been imported to it.
*   The project autobuilder is running at slightly reduced capacity (but
not functionality) due to hardware failures.
*   The project is considering moving its mailing list hosting to
groups.io, if anyone has any experience of that, positive or negative please
let Michael, Nico and Richard know
*   We're becoming seriously concerned about the lack of response to the
last round of AUH patches

 

Planned Releases for YP 2.7:

*   YP 2.7 M2 is built and in QA.
*   YP 2.7 M2 Release Target is Feb. 1, 2019
*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2356 (last week 2393) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1572 (last week 1583
*   Patches in the Pending State: 678 (43%) [last week 677 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.27

[Bruce Ashfield]

On 2/5/19 9:06 AM, Paul Gortmaker wrote:

Bruce, Yocto kernel folks:

Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.26 release.

There are about 215 commits here, based on commits chosen from what
were used in the existing 4.19.16 --> 4.19.18 stable releases, so back
to "normal" vs. what was done for 4.18.26 content choices.

I've put this 4.18.x queue through the usual testing; build testing
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
and finally some sanity runtime tests on x86-64.

I did the signed tag just as per the previously released versions.
Please find a signed v4.18.27 tag using this key:

http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6

in the repo in the kernel.org directory here:

https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/
git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git


Thanks Paul,

This is merged.

Bruce



for merge to standard/base in linux-yocto-4.18 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 4.18.x release.

Paul.



--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] yocto touchscreen

[Marc Ferland]

On Mon, Feb 4, 2019 at 6:17 AM Stanisavljevic <
n.stanisavlje...@polycaptil.fr> wrote:

> Hy Team,
>
>
>
> I have a problem
>
>
>
> I buid a custom os for AM335x processor and I used yocto to do it.
>
>
>
> I build a first version of this os with version krogoth and it work fine.
>
>
>
> Now I build a second version of this os with version sumo and the
> touchscreen work fine during boot process but when kernel is loaded,
> touchscreen freeze / lock and impossible to use it.
>
> The terminal is printed on the touchscreen but the screen is locked,
> impossible to write a command or to move the mouse to select, ….
>
>
>
> Here is the log of boot to the user session (log got with serial
> communication between PC and board) :
>
>
>
...

> X.Org X Server 1.19.6
>
> Release Date: 2017-12-20
>
> X Protocol Version 11, Revision 0
>
> Build Operating System: Linux 4.15.0-38-generic x86_64
>
> Current Operating System: Linux polycaptil-machine-am335x-evmsk
> 4.4.19-ge581bb1cac #1 PREEMPT Thu May 24 11:42:17 CEST 2018 armv7l
>
> Kernel command line: console=ttyO0,115200 root=/dev/mmcblk0p3 rw
>
> Build Date: 05 November 2018  09:33:21PM
>
>
>
> Current version of pixman: 0.34.0
>
> Before reporting problems, check http://wiki.x.org
>
> to make sure that you have the latest version.
>
> Markers: (--) probed, (**) from config file, (==) default setting,
>
> (++) from command line, (!!) notice, (II) informational,
>
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb  1 20:08:02 2019
>
> (==) Using config file: "/etc/X11/xorg.conf"
>
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>
> done.
>

Please post the full /var/log/Xorg.log.

Marc
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] v4.18.x - stable updates comprising v4.18.27

[Paul Gortmaker]

Bruce, Yocto kernel folks:

Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.26 release.

There are about 215 commits here, based on commits chosen from what
were used in the existing 4.19.16 --> 4.19.18 stable releases, so back
to "normal" vs. what was done for 4.18.26 content choices.

I've put this 4.18.x queue through the usual testing; build testing
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
and finally some sanity runtime tests on x86-64.

I did the signed tag just as per the previously released versions.
Please find a signed v4.18.27 tag using this key:

http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6

in the repo in the kernel.org directory here:

   https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/
   git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git

for merge to standard/base in linux-yocto-4.18 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

   https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 4.18.x release.

Paul.
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] Happy to be hear.

[Matt-Klaus Mushi]

Greetings, to the brains behind the YoctoProject.

My name is Mbah Matt-Klaus, an undergrad student from Cameroon.
Our community here encourages contributing to OpenSource, and there have
been a lot going on.

So, I went through a list of OS communities, and my greatest interest was
in this community (due to my love for electronics and embedded systems). My
excitement led me to watch a few videos, read from YoctoProject
 and consequently subscribe. Despite this, I am
new to Yocto and Linux (I basically use Linux Mint on my dual-booted PC). I
would appreciate any materials to get me up to speed (I program in Python
and C++).

Thanks in advance.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto touchscreen

[Zoran Stojsavljevic]

Hello Nikola,

> I created a kernel recipe with a bbappend file, and, I added
> the same defconfig that I used for krogoth version.
> The bbappend for kernel recipe concern meta-ti layer.
> I didn't edited defconfig file in other layers which contain a
> kernel recipe.

It could be some problem that Sumo does not take your bbappend file into the
consideration as placed.

It could be something else, as well.

I have the same issue with my defconfig file for my Thud Beagle Bone Black
(BBB)
standard board. Every time I recompile my YOCTO for it for different
releases, I need
to import my specific defconfig. But I use complete different repos for my
standard
Beagle Bone Black than YOCTO BBB Poky reference distro.

Here is what I use in Thud (my bblayers.conf):

POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
/home/user/projects2/beaglebone-black/yocto-thud/meta-bbb \

/home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-networking
\

/home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-oe \

/home/user/projects2/beaglebone-black/yocto-thud/meta-openembedded/meta-python
\
/home/user/projects2/beaglebone-black/yocto-thud/meta-qt5 \
/home/user/projects2/beaglebone-black/yocto-thud/poky/meta \
/home/user/projects2/beaglebone-black/yocto-thud/poky/meta-poky"

There, I replace defconfig in this layer:
/home/user/projects2/beaglebone-black/yocto-thud/meta-bbb
with my own defconfig.

In the directory:
/home/user/projects2/beaglebone-black/yocto-thud/meta-bbb/recipes-kernel/linux/linux-stable-4.19/beaglebone

If you use only Poky repository, then you need to read the following
paragraph (how to use
your defconfig with Poky):



*[2.3.3. Changing the Configuration] YOCTO Project Linux Development
Manualhttps://www.yoctoproject.org/docs/2.5/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
*
*2.3.3. Changing the Configuration*

I hope this will help. Please, keep us posted!

Zoran
___


On Tue, Feb 5, 2019 at 10:54 AM Stanisavljevic <
n.stanisavlje...@polycaptil.fr> wrote:

> Hy Zoran
>
> Thank's to take time to answer
>
> I created a kernel recipe with a bbappend file, and, I added the same
> defconfig that I used for krogoth version.
> The bbappend for kernel recipe concern meta-ti layer.
> I didn't edited defconfig file in other layers which contain a kernel
> recipe.
>
> I think it's a problem which concern the screen resolution, screen
> frequency and adc touchscreen.
> Something is different between the krogoth and sumo version, but I didn't
> find what is changed...
>
> Xrandr show that problem is maybe around the screen resolution.
> It's show the next message : "Size 1024x768 not found in available modes"
> Maybe it was changed between krogoth and sumo version...but I don't know
> where it is indicated if sources files...
>
> What do you think ? problem can be around the screen resolution, screen
> frequency and adc touchscreen ?
>
> Nikola
>
> -Message d'origine-
> De : Zoran Stojsavljevic 
> Envoyé : lundi 4 février 2019 17:08
> À : Stanisavljevic 
> Cc : Yocto Project 
> Objet : Re: [yocto] yocto touchscreen
>
> > I built a first version of this os with version krogoth and it works
> fine.
> >
> > Now I build a second version of this os with version sumo and the
> > touch screen works fine during boot process but when kernel is loaded,
> > touchscreen freeze / lock and impossible to use it.
>
> Did you compare Krogoth kernel defconfig with Sumo kernel defconfig?
>
> May there are some mismatches in drivers' setup between these two?
>
> Zoran
> ___
>
> On Mon, Feb 4, 2019 at 12:24 PM Stanisavljevic <
> n.stanisavlje...@polycaptil.fr> wrote:
> >
> > Hy Team,
> >
> >
> >
> > I have a problem
> >
> >
> >
> > I buid a custom os for AM335x processor and I used yocto to do it.
> >
> >
> >
> > I build a first version of this os with version krogoth and it work fine.
> >
> >
> >
> > Now I build a second version of this os with version sumo and the
> touchscreen work fine during boot process but when kernel is loaded,
> touchscreen freeze / lock and impossible to use it.
> >
> > The terminal is printed on the touchscreen but the screen is locked,
> impossible to write a command or to move the mouse to select, ….
> >
> >
> >
> > Here is the log of boot to the user session (log got with serial
> communication between PC and board) :
> >
> >
> >
> > U-Boot SPL 2017.05-1-g041a398 (May 02 2018 - 18:36:57)
> >
> > Trying to boot from MMC1
> >
> > reading uboot.env
> >
> > reading u-boot.img
> >
> > reading u-boot.img
> >
> > reading u-boot.img
> >
> > reading u-boot.img
> >
> >
> >
> >
> >
> > U-Boot 2017.05-1-g041a398 (May 02 2018 - 18:36:57 +0200)
> >
> >
> >
> > CPU  : AM335X-GP rev 2.1
> >
> > Model: TI AM335x EVM-SK
> >
> > DRAM:  256 MiB
> >
> > NAND:  0 MiB
> >
> > MMC:   OMAP SD/MMC: 0, OMAP 

Re: [yocto] How to add/modify files in the root file systems in Yocto

[Nicolas Dechesne]

hi,

On Tue, Feb 5, 2019 at 1:30 PM Bhupendra Singh <
bhupendra.si...@ppsinternational.in> wrote:

>
>
> Dear sir,
>
> Are there any examples on how to add startup scripts and other files to
> the target root file system using yocto? ie placing shell scripts into the
> etc/init.d directory.
>

Please have a first look at the documentation on this topic:
https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#new-recipe-enabling-system-services

and let us know if you have any more questions.


>
>
>
>
> Thanks & Regards
>
> Bhupendra Singh
>
> Mob.+919599502188
>
>  [image: cid:image001.png@01CC0B4C.B6F26260]
>
>  PT Communication Systems Pvt. Ltd.
>
>  32,Udyog Kendra, Echotech III,Greater Noida (U.P.) 201308  India
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to add/modify files in the root file systems in Yocto

[Bhupendra Singh]

 

Dear sir,

Are there any examples on how to add startup scripts and other files to the
target root file system using yocto? ie placing shell scripts into the
etc/init.d directory.

 

 

Thanks & Regards

Bhupendra Singh

Mob.+919599502188

 cid:image001.png@01CC0B4C.B6F26260

 PT Communication Systems Pvt. Ltd.

 32,Udyog Kendra, Echotech III,Greater Noida (U.P.) 201308  India

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto touchscreen

[Stanisavljevic]

Hy Zoran

Thank's to take time to answer

I created a kernel recipe with a bbappend file, and, I added the same defconfig 
that I used for krogoth version.
The bbappend for kernel recipe concern meta-ti layer.
I didn't edited defconfig file in other layers which contain a kernel recipe.

I think it's a problem which concern the screen resolution, screen frequency 
and adc touchscreen.
Something is different between the krogoth and sumo version, but I didn't find 
what is changed...

Xrandr show that problem is maybe around the screen resolution.
It's show the next message : "Size 1024x768 not found in available modes"
Maybe it was changed between krogoth and sumo version...but I don't know where 
it is indicated if sources files...

What do you think ? problem can be around the screen resolution, screen 
frequency and adc touchscreen ?

Nikola

-Message d'origine-
De : Zoran Stojsavljevic  
Envoyé : lundi 4 février 2019 17:08
À : Stanisavljevic 
Cc : Yocto Project 
Objet : Re: [yocto] yocto touchscreen

> I built a first version of this os with version krogoth and it works fine.
>
> Now I build a second version of this os with version sumo and the 
> touch screen works fine during boot process but when kernel is loaded, 
> touchscreen freeze / lock and impossible to use it.

Did you compare Krogoth kernel defconfig with Sumo kernel defconfig?

May there are some mismatches in drivers' setup between these two?

Zoran
___

On Mon, Feb 4, 2019 at 12:24 PM Stanisavljevic  
wrote:
>
> Hy Team,
>
>
>
> I have a problem
>
>
>
> I buid a custom os for AM335x processor and I used yocto to do it.
>
>
>
> I build a first version of this os with version krogoth and it work fine.
>
>
>
> Now I build a second version of this os with version sumo and the touchscreen 
> work fine during boot process but when kernel is loaded, touchscreen freeze / 
> lock and impossible to use it.
>
> The terminal is printed on the touchscreen but the screen is locked, 
> impossible to write a command or to move the mouse to select, ….
>
>
>
> Here is the log of boot to the user session (log got with serial 
> communication between PC and board) :
>
>
>
> U-Boot SPL 2017.05-1-g041a398 (May 02 2018 - 18:36:57)
>
> Trying to boot from MMC1
>
> reading uboot.env
>
> reading u-boot.img
>
> reading u-boot.img
>
> reading u-boot.img
>
> reading u-boot.img
>
>
>
>
>
> U-Boot 2017.05-1-g041a398 (May 02 2018 - 18:36:57 +0200)
>
>
>
> CPU  : AM335X-GP rev 2.1
>
> Model: TI AM335x EVM-SK
>
> DRAM:  256 MiB
>
> NAND:  0 MiB
>
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>
> reading uboot.env
>
> ERROR: No USB device found
>
>
>
> at drivers/usb/gadget/ether.c:2709/usb_ether_init()
>
> Net:   CACHE: Misaligned operation at range [8df323c0, 8df32464]
>
>
>
> Warning: ethernet@4a10 using MAC address from ROM
>
> eth0: ethernet@4a10
>
> Hit any key to stop autoboot:  0
>
> reading zImage
>
> 3412752 bytes read in 251 ms (13 MiB/s)
>
> reading dtb
>
> 39733 bytes read in 12 ms (3.2 MiB/s)
>
> ## Flattened Device Tree blob at 8200
>
>Booting using the fdt blob at 0x8200
>
>Loading Device Tree to 8df19000, end 8df25b34 ... OK
>
>
>
> Starting kernel ...
>
>
>
> [0.00] Booting Linux on physical CPU 0x0
>
> [0.00] Initializing cgroup subsys cpu
>
> [0.00] Initializing cgroup subsys cpuacct
>
> [0.00] Linux version 4.4.19-ge581bb1cac 
> (polycaptil@polycaptil-HP-Notebook) (gcc version 5.3.0 (GCC) ) #1 PREEMPT Thu 
> May 24 11:42:17 CEST 2018
>
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
>
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache
>
> [0.00] Machine model: TI AM335x EVM-SK
>
> [0.00] cma: Reserved 48 MiB at 0x8a80
>
> [0.00] Memory policy: Data cache writeback
>
> [0.00] CPU: All CPU(s) started in SVC mode.
>
> [0.00] AM335X ES2.1 (sgx neon )
>
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
> pages: 64960
>
> [0.00] Kernel command line: console=ttyO0,115200 root=/dev/mmcblk0p3 
> rw
>
> [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes)
>
> [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
>
> [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
>
> [0.00] Memory: 200444K/262144K available (6495K kernel code, 313K 
> rwdata, 2368K rodata, 260K init, 265K bss, 12548K reserved, 49152K 
> cma-reserved, 0K highmem)
>
> [0.00] Virtual kernel memory layout:
>
> [0.00] vector  : 0x - 0x1000   (   4 kB)
>
> [0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
>
> [0.00] vmalloc : 0xd080 - 0xff80   ( 752 MB)
>
> [0.00] lowmem  : 0xc000 - 0xd000   ( 256 MB)
>
> [0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
>
> [0.00] modules : 0xbf00 - 

Re: [yocto] cmake / no such file or directory ??!

[Guy Morand]

Sorry Yocto developers!

I have found the issue, in my CMakeLists.txt, I changed this:
set(CMAKE_CXX_FLAGS "-Wall -Wextra -Werror")

to this:
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wextra -Werror")

Now it works like a charm, stupid me :D! Sorry for all the noise!

Best regards,

Guy Morand

On 2/5/19 8:21 AM, Guy Morand wrote:


Hello Yocto developpers!

I'm facing a weird problem that seems very strange. I can 
cross-compile a project based on cmake with the generated Yocto SDK.


However, after adding a recipe, the compilation fails:
/mnt/ssd/yocto-build-script/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/communication-library/git-AUTOINC+f5cd493ce5-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++ 
-Dcommunication_interface_EXPORTS 
-I/mnt/ssd/yocto-build-script/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/communication-library/git-AUTOINC+f5cd493ce5-r0/git/library 
-Wall -Wextra -Werror -fPIC   -std=gnu++11 -MD -MT 
CMakeFiles/communication-interface.dir/communication_interface.cpp.o 
-MF 
CMakeFiles/communication-interface.dir/communication_interface.cpp.o.d 
-o 
CMakeFiles/communication-interface.dir/communication_interface.cpp.o 
-c 
/mnt/ssd/yocto-build-script/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/communication-library/git-AUTOINC+f5cd493ce5-r0/git/communication_interface.cpp
| In file included from 
/mnt/ssd/yocto-build-script/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/communication-library/git-AUTOINC+f5cd493ce5-r0/git/communication_interface.cpp:1:
| 
/mnt/ssd/yocto-build-script/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/communication-library/git-AUTOINC+f5cd493ce5-r0/git/library/communication_interface.h:4:10: 
fatal error: string: No such file or directory

|  #include 
|   ^~~~
| compilation terminated.

I also tried to change the cmake generator to unix makefile (who knows 
...):

OECMAKE_GENERATOR = "Unix Makefiles"

But I have the same issue. I am working on the thud branch. Anyone had 
the same problem? What am I doing wrong?


Best regards,

Guy Morand


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto