Re: [yocto] replace etc/network/interfaces with symbolic link
Thank you for all answers, I looked
In fact I found another problem, even if I modify the original recipe I
can't get a modified rpm, or rootfs...
I commented lines concerning interfaces files but it seems that nothing is
modified in the rootfs and in the rpm...
if someone understands what I missed...
the bitbake file :
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb
and I commented out :
#install -m 0644 ${WORKDIR}/interfaces ${D}${sysconfdir}/network/interfaces
#CONFFILES_${PN} = ${sysconfdir}/network/interfaces
Aurèle
2015-02-06 20:38 GMT+01:00 Bryan Evenson beven...@melinkcorp.com:
Aurele,
One possible issue is ${sysconfdir}/network/interfaces is listed in the
CONFFILES in the original recipe. It may still be installing this file
because it is listed under CONFFILES. Try adding:
CONFFILES_${PN} =
To your bbappend.
Regards,
Bryan
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Aurele Traynard
Sent: Friday, February 06, 2015 10:55 AM
To: yocto@yoctoproject.org
Subject: [yocto] replace etc/network/interfaces with symbolic link
Hi,
I'm trying to find a clean way to replace /etc/network/interfaces with a
symbolic link. (it comes with init-ifupdown recipe) I tried with a
bbappend
but nothing appear in final filesystem and /etc/network/interfaces still
exists...
I'm sure the following code is completely wrong, but I don't know how to
do
this with the right way...
do_install_append () {
mkdir -p datas/network
install -d 0755 ${D}/datas
install -d 0755 ${D}/datas/network
install -m 0755 ${D}${sysconfdir}/network/interfaces
${D}/datas/network
#mv ${D}${sysconfdir}/network/interfaces ${D}/datas/network
rm ${D}${sysconfdir}/network/interfaces
ln -sf /datas/network/interfaces ${D}${sysconfdir}/network/interfaces
}
FILES_${PN} += /datas/ /datas/network/interfaces
thanks for any help
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Multiple packages from single recipe file
Hi,
We have done on similar line for one of the package. We have to write another
recipe for a package in which we need to just create packages and delivery it.
But we need to do it for couple of directories i.e. let say 10 directories.
Previously we have an script which perform some conversion and then create
package in loop i.e. creating RPM in loop for such package.
Now we want to achieve the same using a recipe.
One of the solution is to write 10 such recipe and creating a package, But it
means we need to check-out 10 times the code and then create the package.
But we are looking for some optimize way to do so as below
1. Check out all 10 directories in one shot.
2. Write small shell script code and call do_install() passing ${S} and ${D} as
argument to create the package. Here we are also looking for package name for
each such call different say package-1-ro.rpm package-2.r0.rpm etc.
3. Also avoid calling do_compile() as there is no makefile its plain file repo
which need to be packaged.
So any thoughts how to do such job.
Thanks,
Abhinav
From: Anders Darander [and...@chargestorm.se]
Sent: Monday, February 09, 2015 7:43 PM
To: Bipnesh, Abhinav (Abhinav)
Cc: Victor Rodriguez; yocto@yoctoproject.org
Subject: Re: [yocto] Multiple packages from single recipe file
* Bipnesh, Abhinav (Abhinav) abhinavbipn...@avaya.com [150209 14:26]:
In case of writing the spec file for RPM we need to create first the
directory layout and then putting the files using cp or other commands
and then perform %file etc. stuff. But when I take a look to some of
the recipe file present under poky sometime I see FILES_${PN} and it
didn’t specify from where to pick the files.
May be the case is that these project use Auto tools for building. But
in our case we have plain Makefile for building and then collecting
files from different location and putting in package. So I was
thinking can be use such shortcut method for such job.
In your case, add a do_install() function and make install all your
files into ${D}. See e.g. the setserial recipe:
https://urldefense.proofpoint.com/v2/url?u=http-3A__git.openembedded.org_openembedded-2Dcore_tree_meta_recipes-2Dbsp_setserial_setserial-5F2.17.bbd=AwIFaQc=BFpWQw8bsuKpl1SgiZH64Qr=geJ1wB7xRIMmteYB2Fo8esL32BOWvwP1HmY0YuLEB4Em=aZjRWREP73CkvukWYDIq6EBYm-V9PXDui-fbP3IIRjIs=jDlPZCpV9O0A6xPnqSw-Ee2XPHnFTU1O_vV-YNexwKke=
Cheers,
Anders
-Original Message-
From: Victor Rodriguez [mailto:vm.ro...@gmail.com]
Sent: Monday, February 09, 2015 18:46
To: Bipnesh, Abhinav (Abhinav)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Multiple packages from single recipe file
On Mon, Feb 9, 2015 at 4:51 AM, Bipnesh, Abhinav (Abhinav)
abhinavbipn...@avaya.com wrote:
Hi,
I was looking further into the document to find a way to define
multiple packages from a single recipe file. As in current recipe I
have written a
do_install() function for putting files in particular directories. So
it copies files from ${S} to ${D}.
But some of the documents talk about multiple package something as
below
FILES_${PN} = \
${bindir}/* \
${sbindir}/* \
${libexecdir}/* \
${libdir}/lib*.so.* \
${sysconfdir} \
${sharedstatedir} \
${localstatedir} \
/bin/* \
/sbin/* \
/lib/*.so* \
${datadir}/${PN} \
${libdir}/${PN}/* \
${datadir}/pixmaps \
${datadir}/applications \
${datadir}/idl \
${datadir}/omf \
${datadir}/sounds \
${libdir}/bonobo/servers
FILES_${PN}-dbg = \
${bindir}/.debug \
${sbindir}/.debug \
${libexecdir}/.debug \
${libdir}/.debug \
/bin/.debug \
/sbin/.debug \
/lib/.debug \
${libdir}/${PN}/.debug
But I am not getting how the source for such file will be determine as
in our project files will be present in different directories and need
to be placed in some predefined paths.
So how we can achieve the same.
Thanks,
Abhinav
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] boot delay but recovery??
I'm booting Dizzy 1.7.1 on a Pandaboard (ARM). The image is core-image-base. My local.conf additions are : MACHINE ??= pandaboard IMAGE_INSTALL_append = oracle-jse-jre dropbear linux-firmware resolvconf LICENSE_FLAGS_WHITELIST += oracle_java I get a 30 second delay while the boot process hangs then kills a process. Not sure I know why. Can someone enlighten me. Below is the log showing what is happening before and after the delay: [6.087097] cfg80211: Calling CRDA to update world regulatory domain udevd[947]: worker [950] timeout, kill it udevd[947]: seq 1291 '/devices/platform/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' killed [ 36.711120] wl12xx: loaded udevd[947]: worker [950] terminated by signal 9 (Killed) Once the board is booted I have both LAN and WiFi and both are connected and working. It's just 30 seconds longer than it should be. Jim A -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Confused with adding drivers to kernel via bitbake -c menuconfig
From my understanding bitbake -c cleansstate deletes sstate-cache and
$(WORKDIR), so if I want to replace the previous kernel configuration with a
new one, I should run cleansstate right?
From: Kevyn-Alexandre Paré [kap...@rogue-research.com]
Sent: Saturday, February 07, 2015 3:21 AM
To: Alvin D.M. DIZON
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Confused with adding drivers to kernel via bitbake -c
menuconfig
Alvin,,
On Thu, Feb 5, 2015 at 8:35 PM, Alvin D.M. DIZON
adm.di...@pciltd.com.sg wrote:
Hello Kevyn,
Thanks for your help. Do I still have to run bitbake -c cleansstate after
creating the configuration fragment? Or do I go straight to bitbake linux-imx
or bitbake fsl-image-x11?
Look into ${WORKDIR}/temp for what's happening
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-WORKDIR
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#usingpoky-debugging-taskfailures
It depends what you want to do.
-KA
On Thu, Feb 5, 2015 at 8:35 PM, Alvin D.M. DIZON
adm.di...@pciltd.com.sg wrote:
Hello Kevyn,
Thanks for your help. Do I still have to run bitbake -c cleansstate after
creating the configuration fragment? Or do I go straight to bitbake linux-imx
or bitbake fsl-image-x11?
Thanks
From: Kevyn-Alexandre Paré [kap...@rogue-research.com]
Sent: Friday, February 06, 2015 12:58 AM
To: Alvin D.M. DIZON
Subject: Re: [yocto] Confused with adding drivers to kernel via bitbake -c
menuconfig
Hi Alvin,
On Thu, Feb 5, 2015 at 12:43 AM, Alvin D.M. DIZON
adm.di...@pciltd.com.sg wrote:
Hello,
I would like to the generic USB bluetooth driver btusb to my i.MX6Q SABRE
SD, so that my USB Bluetooth dongle(Cambridge Silicon Radio). Upon reading
https://community.freescale.com/docs/DOC-100847 I enabled the Bluetooth
subsystem support, RFCOMM, BNEP, and HIDP, as well as the HCI USB driver. I
saved the .config file and copied it to the directory where my Linux recipe
is (linux-imx_3.10.17.bb). I then renamed my .config file into defconfig,
made a new folder called files and placed the defconfig in it. I also made
a .bbappend file that contained
I personally prefer this approach:
http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html#changing-the-configuration
second part with the .cfg
Doing this you can then validate it:
bitbake linux-imx -c configure -f
cat tmp/work/PATH/linux-imx/VERSION/build/.config | grep CONFIG_BT
FILESEXTRAPATHS_prepend := ${THISDIR}/files:
SRC_URI += file://defconfig
I then ran bitbake -c cleansstate linux-imx, after that I ran bitbake
fsl-image-x11. I flashed the resulting .sdcard file to an SD card, booted
up my board, but found no trace of btusb. I tried doing bitbake -f -c
compile linux-imx and then bitbake -f -c deploy linux-imx, and copied the
resulting uImage to my SD card's /media/Boot folder, but still no trace of
btusb. I checked the tar archive for the kernel modules found in the
/tmp/deploy/images/imx6qsabresd folder, and found two files called
modules.order and modules.builtin, the btusb driver is listed in the
modules.builtin file, but not mentioned in the modules.order file, I have
also tried compiling the driver as module, and then ran the same commands as
listed in the said link, but could not find the module. What am I doing
wrong here? Any help will be will be appreciated, since I am new to Linux
and the Yocto Project.
Before putting it on your SD you could validate that btusb is in
tmp/work/PATH/linux-imx/VERSION/image
Or
grep btusb tmp/work/PATH/linux-imx/VERSION/temp/*
Hope it could help,
-KA
Thanks,
Alvin
[PCI]
Innovative Manufacturing Solutions. Professionally Delivered!
The information contained in this email is confidential and is intended for
addressee(s) only. If you have received this email in error, please notify
the originator immediately. Nothing in this email shall constitute an offer
or acceptance leading to a legally binding contract which shall only arise
from a formal written agreement between yourselves and ourselves in the form
of a Purchase Order issued by us and accepted by you in writing. For the
avoidance of doubt, this email shall not be construed in any way as a formal
written agreement. We accept no liability for any damage arising from
alteration of the contents of this message by a third party or as a result
of any virus being passed on. Please consider your environmental
responsibility before printing this e-mail.
--
___
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: [linux-yocto] [PATCH 0/5] LSI AXXIA updates to 3.10 standard/axxia/base
On 15-02-09 12:42 PM, Daniel Dragomir wrote: Hi Bruce! That's another series of patches from LSI/Intel. The last one wasn't reviewed yet. I'm catching up! This one looks pretty simple, no concerns here, so I merged this along with the 52 patch series. Bruce Thanks. Daniel Topics: - tty serial updates - RapidIO driver updates - Misc NCR driver updates Gary McGee (2): misc: lsi-ncr: Locking Mechanism Update arch/arm/mach-axxia: DDR Retention Locking Change John Jacques (2): tty: serial: Updated Baud Rate Calcualtion axxia: Command Completion Done Check in NCR Driver Palani (1): rapidio: axxia-rio: Added support for configuring the sRIO serdes registers arch/arm/mach-axxia/ddr_retention.c | 14 +- drivers/misc/lsi-ncr.c | 312 +--- drivers/misc/lsi-ncr.h | 2 + drivers/rapidio/devices/lsi/axxia-rio-irq.c | 181 +++- drivers/rapidio/devices/lsi/axxia-rio-irq.h | 23 +- drivers/rapidio/devices/lsi/axxia-rio.c | 38 +++- drivers/rapidio/devices/lsi/axxia-rio.h | 2 + drivers/tty/serial/amba-pl011.c | 3 +- 8 files changed, 383 insertions(+), 192 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 00/52] LSI AXXIA updates to 3.10 standard/axxia/base
On 15-01-28 12:18 PM, Daniel Dragomir wrote: Hi Bruce, Resubmitted some patches updated as requested and added some new ones. Sorry for the delay. This is now merged and pushed to the axxia/base branch. Bruce Topics: - Update RapidIO driver to fix some issues. - Add new Device Trees for Axxia Simulation Targets - Update the Axxia NAND Driver for 3500 - Checking in AXM5500 EDAC driver support - Support for CPU Hotplug - Changes in GPIO support - Fix some compiler warnings - Updated smmon driver - Added support for doorbell interrupts - Updated USB driver - Added ARM CCN PMU driver - Updated EDAC driver - Updated MISC NRC driver - Added Support for Big Endian Anders Berg (8): ARM: axxia: Remove unused files gpio: pl061: specify gpio base via device tree arm: axxia: Remove GPIO platform data net: femac: Avoid panic in skb_put() net: femac: Rate limit error logs in RX path arm: axxia: Fix compiler warning from PCI driver arm: kvm: Fix crash when hotplugging CPU ARM: axxia: Support MSI on both PCIe controllers Charlie Paul (1): arch/arm/mach-axxia: Fixed affinity error on IRQ migration Fredrik Markström (1): arm/axxia: pci: Add missing calls to release_resource John Jacques (20): arch/arm/mach-axxia: Clean Up Compatible Names arch/arm/mach-axxia: Make Sure SRIO is Enabled Before Accessing arch/arm: New Device Trees for Axxia Simulation Targets arch/powerpc: Update the Axxia NAND Driver for 3500 arch/arm: Default Configuration for a Guest OS Example (Axxia) arch/powerpc: Reset Updates for Axxia arch/arm/mach-axxia: Support for CPU Hotplug arch/arm/mach-axxia: Check Status and Add Locks to NCR Accesses arch/powerpc: Removed Axxia Specific Changes arch/powerpc: Add a Work Around for Axxia 3500 Resets arch/arm: Add ioremap_cache() (same functionality as ioremap_cached()) arch/arm/mach-axxia: Fix Compiler Warnings drivers/spi: Fix Compiler Warnings drivers/net/ethernet/lsi: Fix Compiler Warnings arch/arm/mach-axxia: Added a Device Tree for Simulation arch/arm/mach-axxia: fixed failure to power up cluster arch/arm/mach-axxia: fixed hang in preempt kernel arch/arm/mach-axxia: Add Support for Big Endian arch/arm/mach-axxia: Backport of KVM BE Patch powerpc: io: implement dummy relaxed accessor macros for writes Jonas Svennebring (10): bus: ARM CCN PMU driver bus: arm-ccn: Fix error handling at event allocation bus: arm-ccn: Fix warning message bus: arm-ccn: Move event cleanup routine bus: arm-ccn: Fix spurious warning message ARM: dts: axxia: add CCN to dts ARM: axxia: uncore perf support, misc fixes ARM: axxia: uncore perf fix for multiple reads ARM: axxia: add dts support to platform perf ARM: dts: axxia: add axxia platform perf to dts Palani (3): LSI AXM55xx RapidIO: Fixed a rare case of missing a RIO interrupt LSI AXM55xx RapidIO: Added support for variable segment size LSI AXM55xx RapidIO: Added support for periodic timer handlers SangeethaRao (9): arch/powerpc/boot/dts: Checking in DTS files for ACP34xx/AXM3500 drivers/misc/lsi-smmon.c: Updated smmon driver arch/arm/mach-axxia: machine_restart() related change to axxia_restart() arch/arm/mach-axxia: Added support for doorbell interrupts Updated USB driver to not apply USB SW workarounds for 3500 arch/arm/mach-axxia: pcie: Add doorbell suport to use IRQF_SHARED edac: Added AXM55xx support for System Memory, L3, L2 cache and CPU misc: Updated lsi-ncr driver for ARM support misc: Exporting ncr_lock/ncr_unlock functions for RTE use Documentation/arm/CCN.txt | 52 + Documentation/devicetree/bindings/arm/ccn.txt | 21 + arch/arm/Kconfig | 39 + arch/arm/Makefile |6 +- arch/arm/boot/dts/Makefile|9 +- arch/arm/boot/dts/axm5504-emu.dts |4 +- arch/arm/boot/dts/axm5504-sim-mmc.dts | 127 +++ arch/arm/boot/dts/axm5504-sim-virtio.dts | 126 +++ arch/arm/boot/dts/axm5504-sim.dts | 133 --- arch/arm/boot/dts/axm5507-emu.dts |6 +- arch/arm/boot/dts/axm5508-amarillo.dts| 14 +- arch/arm/boot/dts/axm5512-amarillo.dts| 14 +- arch/arm/boot/dts/axm5516-amarillo.dts| 24 +- arch/arm/boot/dts/axm5516-sim-common.dts | 131 +++ arch/arm/boot/dts/axm5516-sim-mmc.dts | 127 +++ arch/arm/boot/dts/axm5516-sim-virtio.dts | 126 +++ arch/arm/boot/dts/axm5516-sim.dts | 133 --- arch/arm/boot/dts/axm55xx.dtsi| 46 +- arch/arm/boot/dts/vexpress-a15-guest.dts | 368 +++ arch/arm/boot/fmboot/Makefile |3 +- arch/arm/include/asm/assembler.h |7 + arch/arm/include/asm/hardware/debug-pl01x.S |6 +- arch/arm/include/asm/io.h |2 + arch/arm/include/asm/kvm_asm.h
Re: [yocto] Slashes in branch names
Michael, Could you please be more specific on what the issue is? The Yocto Project's kernel repos use slashes in branch names. :rjs On Monday, February 09, 2015 07:10:49 PM Harvey, Michael wrote: Our git SCM infrastructure uses slashes in the branch names (android style) for organization, and that breaks yocto. Is there any way to support this in yocto? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Slashes in branch names
Our git SCM infrastructure uses slashes in the branch names (android style) for organization, and that breaks yocto. Is there any way to support this in yocto? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH 3/5] misc: lsi-ncr: Locking Mechanism Update
From: Gary McGee gary.mc...@lsi.com
Allow for other drivers to share the locking mechanisms for
lsi-ncr h/w - provide unlocked methods for read/write - provide
consistent way of detecting/reporting lsi-ncr errors
Signed-off-by: Gary McGee gary.mc...@lsi.com
---
drivers/misc/lsi-ncr.c | 308 ++---
drivers/misc/lsi-ncr.h | 2 +
2 files changed, 189 insertions(+), 121 deletions(-)
diff --git a/drivers/misc/lsi-ncr.c b/drivers/misc/lsi-ncr.c
index 20101ef..16b1907 100644
--- a/drivers/misc/lsi-ncr.c
+++ b/drivers/misc/lsi-ncr.c
@@ -42,7 +42,10 @@ static void __iomem *apb2ser0_address;
#define WFC_TIMEOUT (40)
static DEFINE_RAW_SPINLOCK(ncr_spin_lock);
-static unsigned long flags;
+static DEFINE_RAW_SPINLOCK(nca_access_lock);
+EXPORT_SYMBOL(nca_access_lock);
+static unsigned long ncr_spin_flags, axi_access_flags;
+
#define LOCK_DOMAIN 0
@@ -93,6 +96,10 @@ typedef union {
} __packed bits;
} __packed command_data_register_2_t;
+int
+ncr_read_nolock(unsigned long region, unsigned long address, int number,
+void *buffer);
+
#ifdef CONFIG_ARM
/*
@@ -165,6 +172,42 @@ ncr_register_write(const unsigned value, unsigned *address)
#endif
/*
+ --
+ nca_register_read
+*/
+
+inline unsigned long
+nca_register_read(unsigned *address)
+{
+ unsigned long value;
+
+ raw_spin_lock_irqsave(nca_access_lock,
+ axi_access_flags);
+ value = ncr_register_read(address);
+ raw_spin_unlock_irqrestore(nca_access_lock,
+ axi_access_flags);
+
+ return value;
+}
+
+/*
+ --
+ nca_register_write
+*/
+
+void
+inline nca_register_write(const unsigned value, unsigned *address)
+{
+ raw_spin_lock_irqsave(nca_access_lock,
+ axi_access_flags);
+ ncr_register_write(value, address);
+ raw_spin_unlock_irqrestore(nca_access_lock,
+ axi_access_flags);
+
+ return;
+}
+
+/*
--
ncr_lock
*/
@@ -175,42 +218,21 @@ ncr_lock(int domain)
unsigned long offset;
unsigned long value;
unsigned long timeout = jiffies + msecs_to_jiffies(1000);
- command_data_register_0_t cdr0;
- raw_spin_lock_irqsave(ncr_spin_lock, flags);
+ raw_spin_lock_irqsave(ncr_spin_lock, ncr_spin_flags);
offset = (0xff80 + (domain * 4));
do {
- value = ncr_register_read((unsigned *)(nca_address + offset));
+ value = nca_register_read((unsigned *)(nca_address + offset));
} while ((0 != value) (time_before(jiffies, timeout)));
if (!(time_before(jiffies, timeout))) {
- raw_spin_unlock_irqrestore(ncr_spin_lock, flags);
+ raw_spin_unlock_irqrestore(ncr_spin_lock, ncr_spin_flags);
pr_err(ncr_lock() Timeout!\n);
BUG();
return -1;
}
- /*
- Make sure any previous commands completed, and check for errors.
- */
- timeout = jiffies + msecs_to_jiffies(1000);
-
- do {
- cdr0.raw =
- ncr_register_read((unsigned *)(nca_address + 0xf0));
- } while ((0x1 == cdr0.bits.status)
- (time_before(jiffies, timeout)));
-
- if (!(time_before(jiffies, timeout))) {
- raw_spin_unlock_irqrestore(ncr_spin_lock, flags);
- pr_err(ncr_lock() Previous command didn't complete!\n);
- BUG();
-
- return -1;
- }
- if (0x2 == cdr0.bits.status)
- pr_err(Previous ncr access failed!\n);
return 0;
}
@@ -227,13 +249,75 @@ ncr_unlock(int domain)
unsigned long offset;
offset = (0xff80 + (domain * 4));
- ncr_register_write(0, (unsigned *)(nca_address + offset));
- raw_spin_unlock_irqrestore(ncr_spin_lock, flags);
+ nca_register_write(0, (unsigned *)(nca_address + offset));
+ raw_spin_unlock_irqrestore(ncr_spin_lock, ncr_spin_flags);
return;
}
EXPORT_SYMBOL(ncr_unlock);
+
+/*
+
--
+ ncr_pio_error_dump
+*/
+
+static void
+ncr_pio_error_dump(char *str)
+{
+ unsigned long cdr0, cdr1, cdr2;
+ unsigned long stat0, stat1;
+
+ cdr0 = nca_register_read((unsigned *)(nca_address + 0xf0));
+ cdr1 = nca_register_read((unsigned *)(nca_address + 0xf4));
+ cdr2 = nca_register_read((unsigned *)(nca_address + 0xf8));
+
+ stat0 = nca_register_read((unsigned *)(nca_address + 0xe4));
+ stat1 = nca_register_read((unsigned *)(nca_address + 0xe8));
+
+ pr_err(lsi-ncr: %8s failed, error status : 0x%08lx 0x%08lx\n,
+ str, stat0, stat1);
+ pr_err(lsi-ncr: CDR0-2: 0x%08lx 0x%08lx
[linux-yocto] [PATCH 0/5] LSI AXXIA updates to 3.10 standard/axxia/base
Hi Bruce! That's another series of patches from LSI/Intel. The last one wasn't reviewed yet. Thanks. Daniel Topics: - tty serial updates - RapidIO driver updates - Misc NCR driver updates Gary McGee (2): misc: lsi-ncr: Locking Mechanism Update arch/arm/mach-axxia: DDR Retention Locking Change John Jacques (2): tty: serial: Updated Baud Rate Calcualtion axxia: Command Completion Done Check in NCR Driver Palani (1): rapidio: axxia-rio: Added support for configuring the sRIO serdes registers arch/arm/mach-axxia/ddr_retention.c | 14 +- drivers/misc/lsi-ncr.c | 312 +--- drivers/misc/lsi-ncr.h | 2 + drivers/rapidio/devices/lsi/axxia-rio-irq.c | 181 +++- drivers/rapidio/devices/lsi/axxia-rio-irq.h | 23 +- drivers/rapidio/devices/lsi/axxia-rio.c | 38 +++- drivers/rapidio/devices/lsi/axxia-rio.h | 2 + drivers/tty/serial/amba-pl011.c | 3 +- 8 files changed, 383 insertions(+), 192 deletions(-) -- 1.8.1.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/5] tty: serial: Updated Baud Rate Calcualtion
From: John Jacques john.jacq...@lsi.com
The baud rate calculation was truncating instead of rounding. This
caused, in some cases, the initial baud rate to be set incorrectly.
Updated to use DIV_ROUND_CLOSEST().
Signed-off-by: John Jacques john.jacq...@lsi.com
---
drivers/tty/serial/amba-pl011.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c
index 477ebc5..bfbddec 100644
--- a/drivers/tty/serial/amba-pl011.c
+++ b/drivers/tty/serial/amba-pl011.c
@@ -1990,7 +1990,8 @@ pl011_console_get_options(struct uart_amba_port *uap, int
*baud,
ibrd = readw(uap-port.membase + UART011_IBRD);
fbrd = readw(uap-port.membase + UART011_FBRD);
- *baud = uap-port.uartclk * 4 / (64 * ibrd + fbrd);
+ *baud = DIV_ROUND_CLOSEST(uap-port.uartclk * 4,
+ 64 * ibrd + fbrd);
if (uap-vendor-oversampling) {
if (readw(uap-port.membase + UART011_CR)
--
1.8.1.4
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/5] rapidio: axxia-rio: Added support for configuring the sRIO serdes registers
From: Palani palaniappan.ramanat...@lsi.com
Modified the sRIO sw reset handler, required for the reset control
symbol handling. Improved error handling and reporting during sRIO
maintenance and message trasactions.
Signed-off-by: Palani palaniappan.ramanat...@lsi.com
---
drivers/rapidio/devices/lsi/axxia-rio-irq.c | 181 +++-
drivers/rapidio/devices/lsi/axxia-rio-irq.h | 23 +++-
drivers/rapidio/devices/lsi/axxia-rio.c | 38 +-
drivers/rapidio/devices/lsi/axxia-rio.h | 2 +
4 files changed, 179 insertions(+), 65 deletions(-)
diff --git a/drivers/rapidio/devices/lsi/axxia-rio-irq.c
b/drivers/rapidio/devices/lsi/axxia-rio-irq.c
index a5b810e..71e17d1 100644
--- a/drivers/rapidio/devices/lsi/axxia-rio-irq.c
+++ b/drivers/rapidio/devices/lsi/axxia-rio-irq.c
@@ -14,12 +14,6 @@
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*/
-/*
-** Debug Build Flags
-**/
-/* #define AXM55XX_OUTB_DME_BBS 1 */
-
-
#include linux/init.h
#include linux/module.h
#include linux/types.h
@@ -80,6 +74,67 @@ static int __init axxia_hrtimer_setup(char *str)
return 1;
}
__setup(axm_srio_tmr_period=, axxia_hrtimer_setup);
+
+/**sRIO SERDES */
+u32 srio_serdes_write32(struct rio_priv *priv, u32 addr, u32 val)
+{
+ void __iomem *regaddr;
+ u32 regval = 0;
+ regaddr = (priv-linkdown_reset.win) +
+ APB2SER_SRIO_PHY0_CFG_OFFSET;
+ iowrite32(val, (regaddr + SERDES_CMD0_OFFSET));
+ regval = ((1SERDES_CMD1_VALID_SHIFT) |
+ (0x1 SERDES_CMD1_HWRITE_SHIFT) |
+ (0x01SERDES_CMD1_TSHIFT_SHIFT) |
+ (0x2SERDES_CMD1_HSZIE_SHIFT) |
+ (0x2 SERDES_CMD1_HTRANS_SHIFT) |
+ (addr SERDES_CMD1_HADDR_MASK));
+ iowrite32(regval, (regaddr + SERDES_CMD1_OFFSET));
+
+ regval = 0x;
+ while (1) {
+ regval = ioread32((regaddr + SERDES_CMD1_OFFSET));
+ if (!(regval (1 SERDES_CMD1_VALID_SHIFT)))
+ break;
+ }
+
+ regval = ioread32((regaddr + SERDES_READDATA1_OFFSET));
+ if (regval SERDES_READDATA1_HRESP_MASK) {
+ dev_err(priv-dev, SerDes write Failed... Returning 0\n);
+ return 0;
+ } else
+ return 1;
+}
+
+u32 srio_serdes_read32(struct rio_priv *priv, u32 addr)
+{
+ void __iomem *regaddr;
+ u32 regval = 0;
+ regaddr = (priv-linkdown_reset.win) +
+ APB2SER_SRIO_PHY0_CFG_OFFSET;
+ regval = ((1SERDES_CMD1_VALID_SHIFT) |
+ (0x01SERDES_CMD1_TSHIFT_SHIFT) |
+ (0x2SERDES_CMD1_HSZIE_SHIFT) |
+ (0x2 SERDES_CMD1_HTRANS_SHIFT) |
+ (addr SERDES_CMD1_HADDR_MASK));
+
+ iowrite32(regval, (regaddr + SERDES_CMD1_OFFSET));
+ regval = 0x;
+ while (1) {
+ regval = ioread32((regaddr + SERDES_CMD1_OFFSET));
+ if ((regval (1 SERDES_CMD1_VALID_SHIFT)) == 0x0)
+ break;
+ }
+ regval = ioread32((regaddr + SERDES_READDATA1_OFFSET));
+ if (regval SERDES_READDATA1_HRESP_MASK) {
+ dev_err(priv-dev, SerDes Read Failed... Returning 0\n);
+ return 0;
+ }
+ regval = ioread32((regaddr + SERDES_READDATA0_OFFSET));
+ return regval;
+}
+
+/**sRIO SERDES Ends ***/
static void ib_dme_irq_handler(struct rio_irq_handler *h/*, u32 state*/);
/
**
@@ -96,23 +151,57 @@ static void ib_dme_irq_handler(struct rio_irq_handler
*h/*, u32 state*/);
**
*/
-#if defined(CONFIG_AXXIA_RIO_STAT)
-
-static inline void __dme_dw_dbg(struct rio_msg_dme *dme, u32 dw0)
+static inline void __dme_dw_dbg(struct device *dev, struct rio_msg_dme *dme,
+ u32 iout, u32 dw0, u32 dw1)
{
+ int did, mb, let;
+ char *io;
+ char *id;
if (dw0 DME_DESC_DW0_ERROR_MASK) {
+ did = DME_DESC_DW0_GET_DST_ID(dw0);
+ let = DME_DESC_DW1_GET_LETTER(dw1);
+ mb = DME_DESC_DW1_GET_MBOX(dw1);
+ if (iout) {
+ io = OB;
+ id = DID;
+ } else {
+ io = IB;
+ id = SID;
+ }
+#if defined(CONFIG_AXXIA_RIO_STAT)
dme-desc_error_count++;
- if (dw0 DME_DESC_DW0_RIO_ERR)
+#endif
+ if (dw0 DME_DESC_DW0_RIO_ERR) {
+ dev_err(dev,
+ %s RIO ERR: %s = %x,Type:11,mbox=%d,letter=%d\n,
+io, id, did, mb, let);
+#if
[yocto] Prompting for password when fetching git repo over https
Poky Daisy 1.6.1 We have to fetch a git repo using https protocol. We are looking to see whether we can change this to ssh instead, but that is not possible at the moment. Access requires a userid and password. We do not want to hard-code the credentials into the recipe or into some other file like ~/.netrc. Ideally, we would like to get prompted for credentials just as when we invoke git from the command like. Is there any way to do this? MV -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 0/3] initial Forensic packages
Add three forensic applications to layer under there own recipe catagory. Armin Kuster (3): afflib: new package libewf: add package sleuth: add sleuthkit recipes-forensic/afflib/afflib_3.6.6.bb| 30 ++ .../afflib/files/configure_rm_ms_flags.patch | 18 + recipes-forensic/libewf/libewf_20130416.bb | 26 +++ .../sleuth/files/fix_host_poison.patch | 23 + recipes-forensic/sleuth/sleuthkit_4.1.3.bb | 28 5 files changed, 125 insertions(+) create mode 100644 recipes-forensic/afflib/afflib_3.6.6.bb create mode 100644 recipes-forensic/afflib/files/configure_rm_ms_flags.patch create mode 100644 recipes-forensic/libewf/libewf_20130416.bb create mode 100644 recipes-forensic/sleuth/files/fix_host_poison.patch create mode 100644 recipes-forensic/sleuth/sleuthkit_4.1.3.bb -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 2/3] libewf: add package
Signed-off-by: Armin Kuster akuster...@gmail.com
---
recipes-forensic/libewf/libewf_20130416.bb | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 recipes-forensic/libewf/libewf_20130416.bb
diff --git a/recipes-forensic/libewf/libewf_20130416.bb
b/recipes-forensic/libewf/libewf_20130416.bb
new file mode 100644
index 000..c070b80
--- /dev/null
+++ b/recipes-forensic/libewf/libewf_20130416.bb
@@ -0,0 +1,26 @@
+SUMMARY = library with support for Expert Witness Compression Format
+LICENSE = LGPLv3+
+LIC_FILES_CHKSUM = file://COPYING;md5=58c39b26c0549f8e1bb4122173f474cd
+
+DEPENDS = virtual/gettext libtool
+
+SRC_URI =
http://archive.ubuntu.com/ubuntu/pool/universe/libe/${BPN}/${BPN}_${PV}.orig.tar.gz;name=orig
\
+
http://archive.ubuntu.com/ubuntu/pool/universe/libe/${BPN}/${BPN}_${PV}-3.debian.tar.gz;name=dpatch
\
+
+SRC_URI[orig.md5sum] = 3791d6de5910a0f6b4427cdf1e6bc663
+SRC_URI[orig.sha256sum] =
e0f14071665b24a8077a24f4cafbf092ad5ac1859f49994dc4e843e747ba7a89
+SRC_URI[dpatch.md5sum] = 57fb17b34344f741b52dff3ae11fbbd6
+SRC_URI[dpatch.sha256sum] =
988ee0a94f01d452cd227ed5c55401e7674dc6fa41da8358a6ad68e67175a5cc
+
+inherit autotools-brokensep pkgconfig
+
+PACKAGECONFIG ??= zlib ssl bz2
+PACKAGECONFIG[zlib] = --with-zlib, --without-zlib, zlib, zlib
+PACKAGECONFIG[bz2] = --with-bzip2, --without-bzip2, bzip2, bzip2
+PACKAGECONFIG[ssl] = --with-openssl, --without-openssl, openssl, openssl
+PACKAGECONFIG[fuse] = --with-libfuse, --without-libfuse, fuse
+PACKAGECONFIG[python] = --enable-python, --disable-python, python
+
+EXTRA_OECONF += --with-gnu-ld --disable-rpath
+
+RDEPENDS_${PN} += util-linux-libuuid
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 1/3] afflib: new package
Signed-off-by: Armin Kuster akuster...@gmail.com
---
recipes-forensic/afflib/afflib_3.6.6.bb| 30 ++
.../afflib/files/configure_rm_ms_flags.patch | 18 +
2 files changed, 48 insertions(+)
create mode 100644 recipes-forensic/afflib/afflib_3.6.6.bb
create mode 100644 recipes-forensic/afflib/files/configure_rm_ms_flags.patch
diff --git a/recipes-forensic/afflib/afflib_3.6.6.bb
b/recipes-forensic/afflib/afflib_3.6.6.bb
new file mode 100644
index 000..5fb6e21
--- /dev/null
+++ b/recipes-forensic/afflib/afflib_3.6.6.bb
@@ -0,0 +1,30 @@
+SUMMARY = The Advanced Forensic Format (AFF) is on-disk format for storing
computer forensic information.
+HOMEPAGE = http://www.afflib.org/;
+LICENSE = BSD-4-Clause CPL-1.0
+LIC_FILES_CHKSUM = file://COPYING;md5=d1b2c6d0d6908f45d143ef6380727828
+
+DEPENDS = zlib ncurses readline openssl libgcrypt
+
+SRC_URI =
http://archive.ubuntu.com/ubuntu/pool/universe/a/${BPN}/${BPN}_${PV}.orig.tar.gz;name=orig
\
+
http://archive.ubuntu.com/ubuntu/pool/universe/a/${BPN}/${BPN}_${PV}-1.1.diff.gz;name=dpatch
\
+file://configure_rm_ms_flags.patch \
+
+
+SRC_URI[orig.md5sum] = b7ff4d2945882018eb1536cad182ad01
+SRC_URI[orig.sha256sum] =
19cacfd558dc00e11975e820e3c4383b52aabbd5ca081d27bb7994a035d2f4ad
+SRC_URI[dpatch.md5sum] = 171e871024545b487589e6c85290576f
+SRC_URI[dpatch.sha256sum] =
db632e254ee51a1e4328cd4449d414eff4795053d4e36bfa8e0020fcb4085cdd
+
+inherit autotools-brokensep
+
+CPPFLAGS = -I${STAGING_INCDIR}
+LDFLAGS = -L${STAGING_LIBDIR}
+
+PACKAGECONFIG ??=
+PACKAGECONFIG[curl] = --with-curl=PATH, --without-curl, curl
+PACKAGECONFIG[expat] = --with-expat=PATH, --without-expat, expat
+PACKAGECONFIG[fuse] = --enable-fuse=yes, --enable-fuse=no, fuse
+PACKAGECONFIG[python] = --enable-python=yes, --enable-python=no, python
+
+EXTRA_OECONF += --enable-s3=no CPPFLAGS=-I${STAGING_INCDIR}
LDFLAGS=-L${STAGING_LIBDIR}
+EXTRA_OEMAKE += CPPFLAGS='${CPPFLAGS}' LDFLAGS='-L${STAGING_LIBDIR}'
diff --git a/recipes-forensic/afflib/files/configure_rm_ms_flags.patch
b/recipes-forensic/afflib/files/configure_rm_ms_flags.patch
new file mode 100644
index 000..ac33500
--- /dev/null
+++ b/recipes-forensic/afflib/files/configure_rm_ms_flags.patch
@@ -0,0 +1,18 @@
+Upstream-Status: Inappropriate [configuration]
+
+remove ms lib options when cross compiling
+
+Signed-Off-By: Armin Kuster akuster...@gmail.com
+
+Index: configure.ac
+===
+--- a.orig/configure.ac
a/configure.ac
+@@ -47,7 +47,6 @@ if test x${cross_compiling} = xno ;
+ AC_MSG_NOTICE([ LDFLAGS = ${LDFLAGS} ])
+ else
+ AC_MSG_NOTICE([Cross Compiling --- will not update CPPFALGS or LDFLAGS with
/usr/local, /opt/local or /sw])
+- LIBS=$LIBS -lws2_32 -lgdi32
+ fi
+
+ if test -r /bin/uname.exe ; then
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 3/3] sleuth: add sleuthkit
Signed-off-by: Armin Kuster akuster...@gmail.com
---
.../sleuth/files/fix_host_poison.patch | 23 ++
recipes-forensic/sleuth/sleuthkit_4.1.3.bb | 28 ++
2 files changed, 51 insertions(+)
create mode 100644 recipes-forensic/sleuth/files/fix_host_poison.patch
create mode 100644 recipes-forensic/sleuth/sleuthkit_4.1.3.bb
diff --git a/recipes-forensic/sleuth/files/fix_host_poison.patch
b/recipes-forensic/sleuth/files/fix_host_poison.patch
new file mode 100644
index 000..03b1fb9
--- /dev/null
+++ b/recipes-forensic/sleuth/files/fix_host_poison.patch
@@ -0,0 +1,23 @@
+Upstream-Status: Inappropriate [configuration]
+
+Don't use host include or lib paths in *FLAGS
+
+Signed-off-by: Armin Kuster akuster...@gmail.com
+
+Index: configure.ac
+===
+--- a/configure.ac
b/configure.ac
+@@ -84,12 +84,6 @@ AX_PTHREAD([
+ LDFLAGS=$LDFLAGS $PTHREAD_CFLAGS
+ CC=$PTHREAD_CC],[])
+
+-dnl Not all compilers include /usr/local in the include and link path
+-if test -d /usr/local/include; then
+-CPPFLAGS=$CPPFLAGS -I/usr/local/include
+-LDFLAGS=$LDFLAGS -L/usr/local/lib
+-fi
+-
+ dnl Add enable/disable option
+ AC_ARG_ENABLE([java],
+ [AS_HELP_STRING([--disable-java], [Do not build the java bindings or jar
file])])
diff --git a/recipes-forensic/sleuth/sleuthkit_4.1.3.bb
b/recipes-forensic/sleuth/sleuthkit_4.1.3.bb
new file mode 100644
index 000..4b82616
--- /dev/null
+++ b/recipes-forensic/sleuth/sleuthkit_4.1.3.bb
@@ -0,0 +1,28 @@
+SUMMARY = The Sleuth Kit (TSK) is a library and collection of command line
tools that allow you to investigate disk images.
+HOMEPAGE = http://www.sleuthkit.org/sleuthkit/;
+LICENSE = IPL-1.0 GPLv2 CPL-1.0
+LIC_FILES_CHKSUM =
file://licenses/GNU-COPYING;startline=4;endline=5;md5=475b4784903850b579dc6e6310bd5f08\
+
file://licenses/IBM-LICENSE;startline=1;endline=2;md5=1fc3300388b0d6e6216825dd89c2e3a2\
+
file://licenses/cpl1.0.txt;startline=1;endline=2;md5=9e58c878202c73a4e3ed4be72598fb92
+
+DEPENDS = libtool
+
+SRC_URI =
http://archive.ubuntu.com/ubuntu/pool/universe/s/${BPN}/${BPN}_${PV}.orig.tar.gz;name=orig
\
+file://fix_host_poison.patch \
+
+SRC_URI[orig.md5sum] = 139a12f06952d8a40bbe07884994cf5d
+SRC_URI[orig.sha256sum] =
67f9d2a31a8884d58698d6122fc1a1bfa9bf238582bde2b49228ec9b899f0327
+
+inherit autotools-brokensep pkgconfig gettext
+
+PACKAGECONFIG ??= aff zlib ewf
+PACKAGECONFIG[aff] = --with-afflib=${STAGING_DIR_HOST}/usr, --without-afflib,
afflib
+PACKAGECONFIG[zlib] = --with-zlib=${STAGING_DIR_HOST}/usr, --without-zlib,
zlib
+PACKAGECONFIG[ewf] = --with-libewf=${STAGING_DIR_HOST}/usr, --without-libewf,
libewf
+
+#--with-gnu-ld
+EXTRA_OECONF += --enable-static=no --disable-java LIBS='-L${STAGING_LIBDIR}'
LDFLAGS='-L${STAGING_LIBDIR}' CPPFLAGS='-I${STAGING_INCDIR}'
+
+FILES_${PN} += ${datadir}/tsk
+
+RDEPENDS_${PN} += perl
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, Feb. 10, 2015 8:00 AM US Pacific Time
Tuesday, February 10, 2015 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.8_Status https://wiki.yoctoproject.org/wiki/Yocto_1.8_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.8_Features * SWAT team rotation: Ross - Cristian https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min * Team Sharing - 10 min We encourage people attending the meeting to logon the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference Details: Company: WIND RIVER SYS Ready-Access Number: 8007302996/9139049836 Access Code: 2705751 For International numbers see: https://www.yoctoproject.org/tools-resources/community/weekly-technical-call Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, Feb. 10, 2015 8:00 AM US Pacific Time
On 2015-02-09 08:15 PM, Jolley, Stephen K wrote: Tuesday, February 10, 2015 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.8_Status https://wiki.yoctoproject.org/wiki/Yocto_1.8_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.8_Features * SWAT team rotation: Ross - Cristian https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min * Team Sharing - 10 min We encourage people attending the meeting to logon the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference Details: Company: WIND RIVER SYS Ready-Access Number: 8007302996/9139049836 Access Code: 2705751 For International numbers see: https://www.yoctoproject.org/tools-resources/community/weekly-technical-call Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com Greetings All, I can't IRC tomorrow for the meeting as I am at school :(. Would someone either email me the major points of the meeting or think of some way to allow me to known what happened during the meeting. Thanks, Nick -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SDKMACHINE settings
Hi Parthiban, On Thursday 05 February 2015 17:43:31 Parthiban Kandasamy wrote: entirely i am new to embedded linux. first i did bitbake of core-image-minimal it came out very well. then again i tried sdk toolchain development using bitbake -k meta-toolchain-qte. it gives so many error. so could you provide details for how do i start to develop BSP for beagleboard-XM. i am entirely confused to understand yocto online document. Can you please include a log of the errors you are receiving? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Multiple packages from single recipe file
* Bipnesh, Abhinav (Abhinav) abhinavbipn...@avaya.com [150209 14:26]:
In case of writing the spec file for RPM we need to create first the
directory layout and then putting the files using cp or other commands
and then perform %file etc. stuff. But when I take a look to some of
the recipe file present under poky sometime I see FILES_${PN} and it
didn’t specify from where to pick the files.
May be the case is that these project use Auto tools for building. But
in our case we have plain Makefile for building and then collecting
files from different location and putting in package. So I was
thinking can be use such shortcut method for such job.
In your case, add a do_install() function and make install all your
files into ${D}. See e.g. the setserial recipe:
http://git.openembedded.org/openembedded-core/tree/meta/recipes-bsp/setserial/setserial_2.17.bb
Cheers,
Anders
-Original Message-
From: Victor Rodriguez [mailto:vm.ro...@gmail.com]
Sent: Monday, February 09, 2015 18:46
To: Bipnesh, Abhinav (Abhinav)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Multiple packages from single recipe file
On Mon, Feb 9, 2015 at 4:51 AM, Bipnesh, Abhinav (Abhinav)
abhinavbipn...@avaya.com wrote:
Hi,
I was looking further into the document to find a way to define
multiple packages from a single recipe file. As in current recipe I
have written a
do_install() function for putting files in particular directories. So
it copies files from ${S} to ${D}.
But some of the documents talk about multiple package something as
below
FILES_${PN} = \
${bindir}/* \
${sbindir}/* \
${libexecdir}/* \
${libdir}/lib*.so.* \
${sysconfdir} \
${sharedstatedir} \
${localstatedir} \
/bin/* \
/sbin/* \
/lib/*.so* \
${datadir}/${PN} \
${libdir}/${PN}/* \
${datadir}/pixmaps \
${datadir}/applications \
${datadir}/idl \
${datadir}/omf \
${datadir}/sounds \
${libdir}/bonobo/servers
FILES_${PN}-dbg = \
${bindir}/.debug \
${sbindir}/.debug \
${libexecdir}/.debug \
${libdir}/.debug \
/bin/.debug \
/sbin/.debug \
/lib/.debug \
${libdir}/${PN}/.debug
But I am not getting how the source for such file will be determine as
in our project files will be present in different directories and need
to be placed in some predefined paths.
So how we can achieve the same.
Thanks,
Abhinav
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] replace etc/network/interfaces with symbolic link
Aurèle,
-Original Message-
From: Aurele Traynard [mailto:aurele.trayn...@gmail.com]
Sent: Monday, February 09, 2015 4:59 AM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] replace etc/network/interfaces with symbolic link
Thank you for all answers, I looked
In fact I found another problem, even if I modify the original recipe I can't
get
a modified rpm, or rootfs...
I commented lines concerning interfaces files but it seems that nothing is
modified in the rootfs and in the rpm...
if someone understands what I missed...
the bitbake file :
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/init-
ifupdown/init-ifupdown_1.0.bb
and I commented out :
#install -m 0644 ${WORKDIR}/interfaces
${D}${sysconfdir}/network/interfaces
#CONFFILES_${PN} = ${sysconfdir}/network/interfaces
If you comment those lines out, then ${sysconfdir}/network/interfaces should
not be in the built RPM. So either there is a .bbappend that is adding the
file back in, or the package isn't being rebuilt. Try checking the following
to see what may be happening:
1. Check the creation date on the init-ifupdown RPM. If the RPM has not been
re-created since the last time you modified the recipe, then the RPM is not
being rebuilt with your changes. If you are not running a PR server, then you
need to increment the PR version in your .bbappend. See
http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#working-with-a-pr-service
for details on the PR service and how to handle PRs without the PR service.
Note that if you are on an older poky branch that the steps for handling the PR
service may be slightly different. Read the version of documentation that
matches your current branch.
2. If the RPM is being rebuilt, extract the RPM on your build machine to look
at its contents. If the interfaces file is still there, then there is still
something not working right with the do_install step. Under
tmp/work/MACHINE/init-ifupdown/PV-PR/temp/, open the file run.do_install
(the filename will have a PID appended to the end, so it'll be named something
like run.do_install.15612. If there are multiple in the temp directory, make
sure you look at the latest one). In this file is the final do_install script
that is run when performing the install step for the recipe. If this does not
look like what you want, then something between the main recipe and the
.bbappends are building the do_install step incorrectly.
Since you are removing files that the original recipe adds, the cleanest
approach may be to leave the original recipe untouched and to replace the
do_install step in your .bbappend. If you modify the main recipe, later on if
you switch to a different poky branch you'll lose your changes.
Regards,
Bryan
Aurèle
2015-02-06 20:38 GMT+01:00 Bryan Evenson beven...@melinkcorp.com
mailto:beven...@melinkcorp.com :
Aurele,
One possible issue is ${sysconfdir}/network/interfaces is listed in the
CONFFILES in the original recipe. It may still be installing this file
because it is
listed under CONFFILES. Try adding:
CONFFILES_${PN} =
To your bbappend.
Regards,
Bryan
-Original Message-
From: yocto-boun...@yoctoproject.org mailto:yocto-
boun...@yoctoproject.org [mailto:yocto- mailto:yocto-
boun...@yoctoproject.org mailto:boun...@yoctoproject.org ]
On Behalf Of Aurele Traynard
Sent: Friday, February 06, 2015 10:55 AM
To: yocto@yoctoproject.org mailto:yocto@yoctoproject.org
Subject: [yocto] replace etc/network/interfaces with symbolic link
Hi,
I'm trying to find a clean way to replace /etc/network/interfaces
with a
symbolic link. (it comes with init-ifupdown recipe) I tried with a
bbappend
but nothing appear in final filesystem and /etc/network/interfaces
still
exists...
I'm sure the following code is completely wrong, but I don't know
how to do
this with the right way...
do_install_append () {
mkdir -p datas/network
install -d 0755 ${D}/datas
install -d 0755 ${D}/datas/network
install -m 0755 ${D}${sysconfdir}/network/interfaces
${D}/datas/network
#mv ${D}${sysconfdir}/network/interfaces ${D}/datas/network
rm ${D}${sysconfdir}/network/interfaces
ln -sf /datas/network/interfaces
${D}${sysconfdir}/network/interfaces
}
FILES_${PN} += /datas/ /datas/network/interfaces
thanks for any help
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] replace etc/network/interfaces with symbolic link
many thanks for your concern, I finaly found my issue... there was no error.
I'm using a new distro since friday, this resulted in a new tmp-glibc
directory instead of my old tmp directory created by poky... I was
looking in the wrong directory. As you said in your first point I should
check the creation date!.
thanks
Aurèle
2015-02-09 15:01 GMT+01:00 Bryan Evenson beven...@melinkcorp.com:
Aurèle,
-Original Message-
From: Aurele Traynard [mailto:aurele.trayn...@gmail.com]
Sent: Monday, February 09, 2015 4:59 AM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] replace etc/network/interfaces with symbolic link
Thank you for all answers, I looked
In fact I found another problem, even if I modify the original recipe I
can't get
a modified rpm, or rootfs...
I commented lines concerning interfaces files but it seems that nothing
is
modified in the rootfs and in the rpm...
if someone understands what I missed...
the bitbake file :
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/init-
ifupdown/init-ifupdown_1.0.bb
and I commented out :
#install -m 0644 ${WORKDIR}/interfaces
${D}${sysconfdir}/network/interfaces
#CONFFILES_${PN} = ${sysconfdir}/network/interfaces
If you comment those lines out, then ${sysconfdir}/network/interfaces
should not be in the built RPM. So either there is a .bbappend that is
adding the file back in, or the package isn't being rebuilt. Try checking
the following to see what may be happening:
1. Check the creation date on the init-ifupdown RPM. If the RPM has not
been re-created since the last time you modified the recipe, then the RPM
is not being rebuilt with your changes. If you are not running a PR
server, then you need to increment the PR version in your .bbappend. See
http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#working-with-a-pr-service
for details on the PR service and how to handle PRs without the PR
service. Note that if you are on an older poky branch that the steps for
handling the PR service may be slightly different. Read the version of
documentation that matches your current branch.
2. If the RPM is being rebuilt, extract the RPM on your build machine to
look at its contents. If the interfaces file is still there, then there is
still something not working right with the do_install step. Under
tmp/work/MACHINE/init-ifupdown/PV-PR/temp/, open the file
run.do_install (the filename will have a PID appended to the end, so it'll
be named something like run.do_install.15612. If there are multiple in the
temp directory, make sure you look at the latest one). In this file is the
final do_install script that is run when performing the install step for
the recipe. If this does not look like what you want, then something
between the main recipe and the .bbappends are building the do_install step
incorrectly.
Since you are removing files that the original recipe adds, the cleanest
approach may be to leave the original recipe untouched and to replace the
do_install step in your .bbappend. If you modify the main recipe, later on
if you switch to a different poky branch you'll lose your changes.
Regards,
Bryan
Aurèle
2015-02-06 20:38 GMT+01:00 Bryan Evenson beven...@melinkcorp.com
mailto:beven...@melinkcorp.com :
Aurele,
One possible issue is ${sysconfdir}/network/interfaces is listed
in the
CONFFILES in the original recipe. It may still be installing this file
because it is
listed under CONFFILES. Try adding:
CONFFILES_${PN} =
To your bbappend.
Regards,
Bryan
-Original Message-
From: yocto-boun...@yoctoproject.org mailto:yocto-
boun...@yoctoproject.org [mailto:yocto- mailto:yocto-
boun...@yoctoproject.org mailto:boun...@yoctoproject.org ]
On Behalf Of Aurele Traynard
Sent: Friday, February 06, 2015 10:55 AM
To: yocto@yoctoproject.org mailto:yocto@yoctoproject.org
Subject: [yocto] replace etc/network/interfaces with symbolic
link
Hi,
I'm trying to find a clean way to replace /etc/network/interfaces
with a
symbolic link. (it comes with init-ifupdown recipe) I tried
with a
bbappend
but nothing appear in final filesystem and
/etc/network/interfaces
still
exists...
I'm sure the following code is completely wrong, but I don't know
how to do
this with the right way...
do_install_append () {
mkdir -p datas/network
install -d 0755 ${D}/datas
install -d 0755 ${D}/datas/network
install -m 0755 ${D}${sysconfdir}/network/interfaces
${D}/datas/network
#mv ${D}${sysconfdir}/network/interfaces ${D}/datas/network
rm ${D}${sysconfdir}/network/interfaces
ln -sf
Re: [yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi: Refactor kernel recipes
Hmm the formatting in my previous mail looks weird, I try to send this
again.. See my comment inline.
Cheers
Petter
On 02/08/2015 12:58 PM, Andrei Gherzan wrote:
We use this to simplify the update process. Updating a kernel version will not
require renaming the recipe but only tweaking LINUX_VERSION.
Update kernel version:
- bump SRCREV
- bump LINUX_VERSION if needed
[Support #26]
Change-Id: I7565ddd1f03cc34c34aa5da92664a0057b415c9a
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
recipes-kernel/linux/linux-raspberrypi.inc| 2 +-
recipes-kernel/linux/linux-raspberrypi_3.10.38.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.10.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.12.36.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.12.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.16.5.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.16.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.18.5.bb | 5 -
recipes-kernel/linux/linux-raspberrypi_3.18.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.6.11.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.6.bb | 8
recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.8.bb | 8
13 files changed, 49 insertions(+), 36 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.10.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.12.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.18.5.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.18.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.6.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.bb
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index ff0c5ce..c00128d 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -11,7 +11,7 @@ SRC_URI += \
COMPATIBLE_MACHINE = raspberrypi
-PV_append = +git${SRCREV}
+PV = ${LINUX_VERSION}+git${SRCREV}
# NOTE: For now we pull in the default config from the RPi kernel GIT tree.
KERNEL_DEFCONFIG = bcmrpi_defconfig
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
b/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
deleted file mode 100644
index a0c5012..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 1b49b450222df26e4abf7abb6d9302f72b2ed386
-SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.10.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.10.bb
b/recipes-kernel/linux/linux-raspberrypi_3.10.bb
new file mode 100644
index 000..e5d5bf2
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.10.bb
@@ -0,0 +1,8 @@
+LINUX_VERSION ?= 3.10.38
+
+SRCREV = 1b49b450222df26e4abf7abb6d9302f72b2ed386
+SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.10.y \
+ file://sl030raspberrypii2ckernel.patch \
+
+
+require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
b/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
deleted file mode 100644
index e9e9ad7..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 90fa5df724d147564149c7b79cb1ffc571a345ec
-SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.12.bb
b/recipes-kernel/linux/linux-raspberrypi_3.12.bb
new file mode 100644
index 000..08be83e
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.12.bb
@@ -0,0 +1,8 @@
+LINUX_VERSION ?= 3.12.26
+
Small typo here. It should be 3.12.36.
BR,
Petter
+SRCREV = 90fa5df724d147564149c7b79cb1ffc571a345ec
+SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y \
+ file://sl030raspberrypii2ckernel.patch \
+
+
+require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
b/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
deleted file mode 100644
index 97947c2..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV =
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-xxx = Not upgrade to 2.0 is unstable You can check the detail information at: http://packages.yoctoproject.org/upgradepkgname Package VersionUpstream version Maintainer NoUpgradeReason - --- -- gnome-icon-theme 2.31.0 3.7.4 Alejandro Hernandez waiting for the sato gtk3 port nfs-utils 1.3.1 1.3.2 Alejandro Hernandez midori0.5.8 0.5.9 Alejandro Hernandez screen4.0.3 4.2.1 Aníbal Limón jpeg 8d 9 Aníbal Limón webkit-gtk 1.8.3 doesn't wo... apt 0.9.9.41.0.9.6 Aníbal Limón dpkg 1.17.211.17.23 Aníbal Limón nettle2.7.1 3.0 Armin Kuster 3.0.0 breaks gnutls, api ch... linux-libc-headers3.17.7 3.19 Bruce Ashfield sysstat 11.0.2 11.1.2Chen Qi resolvconf1.76 1.76.1Chen Qi busybox 1.22.1 1.23.1Chen Qi console-tools 0.3.2 1999.03.02Chen Qi systemd 216+gitX 218+gitAUTOINC+c8... Chen Qi quilt 0.63 0.64 Chong Lu dbus-test 1.8.10 1.9.8 Chong Lu dbus 1.8.10 1.9.8 Chong Lu D-BUS 1.9.x is the developm... bison 2.7.1 3.0.4 Chong Lu libatomics-ops7.27.4.0 Cristian Iorga pulseaudio5.05.99.3Cristian Iorga speex 1.2rc1 1.2rc2Cristian Iorga db6.0.30 6.1.19Cristian Iorga API compatibility issue libical 1.0.0 1.0.1 Cristian Iorga neon 0.30.0 0.30.1Cristian Iorga quota 4.01 4.02 Cristian Iorga harfbuzz 0.9.37 0.9.38Cristian Iorga bluez44.101 5.28 Cristian Iorga BlueZ 5.x is not backward-c... gst-plugin-bluetooth 4.101 5.28 Cristian Iorga bluez55.27 5.28 Cristian Iorga connman 1.26 1.28 Cristian Iorga iproute2 3.17.0 3.18.0Cristian Iorga ofono 1.15 1.16 Cristian Iorga gst-fluendo-mpegd... 0.10.720.10.85 Cristian Iorga gst-fluendo-mp3 0.10.310.10.32 Cristian Iorga hwlatdetect 0.89 0.90 Darren Hart rt-tests 0.89 0.90 Darren Hart linux-yocto-tiny 3.17.8+gitX2012+gitAUTOINC+0... Darren Hart kernelshark 1.2+gitX 2.5.2+gitAUTOINC+... Darren Hart 0.2 is the latest version. trace-cmd 2.3.2+gitX 2.5.2+gitAUTOINC+... Darren Hart u-boot-fw-utils v2014.07+gitX v2015.01+gitAUTOI... Denys Dmytriyenko u-boot-mkimagev2014.07+gitX v2015.01+gitAUTOI... Denys Dmytriyenko u-bootv2014.07+gitX v2015.01+gitAUTOI... Denys Dmytriyenko qmmp 0.7.7 0.8.3 Hongxu Jia patch 2.7.1 2.7.4 Hongxu Jia perl 5.20.0 5.21.8Hongxu Jia bash 4.34.3.30Hongxu Jia The latest version in yocto... groff 1.22.2 1.22.3Hongxu Jia 1.18.1.4 is latest GPLv2 Ve... man-pages 3.76 3.79 Hongxu Jia man 1.6g 2.5a6 Hongxu Jia socat 1.7.2.41.7.3.0 Hongxu Jia adt-installer 0.2.0 1.1 Jessica Zhang libsdl1.2.15 1.2.15-1 Kai Kang bind 9.9.5 21Kai Kang python-numpy 1.7.0 1.9.1 Khem Raj rpm 5.4.14 5.4.15-0.20140824 Mark
Re: [yocto] Multiple packages from single recipe file
Hi,
In case of writing the spec file for RPM we need to create first the directory
layout and then putting the files using cp or other commands and then perform
%file etc. stuff. But when I take a look to some of the recipe file present
under poky sometime I see FILES_${PN} and it didn’t specify from where to pick
the files.
May be the case is that these project use Auto tools for building. But in our
case we have plain Makefile for building and then collecting files from
different location and putting in package.
So I was thinking can be use such shortcut method for such job.
-Abhinav
-Original Message-
From: Victor Rodriguez [mailto:vm.ro...@gmail.com]
Sent: Monday, February 09, 2015 18:46
To: Bipnesh, Abhinav (Abhinav)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Multiple packages from single recipe file
On Mon, Feb 9, 2015 at 4:51 AM, Bipnesh, Abhinav (Abhinav)
abhinavbipn...@avaya.com wrote:
Hi,
I was looking further into the document to find a way to define
multiple packages from a single recipe file. As in current recipe I
have written a
do_install() function for putting files in particular directories. So
it copies files from ${S} to ${D}.
But some of the documents talk about multiple package something as
below
FILES_${PN} = \
${bindir}/* \
${sbindir}/* \
${libexecdir}/* \
${libdir}/lib*.so.* \
${sysconfdir} \
${sharedstatedir} \
${localstatedir} \
/bin/* \
/sbin/* \
/lib/*.so* \
${datadir}/${PN} \
${libdir}/${PN}/* \
${datadir}/pixmaps \
${datadir}/applications \
${datadir}/idl \
${datadir}/omf \
${datadir}/sounds \
${libdir}/bonobo/servers
FILES_${PN}-dbg = \
${bindir}/.debug \
${sbindir}/.debug \
${libexecdir}/.debug \
${libdir}/.debug \
/bin/.debug \
/sbin/.debug \
/lib/.debug \
${libdir}/${PN}/.debug
But I am not getting how the source for such file will be determine as
in our project files will be present in different directories and need
to be placed in some predefined paths.
So how we can achieve the same.
Thanks,
Abhinav
--
___
yocto mailing list
yocto@yoctoproject.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
t.org_listinfo_yoctod=AwIBaQc=BFpWQw8bsuKpl1SgiZH64Qr=geJ1wB7xRIMmt
eYB2Fo8esL32BOWvwP1HmY0YuLEB4Em=Le2EtCjj9AW08t4Lrx7TNDzfZB3qnUINViKNg
ly8NfYs=4rO6-qcX4Lhvfc0WXO7Z7njj_OXkMHo3K_ITC2P5cmge=
Hi , basically the yocto recepeis work exactly as an spec file:
www.rpm.org/max-rpm/s1-rpm-build-creating-spec-file.html
The scenario you mention is possible:
rpm5.org/docs/rpm-guide.html
Hope it helps
Victor Rodriguez
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi: Refactor kernel recipes
On Mon, Feb 9, 2015 at 11:06 PM, Petter Mabäcker pet...@technux.se wrote:
Hmm the formatting in my previous mail looks weird, I try to send this
again.. See my comment inline.
Cheers
Petter
On 02/08/2015 12:58 PM, Andrei Gherzan wrote:
We use this to simplify the update process. Updating a kernel version
will not
require renaming the recipe but only tweaking LINUX_VERSION.
Update kernel version:
- bump SRCREV
- bump LINUX_VERSION if needed
[Support #26]
Change-Id: I7565ddd1f03cc34c34aa5da92664a0057b415c9a
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
recipes-kernel/linux/linux-raspberrypi.inc| 2 +-
recipes-kernel/linux/linux-raspberrypi_3.10.38.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.10.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.12.36.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.12.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.16.5.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.16.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.18.5.bb | 5 -
recipes-kernel/linux/linux-raspberrypi_3.18.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.6.11.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.6.bb | 8
recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.8.bb | 8
13 files changed, 49 insertions(+), 36 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.10.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.12.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.18.5.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.18.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.6.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.bb
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index ff0c5ce..c00128d 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -11,7 +11,7 @@ SRC_URI += \
COMPATIBLE_MACHINE = raspberrypi
-PV_append = +git${SRCREV}
+PV = ${LINUX_VERSION}+git${SRCREV}
# NOTE: For now we pull in the default config from the RPi kernel GIT
tree.
KERNEL_DEFCONFIG = bcmrpi_defconfig
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
b/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
deleted file mode 100644
index a0c5012..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 1b49b450222df26e4abf7abb6d9302f72b2ed386
-SRC_URI = git://github.com/raspberrypi/linux.git;protocol=git;branch=
rpi-3.10.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.10.bb
b/recipes-kernel/linux/linux-raspberrypi_3.10.bb
new file mode 100644
index 000..e5d5bf2
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.10.bb
@@ -0,0 +1,8 @@
+LINUX_VERSION ?= 3.10.38
+
+SRCREV = 1b49b450222df26e4abf7abb6d9302f72b2ed386
+SRC_URI = git://github.com/raspberrypi/linux.git;protocol=git;branch=
rpi-3.10.y \
+ file://sl030raspberrypii2ckernel.patch \
+
+
+require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
b/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
deleted file mode 100644
index e9e9ad7..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 90fa5df724d147564149c7b79cb1ffc571a345ec
-SRC_URI = git://github.com/raspberrypi/linux.git;protocol=git;branch=
rpi-3.12.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.12.bb
b/recipes-kernel/linux/linux-raspberrypi_3.12.bb
new file mode 100644
index 000..08be83e
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.12.bb
@@ -0,0 +1,8 @@
+LINUX_VERSION ?= 3.12.26
+
Small typo here. It should be 3.12.36.
Good catch. Thanks.
--
*Andrei Gherzan*
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 2/5] omxplayer: Bump SRCREV
Add a patch to fix the pkg-config mechanism in ffmpeg.
Change-Id: Ib506bb4e26a8a0c5c294ed55da0a0da8dc67a2d7
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
.../omxplayer/omxplayer/use-native-pkg-config.patch | 19 +++
recipes-multimedia/omxplayer/omxplayer_git.bb | 7 ---
2 files changed, 23 insertions(+), 3 deletions(-)
create mode 100644
recipes-multimedia/omxplayer/omxplayer/use-native-pkg-config.patch
diff --git a/recipes-multimedia/omxplayer/omxplayer/use-native-pkg-config.patch
b/recipes-multimedia/omxplayer/omxplayer/use-native-pkg-config.patch
new file mode 100644
index 000..ed81999
--- /dev/null
+++ b/recipes-multimedia/omxplayer/omxplayer/use-native-pkg-config.patch
@@ -0,0 +1,19 @@
+Force the pkg-config native tool. Strangely ffmpeg prepends cross_prefix
+to the default value which obviously is wrong.
+
+Signed-off-by: Andrei Gherzan and...@gherzan.ro
+
+Index: git/Makefile.ffmpeg
+===
+--- git.orig/Makefile.ffmpeg
git/Makefile.ffmpeg
+@@ -245,7 +245,8 @@ configure:
+ --disable-decoder=idf \
+ --enable-decoder=opus \
+ --cross-prefix=$(HOST)- \
+- --disable-stripping
++ --disable-stripping \
++ --pkg-config=pkg-config
+
+ .PHONY : clean
+ clean:
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index 41ef339..c71a743 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,22 +7,23 @@ SECTION = console/utils
LICENSE = GPLv2
LIC_FILES_CHKSUM = file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f
-DEPENDS = libpcre libav virtual/egl boost freetype dbus openssl
+DEPENDS = libpcre libav virtual/egl boost freetype dbus openssl samba libssh
PR = r3
-SRCREV = 1817503430b8f195bef12bd7a3542bdd251f8389
+SRCREV = 18f051d64d9c837edbf718bc4935204583cfa030
SRC_URI =
git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
file://0001-Remove-Makefile.include-which-includes-hardcoded.patch \
file://0002-Libraries-and-headers-from-ffmpeg-are-installed-in-u.patch \
file://0003-Remove-strip-step-in-Makefile.patch \
file://0004-Add-FFMPEG_EXTRA_CFLAGS-and-FFMPEG_EXTRA_LDFLAGS.patch \
file://fix-tar-command-with-DIST.patch \
+ file://use-native-pkg-config.patch \
S = ${WORKDIR}/git
COMPATIBLE_MACHINE = raspberrypi
-inherit autotools-brokensep
+inherit autotools-brokensep pkgconfig
# Needed in ffmpeg configure
export TEMPDIR = ${S}/tmp
--
2.1.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 4/5] bcm2835: Update to v1.38
Change-Id: Iebac94415602454dd4e2808c8e02d0083f804029
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
recipes-bcm/bcm2835/bcm2835_1.36.bb | 40 -
recipes-bcm/bcm2835/bcm2835_1.38.bb | 40 +
2 files changed, 40 insertions(+), 40 deletions(-)
delete mode 100644 recipes-bcm/bcm2835/bcm2835_1.36.bb
create mode 100644 recipes-bcm/bcm2835/bcm2835_1.38.bb
diff --git a/recipes-bcm/bcm2835/bcm2835_1.36.bb
b/recipes-bcm/bcm2835/bcm2835_1.36.bb
deleted file mode 100644
index 6997565..000
--- a/recipes-bcm/bcm2835/bcm2835_1.36.bb
+++ /dev/null
@@ -1,40 +0,0 @@
-DESCRIPTION = Package that provides access to GPIO and other IO\
-functions on the Broadcom BCM 2835 chip, allowing access to the\
-GPIO pins on the 26 pin IDE plug on the RPi board
-SECTION = base
-HOMEPAGE = http://www.open.com.au/mikem/bcm2835;
-AUTHOR = Mike McCauley (mi...@open.com.au)
-
-LICENSE = GPLv2
-LIC_FILES_CHKSUM = file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263
-
-COMPATIBLE_MACHINE = raspberrypi
-
-SRC_URI = http://www.open.com.au/mikem/bcm2835/bcm2835-${PV}.tar.gz;
-
-SRC_URI[md5sum] = 3299ddaef60f80b7f85de3318f08dee7
-SRC_URI[sha256sum] =
b4dfcdb453d44ba9ff55634ce7e0ddca21b96355ab61e40b4c3afb9406d4b8d2
-
-inherit autotools
-
-do_compile_append() {
-# Now compiling the examples provided by the package
-mkdir -p ${B}/examples
-for file in `ls ${S}/examples`; do
-${CC} ${S}/examples/${file}/${file}.c -o ${B}/examples/${file}
-Bstatic -L${B}/src -lbcm2835 -I${S}/src
-done
-}
-
-do_install_append() {
-install -d ${D}/${libdir}/${BPN}
-for file in ${B}/examples/*
-do
-install -m 0755 ${file} ${D}/${libdir}/${BPN}
-done
-}
-
-PACKAGES += ${PN}-tests
-
-FILES_${PN} =
-FILES_${PN}-tests = ${libdir}/${BPN}
-FILES_${PN}-dbg += ${libdir}/${BPN}/.debug
diff --git a/recipes-bcm/bcm2835/bcm2835_1.38.bb
b/recipes-bcm/bcm2835/bcm2835_1.38.bb
new file mode 100644
index 000..71395af
--- /dev/null
+++ b/recipes-bcm/bcm2835/bcm2835_1.38.bb
@@ -0,0 +1,40 @@
+DESCRIPTION = Package that provides access to GPIO and other IO\
+functions on the Broadcom BCM 2835 chip, allowing access to the\
+GPIO pins on the 26 pin IDE plug on the RPi board
+SECTION = base
+HOMEPAGE = http://www.open.com.au/mikem/bcm2835;
+AUTHOR = Mike McCauley (mi...@open.com.au)
+
+LICENSE = GPLv2
+LIC_FILES_CHKSUM = file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263
+
+COMPATIBLE_MACHINE = raspberrypi
+
+SRC_URI = http://www.open.com.au/mikem/bcm2835/bcm2835-${PV}.tar.gz;
+
+SRC_URI[md5sum] = 22d431f7402b9c7f93baef348a459cb1
+SRC_URI[sha256sum] =
90c993559ea273ae2e0587f6b815f7c80f19f47ee7f8aa7799b883f975196dbe
+
+inherit autotools
+
+do_compile_append() {
+# Now compiling the examples provided by the package
+mkdir -p ${B}/examples
+for file in `ls ${S}/examples`; do
+${CC} ${S}/examples/${file}/${file}.c -o ${B}/examples/${file}
-Bstatic -L${B}/src -lbcm2835 -I${S}/src
+done
+}
+
+do_install_append() {
+install -d ${D}/${libdir}/${BPN}
+for file in ${B}/examples/*
+do
+install -m 0755 ${file} ${D}/${libdir}/${BPN}
+done
+}
+
+PACKAGES += ${PN}-tests
+
+FILES_${PN} =
+FILES_${PN}-tests = ${libdir}/${BPN}
+FILES_${PN}-dbg += ${libdir}/${BPN}/.debug
--
2.1.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 5/5] userland: Bump SRCREV
Change-Id: If1d2608322749db4baa445ba94bc471a0ac86a5c
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
recipes-graphics/userland/userland_git.bb | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/recipes-graphics/userland/userland_git.bb
b/recipes-graphics/userland/userland_git.bb
index 77c98d7..1e60ea8 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -13,7 +13,7 @@ COMPATIBLE_MACHINE = raspberrypi
SRCBRANCH = master
SRCFORK = raspberrypi
-SRCREV = 85441185e653347e6b3c2bbc7494f5e29a6ca4a2
+SRCREV = 3b81b91c18ff19f97033e146a9f3262ca631f0e9
SRC_URI =
git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
@@ -32,10 +32,13 @@ do_install_append() {
rm -rf ${D}/opt
}
-FILES_${PN} += ${libdir}/*${SOLIBS}
+FILES_${PN} += \
+${libdir}/*${SOLIBS} \
+${libdir}/plugins
FILES_${PN}-dev = ${includedir} \
${prefix}/src
FILES_${PN}-doc += ${datadir}/install
+FILES_${PN}-dbg += ${libdir}/plugins/.debug
PACKAGE_ARCH = ${MACHINE_ARCH}
--
2.1.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 1/5] linux-raspberrypi: Refactor kernel recipes
We use this to simplify the update process. Updating a kernel version will not
require renaming the recipe but only tweaking LINUX_VERSION.
Update kernel version:
- bump SRCREV
- bump LINUX_VERSION if needed
[Support #26]
Change-Id: I7565ddd1f03cc34c34aa5da92664a0057b415c9a
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
recipes-kernel/linux/linux-raspberrypi.inc| 2 +-
recipes-kernel/linux/linux-raspberrypi_3.10.38.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.10.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.12.36.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.12.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.16.5.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.16.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.18.5.bb | 5 -
recipes-kernel/linux/linux-raspberrypi_3.18.bb| 8
recipes-kernel/linux/linux-raspberrypi_3.6.11.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.6.bb | 8
recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 6 --
recipes-kernel/linux/linux-raspberrypi_3.8.bb | 8
13 files changed, 49 insertions(+), 36 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.10.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.12.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.18.5.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.18.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.6.bb
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.bb
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index ff0c5ce..c00128d 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -11,7 +11,7 @@ SRC_URI += \
COMPATIBLE_MACHINE = raspberrypi
-PV_append = +git${SRCREV}
+PV = ${LINUX_VERSION}+git${SRCREV}
# NOTE: For now we pull in the default config from the RPi kernel GIT tree.
KERNEL_DEFCONFIG = bcmrpi_defconfig
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
b/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
deleted file mode 100644
index a0c5012..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.10.38.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 1b49b450222df26e4abf7abb6d9302f72b2ed386
-SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.10.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.10.bb
b/recipes-kernel/linux/linux-raspberrypi_3.10.bb
new file mode 100644
index 000..e5d5bf2
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.10.bb
@@ -0,0 +1,8 @@
+LINUX_VERSION ?= 3.10.38
+
+SRCREV = 1b49b450222df26e4abf7abb6d9302f72b2ed386
+SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.10.y \
+ file://sl030raspberrypii2ckernel.patch \
+
+
+require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
b/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
deleted file mode 100644
index e9e9ad7..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.12.36.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 90fa5df724d147564149c7b79cb1ffc571a345ec
-SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.12.bb
b/recipes-kernel/linux/linux-raspberrypi_3.12.bb
new file mode 100644
index 000..2952778
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.12.bb
@@ -0,0 +1,8 @@
+LINUX_VERSION ?= 3.12.36
+
+SRCREV = 90fa5df724d147564149c7b79cb1ffc571a345ec
+SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y \
+ file://sl030raspberrypii2ckernel.patch \
+
+
+require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
b/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
deleted file mode 100644
index 97947c2..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = 377c82aa1d31b37f1096096b0e4c65beb0bc5c49
-SRC_URI =
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.16.y \
- file://sl030raspberrypii2ckernel.patch \
-
-
-require linux-raspberrypi.inc
diff --git
[yocto] [meta-raspberrypi][PATCH V2 3/5] rpi-gpio: Update to v0.5.9
Change-Id: Ifc455b9106f07583ccaf3fe82723baaeb5e04d2e
Signed-off-by: Andrei Gherzan and...@gherzan.ro
---
recipes-devtools/python/rpi-gpio_0.5.6.bb | 19 ---
recipes-devtools/python/rpi-gpio_0.5.9.bb | 19 +++
2 files changed, 19 insertions(+), 19 deletions(-)
delete mode 100644 recipes-devtools/python/rpi-gpio_0.5.6.bb
create mode 100644 recipes-devtools/python/rpi-gpio_0.5.9.bb
diff --git a/recipes-devtools/python/rpi-gpio_0.5.6.bb
b/recipes-devtools/python/rpi-gpio_0.5.6.bb
deleted file mode 100644
index eff22d0..000
--- a/recipes-devtools/python/rpi-gpio_0.5.6.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-DESCRIPTION = A module to control Raspberry Pi GPIO channels
-HOMEPAGE = http://code.google.com/p/raspberry-gpio-python/;
-SECTION = devel/python
-LICENSE = MIT
-LIC_FILES_CHKSUM = file://LICENCE.txt;md5=35af90ff2a10e8bdc967653b9dfcb22a
-
-SRCNAME = RPi.GPIO
-
-SRC_URI = \
-
http://pypi.python.org/packages/source/R/RPi.GPIO/${SRCNAME}-${PV}.tar.gz \
-
-S = ${WORKDIR}/${SRCNAME}-${PV}
-
-inherit distutils
-
-COMPATIBLE_MACHINE = raspberrypi
-
-SRC_URI[md5sum] = cbdff15871230ceef29bb407d31da485
-SRC_URI[sha256sum] =
36b64a9485d6a0dc8f24cfca6af45759ee367ce412b952ebcf0409364e05813a
diff --git a/recipes-devtools/python/rpi-gpio_0.5.9.bb
b/recipes-devtools/python/rpi-gpio_0.5.9.bb
new file mode 100644
index 000..9394fd8
--- /dev/null
+++ b/recipes-devtools/python/rpi-gpio_0.5.9.bb
@@ -0,0 +1,19 @@
+DESCRIPTION = A module to control Raspberry Pi GPIO channels
+HOMEPAGE = http://code.google.com/p/raspberry-gpio-python/;
+SECTION = devel/python
+LICENSE = MIT
+LIC_FILES_CHKSUM = file://LICENCE.txt;md5=9b95630a648966b142f1a0dcea001cb7
+
+SRCNAME = RPi.GPIO
+
+SRC_URI = \
+
http://pypi.python.org/packages/source/R/RPi.GPIO/${SRCNAME}-${PV}.tar.gz \
+
+S = ${WORKDIR}/${SRCNAME}-${PV}
+
+inherit distutils
+
+COMPATIBLE_MACHINE = raspberrypi
+
+SRC_URI[md5sum] = 54ea6ef33502d43e3a89713593315e5a
+SRC_URI[sha256sum] =
167fab1861093677af69db135ce815729dd4fbfb8f8e2eb830eab6324bc89152
--
2.1.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Multiple packages from single recipe file
On Mon, Feb 9, 2015 at 4:51 AM, Bipnesh, Abhinav (Abhinav)
abhinavbipn...@avaya.com wrote:
Hi,
I was looking further into the document to find a way to define multiple
packages from a single recipe file. As in current recipe I have written a
do_install() function for putting files in particular directories. So it
copies files from ${S} to ${D}.
But some of the documents talk about multiple package something as below
FILES_${PN} = \
${bindir}/* \
${sbindir}/* \
${libexecdir}/* \
${libdir}/lib*.so.* \
${sysconfdir} \
${sharedstatedir} \
${localstatedir} \
/bin/* \
/sbin/* \
/lib/*.so* \
${datadir}/${PN} \
${libdir}/${PN}/* \
${datadir}/pixmaps \
${datadir}/applications \
${datadir}/idl \
${datadir}/omf \
${datadir}/sounds \
${libdir}/bonobo/servers
FILES_${PN}-dbg = \
${bindir}/.debug \
${sbindir}/.debug \
${libexecdir}/.debug \
${libdir}/.debug \
/bin/.debug \
/sbin/.debug \
/lib/.debug \
${libdir}/${PN}/.debug
But I am not getting how the source for such file will be determine as in
our project files will be present in different directories and need to be
placed in some predefined paths.
So how we can achieve the same.
Thanks,
Abhinav
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi , basically the yocto recepeis work exactly as an spec file:
www.rpm.org/max-rpm/s1-rpm-build-creating-spec-file.html
The scenario you mention is possible:
rpm5.org/docs/rpm-guide.html
Hope it helps
Victor Rodriguez
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
