Russell Senior [2021-05-25 04:06:30]:
Hi,
> Looking closer, I realize that the mtd-mac-address line isn't even
> needed, since it will inherit it from the included
> ar9342_ubnt_xw.dtsi.
>
> I took a swing at replacing mtd-mac-address with nvmem-cells as in
> your example, but I got an
When support for Luma WRTQ-329ACN was added, the instructions for
flashing this device include using tools from uboot-envtools package.
Unfortunately the OpenWrt buildroot system omits packages from
DEVICE_PACKAGES when CONFIG_TARGET_MULTI_PROFILE,
CONFIG_TARGET_PER_DEVICE_ROOTFS,
Hi.
W dniu 25.05.2021 o 10:22, Daniel Golle pisze:
> Hi!
>
> thank you for submitting support for this interesting hardware.
> There are some minor style issues which need to be addressed before
> the patch can be merged into our tree.
> It would also be better to split this into at least two
I'd like to abort uclient connection after getting HTTP error code in a
response header.
Example:
static void foo_header_done_cb(struct uclient *cl)
{
if (cl->status_code != 200) {
uclient_disconnect(cl);
uclient_free(cl);
}
}
The problem is that
On 23.05.2021 13:59, Russell Senior wrote:
+ {
+ status = "okay";
+
+ /* default for ar934x, except for 1000M and 10M */
+ pll-data = <0x0200 0x0101 0x1313>;
+
+ mtd-mac-address = < 0x0>;
I'd love to have new DTS use upstream "nvmem-cells" property for that
On Tue, May 25, 2021 at 2:33 AM Russell Senior
wrote:
>
> On Tue, May 25, 2021 at 1:40 AM Rafał Miłecki wrote:
> >
> > On 23.05.2021 13:59, Russell Senior wrote:
> > > + {
> > > + status = "okay";
> > > +
> > > + /* default for ar934x, except for 1000M and 10M */
> > > + pll-data =
This patch has been added with initial support for ESPRESSObin board and
mistakenly it affects all boards with this SoC. Drop this patch since
the aliases are now in upstream dts for ESPRESSObin. If any boards are
relying on this, please add the respective alias to that board dts.
Signed-off-by:
On 2021-05-24 15:35, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Interfaces need to be assigned to devices. For that purpose a "device"
> option should be more accurate than "ifname" one.
>
> For backward compatibility add a temporary config translation.
>
> Config example:
>
> config
On Tue, May 25, 2021 at 3:33 AM Vincent Wiemann
wrote:
>
> On 5/25/21 2:23 AM, Russell Senior wrote:
> > On Mon, May 24, 2021 at 2:51 AM Vincent Wiemann
> > wrote:
> >>
> >> Hi Russel,
> >>
> >> On 5/24/21 1:06 AM, Russell Senior wrote:
> >>> On the PowerBeam M2 (PBE-M2-400) I see "e2 c2" in the
On Tue, May 25, 2021 at 1:40 AM Rafał Miłecki wrote:
>
> On 23.05.2021 13:59, Russell Senior wrote:
> > + {
> > + status = "okay";
> > +
> > + /* default for ar934x, except for 1000M and 10M */
> > + pll-data = <0x0200 0x0101 0x1313>;
> > +
> > + mtd-mac-address = <
On Tue, May 25, 2021 at 3:57 AM Russell Senior
wrote:
>
> On Tue, May 25, 2021 at 3:33 AM Vincent Wiemann
> wrote:
> >
> > On 5/25/21 2:23 AM, Russell Senior wrote:
> > > On Mon, May 24, 2021 at 2:51 AM Vincent Wiemann
> > > wrote:
> > >>
> > >> Hi Russel,
> > >>
> > >> On 5/24/21 1:06 AM,
On 5/25/21 2:23 AM, Russell Senior wrote:
On Mon, May 24, 2021 at 2:51 AM Vincent Wiemann
wrote:
Hi Russel,
On 5/24/21 1:06 AM, Russell Senior wrote:
On the PowerBeam M2 (PBE-M2-400) I see "e2 c2" in the same locations, not "e6
c2".
That's very interesting... I think the PowerBeam 400
From: Rafał Miłecki
Interfaces need to be assigned to devices. For that purpose a "device"
option should be more accurate than "ifname" one.
For backward compatibility old option remains supported too.
Config example:
config device
option name 'br-lan'
option type 'bridge'
Hi,
I'm thinking about something like (taken from my home router):
config route
option target '103.136.220.0/22'
option interface 'wan'
option type 'blackhole'
config route
option target '103.123.116.0/22'
option interface 'wan'
option type
14 matches
Mail list logo
