[yocto] yocto touchscreen

[Stanisavljevic]

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 - 0xbfe0   (  14 MB)

[0.00]   .text : 0xc0008000 - 0xc08b0034   (8865 kB)

[0.00]   .init : 0xc08b1000 - 0xc08f2000   ( 260 kB)

[0.00]   .data : 0xc08f2000 - 0xc09407f0   ( 314 kB)

[0.00].bss : 0xc09407f0 - 0xc0982d58   ( 266 kB)

[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[0.00] Preemptible hierarchical RCU implementation.

[0.00]  Build-time adjustment of leaf fanout to 32.

[0.00] NR_IRQS:16 nr_irqs:16 16

[0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128
interrupts

[0.00] OMAP clockevent source: timer2 at 2400 Hz

[0.15] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every
89478484971ns

[0.36] clocksource: timer1: mask: 0x max_cycles: 0x,
max_idle_ns: 79635851949 ns

[0.47] OMAP clocksource: timer1 at 2400 Hz

[0.000222] clocksource_probe: no matching clocksources found

[0.000415] Console: colour dummy device 80x30

[0.000442] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'

[0.000448] This ensures that you still see kernel messages. Please

[0.000454] update your kernel commandline.

[0.000473] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)

[0.089064] pid_max: default: 32768 minimum: 301

[0.089193] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)

[0.089205] Mountpoint-cache hash table entries: 1024 (order: 0, 4096
bytes)

[0.089932] Initializing cgroup subsys io

[0.089964] Initializing cgroup subsys memory

[0.090005] Initializing cgroup subsys devices

[0.090021] Initializing cgroup subsys freezer

[0.090036] Initializi

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ulf Samuelsson]

> 3 feb. 2019 kl. 20:09 skrev Ken Sloat :
> 
>> On Sun, Feb 3, 2019 at 12:51 AM Ulf Samuelsson  wrote:
>> 
>>> Den 2019-02-03 kl. 04:16, skrev Ken Sloat:
>>> 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} \
>>> "
>>> 
>>> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
>>> 
>> 
>> One would think that the file should be added automatically,
>> but this might be required, - or a workaround...
>> 
>> FILES_${PN} = " \
>>   /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
>>   ${sysconfdir}/modules-load.d/${MODULE_NAME}.conf \
>> "
>> 
>> 
>> --
>> Best Regards
>> Ulf Samuelsson
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> Hi Ulf,
> 
> Yes it seems that this indeed allows it to end up in the final image.
> 
> Not sure why it doesn't work without as I see the kernel-module-split
> class seems to have statements to do this automatically:
> 
>files = d.getVar('FILES_%s' % pkg, True)
>files = "%s /etc/modules-load.d/%s.conf
> /etc/modprobe.d/%s.conf" % (files, basename, basename)
>d.setVar('FILES_%s' % pkg, files)
> 
> Maybe there's some type of name mismatch or something in my case?
> 
> Thanks,
> Ken Sloat

I would log those statements when building.
Either pkg, or basename has a different value, than what is expected.

Best Regards,
Ulf Samuelsson
+46 722 427 437
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] GPG key used to authenticate DEB packages

[Mauro Ziliani]

Hi all.

My yocto image integrates package-management for package_deb.

I made my own debian repository and all works fine.

I miss only where Yocto save the gpg key  used to sign Release.gpg files.


So when I try apt-get update/upgrade onto my production system, apt-get
tell me that all packages are not recognized as authenticate.


Where is the gpg key to copy in production system?


Best regards,

  MZ

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

Re: [yocto] GPG key used to authenticate DEB packages

[Mauro Ziliani]

Sorry.

Relase.gpg miss in Yocto deploy/deb folders.

I need to build Release.gpg on my own


MZ

Il 04/02/19 16:35, Mauro Ziliani ha scritto:
> Hi all.
>
> My yocto image integrates package-management for package_deb.
>
> I made my own debian repository and all works fine.
>
> I miss only where Yocto save the gpg key  used to sign Release.gpg files.
>
>
> So when I try apt-get update/upgrade onto my production system, apt-get
> tell me that all packages are not recognized as authenticate.
>
>
> Where is the gpg key to copy in production system?
>
>
> Best regards,
>
>   MZ
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Robert Berger]

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
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto touchscreen

[Zoran Stojsavljevic]

