Re: [yocto] how to create a named_pipe in my image

Thank you Ross. Switching to rpm package showed the same behavior. Is there another workaround than a post install script? Regards, Michael From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Monday, February 08, 2016 5:15 PM To: Baumann, Michael Cc: yocto@yoctoproject.org Subject: Re:

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 16:12, Baumann, Michael wrote: > Possibly it's because named pipes cannot be packed into an archive? If > yes, how can I circumvent this? > It would be interesting to see what happens if you change PACKAGE_CLASSES to use rpm instead of ipkg.

[yocto] fortran in yocto

Hi, I want to add fortran support to yocto build. I try different way whitch describe in the ethernet but enyone does't work. I use fido branch and gcc 4.9. Can you describe me step by step how to enable fortran in yocto or where I can find work instruction. Thanks for help. Best regards,

Re: [linux-yocto] [PATCH 00/29] Backports and other features for Galileo

On 16-02-05 09:53 AM, Saul Wold wrote: Bruce, This is a set of patches that are currently being maintained in the meta-intel-galileo BSP which we are working to merge into meta-intel proper. These include items that are backported from newer versions as well as some galileo specific items.

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 5 February 2016 at 10:45, Reshetova, Elena wrote: > recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) > > > > or even simple: > > > > recipe.r_deps = d.getVar('RDEPENDS’, True) > > Did you mean RDEPENDS_ + package name? Ross --

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 5 February 2016 at 10:45, Reshetova, Elena > wrote: recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) or even simple: recipe.r_deps = d.getVar('RDEPENDS’, True) >Did you mean RDEPENDS_ +

Re: [yocto] how to create a named_pipe in my image

To make my question more precise: mkfifo in the do_install() section works. I can see the named pipe in build/tmp-glibc/work/*/*/*/ but my bitbake hangs in the do_package_write_ipk and do_package_qa tasks. Possibly it's because named pipes cannot be packed into an archive? If yes, how can I

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 8 February 2016 at 16:20, Reshetova, Elena wrote: > >Did you mean RDEPENDS_ + package name? > > > > I have it like this: > > > > recipe.name = d.getVar('PN', True) > > recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) > So I wasn't quite right - I think you

Re: [yocto] fortran in yocto

Hi On Mon, 8 Feb 2016 08:19:53 + "Liubchynskyi, Stanislav (Nokia - PL/Wroclaw)" wrote: > Hi, > I want to add fortran support to yocto build. I try different way whitch > describe in the ethernet but enyone does't work. I use fido branch and gcc > 4.9.

Re: [yocto] Installing only part of linux-firmware

On 7 February 2016 at 21:49, Chris Tapp wrote: > I’ve now done this by creating a bbappend for linux-firmware: > > PACKAGES =+ "${PN}-rtl_nic" > > FILES_${PN}-rtl_nic = " \ > /lib/firmware/rtl_nic/* \ > “ > > Does what I want, but is that the best way of doing it? >

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

>So I wasn't quite right - I think you also need to come after do_packagedata >and also you'll need to read the subpackage metadata. Inspired by >insane.bbclass, this works: >addtask printrdeps before do_build after do_package do_packagedata >do_printrdeps[nostamp] = "1" >python

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

The problem is, it doesn't doit delirebately, when I run bitbake -f -c latest_link myrecipe , it works when the process is in the tasks batch running bitbake myrecipe it doesn't What am I doing wrong ? Kind regards, Bartosz Woronicz Engineer, Software Configuration (SCM) NSN - PL/Wroclaw On

[yocto] [Build dependencies]

Hello, I am trying to use some things from one recipe in another the things what I did: Defined default package with files the next step I added in another recipe dependencies field. So as I check defaul .rpms was generated with proper contain. But when I look to my child recipe there is no

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On pon, 2016-02-08 at 14:20 +0100, Woronicz, Bartosz ( NSN - PL/Wroclaw) wrote: > The problem is, it doesn't doit delirebately, > > when I run > > bitbake -f -c latest_link myrecipe , it works > > when the process is in the tasks batch running > bitbake myrecipe > it doesn't > What am I doing

[yocto] how to create a named_pipe in my image

Hi, I try to create a named pipe (fifo) for my target filesystem. I tried it in my .bb file in the do_install() section with "mkfifo " Any ideas gratefully received. Regards Michael -- ___ yocto mailing list yocto@yoctoproject.org

[linux-yocto] [PATCH v2] iio: light: add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light sensors

From: Tomasz Duszynski commit 3a11fbb037a1ecd3e1070ee484f1ea887133f21b upstream Add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light sensors. Signed-off-by: Tomasz Duszynski Signed-off-by: Jonathan Cameron --- v2:

Re: [linux-yocto] [PATCH 01/29] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned

