Re: [OpenWrt-Devel] Make UCI support for other software?

2012-08-02 Thread Nguyễn Hồng Quân
Thank you On Thu 02 Aug 2012 10:34:27 PM ICT, Ryan Nowakowski wrote: On Thu, Aug 02, 2012 at 05:32:51PM +0700, Nguyễn Hồng Quân wrote: To make a software use UCI for configuration instead of its own config, what do we have to do? Do we change in that software source code or UCI source code? Fo

Re: [OpenWrt-Devel] ramips eth tx timeout

2012-08-02 Thread Tobias Diedrich
Tobias Diedrich wrote: > If you want to poke at the ramips ethernet driver, I have a patch > that I haven't submitted yet (I think it has occasional problems on > bootup and probably unconditionally uses features that are not available on > all chipset types): > > This adds support for HW checksum

Re: [OpenWrt-Devel] ramips eth tx timeout

2012-08-02 Thread Tobias Diedrich
If you want to poke at the ramips ethernet driver, I have a patch that I haven't submitted yet (I think it has occasional problems on bootup and probably unconditionally uses features that are not available on all chipset types): This adds support for HW checksumming, scatter/gather DMA and generi

Re: [OpenWrt-Devel] WMAC LED Problems

2012-08-02 Thread LEO Airwarosu Yoichi Shinoda
On 2012/08/01, at 15:45, LEO Airwarosu Yoichi Shinoda wrote: > WZR-HP-AG300H > - Current /etc/diag.sh does not support boot/init progress > indication. > > - Wmac leds REQUIRES phy initialization (by means of wifi > command execution) to start working. After the first > phy initialization, the

Re: [OpenWrt-Devel] WMAC LED Problems

2012-08-02 Thread LEO Airwarosu Yoichi Shinoda
Andy, On 2012/08/02, at 23:37, Andy Botting wrote: > Hi Shinoda, > >> - I wonder if other non-buffalo units with wmac leds are dealing >> with the problem. > > I've just recently bought the Buffalo WBMR-HP-G300H and it doesn't > seem to have any power/status LEDs on startup. I didn't have any

Re: [OpenWrt-Devel] Make UCI support for other software?

2012-08-02 Thread Ryan Nowakowski
On Thu, Aug 02, 2012 at 05:32:51PM +0700, Nguyễn Hồng Quân wrote: > To make a software use UCI for configuration instead of its own > config, what do we have to do? Do we change in that software source > code or UCI source code? > > For example, I want to make UCI setting for WifiDog. Many package

Re: [OpenWrt-Devel] WMAC LED Problems

2012-08-02 Thread Peter Naulls
On 08/01/2012 09:03 PM, LEO Airwarosu Yoichi Shinoda wrote: On 2012/08/01, at 22:39, Peter Naulls wrote: The problem here is that the LED handling is done in the wrong order. I submitted a fix/patch(?) for this months ago, but it seems to have been ignored or lost. I can dig it out again - th

Re: [OpenWrt-Devel] WMAC LED Problems

2012-08-02 Thread Andy Botting
Hi Shinoda, > - I wonder if other non-buffalo units with wmac leds are dealing > with the problem. I've just recently bought the Buffalo WBMR-HP-G300H and it doesn't seem to have any power/status LEDs on startup. I didn't have any LEDs at all until I set them up myself. I'm not sure if it's th

Re: [OpenWrt-Devel] [PATCH] Codel: avoid a nul rec_inv_sqrt

2012-08-02 Thread John Crispin
On 31/07/12 23:19, Dave Taht wrote: > One condition before codel_Newton_step() was not good if > we never left the dropping state for a flow. As a result > rec_inv_sqrt was 0, instead of the ~0 initial value. > > codel control law was then set to a very aggressive mode, dropping > many packets bef

[OpenWrt-Devel] Make UCI support for other software?

2012-08-02 Thread Nguyễn Hồng Quân
Hello To make a software use UCI for configuration instead of its own config, what do we have to do? Do we change in that software source code or UCI source code? For example, I want to make UCI setting for WifiDog. Also, is there documentation about using C API of libuci? I searched but fo

Re: [OpenWrt-Devel] Linux 3.3.x has been EOLed ; time to move on ?

2012-08-02 Thread John Crispin
Hi, due to several devs being on vacation atm I will keep this short. We will drop a more complete statement start of next week. 3.3 was mainly chosen to get access to the bufferbloat related fixes. The intent was to use this for the upcoming AA release. We hope to push AA rather soon. Currently

Re: [OpenWrt-Devel] Linux 3.3.x has been EOLed ; time to move on ?

2012-08-02 Thread Emmanuel Deloget
Le 01/08/2012 16:51, Weedy a écrit : > On 01/08/12 04:57 AM, Emmanuel Deloget wrote: >> Hello, >> >> I understand that a lot of effort has been pushed in making >> Linux 3.3 the trunk kernel, and I understand that I probably >> missed long (IRC?) discussions on this very subject, but since >> 3