Hi,
Thank you for your advices. I will submit patch again.
Best wishes
Robinson Wu___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> -Original Message-
> From: Tom Psyborg [mailto:pozega.tomis...@gmail.com]
> Sent: Mittwoch, 7. August 2019 23:19
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 2/3] ath79: fix IMAGE_SIZE for
> common TP-Link definitions
>
> Correct me
Correct me if I'm wrong but I thought all the data beyond IMAGE_SIZE
remain intact by OpenWrt on firstboot. Experimenting with Archer C7 v1
recently I was able to flash OpenWrt image (ar71xx) and after
reflashing tplink fw previous settings were still valid indicating
config partition hasn't been o
Add support for the ar71xx supported Netgear WNDR3800CH to ath79.
The device is identical to WNDR3800 except NETGEAR_BOARD_ID.
Signed-off-by: Dmitry Tunin
---
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 6 ++--
.../linux/ath79
Oops again. I didn't pull master for a while, because was playing with 19.07.
ср, 7 авг. 2019 г. в 22:58, Dmitry Tunin :
>
> > Are you using recent master?
> >
> > DEVICE_MODEL is the way to go now.
> Yes, I do.
___
openwrt-devel mailing list
openwrt-de
> Are you using recent master?
>
> DEVICE_MODEL is the way to go now.
Yes, I do.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Are you using recent master?
DEVICE_MODEL is the way to go now.
> -Original Message-
> From: Dmitry Tunin [mailto:hanipouspi...@gmail.com]
> Sent: Mittwoch, 7. August 2019 21:27
> To: Adrian Schmutzler
> Cc: OpenWrt Development List
> Subject: Re: [OpenWrt-Devel] [PATCH] ath79: add supp
Add support for the ar71xx supported Netgear WNDR3800CH to ath79.
The device is identical to WNDR3800 except NETGEAR_BOARD_ID.
Signed-off-by: Dmitry Tunin
---
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 6 ++--
.../linux/ath79
Add support for the ar71xx supported Netgear WNDR3800CH to ath79.
The device is identical to WNDR3800 except NETGEAR_BOARD_ID.
Signed-off-by: Dmitry Tunin
---
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 6 ++--
.../linux/ath79
With VENDOR/MODEL it doesn't appear in menuconfig.
So v1 with WNDR fix should work.
ср, 7 авг. 2019 г. в 22:11, Dmitry Tunin :
>
> > You still have one WNR in the commit description and you can remove the
> > DEVICE_VENDOR, as it is still inherited.
> It looks like all the file should be changed
Add support for the ar71xx supported Netgear WNDR3800CH to ath79.
The device is identical to WNDR3800 except NETGEAR_BOARD_ID.
Signed-off-by: Dmitry Tunin
---
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 6 ++--
.../linux/ath79
> You still have one WNR in the commit description and you can remove the
> DEVICE_VENDOR, as it is still inherited.
It looks like all the file should be changed to VENDOR/MODEL, but you
are correct.
___
openwrt-devel mailing list
openwrt-devel@lists.op
> CH is used in BOARD_ID.
Ah, I see. I'm fine with the solution in v2.
You still have one WNR in the commit description and you can remove the
DEVICE_VENDOR, as it is still inherited.
Best
Adrian
openpgp-digital-signature.asc
Description: PGP signature
___
> If the CH stands for China, as I've also read when googleing, I would prefer
> having CN here. This will then very much depend upon whether the CH is used
> officially somewhere or whether it's just an invention of previous OpenWrt
> versions ... (Where in the latter case I'd actually change t
Sent v2.
ср, 7 авг. 2019 г. в 21:48, Adrian Schmutzler :
>
> > > Note that you also have to update to DEVICE_VENDOR/DEVICE_MODEL syntax ...
> > I don't quite get it. Where is this syntax?
>
> Here:
>
> > +define Device/netgear_wndr3800ch
> > + $(Device/netgear_wndr3800)
> > + DEVICE_TITLE := NET
Add support for the ar71xx supported Netgear WNR3800CH to ath79.
The device is identical to WNDR3800 except NETGEAR_BOARD_ID.
Signed-off-by: Dmitry Tunin
---
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 6 ++--
.../linux/ath79/
> Maybe DEVICE_VARIANT := CH is a better choice, since it is the same device.
Well, is it a variant? If yes, CH implies Switzerland to me, which most
probably is wrong.
Despite, if you decide to use CH as variant, you would have to introduce
hyphens to device definition name and compatible, i.e.
> > Note that you also have to update to DEVICE_VENDOR/DEVICE_MODEL syntax ...
> I don't quite get it. Where is this syntax?
Here:
> +define Device/netgear_wndr3800ch
> + $(Device/netgear_wndr3800)
> + DEVICE_TITLE := NETGEAR WNDR3800 (Ch)
> + NETGEAR_BOARD_ID := WNDR3800CH
> + SUPPORTED_DEVI
Maybe DEVICE_VARIANT := CH is a better choice, since it is the same device.
ср, 7 авг. 2019 г. в 21:40, Dmitry Tunin :
>
> > in commit title/description, you are using "WNR" instead of "WNDR" ...
> Oops.
>
> > Despite, from a quick research, it looks like the device is called
> > "WNDR3800CH" mos
> in commit title/description, you are using "WNR" instead of "WNDR" ...
Oops.
> Despite, from a quick research, it looks like the device is called
> "WNDR3800CH" most frequently.
> I would update the name accordingly.
I copied the ar71xx name, but I agree.
> Note that you also have to update to
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Dmitry Tunin
> Sent: Mittwoch, 7. August 2019 19:55
> To: openwrt-devel@lists.openwrt.org
> Cc: Dmitry Tunin
> Subject: [OpenWrt-Devel] [PATCH] ath79: add support of Netgear WNR
Add support for the ar71xx supported Netgear WNR3800 (Ch) to ath79.
The device is identical to WNR3800 except NETGEAR_BOARD_ID.
Signed-off-by: Dmitry Tunin
---
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 6 ++--
.../linux/ath7
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Tom Psyborg
> Sent: Mittwoch, 7. August 2019 17:58
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 2/3] ath79: fix IMAGE_SIZE for
Hi
Looks like there were many doubts about image size over the years.
One thing that should be considered is use of OEM firmware, either in
case of just a single revert after OpenWrt flashing, or multiple
reverts/switching between OEM/OpenWrt firmwares.
Relevant in this case is config partition
Hi,
> + lna0 {
is there a scheme for proper names already?
While I do not have an opinion for lnaX, I'd prefer "usb_power"/"usb0_power"
over just "usb"/"usb0".
> + gpio-hog;
> + line-name = "tp-link:ext:lna0";
> + gpios = <18 GPIO_ACTIVE_HIGH>;
At least for lnaX, so fa
Hi Petr,
Le jeu. 1 août 2019 à 12:51, Etienne Champetier
a écrit :
>
> Hi Petr,
>
> Le jeu. 1 août 2019 à 11:39, Petr Štetiar a écrit :
> >
> > Etienne Champetier [2019-08-01 07:23:18]:
> >
> > > If the fix was to workaround a client bug we might want to keep it,
> >
> > Actually we don't know
> Hi,
> I decided to put it here as USB is controlled by pin 4 of wireless chip
> not CPU. If there is another better formal way to define it, please let
> me know. I've analyzed gpio_hog patch for other dts files but all these
> routers steer USB via GPIO pins connected to main SoC.
> Cheers
Hi,
> I would like to know how the patch I submitted is going? Should I submit it
> again?
I’m only a developer, too, so I cannot speak with authority and also cannot
push this forward myself.
If you ask for my _opinion_, I’d send a v2 with the RAM-removal renames (as
this introduces several
Hi Adrian,
I would like to know how the patch I submitted is going? Should I submit it
again? Or will you help me to fix it? Please tell me what should I do.
Best wishes
Robinson Wu___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://
On Mon, Aug 5, 2019 at 6:09 PM Paul Spooren wrote:
>
> Applies patch from @mikma [0] to fix Docker shutdown. Added detection to
> state.c if running in a containre or not.
>
> Tested with a x86/64 Docker image.
>
> Fixes FS#2425
>
> CC: Mikael Magnusson
> CC: Petr Štetiar
>
> [0]:
> https://git
We are not sure if 640-bridge-only-accept-EAP-locally.patch is still needed
as a first step, add disable_eap_hack sysfs config to allow to disable it
Signed-off-by: Etienne Champetier
---
.../640-bridge-only-accept-EAP-locally.patch | 59 +--
.../640-bridge-only-accept-EAP-local
Please ignore this. I was terribly wrong. There is a regression, but
it is related to the specific USB device and not to the Mamba system or
the EJ168 xhci controller. The USB3 port on Mamba is working fine with
other USB devices.
Sorry for the noise. I was confused by all the reports of failin
32 matches
Mail list logo
