[OpenWrt-Devel] [PATCH] at91: add SAMA5D3-Xplained board UBI parameters to makefile.

2015-03-04 Thread Songjun Wu
Signed-off-by: Songjun Wu --- target/linux/at91/image/Makefile |3 +++ 1 file changed, 3 insertions(+) diff --git a/target/linux/at91/image/Makefile b/target/linux/at91/image/Makefile index f88cab4..49e2bee 100644 --- a/target/linux/at91/image/Makefile +++ b/target/linux/at91/image/Makefile

[OpenWrt-Devel] [PATCH] toolchain/uClibc: Add uClibc snapshot as selectable version

2015-03-04 Thread Jeff Waugh
Hi all, Here's an alternative version of my uClibc snapshot change. This one just uses uClibc-snapshot.tar.bz2, which is super-easy but has some drawbacks: - You won't get a like-for-like build from a fresh OpenWrt checkout (though once you've cached the download, you'll have like-for-like bui

Re: [OpenWrt-Devel] [PATCH] toolchain/uClibc: Add uClibc snapshot as selectable version

2015-03-04 Thread Jeff Waugh
On Thu, Mar 5, 2015 at 1:19 PM, Jeff Waugh wrote: > 1) use uclibc-snapshot.tar.bz2 instead of a dated, known working version > (though we can't check the md5sum) > 2) use uclibc git at a specific revision > 3) use uclibc git at head > 4) anything I don't know about? uclibc-ng? > > I'm leaning tow

Re: [OpenWrt-Devel] [PATCH] toolchain/uClibc: Add uClibc snapshot as selectable version

2015-03-04 Thread Jeff Waugh
On Thu, Mar 5, 2015 at 7:04 AM, Dirk Neukirchen wrote: > adding uclibc snapshots maybe other (patched) variants > might improve well some things (quality ? pressure to release new > stable version?) > So we have some options: 1) use uclibc-snapshot.tar.bz2 instead of a dated, known working

Re: [OpenWrt-Devel] [PATCH] procd: Use pkg-config to find json-c

2015-03-04 Thread Yousong Zhou
Hi, Karl On 4 March 2015 at 21:51, Karl Palsson wrote: > > Comments inline, I thought I'd made similar comments earlier, but > perhaps I forgot... > > William Holland wrote: >> --- >> CMakeLists.txt |4 >> plug/hotplug.c |2 +- >> service/validate.c |2 +- >> 3 files ch

Re: [OpenWrt-Devel] [PATCH] toolchain/uClibc: Add uClibc snapshot as selectable version

2015-03-04 Thread Jeff Waugh
On Thu, Mar 5, 2015 at 7:04 AM, Dirk Neukirchen wrote: > Its probably a good thing to get easier access to a uclibc variant than > using > - "abandoned" eglibc = bad ("EGLIBC is no longer developed and such goals > are now being addressed directly in GLIBC. ") > By the way, I've also been work

Re: [OpenWrt-Devel] [PATCH] toolchain/uClibc: Add uClibc snapshot as selectable version

2015-03-04 Thread Dirk Neukirchen
On 04.03.2015 20:13, Jeff Waugh wrote: > There hasn't been a uClibc release since May 2012, but some useful things have > landed in git since then... for example, make/get/setcontext are necessary for > uClibc + gccgo/libgo (c.f. my last patch set). > > This adds a non-default option for a known-g

[OpenWrt-Devel] [PATCH] toolchain/uClibc: Add uClibc snapshot as selectable version

2015-03-04 Thread Jeff Waugh
eckout. But I did it this way to get it ready for feedback. Thanks, Jeff Signed-off-by: Jeff Waugh --- toolchain/uClibc/Config.in | 4 + toolchain/uClibc/Config.version| 4 + toolchain/uClibc/common.mk | 11 ++ toolchain/u

[OpenWrt-Devel] [PATCH 2/2] toolchain/gcc/final: Add --disable-werror