On Sun, 2016-02-07 at 17:09 -0500, Paul Gortmaker wrote: > [[linux-yocto] [PATCH 01/29] i2c / ACPI: Use 0 to indicate that > device does not have interrupt assigned] On 05/02/2016 (Fri 06:53) > Saul Wold wrote: > > > From: Mika Westerberg > > Normally here at

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 16:39, Baumann, Michael wrote: > Switching to rpm package showed the same behavior. > > Is there another workaround than a post install script? > > So I had a quick look at this. The fifo certainly ends up in the resulting ipk at least, but as

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 17:36, Burton, Ross wrote: > So I had a quick look at this. The fifo certainly ends up in the > resulting ipk at least, but as you say package_qa hangs. It's probably > encountering a non-file and breaking somewhere. A really nasty workaround >

Re: [linux-yocto] [PATCH 01/29] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned

[Cc trimmed of non-yocto folks to spare them the noise] [Re: [linux-yocto] [PATCH 01/29] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned] On 08/02/2016 (Mon 09:13) Saul Wold wrote: > On Sun, 2016-02-07 at 17:09 -0500, Paul Gortmaker wrote: > > [[linux-yocto] [PATCH

Re: [linux-yocto] [PATCH 06/13] intel-common-drivers.scc: move profiling and latencytop to a new file

On 2016-02-07 6:25 PM, Paul Gortmaker wrote: [[linux-yocto] [PATCH 06/13] intel-common-drivers.scc: move profiling and latencytop to a new file] On 04/02/2016 (Thu 16:25) California Sullivan wrote: Profiling and latencytop enable DEBUG_KERNEL, which is no longer a standard config option. Move

Re: [linux-yocto] [PATCH 02/13] ktypes: add extended ktype

On 2016-02-07 6:14 PM, Paul Gortmaker wrote: [[linux-yocto] [PATCH 02/13] ktypes: add extended ktype] On 04/02/2016 (Thu 16:25) California Sullivan wrote: The extended ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL, opening up more kernel options. I wonder if adding a ktype is too heavy

[yocto] Release Candidate Build for yocto-2.0.1.rc6.rc6 now available.

-e A release candidate build for yocto-2.0.1.rc6 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc6 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 4e87c59bdedaa8c3e44fc02fd23be726c4d1dfb9 meta-fsl-arm :

[linux-yocto] [PATCH 15/19] mfd: intel_quark_i2c_gpio: support devices behind i2c bus

From: Andy Shevchenko commit 9b00926f46d882429bee435960c40b49d39e6a4f upstream. On Intel Galileo Gen2 the GPIO expanders are connected to the i2c bus. For those devices the ACPI table has specific parameters that refer to an actual i2c host controller. Since

Re: [linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL

On 02/07/2016 03:17 PM, Paul Gortmaker wrote: > [[linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL] > On 04/02/2016 (Thu 16:25) California Sullivan wrote: > >> DEBUG_KERNEL should not be in the base ktype, as a production kernel >> may not necessarily want any debug

Re: [linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in intel-core* bsps

On 02/07/2016 03:33 PM, Paul Gortmaker wrote: > [[linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in > intel-core* bsps] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > >> Without EXPERT, we hit a select on I2C_I801, forcing it to yes and >> causing a warning. Set I2C_I801 to

[linux-yocto] [PATCH 07/19] i2c: core: only use set_scl for bus recovery after calling prepare_recovery

From: Jan Luebbe commit 49c46cd7bf99f5a5af5df9a92b73db54b94f46f0 upstream. Using set_scl may be ineffective before calling the driver specific prepare_recovery callback, which might change into a test mode. So instead of setting SCL in i2c_generic_scl_recovery, move it to

[linux-yocto] [PATCH 10/19] GPIO / ACPI: export acpi_gpiochip_request(free)_interrupts for module use

From: Hanjun Guo commit dd8f9d05019c5c086113b967850bf8e2f2a964e6 upstream. acpi_gpiochip_request(free)_interrupts can be used for modules, so export them. This also fixs a compile error when xgene-sb configured as kernel module. Fixes: 733cf014f020 "gpio: xgene: add ACPI

[linux-yocto] [PATCH 00/19 v2] Galileo patches that are upstreamed or pending

Bruce, I am refactoring the large patchset I sent earlier, this includes just the patches that have upstream commits, I have already sent one general iio, these are More galileo specific. These should all have the upstream commit info in them. These are all for the 4.1 linux-yocto, I will send

[linux-yocto] [PATCH 14/19] mfd: intel_quark_i2c_gpio: load gpio driver first

From: Andy Shevchenko commit b91b0d397c3b35a039867ca0f43f1a0d5965cad6 upstream. On Intel Galileo boards the GPIO expander is connected to i2c bus. Moreover it is able to generate interrupt, but interrupt line is connected to GPIO. That's why we have to have

[linux-yocto] [PATCH 11/19] gpio / ACPI: Return -EPROBE_DEFER if the gpiochip was not found

From: Mika Westerberg commit d8213ae03aebde8074f071d1da48007d55e3b41d upstream. If a driver requests a GPIO described in its _CRS but the GPIO host controller (gpiochip) driver providing the GPIO has not been loaded yet acpi_get_gpiod() returns -ENODEV which

[linux-yocto] [PATCH 12/19] i2c / ACPI: Rework I2C device scanning

From: Mika Westerberg commit 4bba25bbe10ace5ad135020c1e6d621872d5faf5 upstream. The way we currently scan I2C devices behind an I2C host controller does not work in cases where the I2C device in question is not declared directly below the host controller ACPI

[linux-yocto] [PATCH 13/19] mfd: core: redo ACPI matching of the children devices

From: Andy Shevchenko commit 541019157c6b5951f2a488dbf4f7fa5f4b8f9b98 upstream. There is at least one board on the market, i.e. Intel Galileo Gen2, that uses _ADR to distinguish the devices under one actual device. Due to this we have to improve the quirk in

[linux-yocto] [PATCH 17/19] gpio: pca953x: support ACPI devices found on Galileo Gen2

From: Andy Shevchenko commit 99e17e265a9df3b2ef8fbc1a568cbb2b05a1b977 upstream. This patch adds a support of the expandes found on Intel Galileo Gen2 board. The platform information comes from ACPI. Signed-off-by: Andy Shevchenko

[linux-yocto] [PATCH 08/19] i2c: fix leaked device refcount on of_find_i2c_* error path

From: Vladimir Zapolskiy commit 6b5d9d07c7ea4df3cf27f9eeb2fbb9c48a0c034b upstream. If of_find_i2c_device_by_node() or of_find_i2c_adapter_by_node() find a device by node, but its type does not match, a reference to that device is still held. This change fixes the

[linux-yocto] [PATCH 04/19] i2c: check for proper length of the reg property

From: Wolfram Sang commit bc280e47bc3944af5c7ca3cebaaf07819805ecb6 upstream. int is vague, let's simply use the type of the variable in question. Signed-off-by: Wolfram Sang Reviewed-by: Simon Horman

[linux-yocto] [PATCH 03/19] i2c: slave: add error messages to slave core

From: Wolfram Sang commit 429d57334d73b2c515363d21ad58be16c01d8d25 upstream. Inform users what went wrong from the core, so drivers don't have to do it. Signed-off-by: Wolfram Sang Acked-by: Geert Uytterhoeven

[linux-yocto] [PATCH 09/19] gpio / ACPI: Add support for retrieving GpioInt resources from a device

From: Mika Westerberg commit ad5b1c69a4ed2cc8486c6afa4d2545b21e5acd9b upstream. ACPI specification knows two types of GPIOs: GpioIo and GpioInt. The latter is used to describe that a given device interrupt line is connected to a specific GPIO pin. Typical ACPI

[linux-yocto] [PATCH 05/19] i2c: core: fix typo in comment

From: Shailendra Verma commit 891e1f106f375232431587baa8a72e2be39a845a upstream. Signed-off-by: Shailendra Verma Signed-off-by: Wolfram Sang (cherry picked from commit 95cc1e3d76398c4e8003dafe652285e43be90ee7)

[linux-yocto] [PATCH 01/19] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned

From: Mika Westerberg commit ad5f75aed7f6241aeaf4de293b7caedbc794dcae upstream. This is the convention used in most parts of the kernel including DT counterpart of I2C slave enumeration. To make things consistent do the same for ACPI I2C slave enumeration path

[linux-yocto] [PATCH 06/19] i2c: core: Reduce stack size of acpi_i2c_space_handler()

From: Jarkko Nikula commit 8e5d11906f6409f0374527d181808411fa6001e1 upstream. sizeof(struct i2c_client) is 1088 bytes on a CONFIG_X86_64=y build and produces following warning when CONFIG_FRAME_WARN is set to 1024: drivers/i2c/i2c-core.c: In function

[linux-yocto] [PATCH 02/19] i2c / ACPI: Assign IRQ for devices that have GpioInt automatically

From: Mika Westerberg commit ed457856e712370c6e77303d103ec0103a44e4e9 upstream. Following what DT already does. If the device does not have ACPI Interrupt resource but instead it has one or more GpioInt resources listed below it, we take the first GpioInt

[linux-yocto] [PATCH 18/19] at24: enable ACPI device found on Galileo Gen2

From: Andy Shevchenko commit afbc80ff5adf081edaa2ecb62e291580988f6643 upstream. There is a 24c08 chip connected to i2c bus on Intel Galileo Gen2 board. Enable it via ACPI ID INT3499. Signed-off-by: Andy Shevchenko

[linux-yocto] [PATCH 19/19] pwm-pca9685: enable ACPI device found on Galileo Gen2

From: Andy Shevchenko commit c28d0a843b44f79f71249d5612804c29483b586d upstream. There is a chip connected to i2c bus on Intel Galileo Gen2 board. Enable it via ACPI ID INT3492. Cc: Thierry Reding Signed-off-by: Andy Shevchenko

[linux-yocto] [PATCH 16/19] gpio: pca953x: store driver_data for future use

From: Andy Shevchenko commit e0599e216341d4e0b69b57145c956a7028f06a81 upstream. Instead of using id->driver_data directly we copied it to the internal structure. This will help to adapt driver for ACPI use. Signed-off-by: Andy Shevchenko