> 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 - 0xbfe0   (  14 MB)
>
> [0.00]   .text : 0xc0008000 - 0xc08b0034   (8865 kB)
>
> [0.00]   .init : 0xc08b1000 - 0xc08f2000   ( 260 kB)
>
> [0.00]   .data : 0xc08f2000 - 0xc09407f0   ( 314 kB)
>
> [0.00].bss : 0xc09407f0 - 0xc0982d58   ( 266 kB)
>
> [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
>
> [0.00] Preemptible hierarchical RCU implementation.
>
> [0.00]  Build-time adjustment of leaf fanout to 32.
>
> [0.00] NR_IRQS:16 nr_irqs:16 16
>
> [0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 
> interrupts
>
> [0.00] OMAP clockevent source: timer2 at 2400 Hz
>
> [0.15] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
> 89478484971ns
>
> [0.36] clocksource: timer1: mask: 0x max_cycles: 0x, 
> max_idle_ns: 79635851949 ns
>
> [0.47] OMAP clocksource: timer1 at 2400 Hz
>
> [0.000222] clocksource_probe: no matching clocksources 

Re: [yocto] How to archive only packages contained in a certain image

[Burton, Ross]

Those recipes are special: the gcc-source recipe fetches and and
unpacks the GCC source tree, and gcc builds it.  So gcc has no
source...  Add gcc-source explicitly to your list and you'll be
sorted.

Ross

On Mon, 4 Feb 2019 at 16:23, David Zimmermann  wrote:
>
> Thanks for your helpful hints Ross !
>
> I now have a script in place which:
> - extracts package names from image manifest
> - translates package names to recipe names
> - grabs the source packages for those recipes (from what the archiver 
> extracted according to it’s config)
>
> For two recipes, referenced by the manifest file, the archiver does extract 
> no source packages:
> - libgcc
> - gcc-runtime
> Why is that ?
>
> Regards,
> David
>
> > Am 31.01.2019 um 15:46 schrieb Burton, Ross :
> >
> > Please remember to keep the list on CC.
> >
> > The reason is that those recipes are built for the target so they'll
> > be archived, the archiver doesn't distinguish what recipes go into
> > what image.
> >
> > It's relatively simple to filter the list after the build if you want
> > to produce just what is in a specific image, take the image manifest
> > and use oe-pkgdata-util to turn the package names into recipes.
> >
> > Ross
> >
> > On Thu, 31 Jan 2019 at 14:01, David Zimmermann
> >  wrote:
> >>
> >> Hi Ross,
> >>
> >> and thanks for your reply.
> >> I do bake an image based on core-image-minimal with additional packages 
> >> like openssh and qt (-base, -declarative, -quickcontrols).
> >> My folder ’tmp/deploy/sources/arm-poky-linux-gnueabi’ e.g. contains:
> >> perl, pulseaudio and python
> >>
> >> Even though those might be dependencies I inherited by other recipes - 
> >> python e.g. is not contained / will be installed to my image.
> >> As a countercheck I see what licenses will be placed in the image 
> >> (COPY_LIC_DIRS = 1 && COPY_LIC_MANIFEST = 1) which reflects the limited 
> >> number of packages I do expect.
> >>
> >> Regards,
> >> David
> >>
> >>> Am 31.01.2019 um 11:11 schrieb Burton, Ross :
> >>>
> >>> Does it not just contain the packages used to build the entire image,
> >>> so build-time dependents.  Can you give an example of a recipe that is
> >>> archived but shouldn't be?
> >>>
> >>> Ross
> >>>
> >>> On Thu, 31 Jan 2019 at 08:46, David Zimmermann
> >>>  wrote:
> 
>  Hi List,
> 
>  I use Yocto Krogoth and the following configuration for the archiver:
> 
>  INHERIT += „archiver“
>  COPYLEFT_RECIPE_TYPES = ’target’
> 
>  But the ‚tmp/deploy/sources/…/‚ folder for my target architecture 
>  contains much more packages then those ‚used‘ to build my image.
>  Is there a way to extract / archive / isolate only those package sources 
>  used for a certain image (kernel + rootfs) ?
> 
>  Thanks for your help,
>  David
>  --
>  ___
>  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] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT)

[sjolley.yp.pm]

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PDT tomorrow. (2/5)  

 

I will start tracking the minutes at:

