[yocto] [PATCH] linux-raspberrypi: Fix i2c issues
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-kernel/linux/linux-raspberrypi_3.6.11.bb |1 +
3 files changed, 34 insertions(+)
create mode 100644
recipes-kernel/linux/linux-raspberrypi/sl030raspberrypii2ckernel.patch
diff --git
a/recipes-kernel/linux/linux-raspberrypi/sl030raspberrypii2ckernel.patch
b/recipes-kernel/linux/linux-raspberrypi/sl030raspberrypii2ckernel.patch
new file mode 100644
index 000..8534ecb
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi/sl030raspberrypii2ckernel.patch
@@ -0,0 +1,32 @@
+Fix i2c timing errors.
+
+When Transmitting: Make SDA valid quarter of a cycle after the falling edge of
SCL.
+When Receiving: Sample SDA Quarter of a cycle after the rising edge of SCL.
+
+Upstream-Status: Pending
+
+RP 2013/04/21
+
+Index: git/drivers/i2c/busses/i2c-bcm2708.c
+===
+--- git.orig/drivers/i2c/busses/i2c-bcm2708.c 2013-01-06 17:15:00.754954587
+
git/drivers/i2c/busses/i2c-bcm2708.c 2013-01-06 17:50:09.794905741
+
+@@ -150,6 +150,7 @@
+ unsigned long bus_hz;
+ u32 cdiv;
+ u32 c = BSC_C_I2CEN | BSC_C_INTD | BSC_C_ST | BSC_C_CLEAR_1;
++ u32 cdel;
+
+ bus_hz = clk_get_rate(bi->clk);
+ cdiv = bus_hz / baudrate;
+@@ -163,6 +164,10 @@
+ bcm2708_wr(bi, BSC_A, bi->msg->addr);
+ bcm2708_wr(bi, BSC_DLEN, bi->msg->len);
+ bcm2708_wr(bi, BSC_C, c);
++
++ cdel = (cdiv / 4) & 0x;
++ cdel = cdel << 16 | cdel;
++ bcm2708_wr(bi, BSC_DEL, cdel);
+ }
+
+ static irqreturn_t bcm2708_i2c_interrupt(int irq, void *dev_id)
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.2.27.bb
b/recipes-kernel/linux/linux-raspberrypi_3.2.27.bb
index c7a12e6..a68186b 100644
--- a/recipes-kernel/linux/linux-raspberrypi_3.2.27.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_3.2.27.bb
@@ -8,6 +8,7 @@ PV_append = "+git${SRCREV}"
SRCREV = "10182a3bc434b27740f81c2b836a1af943060241"
SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.2.27 \
+ file://sl030raspberrypii2ckernel.patch \
"
S = "${WORKDIR}/git"
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
b/recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
index caee7f2..07b0ae8 100644
--- a/recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_3.6.11.bb
@@ -8,6 +8,7 @@ PV_append = "+git${SRCREV}"
SRCREV = "31a951046155b27361127d9cf85a1f58719fe9b3"
SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.6.y \
+ file://sl030raspberrypii2ckernel.patch \
"
S = "${WORKDIR}/git"
--
1.7.10.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] linux-libc-headers-raspberrypi: Drop, its unneeded and bad practise
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 since the sstate checksums change. These headers are
just part
of the toolchain bootstrap process so "standard" kernel headers are fine. The
kernel
header version does need to be later of equal to the kernel version but we're
fine in
that regard since the core is on 3.8, the latest pi kernel is 3.6.
There is nothing special about these headers so lets remove them and use the
standard
system provided recipe, avoding any rebuilds. I tested the various other
recipes in
the layer and there doesn't seem to be any dependency on these headers.
Signed-off-by: Richard Purdie
---
.../linux-libc-headers-raspberrypi_3.2.27.bb | 12
1 file changed, 12 deletions(-)
delete mode 100644
recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
diff --git
a/recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
b/recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
deleted file mode 100644
index a5964ab..000
--- a/recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
+++ /dev/null
@@ -1,12 +0,0 @@
-require recipes-kernel/linux-libc-headers/linux-libc-headers.inc
-
-PR = "r0"
-
-PROVIDES = "linux-libc-headers"
-RPROVIDES_${PN}-dev = "linux-libc-headers-dev"
-RPROVIDES_${PN}-dbg = "linux-libc-headers-dbg"
-
-SRCREV = "10182a3bc434b27740f81c2b836a1af943060241"
-SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.2.27 \
- "
-S = "${WORKDIR}/git"
--
1.7.10.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] looking to "yoctify" mips-based ubiquiti edgerouter lite
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). this is what i'm talking about: http://ubnt.ca/en/edgemax/61-edgemax.html salient specs: * dual-core 500MHz, MIPS64 (cavium octeon+) * 512MB DDR2 RAM * 2 GB onboard flash storage anyway, i wrote a bunch of wiki pages on it starting here: http://www.crashcourse.ca/wiki/index.php/EdgeRouter_Lite i've already downloaded the source so i have the kernel and the .config file and was interested in building the toolchain so i could at least compile and test the kernel. i know next to nothing about MIPS but, based on what i've read and the possible tunings being: AVAILTUNES += "mips mips64-n32 mips64 mipsel mips64el-n32 mips64el mips-nf mips64-nf-n32 mips64-nf mipsel-nf mips64el-nf-n32 mips64el-nf" i would think what i want is "mips64-nf", but anyone who's a MIPS expert is welcome to correct me. this seems like a perfectly respectable MIPS platform for experimenting, and it seems like it wouldn't be hard to come up with a yocto machine definition for it. rday p.s. one of the ubnt engineers i've been chatting with is adamant that they're keeping the price of this thing at $99 USD (MSRP), so it's certainly affordable for hackers. -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] looking to "yoctify" mips-based ubiquiti edgerouter lite
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 reference board, the routerstation pro > (both being from ubiquiti). Indeed! Over the next few weeks, I'll have a meta-yocto-bsp and linux-yocto-dev support for the board, and once that is done and working, I can throw the switch and make this the MIPS hardware reference for yocto 1.5. So if anyone else is working on this, let me know and I'll keep you in the loop on the development of the reference BSP. Cheers, Bruce > > this is what i'm talking about: > > http://ubnt.ca/en/edgemax/61-edgemax.html > > salient specs: > > * dual-core 500MHz, MIPS64 (cavium octeon+) > * 512MB DDR2 RAM > * 2 GB onboard flash storage > > anyway, i wrote a bunch of wiki pages on it starting here: > > http://www.crashcourse.ca/wiki/index.php/EdgeRouter_Lite > > i've already downloaded the source so i have the kernel and the > .config file and was interested in building the toolchain so i could > at least compile and test the kernel. > > i know next to nothing about MIPS but, based on what i've read and > the possible tunings being: > > AVAILTUNES += "mips mips64-n32 mips64 mipsel mips64el-n32 mips64el > mips-nf mips64-nf-n32 mips64-nf mipsel-nf mips64el-nf-n32 mips64el-nf" > > i would think what i want is "mips64-nf", but anyone who's a MIPS > expert is welcome to correct me. > > this seems like a perfectly respectable MIPS platform for > experimenting, and it seems like it wouldn't be hard to come up with a > yocto machine definition for it. > > rday > > p.s. one of the ubnt engineers i've been chatting with is adamant > that they're keeping the price of this thing at $99 USD (MSRP), so > it's certainly affordable for hackers. > > -- > > > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Upgrade recipes name list
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 upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version is unstable" You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason lsb 4.1 1.4 Yi Zhao ccache3.1.8 3.1.9 Wenzong Fan gettext 0.18.20.18.2.1 Wenzong Fan swabber-native0.0+gitAUTOINC+a079239 0.0+gitAUTOINC+2d1fe36Saul Wold lsbinitscripts9.45 9.46 Saul Wold mkelfimage1.0.0+svn6637 5914 Saul Wold libcheck 0.9.9 0.9.10 Saul Wold mesa-demos8.0.1 8.1.0 Saul Wold nspr 4.9.5 4.9.6 Saul Wold cups 1.6.1 1.6.2 Saul Wold pkgconfig 0.25 0.28 Saul Woldremoves glib-conf, adds circu... kconfig-frontends 3.8.0 3.8.0.0 Saul Wold dpkg 1.16.91.16.10 Saul Wold glib-networking 2.28.72.36.1 Saul Wold docbook-sgml-dtd-4.1-native 1.0 41 Saul Wold docbook-sgml-dtd-3.1-native 1.0 31 Saul Wold createrepo0.4.110.9.9 Saul WoldVersions after 0.9.* use YUM,... guilt-native 0.33 0.35 Saul Wold help2man-native 1.40.13 1.41.2 Saul Wold vte 0.28.20.34.4 Saul Wold libgcrypt 1.5.0 1.5.2 Saul Wold libxkbcommon 0.2.0 0.3.0 Saul Wold sysstat 10.1.410.1.5 Saul Wold resolvconf1.70 1.71 Saul Wold libxml2 2.9.0 2.9.1 Saul Wold oprofileui-server 0.0+gitAUTOINC+82ecf8c 0.0+gitAUTOINC+f168b8bSaul Wold texinfo 4.13a 5.1 Saul WoldChecking script parses direct... sqlite3 3071502 3071602 Saul Wold mklibs-native 0.1.340.1.35 Saul Wold build-appliance-image 1.0 8.0.1 Saul Wold dhcp 4.2.5 4.2.5-P1 Saul Wold less 457 458 Saul Wold tzcode-native 2013b 2013c Saul Wold desktop-file-utils-native 0.15 0.21 Saul Wold docbook-sgml-dtd-4.5-native 1.0 4.5 Saul Wold
[yocto] [Package Report System]Manual check recipes name list
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 Version LastChkVersion LastChkTime Maintainer NoUpgradeReason tinylogin1.4 1.4 231 day Radu Moisan ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
