Hi everybody,
Buildbot had some issue with mpc85xx/p1010 subtarget:
https://buildbot.openwrt.org/images/#/builders/231
It looks like only `osuosl-vm5-dock-02` can build this subtarget.
Could someone look at this issue?
Best regards,
Pawel Dembicki
___
; >
> > Hello Paweł,
> > I can see it now. It applies foo me but I get whitespace warning and you
> > get an error. Porbably git settings. I will try to fix this and send V2.
> > Best Regards,
> > Wojciech Dubowik
> >
> I really have problems telling git that
_swap-host-bui.patch:26
error:
package/boot/tfa-layerscape/patches/003-plat-nxp-tools-fix-create_pbl-and-byte_swap-host-bui.patch:
patch does not apply
Patch failed at 0001 tfa-layerscape: Bump to lf-6.1.1-1.0.0 and switch to github
--
Best Regards,
Paweł Dembicki
__
Hi everybody,
I am preparing support for the T4240RDB board. But I'm stuck with one problem:
Qoriq target is powerpc64. But T4240RDB in u-boot is supported as
mpc85xx family and requires a 32-bit compiler.
I tried setting OpenWrt config: EXTRA_TARGET_ARCH to y and
EXTRA_TARGET_ARCH_NAME to pow
pt., 8 paź 2021 o 11:16 Paul Spooren napisał(a):
>
> Hi,
>
Hi Paul
> --- %< ---
> >
> > based on my overview[1] things are moving forward and being tested,
> > great! What about the targets that did not see any 5.10 ambitions
> > yet?
> > Specifically:
> >
> > - arc770
> >
czw., 9 wrz 2021 o 10:49 Rui Salvaterra napisał(a):
>
> Tested on mt7621 (Redmi AC2100) and running stable for several months.
>
Hi Rui,
Please remember, if this patch will be merged before my PR #4255 [1],
all mt7620 JBOOT devices will be broken.
The reason is simple: The 5.10 kernel will be >
pt., 1 sty 2021 o 12:09 Hannu Nyman napisał(a):
>
> Paweł Dembicki kirjoitti 31.12.2020 klo 23.42:
> >
> > Thanks Hannu for the inspection. It was a great job. Kconfig entry was
> > misplaced after rebase in the early stage of my work.
> >
> > I moved it to the
czw., 31 gru 2020 o 16:51 Adrian Schmutzler
napisał(a):
>
> Hi,
>
Hi all,
> Pawel hasn't been in the recipients list, so I added him:
>
> @Pawel: If you haven't followed the thread via openwrt-devel anyway, you
> should definitely have a look, particularly at the latest findings by Hannu
> (be
On 03.09.2020 at 03:35 Raylynn Knight via openwrt-devel
wrote:
>
> Since I chose the ZyXel NSA320 as my first device I think it best to follow
> your example for consistency on the ZyXel NAS devices. My follow up support
> will likely be for the 3 different Netgear NAS devices I have.
>
If yo
niedz., 14 cze 2020 o 22:12 napisał(a):
>
> Hi,
>
> > > + SUPPORTED_DEVICES += linksys,audi
> >
> > You didn't add "SUPPORTED_DEVICES" in mvebu. After movement to DSA,
> > images have broken config after sysupgrade. Maybe at this moment drop
> > this line?
>
> Hmm, adding support for DSA has been
sob., 13 cze 2020 o 22:09 Adrian Schmutzler
napisał(a):
>
Hi Adrian,
> This replaces the internal device names "Audi" and "Viper" with the
> real model names, which a user would look for. This makes the
> Linksys devices on this target consistent with the names recently
> changed for mvebu based
On 04.062020 at 09:58 Adrian Schmutzler wrote:
>
> Hi,
>
Hi Adrian,
> we regularly encounter the situation that devices are subject to changes
> that will make them incompatible to previous versions.
> Removing SUPPORTED_DEVICES will not really be helpful in most of these
> cases, as this only h
On 18.05.2020 at 03:46 Raylynn Knight wrote:
>
> I have two of these devices. One with Wifi and one without. I’d like to
> test with your patch, but step 2 is:
>
> Step two -> Use kwboot tool to upload openwrt u-boot to RAM:
>
> Where can I find the appropriate patch for u-boot?
Every patches
On 21.04.2020 at 07:20 Pawel Dembicki wrote:
>
> Hi everybody,
>
> sometime ago I sent github PR[1] with support for Check Point L-50.
>
> Could someone take a look at this and review it?
>
> [1] https://github.com/openwrt/openwrt/pull/2719
>
Anyone?
Adrian helped me with a lot, but He need someo
On 20.04.2020 at 21:42 wrote:
>
> Please share your thoughts.
>
I think about it.
My proposal:
Three steps of convention:
1. Use name from device, when is described at chassis.
2. Use variant "2", when ports have only numbers. lanX, where X is
number from chassis.
3. Use natural port numeration f
Hi everybody,
sometime ago I sent github PR[1] with support for Check Point L-50.
Could someone take a look at this and review it?
[1] https://github.com/openwrt/openwrt/pull/2719
Regards,
Pawel Dembicki
___
openwrt-devel mailing list
openwrt-devel@l
Hi everybody,
sometime ago I sent github PR[1] with support for D-Link DWR-960.
I prepared patch for mt7620, which add rgmii delays setting
possibility. Could someone take a look at this and review it?
[1] https://github.com/openwrt/openwrt/pull/2857
Regards,
Pawel Dembicki
___
sob., 7 mar 2020 o 22:55 Enrico Mioso napisał(a):
>
> Hello guys! May I ask for an amazon link where I may buy the ramips-based
> NETGEAR R6700v2/AC2400 device added in
> 6e80df5e3344092a391468b1718e412f0dd151c1 ?
>
Hi!
Netgear R6700v2 and AC2400 are clones. R6800 have additional USB 2.0 port.
> On Fri, Jul 19, 2019 at 09:51 Linus Walleij wrote:
>
> > I think, that the best approach is vlan filtering. I started some work:
> > https://github.com/CHKDSK88/linux/commit/38b62482d9f828b5720db11145fa474e368b248c
>
> Hey! I wanted to do that but never had time,
> so very happy that you're fix
On Sun, Jul 14, 2019 at 23:12 Linus Walleij wrote:
>
>
> I don't know if there is any better way to fix it?
>
I think, that the best approach is vlan filtering. I started some work:
https://github.com/CHKDSK88/linux/commit/38b62482d9f828b5720db11145fa474e368b248c
At this moment it works (I used
20 matches
Mail list logo
