Buffer manager (BM) is a dedicated hardware unit that can be used by all
ethernet ports of Armada XP and 38x SoC's. It allows to offload CPU on RX
path by sparing DRAM access on refilling buffer pool, hardware-based
filling of descriptor ring data and better memory utilization due to HW
arbitration
Buffer manager (BM) is a dedicated hardware unit that can be used by all
ethernet ports of Armada XP and 38x SoC's. It allows to offload CPU on RX
path by sparing DRAM access on refilling buffer pool, hardware-based
filling of descriptor ring data and better memory utilization due to HW
arbitration
This change switches ARC tools to the most recent arc-2016.03
version.
ARC GNU tools of version arc-2016.03 bring some quite significant
changes like:
* Binutils v2.26+ (upstream commit id 202ac19 with additional ARC
* patches)
* GCC v4.8.5
* GDB 7.10
More about changes, improvements and fixe
When the IP_MULTICAST_LOOP/IPV6_MULTICAST_LOOP socket options are not enabled,
locally generated queries are ignored by mdnsd; This prevents local
applications from being able to discover locally published services.
Signed-off-by: Eyal Birger
---
interface.c | 8
1 file changed, 4 inser
Hi all!
prpl Foundation has made the invitation to propose OpenWrt enhancement
ideas which may end up funded by the same organization [1]. With this
email I'm offering to prpl Foundation to fund Rocket CWMP project -
which is the client implementation of CWMP / TR-069 protocol. Since this
is a goo
On Wed, May 18, 2016 at 01:19:59PM +0200, Mathias Kresin wrote:
> But I need to identify the boot_sel pins first. I have looked at it
> only briefly and was only able to identify one of the boot_sel pins:
> R77. Unfortunately this pin alone doesn't switch the SoC to UART mode.
> Did you found alrea
Dear list members,
I'm coming to you with an installation problem on my brand new Linksys
E1700 devices, but I think this is the right forum for this. Also
because the WIKI entries for the E1700 router tells to report a working
device - which unfortunately is not the case...
I tried it with uploa
This patch adds a reply to the file write ubus call:
{
"code": 0,
"bytes": 9
}
Where code is the return code of the operation and bytes is the number of
bytes written.
Getting a response is helpful since it lets the user know if the write
operation was successful, knowing the number of bytes writ
On 2016-05-18 15:59, Alexey Brodkin wrote:
> Hi Felix,
>
> On Wed, 2016-05-18 at 15:49 +0200, Felix Fietkau wrote:
>> On 2016-05-18 15:06, Alexey Brodkin wrote:
>> >
>> > Hi Felix,
>> >
>> > On Wed, 2016-05-18 at 14:57 +0200, Felix Fietkau wrote:
>> > >
>> > > On 2016-05-16 16:42, Alexey Brodki
Hi Felix,
On Wed, 2016-05-18 at 15:49 +0200, Felix Fietkau wrote:
> On 2016-05-18 15:06, Alexey Brodkin wrote:
> >
> > Hi Felix,
> >
> > On Wed, 2016-05-18 at 14:57 +0200, Felix Fietkau wrote:
> > >
> > > On 2016-05-16 16:42, Alexey Brodkin wrote:
> > > >
> > > >
> > > > If an image gets buil
On 2016-05-18 15:06, Alexey Brodkin wrote:
> Hi Felix,
>
> On Wed, 2016-05-18 at 14:57 +0200, Felix Fietkau wrote:
>> On 2016-05-16 16:42, Alexey Brodkin wrote:
>> >
>> > If an image gets built as an Elf there's a chance
>> > it will be used by developers for debugging purposes.
>> > In that case
Hi Felix,
On Wed, 2016-05-18 at 14:57 +0200, Felix Fietkau wrote:
> On 2016-05-16 16:42, Alexey Brodkin wrote:
> >
> > If an image gets built as an Elf there's a chance
> > it will be used by developers for debugging purposes.
> > In that case it's very helpful to keep debugging info
> > in that
On 2016-05-16 16:42, Alexey Brodkin wrote:
> If an image gets built as an Elf there's a chance
> it will be used by developers for debugging purposes.
> In that case it's very helpful to keep debugging info
> in that image.
>
> I would think that most OWRT-powered devices in production
> will use
I got the same device last Weekend and planned to add support for this
device during the next days. Glad to see that most of the work is
already done.
Find my remarks in-line.
2016-05-18 9:37 GMT+02:00 Oswald Buddenhagen :
> Ethernet, WiFi, ADSL2+, and LEDS are fully functional.
>
> The RFkill sw
On Wed, May 18, 2016 at 9:54 AM, Ben Mulvihill wrote:
> On Wed, 2016-05-18 at 09:39 +0200, Oswald Buddenhagen wrote:
>> - NAND/UBI support is completely irrelevant for my box, and for
>> lantiq/Danube in general (IIRC). It appears to me that it would make
>> sense to split it off from the xway
Hi Oswald,
On Wed, 2016-05-18 at 09:39 +0200, Oswald Buddenhagen wrote:
> - NAND/UBI support is completely irrelevant for my box, and for
> lantiq/Danube in general (IIRC). It appears to me that it would make
> sense to split it off from the xway target.
NAND/UBI is required on BTHOMEHUB2B (x
There is no such property. It was probably meant as the counterpart
to lantiq,external-clock, but the internal clock always exists anyway.
Signed-off-by: Oswald Buddenhagen
---
target/linux/lantiq/dts/ARV4518PWR01.dts | 8
target/linux/lantiq/dts/GIGASX76X.dts| 1 -
2 files changed,
Signed-off-by: Oswald Buddenhagen
---
target/linux/lantiq/dts/FRITZ7320.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/lantiq/dts/FRITZ7320.dts
b/target/linux/lantiq/dts/FRITZ7320.dts
index 475da7a..04581c5 100644
--- a/target/linux/lantiq/dts/FRITZ7320.dts
+++ b/target/linu
They clearly are meant to be, and the bootloader (presumably) sets them
up accordingly, but it's nicer to state it explicitly in the DT.
Entirely untested.
Signed-off-by: Oswald Buddenhagen
---
target/linux/lantiq/dts/ARV4520PW.dts| 1 +
target/linux/lantiq/dts/BTHOMEHUBV2B.dts | 1 +
targe
This property makes no sense for inputs.
Or maybe it does? the lantiq,output devicetree mapping is undocumented,
and consequently its relationship with lantiq,open-drain. So i can't
preclude the possibility that there is an unexpected relation ...
Signed-off-by: Oswald Buddenhagen
---
target/li
- NAND/UBI support is completely irrelevant for my box, and for
lantiq/Danube in general (IIRC). It appears to me that it would make
sense to split it off from the xway target.
- My box has no USB port and no other sensible option to connect
mass storage devices, so anything related to that m
Ethernet, WiFi, ADSL2+, and LEDS are fully functional.
The RFkill switch doesn't appear to be correctly configured.
Supporting the two TAE ports and SIP gateway was not attempted.
The firmware image needs to be kept below ~3.6MiB due to brnboot's dual
image magic. This is just enough for the abo
22 matches
Mail list logo
