I was having intermittent i2c issues on the device until I applied this kernel
patch
which I found online.
Signed-off-by: Richard Purdie
---
.../sl030raspberrypii2ckernel.patch| 32
recipes-kernel/linux/linux-raspberrypi_3.2.27.bb |1 +
recipes-kerne
If we have this recipe, it means the whole armv6 (or whichever tune) is chosen
depends
on a machine specific recipe. This makes no sense as armX packages are meant to
be
machine independent.
We've had this problem in other layers and it causes needed rebuilds of packages
when you switch machines
bruce ashfield will know what i'm talking about as i've been
torturing him over the last few days with this cool, new 64-bit, dual
core MIPS router that looks like a perfectly respectable replacement
for the current MIPS yocto reference board, the routerstation pro
(both being from ubiquiti).
On Sun, Apr 21, 2013 at 3:53 PM, Robert P. J. Day wrote:
>
> bruce ashfield will know what i'm talking about as i've been
> torturing him over the last few days with this cool, new 64-bit, dual
> core MIPS router that looks like a perfectly respectable replacement
> for the current MIPS yocto re
This mail was sent out by Package Report 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 u
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