https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU
9pg/edit?ts=5c06b22d  Please request access if you want to assist in editing
them.  The world should have view access. 

 

Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC:  
http://webchat.freenode.net/?channels=#yocto

 

Wiki:  
https://www.yoctoproject.org/public-virtual-meetings/

 

WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time

Where   Zoom Meeting:  
https://zoom.us/j/990892712 

 

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] How to archive only packages contained in a certain image

[David Zimmermann]

Thanks for your helpful hints Ross !

I now have a script in place which:
- extracts package names from image manifest
- translates package names to recipe names
- grabs the source packages for those recipes (from what the archiver extracted 
according to it’s config)

For two recipes, referenced by the manifest file, the archiver does extract no 
source packages:
- libgcc
- gcc-runtime
Why is that ?

Regards,
David
 
> Am 31.01.2019 um 15:46 schrieb Burton, Ross :
> 
> Please remember to keep the list on CC.
> 
> The reason is that those recipes are built for the target so they'll
> be archived, the archiver doesn't distinguish what recipes go into
> what image.
> 
> It's relatively simple to filter the list after the build if you want
> to produce just what is in a specific image, take the image manifest
> and use oe-pkgdata-util to turn the package names into recipes.
> 
> Ross
> 
> On Thu, 31 Jan 2019 at 14:01, David Zimmermann
>  wrote:
>> 
>> Hi Ross,
>> 
>> and thanks for your reply.
>> I do bake an image based on core-image-minimal with additional packages like 
>> openssh and qt (-base, -declarative, -quickcontrols).
>> My folder ’tmp/deploy/sources/arm-poky-linux-gnueabi’ e.g. contains:
>> perl, pulseaudio and python
>> 
>> Even though those might be dependencies I inherited by other recipes - 
>> python e.g. is not contained / will be installed to my image.
>> As a countercheck I see what licenses will be placed in the image 
>> (COPY_LIC_DIRS = 1 && COPY_LIC_MANIFEST = 1) which reflects the limited 
>> number of packages I do expect.
>> 
>> Regards,
>> David
>> 
>>> Am 31.01.2019 um 11:11 schrieb Burton, Ross :
>>> 
>>> Does it not just contain the packages used to build the entire image,
>>> so build-time dependents.  Can you give an example of a recipe that is
>>> archived but shouldn't be?
>>> 
>>> Ross
>>> 
>>> On Thu, 31 Jan 2019 at 08:46, David Zimmermann
>>>  wrote:
 
 Hi List,
 
 I use Yocto Krogoth and the following configuration for the archiver:
 
 INHERIT += „archiver“
 COPYLEFT_RECIPE_TYPES = ’target’
 
 But the ‚tmp/deploy/sources/…/‚ folder for my target architecture contains 
 much more packages then those ‚used‘ to build my image.
 Is there a way to extract / archive / isolate only those package sources 
 used for a certain image (kernel + rootfs) ?
 
 Thanks for your help,
 David
 --
 ___
 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 Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 

*Cell:(208) 244-4460

* Email: stephen.k.jol...@intel.com

 

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

[yocto] XSLT-CONFIG ERROR

[Igor Miranda]

Hey guys, I'm trying to compile the Icecast, but I'm getting the
xslt-config error, which says that I need to change to pkg-config, but I
dont know how to do this. Should I do a patch? Or its more easy to change
something in the Yocto to enable the use of the xslt-config? If I need to
use a patch, can someone explain to me how do I do something or can someone
send me a patch that works. Please I dont have more time, I need to
give this project, working, as soon as possible. HELP ME!
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] sun rpc missing in thud

[Beaman, Thomas]

Hi,

I am converting to thud and having trouble figuring out how to get sun rpc to 
install in my sysroot.

I can see that the sun rpc files are still in the glibc git  but I cannot 
figure what recipe or options I need to get them included in my distro. (I 
still have some old legacy code that needs them)


I have tried adding the following but they do not bring in the   
usr/include/rpc/rpc.h files like previous releases did.


IMAGE_INSTALL_append = " lib32-glibc-dbg"

IMAGE_INSTALL_append = " rpcsvc-proto"


Any help or suggestions of what to add or modify to get these files back in

Regards,
Tom Beaman

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

Re: [yocto] XSLT-CONFIG ERROR

[Chuck Wolber]

You have to refactor the Icecast bitbake recipe to use pkg-config instead
of xslt-config.

