Re: [OpenWrt-Devel] [PATCH RESENDv2] Create rDNS records for LuCI "Hostnames"

2014-08-27 Thread John Crispin
On 26/08/2014 17:10, Tyler Fenby wrote: > LuCI creates "domain" UCI config sections, which the dnsmasq init > file then, currently, translates into "address" config lines. This > is not the correct usage of "address" (see r36943), and also causes > rDNS records to not be created. This patches dns

Re: [OpenWrt-Devel] [PATCH v2] ar71xx : Fix the sys LEDs on the EasyLink M150 and mini

2014-08-27 Thread John Crispin
Hi, 1) the patch is not sent inline but as an attachement 2) the patch does not apply with git am due to the windows style new lines please start sending inline patches that are unix style and have no whitespace errors i am marking this one as rejected John On 25/08/2014 14:44, L. D. Pi

[OpenWrt-Devel] GPIO Keys and LED definitions for AsiaRF mt7620a AWV002-001 Rev .1

2014-08-27 Thread Luis Soltero
Hello All, I am having issues implementing GPIO definitions in the DTS file for the AsiaRF board that we are trying to bring up.  This is seemingly an easy task but for the life of me I can't figure out why this is not working.   First some info. From t

Re: [OpenWrt-Devel] Including git revision commit hash and svn revision id on release announcement.

2014-08-27 Thread Yousong Zhou
On 28 August 2014 11:11, Alive4Ever wrote: > Hello developers. > > Probably you are annoyed by people asking which revision is Barrier Breaker > RC3 or similar, because they want to be able to compile the specific release > theirselves. > > To address this issue, I think it would be better to add

[OpenWrt-Devel] Including git revision commit hash and svn revision id on release announcement.

2014-08-27 Thread Alive4Ever
Hello developers. Probably you are annoyed by people asking which revision is Barrier Breaker RC3 or similar, because they want to be able to compile the specific release theirselves. To address this issue, I think it would be better to add git revision commit hash for each Openwrt release announ

Re: [OpenWrt-Devel] Using "-" in section names

2014-08-27 Thread Jo-Philipp Wich
> So, it shouldn't be necessary with the C implementation? Correct, but that cannot be changed without breaking support for legacy APIs. > >> Simply replacing dashes with underscores is not possible either as this >> would lead to ambiguous results. > > Yes, I've got exactly this problem: the

Re: [OpenWrt-Devel] Using "-" in section names

2014-08-27 Thread Baptiste Jonglez
On Wed, Aug 27, 2014 at 07:49:21PM +0200, Jo-Philipp Wich wrote: > Hi, > > yes there is a reason, the initial uci implementation was shell based > and section names are part of generated variable names which must not > contain dashes. So, it shouldn't be necessary with the C implementation? > Si

Re: [OpenWrt-Devel] Using "-" in section names

2014-08-27 Thread Jo-Philipp Wich
Hi, yes there is a reason, the initial uci implementation was shell based and section names are part of generated variable names which must not contain dashes. Simply replacing dashes with underscores is not possible either as this would lead to ambiguous results. ~ Jow _

[OpenWrt-Devel] Parsing list of options with the callback method

2014-08-27 Thread Baptiste Jonglez
Hi, According to [1], it should be possible to parse list of options in a UCI file using an "option_cb()" callback. It does not seem to work as expected, for instance this block: config example list 'import_table' '42' list 'import_table' '53' leads to the following calls: config_cb ex

[OpenWrt-Devel] Using "-" in section names

2014-08-27 Thread Baptiste Jonglez
Hi, I am currently writing an init script using the callback method [1], on BB-rc3. However, it does not seem possible to use "-" in a section name, for instance: config interface 'tun-test' option 'rxcost' '42' The "config_cb" function never gets called for this section (but "option_cb

[OpenWrt-Devel] [PATCH] omap: add kernel 3.14 support

2014-08-27 Thread Rafał Miłecki
It has been compile-tested only so far. Please give it a try. Signed-off-by: Rafał Miłecki --- .../0334-video-da8xx-fb-adding-dt-support.patch| 203 + ...-fb-Add-API-to-register-wait-for-vsync-ca.patch | 91 + ...-fb-fix-defect-with-vsync-callback-invoca.patch |

[OpenWrt-Devel] [PATCH 1/3] gemini: switch to kernel 3.10

2014-08-27 Thread Rafał Miłecki
This switches to kernel 3.10 that was prepared by Hauke in: gemini: add support for kernel 3.10 This is compile tested only, please run test and report back. I've simply checked if it still compiles, unfortunately we didn't get any feedback for this target. Signed-off-by: Rafał Miłecki

Re: [OpenWrt-Devel] platform name 'ramips' VS 'ramips_24kec'

2014-08-27 Thread Bastian Bittorf
* Weimarnetz e.V., Vorstand/Vereinsvorsitzender: Bastian Bittorf [27.08.2014 09:42]: > can somebody explain this? bye, bastian digging through 'target/linux/ramips' i can see, that all boards are CPU_TYPE:=24kec but only 1 board 'rt288x' is CPU_TYPE:=mips32r2 (so '24kec' is a special subtype of

[OpenWrt-Devel] platform name 'ramips' VS 'ramips_24kec'

2014-08-27 Thread Bastian Bittorf
i stumbled in a custom script over this problem: root@fonera2n:~ opkg status kernel Package: kernel Version: 3.10.34-1-9ab8a27dee25ed0e5197bf83aebd96c3 Depends: libc Status: install hold installed Architecture: ramips_24kec Installed-Time: 1396519878 # so the platform/architacture name is 'ramips