2015-03-04 Thread Jeff Waugh
Hi all, This was the least dirty way I could find to stop the build blowing up with a maybe-uninitialized error. The code in question hadn't changed upstream, either... at least until it was removed. Thanks, Jeff I'm not convinced this is the right thing to do, but it's required for libgo to bu

[OpenWrt-Devel] [PATCH 1/2] gccgo/libgo toolchain support for OpenWrt

2015-03-04 Thread Jeff Waugh
Hi all, I'm sure there are style weirdnesses with this. Commentary much appreciated! - Jeff - It won't work with uClibc 0.99.33.x because it requires make/get/setcontext - It DOES work with a recent uClibc snapshot (with UCLIBC_HAS_CONTEXT_FUNCS), as well as eglibc - It works with gcc 4.8, an

Re: [OpenWrt-Devel] MI424WR Rev I Hynix NAND Error

2015-03-04 Thread James Hilliard
I wrote the image to flash using tftp from uboot, I'm having trouble isolating the cause of the ECC errors, what I'm not sure of is if there's a quirk with the Hynix NAND that the Eon NAND doesn't have. It would appear that the Hynix and Eon NAND chips are used interchangeably for this router mode

Re: [OpenWrt-Devel] MI424WR Rev I Hynix NAND Error

2015-03-04 Thread Conor O'Gorman
On 22/02/15 01:36, James Hilliard wrote: I've been trying to install OpenWRT on an Actiontec MI424WR Rev I, however some variants of this router use a Hynix NAND chip that OpenWRT doesn't seem to be able to access. There are other versions of this router that use a Eon NAND chip that works fine.

Re: [OpenWrt-Devel] minimal work needed to build just the toolchain

2015-03-04 Thread Claudio Thomas
On 03.03.2015 13:17, John Crispin wrote: > On 03/03/2015 12:27, Claudio Thomas wrote: >> Hi, >> >> the same question was already discussed on 2008-01, but it seems to me, >> that some iterim steps are no more necessary... I guess that there has >> been some improvements made in the last 7 years :-)

Re: [OpenWrt-Devel] [PATCH] procd: Use pkg-config to find json-c

2015-03-04 Thread William Holland
Sorry I missed your reply to Yousong Zhou's email addressing the #include issue. So should it simple be the following? diff --git a/plug/hotplug.c b/plug/hotplug.c index 061833a..6df7971 100644 --- a/plug/hotplug.c +++ b/plug/hotplug.c @@ -22,7 +22,7 @@ #include #include #include -#includ

Re: [OpenWrt-Devel] [PATCH] procd: Use pkg-config to find json-c

2015-03-04 Thread Karl Palsson
Comments inline, I thought I'd made similar comments earlier, but perhaps I forgot... William Holland wrote: > --- > CMakeLists.txt |4 > plug/hotplug.c |2 +- > service/validate.c |2 +- > 3 files changed, 6 insertions(+), 2 deletions(-) > > diff --git a/CMakeLists.tx

Re: [OpenWrt-Devel] Ethernet problem with R8000

2015-03-04 Thread Ian Kent
On Wed, 2015-03-04 at 10:29 +, Conor O'Gorman wrote: > On 04/03/15 05:29, Ian Kent wrote: > > On Sat, 2015-02-28 at 23:07 +0800, Ian Kent wrote: > >> The only things I can say for sure are, packets sent are seen by the > >> bgmac driver and the driver gets a transmit completion interrupt which

Re: [OpenWrt-Devel] Ethernet problem with R8000

2015-03-04 Thread Conor O'Gorman
On 04/03/15 05:29, Ian Kent wrote: On Sat, 2015-02-28 at 23:07 +0800, Ian Kent wrote: The only things I can say for sure are, packets sent are seen by the bgmac driver and the driver gets a transmit completion interrupt which it processes. However, no packets is seen coming from the router switc