Hello Piotr,
On 25/03/2017 23:12:58 CET, Piotr Dymacz wrote:
> Hello Vittorio,
>
> On 25.03.2017 18:08, Vittorio Gambaletta (VittGam) wrote:
>> This router has the same hardware of TP-LINK TL-WR841N v11 (same
>> FCC ID, same TFTP image name...).
>>
>> The stock firmware web interface does not see
Hello,
On 25/03/2017 23:36:03 CET, Mathias Kresin wrote:
> 25.03.2017 18:08, Vittorio Gambaletta (VittGam):
>> Backported from Code Aurora QSDK
>>
>> Signed-off-by: Vittorio Gambaletta
>
> Please describe in the commit message what kind of issues need a
> workaround. Yes, I noticed the comments
This router has the same hardware of TP-LINK TL-WR841N v11 (same
FCC ID, same TFTP image name...).
The stock firmware web interface does not seem to accept the LEDE
factory image, but it can be flashed via the u-boot TFTP recovery
by long-pressing the reset button after power on.
The TFTP image n
RGMII RX delay setting needs to be always specified for AR8337 to
avoid port 5 RX hang on high traffic / flood conditions.
Also, the HOL registers that set per-port and per-packet-priority
buffer sizes are updated with the reduced values suggested by the
QCA switch team.
Finally, AR8327 reserved
On Mon, Mar 20, 2017 at 3:08 PM, Alexandru Ardelean
wrote:
> From: Alexandru Ardelean
>
> The context is that we generate some of the UCI config
> for netifd via scripts/programs.
>
> Every once in a while, there's a goof when doing that
> UCI generation, and netifd prints out the error at
> stde
On Sun, Mar 26, 2017 at 7:06 PM, Hans Dedecker wrote:
> On Mon, Mar 20, 2017 at 3:08 PM, Alexandru Ardelean
> wrote:
>> From: Alexandru Ardelean
>>
>> The context is that we generate some of the UCI config
>> for netifd via scripts/programs.
>>
>> Every once in a while, there's a goof when doing
On Sun, Mar 26, 2017 at 6:21 PM, Alexandru Ardelean
wrote:
> On Sun, Mar 26, 2017 at 7:06 PM, Hans Dedecker wrote:
>> On Mon, Mar 20, 2017 at 3:08 PM, Alexandru Ardelean
>> wrote:
>>> From: Alexandru Ardelean
>>>
>>> The context is that we generate some of the UCI config
>>> for netifd via scri
On Sun, Mar 26, 2017 at 7:38 PM, Hans Dedecker wrote:
> On Sun, Mar 26, 2017 at 6:21 PM, Alexandru Ardelean
> wrote:
>> On Sun, Mar 26, 2017 at 7:06 PM, Hans Dedecker wrote:
>>> On Mon, Mar 20, 2017 at 3:08 PM, Alexandru Ardelean
>>> wrote:
From: Alexandru Ardelean
The context i
On Sun, Mar 26, 2017 at 6:45 PM, Alexandru Ardelean
wrote:
> On Sun, Mar 26, 2017 at 7:38 PM, Hans Dedecker wrote:
>> On Sun, Mar 26, 2017 at 6:21 PM, Alexandru Ardelean
>> wrote:
>>> On Sun, Mar 26, 2017 at 7:06 PM, Hans Dedecker wrote:
On Mon, Mar 20, 2017 at 3:08 PM, Alexandru Ardelean
The context is that we generate some of the UCI config
for netifd via scripts/programs.
Every once in a while, there's a goof when doing that
UCI generation, and netifd prints out the error at
stderr, but returns 0 (success) err-code.
This change will fail the ubus call if UCI config
is invalid o
The patch prefers tmpfs over ramfs adjusting the code to comply with
the kernel docs. Details:
ramfs and tmpfs:
One downside of ramfs is you can keep writing data into it until you
fill up all memory, and the VM can't free it because the VM thinks that
files should get written to
11 matches
Mail list logo
