Recall this patch since the dhcp in oe-core has been updated to 4.3.0.
I'll send v2 after fixed the version number for bbappend.
Sorry for the inconvenience.
// Wenzong
On 06/06/2014 06:00 PM, wenzong@windriver.com wrote:
From: Wenzong Fan wenzong@windriver.com
dhcp-server fails to
Hi
I’m trying to use the meta-raspberrypi BSP with Yocto (1.6, Daisy).
It works great, except I have no idea how to use a custom kernel config!
I have a custom kernel recipe that bbappends to the meta-raspberrypi kernel
recipe.
I’ve tried using defconfig as well as configuration fragments,
Hi
Had the same problem. The problem is in file linux-raspberrpi.inc the
following line:
install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG}
${WORKDIR}/defconfig || die No default configuration for ${MACHINE} /
${KERNEL_DEFCONFIG} available.
it installs always the defconfig at
On 12/06/2014 07:48, Jonatan Magnusson wrote:
Hi
I’m trying to use the meta-raspberrypi BSP with Yocto (1.6, Daisy).
It works great, except I have no idea how to use a custom kernel config!
I have a custom kernel recipe that bbappends to the meta-raspberrypi kernel
recipe.
I’ve tried
On Thu, Jun 12, 2014 at 11:26:57AM +0800, Yao Xinpan wrote:
Signed-off-by: Yao Xinpan ya...@cn.fujitsu.com
Why is this recipe needed in oe-core layer? Wouldn't meta-networking be
more suitable?
The patch also belongs to oe-core ML not yocto.
---
meta/files/common-licenses/DMTF
On 12/06/2014 10:07, Ruud den Bekker wrote:
Hi Alex,
Recently you posted a fix for a dynamic library loading problem
for the RaspberryPi and a graphic library.
I'm now facing a dynamic library not found problem when using
the BeagleBone board RFS in yocto. However, when I use
On 12 June 2014 09:56, Martin Jansa martin.ja...@gmail.com wrote:
Why is this recipe needed in oe-core layer? Wouldn't meta-networking be
more suitable?
The patch also belongs to oe-core ML not yocto.
Agreed, unless there's a strong reason then this should go to
meta-networking (so send to
Good Morning,
pseudo_1.5.1.bb refers to a URL like this
http://www.yoctoproject.org/downloads/${BPN}/${BPN}-${PV}.tar.bz2
but that is not were the sourcecode is located anymore. It looks
like an infrastructure problem? Should I report a bug somewhere
or can this be easily fixed?
holger
--
On Tuesday 03 June 2014 06:25:41 Kweh, Hock Leong wrote:
Hi, understand the patch below is to fix the x264 yocto build issue but it
is for Daisy branch. How about the Dylan branch? Can we use the same
commit id on the SRCREV?
Here is the correct fix for dylan (where the recipe was in meta-oe,
Burton, Ross ross.burton@... writes:
On 15 July 2013 13:38, Amit Kumar Amit.Kumar@... wrote:
Failed to fetch test data from the network. Please ensure your
network
is configured correctly.
Assuming that you did have network connectivity, then the problem
normally is that you need
Hi Alex,
On Friday 30 May 2014 12:39:13 Alex J Lennon wrote:
When I drop into a devshell for an unpacked SRV_REV from a particular
git SRC_URI I have the git remote origin set to a local archive in the
~/downloads tree.
Is there a build variable, say, I can set to leave the original git
On 12/06/2014 11:58, Paul Eggleton wrote:
Hi Alex,
On Friday 30 May 2014 12:39:13 Alex J Lennon wrote:
When I drop into a devshell for an unpacked SRV_REV from a particular
git SRC_URI I have the git remote origin set to a local archive in the
~/downloads tree.
Is there a build variable,
I have a SoM which will be used on several boards, this SoM has a base
kernel for it, with its board-*.c file. In each board I may have
different peripherals, so I have to patch the same board-*.c file
depending on my target board, and that patches may be conflicting one
each other. For
On Thu, Jun 12, 2014 at 1:54 PM, Daniel Hilst Selli
danielhi...@gmail.com wrote:
I have a SoM which will be used on several boards, this SoM has a base
kernel for it, with its board-*.c file. In each board I may have different
peripherals, so I have to patch the same board-*.c file depending on
Hi Holger,
On Wednesday 11 June 2014 06:19:49 Holger Freyther wrote:
pseudo_1.5.1.bb refers to a URL like this
http://www.yoctoproject.org/downloads/${BPN}/${BPN}-${PV}.tar.bz2
but that is not were the sourcecode is located anymore. It looks
like an infrastructure problem? Should I report a
On 14-06-12 09:46 AM, Alex J Lennon wrote:
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
recipes to be linux-yocto style, to provide config frag support.
I'm working with poky master, referencing linux-yocto-custom.bb in
meta-skeleton
This seems to be working as far
On 12/06/2014 14:53, Bruce Ashfield wrote:
On 14-06-12 09:46 AM, Alex J Lennon wrote:
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
recipes to be linux-yocto style, to provide config frag support.
I'm working with poky master, referencing linux-yocto-custom.bb in
On 12/06/2014 14:59, Alex J Lennon wrote:
On 12/06/2014 14:53, Bruce Ashfield wrote:
On 14-06-12 09:46 AM, Alex J Lennon wrote:
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
recipes to be linux-yocto style, to provide config frag support.
I'm working with poky
On 14-06-12 09:59 AM, Alex J Lennon wrote:
On 12/06/2014 14:53, Bruce Ashfield wrote:
On 14-06-12 09:46 AM, Alex J Lennon wrote:
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
recipes to be linux-yocto style, to provide config frag support.
I'm working with poky
On 14-06-12 10:52 AM, Alex J Lennon wrote:
On 12/06/2014 14:59, Alex J Lennon wrote:
On 12/06/2014 14:53, Bruce Ashfield wrote:
On 14-06-12 09:46 AM, Alex J Lennon wrote:
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
recipes to be linux-yocto style, to provide
On 12/06/2014 15:54, Bruce Ashfield wrote:
On 14-06-12 10:52 AM, Alex J Lennon wrote:
On 12/06/2014 14:59, Alex J Lennon wrote:
On 12/06/2014 14:53, Bruce Ashfield wrote:
On 14-06-12 09:46 AM, Alex J Lennon wrote:
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
Hello Yocto-Community,
It's really easy to add auto completion in the SDK setup scripts
with BASH's read -e -p. I attached a short patch that does this.
Makes life very comfortable ;-).
I already asked Paul Eggleton on IRC about the change, and our only concern
is that it could break the script
On 14-06-12 07:54 AM, Daniel Hilst Selli wrote:
I have a SoM which will be used on several boards, this SoM has a base
kernel for it, with its board-*.c file. In each board I may have
different peripherals, so I have to patch the same board-*.c file
depending on my target board, and that patches
I am a newbie to Yocto project...
I wanted to know.. what is the role of the sstate-cache directory?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Thu, Jun 12, 2014 at 6:26 PM, Arun Kumar arunkr.li...@gmail.com wrote:
I am a newbie to Yocto project...
I wanted to know.. what is the role of the sstate-cache directory?
are you asking for clarifications after reading this
I'm sure I'll get tired of looking at this eventually, and learn to
love the normal ncurses style interface of bitbake. But things are
still new enough to me that I want to know what's going on.
As you know, when we bitbake a recipe, we see lots of messages about
individual tasks that are run as
On 12 June 2014 19:53, Patrick Doyle wpds...@gmail.com wrote:
As you know, when we bitbake a recipe, we see lots of messages about
individual tasks that are run as they are being run (do_fetch,
do_configure, etc…), and then a final summary message that reads
something like:
NOTE: Tasks
On Thu, Jun 12, 2014 at 12:00 PM, Burton, Ross ross.bur...@intel.com
wrote:
On 12 June 2014 19:53, Patrick Doyle wpds...@gmail.com wrote:
As you know, when we bitbake a recipe, we see lots of messages about
individual tasks that are run as they are being run (do_fetch,
do_configure, etc…),
Thanks.
bitbake foo | cat
is most likely to be what I was looking for. I found the cooker log
shortly after I asked my question. I'll go look through bitbake and
see what it would take to create a symbolic link to the most recent
logfile, as is done with the logfiles for the individual tasks.
On 12/06/2014 07:48, Jonatan Magnusson wrote:
Hi
I’m trying to use the meta-raspberrypi BSP with Yocto (1.6, Daisy).
It works great, except I have no idea how to use a custom kernel config!
I have a custom kernel recipe that bbappends to the meta-raspberrypi kernel
recipe.
I’ve tried
Guys,
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.1/
poky: a43dba8c2904f9c1ce0425c53c5a7f4718121e6b
oecore: d28b21e01fbc4b780d14495894c4253d422cd9d9
I don't have Beth's scripts to generate the complete list.
--
Sau!
Saul Wold
Yocto Component Wrangler @ Intel
Yocto
Scott Rifenbark
Intel Corporation
Yocto Project Documentation
503.712.2702
503.341.0418 (cell)
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
From: Heikki Krogerus heikki.kroge...@linux.intel.com
DMA engines usually expect the fifo trigger level to be
aligned with the burst size. It should not be changed even
with small baud rates. This will fix an issue with
Designware DMA engine where the data can not be transferred
over UART with
From: H Hartley Sweeten hartl...@visionengravers.com
Add a simple sysfs interface to the generic PWM framework.
/sys/class/pwm/
`-- pwmchipN/ for each PWM chip
|-- export (w/o) ask the kernel to export a PWM channel
|-- npwm(r/o) number of PWM
From: Chew, Kean Ho kean.ho.c...@intel.com
The requested gpio pin must has the func_pin_mux field set
to GPIO function by BIOS/FW in advanced. Else, the gpio pin
request would fail. This is to ensure that we do not expose
any gpio pins which shall be used for alternate functions,
for eg: wakeup
From: Mika Westerberg mika.westerb...@linux.intel.com
Intel Baytrail I2C controllers can be enumerated from PCI as well as from
ACPI. In order to support this add the Baytrail PCI IDs to the driver.
Signed-off-by: Mika Westerberg mika.westerb...@linux.intel.com
Signed-off-by: Wolfram Sang
From: Adrian Hunter adrian.hun...@intel.com
If the SDHCI irq is shared with another device then the interrupt
handler can get called while SDHCI is runtime suspended. That is
harmless but the warning message is not useful so remove it. Also
returning IRQ_NONE is more appropriate.
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Intel BayTrail LPSS consists of two PWM controllers which can
be enumerated from ACPI namespace. This change will cause
platform device objects to be created for Intel BayTrail PWM
controllers which will allow the pwm-lpss driver to bind to them
and
From: Chew, Chiau Ee chiau.ee.c...@intel.com
The pxa2xx pci glue layer only support CE4100 SPI port
by default. To add BYT SPI port support, we make it a
generic PCI glue layer by renaming ce4100_xxx to
pxa2xx_spi_xxx.
This commit is created in reference to Mika's commit
during kernel-3.5
From: Chew, Chiau Ee chiau.ee.c...@intel.com
On Intel BayTrail, there was case whereby the resulting fast mode
bus speed becomes slower (~20% slower compared to expected speed)
if using the HCNT/LCNT calculated in the core layer. Thus, this
patch is added to allow pci glue layer to pass in
From: Alan Stern st...@rowland.harvard.edu
When CONFIG_HAS_DMA isn't enabled, the UDC core gets build errors:
drivers/built-in.o: In function `dma_set_coherent_mask':
include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
include/linux/dma-mapping.h:93: undefined reference to
From: Chew, Chiau Ee chiau.ee.c...@intel.com
BYT ACPI mode SPI not read/writing correctly at low speeds
using DMA mode. Fix the issue by changing DMA SRC_MSIZE and
DEST_MSIZE of SPI FIFO side from 16 to 32.
Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com
Signed-off-by: Maurice Petallo
From: Chew, Chiau Ee chiau.ee.c...@intel.com
All the I2C controllers on Intel BayTrail LPSS subsystem able
to support 10-bit addressing mode functionality.
Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com
Signed-off-by: Ong, Boon Leong boon.leong@intel.com
Signed-off-by: Wolfram Sang
43 matches
Mail list logo