This patch might give you some ideas:
meta/recipes-devtools/swig/swig/0001-configure-use-pkg
-config-for-pcre-detection.patch

I patched modsecurity to fix the same issue. It mostly works, but their
build fails in certain configurations. Feel free to check my patch if you
dare, but I am not an autotools expert, and probably did something wrong.

https://github.com/SpiderLabs/ModSecurity/pull/2014/files

..Ch:W..

On Mon, Feb 4, 2019 at 10:35 AM Igor Miranda 
wrote:

> Hey guys, I'm trying to compile the Icecast, but I'm getting the
> xslt-config error, which says that I need to change to pkg-config, but I
> dont know how to do this. Should I do a patch? Or its more easy to change
> something in the Yocto to enable the use of the xslt-config? If I need to
> use a patch, can someone explain to me how do I do something or can someone
> send me a patch that works. Please I dont have more time, I need to
> give this project, working, as soon as possible. HELP ME!
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 
“I would challenge anyone here to think of a question upon which we once
had a scientific answer, however inadequate, but for which now the best
answer is a religious one."  -Sam Harris
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] sun rpc missing in thud

[Khem Raj]

On Mon, Feb 4, 2019 at 10:44 AM Beaman, Thomas  wrote:
>
> Hi,
>
>
>
> I am converting to thud and having trouble figuring out how to get sun rpc to 
> install in my sysroot.
>
>
>
> I can see that the sun rpc files are still in the glibc git  but I cannot 
> figure what recipe or options I need to get them included in my distro. (I 
> still have some old legacy code that needs them)
>

is it possible to move over to ti-rpc ? we have moved away from built-in glibc
version of rpc and replaced the need with ti-rpc, you might have to explicitly
enable it via a glibc bbappend and take care of packaging and
potential conflcts with ti-rpc.

>
>
>
>
> I have tried adding the following but they do not bring in the   
> usr/include/rpc/rpc.h files like previous releases did.
>
>
>
>
>
> IMAGE_INSTALL_append = " lib32-glibc-dbg"
>
>
>
> IMAGE_INSTALL_append = " rpcsvc-proto"
>
>
>
>
>
> Any help or suggestions of what to add or modify to get these files back in
>
>
>
> Regards,
>
> Tom Beaman
>
>
>
> --
> ___
> 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] sun rpc missing in thud

[Beaman, Thomas]

> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Monday, February 04, 2019 2:32 PM
> To: Beaman, Thomas 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] sun rpc missing in thud
> 
> On Mon, Feb 4, 2019 at 10:44 AM Beaman, Thomas
>  wrote:
> >
> > Hi,
> >
> >
> >
> > I am converting to thud and having trouble figuring out how to get sun rpc
> to install in my sysroot.
> >
> >
> >
> > I can see that the sun rpc files are still in the glibc git  but I
> > cannot figure what recipe or options I need to get them included in my
> > distro. (I still have some old legacy code that needs them)
> >
> 

It may be technically possible to move to ti-rpc but I have an old code base 
that uses sun rpc and no one knowledgeable in making changes to it.  

I am happy to use a glibc bbappend  to bring the old rpc but that is the part I 
need help with. I am not familiar with this recipe and how it is all put 
together. Would you be able to help me with a sample bbappend file as a 
starting point to work with ?

> is it possible to move over to ti-rpc ? we have moved away from built-in glibc
> version of rpc and replaced the need with ti-rpc, you might have to explicitly
> enable it via a glibc bbappend and take care of packaging and potential
> conflcts with ti-rpc.
> 
> > ___
> > 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] [ANNOUNCEMENT] Yocto Project 2.6.1 (thud 20.0.1) Released

[Tracy Graydon]

We are pleased to announce the latest release of the Yocto Project 2.6.1 
(thud-20.0.1) is now available for download at:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/poky-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/poky-thud-20.0.1.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/RELEASENOTES

Full pass test report is available at:

https://wiki.yoctoproject.org/wiki/WW02_-_2019-01-09_-_Full_Test_Cycle_2.6.1_RC1
 

Thank you for everyone's contributions to this release.

Sincerely,

Tracy Graydon
Yocto Project Build and Release
tracy.gray...@intel.com


--
yocto-2.6.1 Errata


