On Sun, Mar 31, 2019 at 11:49 PM Lorenzo Bianconi
wrote:
>
> >
> > On Sun, Mar 31, 2019 at 12:15 PM Lorenzo Bianconi
> > wrote:
> > >
> > > >
> > > > On Sun, Mar 31, 2019 at 6:45 AM Lorenzo Bianconi
> > > > wrote:
> > > > >
> > > > > >
> > > > > > bump.
> > > > >
> > > > > Hi Joe,
> > > > >
> >
Tom Psyborg, check the bottom of this mail, it has the patch in it.
Thanks,
Ben
On 03/25/2019 02:34 PM, Michał Kazior wrote:
On Mon, 25 Mar 2019 at 21:23, Ben Greear wrote:
On 3/25/19 1:08 PM, Michał Kazior wrote:
On Mon, 25 Mar 2019 at 16:55, Ben Greear wrote:
On 3/25/19 5:14 AM, Michał
On 01/04/2019, Ben Greear wrote:
>> please provide link. i did not get such patch in my inbox
>
> I forwarded it separately. If that fixes the problem, then I think it has
> a decent change of being accepted upstream (as well as into my ath10k-ct
> repo).
forwarded to where?!? i can't find it
markus.sche...@gmail.com [2019-03-21 16:43:27]:
Hi,
> + label = "ursus:green:wlan2";
> + label = "ursus:green:wlan5";
could we please make it wlan2g and wlan5g in order to stay consistent?
I found this old PR[1] for ar71xx, which makes me wonder if the
On 4/1/19 2:07 PM, Tom Psyborg wrote:
On 01/04/2019, Ben Greear wrote:
On 4/1/19 1:32 PM, Tomislav Požega wrote:
When chip reset is done before the chip is checked if supported
there will be crash. Previous behaviour caused bootloops on
Archer C7 v1 units, this patch allows clean device boot
On 01/04/2019, Ben Greear wrote:
> On 4/1/19 1:32 PM, Tomislav Požega wrote:
>> When chip reset is done before the chip is checked if supported
>> there will be crash. Previous behaviour caused bootloops on
>> Archer C7 v1 units, this patch allows clean device boot without
>> excluding ath10k
On 4/1/19 1:32 PM, Tomislav Požega wrote:
When chip reset is done before the chip is checked if supported
there will be crash. Previous behaviour caused bootloops on
Archer C7 v1 units, this patch allows clean device boot without
excluding ath10k driver.
Did you try the patch that Michal
When chip reset is done before the chip is checked if supported
there will be crash. Previous behaviour caused bootloops on
Archer C7 v1 units, this patch allows clean device boot without
excluding ath10k driver.
Signed-off-by: Tomislav Požega
---
Switch Archer C7 v1 back to regular ath10k driver and firmware
since it contains fix for bootloop issue present with
QCA9880-AR1A.
Signed-off-by: Tomislav Požega
---
target/linux/ath79/image/generic-tp-link.mk |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
This series patch fixes bootloop issue and device starts
normally with QCA9880-AR1A in mPCIe slot.
Another card tested is QCA9862 and is detected and starts
properly.
Signed-off-by: Tomislav Požega
---
target/linux/ar71xx/image/generic-tp-link.mk |2 +-
1 files changed, 1 insertions(+), 1
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/generic/config-4.19 | 1 +
target/linux/tegra/config-4.19| 558 ++
...interrupts-due-to-tegra2-silicon-bug.patch | 77 +++
...enable-front-panel-leds-in-TrimSlice.patch | 46 ++
4 files changed,
New target introduces initial support for NVIDIA Tegra SoC based devices.
It focuses on Tegra 2 CPUs, for successors supporting NEON instruction
set the target should be split in two subtargets.
This initial commit doesn't create any device image, it's groundwork
for further additions.
Tegra BCT and bootable flash image generator/compiler
>From documentation:
This project provides a tool which compiles BCT (Boot Configuration
Table) images to place into the boot flash of a Tegra-based device.
The tool will either:
a) Compile a textual representation of a BCT into a binary
Add U-Boot for NVIDIA Tegra based boards, with the first being CompuLab
TrimSlice. This is part of initial support for this board.
Signed-off-by: Tomasz Maciej Nowak
---
package/boot/uboot-tegra/Makefile | 64 +++
.../tegra/base-files/lib/upgrade/platform.sh | 2 +
Support for Microelectronic EM3027 real time clock chip.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/linux/modules/other.mk | 18 ++
1 file changed, 18 insertions(+)
diff --git a/package/kernel/linux/modules/other.mk
b/package/kernel/linux/modules/other.mk
index
This provides board configuraion tables for various Tegra boards needed
by cbootimage tool to create flashable bootloader images.
Signed-off-by: Tomasz Maciej Nowak
---
tools/Makefile| 2 +-
tools/cbootimage-configs/Makefile | 32 +++
2 files
It is a small form factor computer with rich amount of expansion ports.
Some hardware specs and supported features in this commit:
CPU: NVIDIA Tegra 2 @ 1GHz
RAM: 1GB DDR2-667
Storage: SDHC card slot
µSDHC card slot
USB to SATA bridge (depends on model)
1MB SPI NOR
This is continuation of effort in [1] PR to old LEDE source tree. It
received few improvement and some commits got split.
Main changes worth mentioning:
- update tools and U-Boot to recent versions,
- added support for 4.19 kernel
- now SD card image is also an rescue image with embedded U-Boot
-
qca8x DSA: Configured Switch Sends Packets Out Wrong Interface
Using qca8k and ipqess on an EA8300 (ipq40xx) under Linux 4.19 based
on patches from chunkeey's staging tree[1] as well as a patch to
resolve the NPE issue[2].
Once the switch has been configured (this is *after* the power-on
config
In case PROTO_CMD_SETUP cannot be handled due to an invalid state; return
-1 so the calling functions are aware the PROTO_CMD_SETUP has failed.
Signed-off-by: Hans Dedecker
---
V1 -> V2: Remove S_SETUP_ABORT, S_TEARDOWN and S_SETUP cases
proto-shell.c | 5 -
1 file changed, 5 deletions(-)
On Mon, Apr 1, 2019 at 11:25 AM Jo-Philipp Wich wrote:
>
> Hi,
>
> minor nitpick below
>
> On 4/1/19 10:34 AM, Hans Dedecker wrote:
> > In case PROTO_CMD_SETUP cannot be handled due to an invalid state; return
> > -1 so the calling functions are aware the PROTO_CMD_SETUP has failed.
> >
> >
On Mon, Apr 1, 2019 at 11:25 AM Jo-Philipp Wich wrote:
>
> Hi,
>
> minor nitpick below
>
> On 4/1/19 10:34 AM, Hans Dedecker wrote:
> > In case PROTO_CMD_SETUP cannot be handled due to an invalid state; return
> > -1 so the calling functions are aware the PROTO_CMD_SETUP has failed.
> >
> >
Jo-Philipp Wich [2019-04-01 11:18:55]:
> > Felix had a good point about sysupgrade, where we would needlesly write few
> > dozen MBs of 0s. In order to avoid that, I would simply add following qemu
> > variants to x86:
>
> I wonder what kind of storage media on x86 is so brittle that writing a
Hi,
minor nitpick below
On 4/1/19 10:34 AM, Hans Dedecker wrote:
> In case PROTO_CMD_SETUP cannot be handled due to an invalid state; return
> -1 so the calling functions are aware the PROTO_CMD_SETUP has failed.
>
> Signed-off-by: Hans Dedecker
> ---
> proto-shell.c | 2 --
> 1 file
Jo-Philipp Wich [2019-04-01 07:33:40]:
> Most other targets ship image artifacts which are usable ootb, requiring
> one extra step to pad the combined images is a waste of user resources
> every single time. It also causes recurring confusion among users
> wanting to use x86 builds
x86, armvirt
In case PROTO_CMD_SETUP cannot be handled due to an invalid state; return
-1 so the calling functions are aware the PROTO_CMD_SETUP has failed.
Signed-off-by: Hans Dedecker
---
proto-shell.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/proto-shell.c b/proto-shell.c
index
From: Hans dedecker
When launching PROTO_CMD_TEARDOWN in interface_check_state() the interface
was set in IFS_DOWN state. In case an interface is now brought into IFS_SETUP
state in __interface_set_up() it will launch PROTO_CMD_SETUP trying to
bring the proto shell handler in S_SETUP state which
On 31.03.19 15:45, Lorenzo Bianconi wrote:
could you please try to attached patch? The max distance the hw can
support depends of channel width:
e.g @20MHz (HT20, 5GHz)
max distance is ~ 61Km
@Koen: do you have any chance to test the attached patch in your
environment? Thx
Hi Lorenzo,
I
I have been busy on other stuff than embedded routing for quite some
time, but I'd like to start folding in some new stuff into openwrt
related to fq_codel starting in the next week or so (I am currently in
prague, heading to berlin next week) - with some new code that looks
quite promising in
Is now up here:
https://www.youtube.com/watch?v=y-7G2ItPwco=5m55
I was unaware of how far behind homenet had fallen on the openwrt
integration front until ted talked to me... and I then "threatened to
help". :P
The outline of all that remains in homenet left to do is in his talk.
>
> On Sun, Mar 31, 2019 at 12:15 PM Lorenzo Bianconi
> wrote:
> >
> > >
> > > On Sun, Mar 31, 2019 at 6:45 AM Lorenzo Bianconi
> > > wrote:
> > > >
> > > > >
> > > > > bump.
> > > >
> > > > Hi Joe,
> > > >
> > > > sorry for the delay
> > > >
> > > > >
> > > > > On Mon, Mar 18, 2019 at 10:59 PM
On Sun, Mar 31, 2019 at 12:15 PM Lorenzo Bianconi
wrote:
>
> >
> > On Sun, Mar 31, 2019 at 6:45 AM Lorenzo Bianconi
> > wrote:
> > >
> > > >
> > > > bump.
> > >
> > > Hi Joe,
> > >
> > > sorry for the delay
> > >
> > > >
> > > > On Mon, Mar 18, 2019 at 10:59 PM Joe Ayers wrote:
> > > >>
> > >
32 matches
Mail list logo