Release Name: poky-thud-20.0.1
Branch: thud
Tag: thud-20.0.1
Hash: 1cab405d88149fd63322a867c6adb4a80ba68db3
md5: 392dad457a33761772a7b95d105352cf
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/poky-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/poky-thud-20.0.1.tar.bz2

Release Name: eclipse-poky-neon-thud-20.0.1
Branch: neon/thud
Tag: neon/thud-20.0.1
Hash: 9ab82dc61d603f3b1456059e9afafab806d0ca0a
md5: 4574709f7f96c8c557267236ef9a95a9
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/eclipse-poky-neon-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/eclipse-poky-neon-thud-20.0.1.tar.bz2

Release Name: eclipse-poky-oxygen-thud-20.0.1
Branch: oxygen/thud
Tag: oxygen/thud-20.0.1
Hash: 94df2cc13127b7347b26e473c3b5c583f9a2b350
md5: 27c29ca5bd266bd4bf1052c507adb3ed
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/eclipse-poky-oxygen-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/eclipse-poky-oxygen-thud-20.0.1.tar.bz2

Release Name: meta-gplv2-thud-20.0.1
Branch: thud
Tag: thud-20.0.1
Hash: aabc30f3bd03f97326fb8596910b94639fea7575
md5: 46205a0ed058456849f6709d0d733726
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/meta-gplv2-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/meta-gplv2-thud-20.0.1.tar.bz2

Release Name: meta-intel-thud-20.0.1
Branch: thud
Tag: thud-20.0.1
Hash: 7ea89b9ddcdd3de1629bae1465425c8077c5aa06
md5: b1d483aeb2d6887ce59dacca0004cf80
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/meta-intel-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/meta-intel-thud-20.0.1.tar.bz2

Release Name: meta-mingw-thud-20.0.1
Branch: thud
Tag: thud-20.0.1
Hash: b4227458cd5bd73beb8ae8e54b6365f326178092
md5: bb6e6bc6758963fc1ef856f35d37ec40
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/meta-mingw-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/meta-mingw-thud-20.0.1.tar.bz2

Release Name: meta-qt3-thud-20.0.1
Branch: thud
Tag: thud-20.0.1
Hash: 23d7543ebd7e82ba95cbe19043ae4229bdb3b6b1
md5: 6ef2954c0428675daefe5e0887d259c3
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/meta-qt3-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/meta-qt3-thud-20.0.1.tar.bz2

Release Name: meta-qt4-thud-20.0.1
Branch: thud
Tag: thud-20.0.1
Hash: b37d8b93924b314df3591b4a61e194ff3feb5517
md5: c0ec4d8521b0bfe9b16b72988b515af4
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.1/meta-qt4-thud-20.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.1/meta-qt4-thud-20.0.1.tar.bz2


---
 Known Issues
---
Bug# 13143: bitbake core-image-minimal failed because no module named 'gpg' on 
CentOS 7 and OpenSuse 42.3 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13143 

Bug# 12991: Bitbake build-appliance-image getting failed during building image 
due to webkitgtk package
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991

Both of these bugs are still being root caused. Please see the respective bugs 
for steps to reproduce and further details.
 

---
Security Fixes
---
linux-yocto/4.18: integrate CVE fixes
ref-manual: Added GCCVERSION variable description to glossary.
curl: actually apply latest CVE patches
unzip: actually apply CVE-2018-18384
binutils: fix four CVE issues
curl: fix for CVE-2018-16839/CVE-2018-16840/CVE-2018-16842
openssl: fix CVE-2018-0735 for 1.1.1
openssl: fix CVE-2018-0734 for both 1.0.2p and 1.1.1
ghostscript: fix CVE-2018-18284
ghostscript: fix CVE-2018-18073
ghostscript: fix CVE-2018-17961
elfutils: fix CVE-2018-18520 & CVE-2018-18521 & CVE-2018-18310
nasm: fix CVE-2018-1000667
unzip: fix for CVE-2018-18384
qemu: fix for CVE-2018-10839
systemd: fix CVE-2018-15688
systemd: fix CVE-2018-15687
systemd: fix CVE-2018-15686
nss: update to 3.39 includes CVE-2018-12384
xserver-xorg: fix CVE-2018-14665


---
Fixes
---
brief-yoctoprojectqs, dev-manual: Update tag checkout examples
poky.ent: Updated release

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

[Guy Morand]

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