Hi!
Sorry for the late reply.
On Wed, Jan 29, 2020 at 11:18 PM Piotr Dymacz wrote:
> AFAIK, there wasn't any official or general rule about what should be
> LAN and WAN (in terms of mapping ethX to 'our' LAN/WAN), so it was
> always up to the device support author (personally I preferred to have
Hi Adrian,
On 28.01.2020 16:59, Adrian Schmutzler wrote:
Hi,
There is easy way to check GMACx <> ethX assignment order in mach-*.c
files. Just check order of ath79_register_eth() calls:
ath79_register_eth(0);
ath79_register_eth(1);
Will register GMAC0 as eth0, GMAC1 as eth1
...@gmail.com;
ansuels...@gmail.com; 'David Bauer'
Subject: Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet
Hi Adrian,
On 27.01.2020 19:35, Adrian Schmutzler wrote:
> Just a quick one:
>
>> > So, no matter what we do, there is no easy way forward.
>>
>>
Hi Peter,
On 27.01.2020 22:05, Peter Geis wrote:
On Mon, Jan 27, 2020 at 4:00 PM Piotr Dymacz wrote:
[...]
But it's not a general rule and, at least in case of generic/basic
settings, user shouldn't be worried about upgrading between major
versions with preserving settings. Otherwise, the
Hi,
> (I should first say that I don't know enough about the ar71xx-ath79 migration
> to know if this idea will work, but I don't recall seeing it mentioned
> before.)
>
> What if we add a migration package for 18.06 that ar71xx users can opt-in and
> install, which (when the user initiates
On Tue, Jan 28, 2020 at 11:48 PM Adrian Schmutzler
wrote:
> I do not really see a viable/desirable option to support eth migration at
> the
> moment. And I'm not really a fan of adding lots of migration stuff which
> spoils
> the new ath79 target already, so after all I think I also do not
Hi,
> There is easy way to check GMACx <> ethX assignment order in mach-*.c
> files. Just check order of ath79_register_eth() calls:
>
> ath79_register_eth(0);
> ath79_register_eth(1);
>
> Will register GMAC0 as eth0, GMAC1 as eth1
>
> ath79_register_eth(1);
> ath79_register_eth(0);
>
> Will
ail.com; 'David Bauer'
> Subject: Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet
>
> Hi Adrian,
>
> On 27.01.2020 19:35, Adrian Schmutzler wrote:
> > Just a quick one:
> >
> >> > So, no matter what we do, there is no easy way forward.
> >&
On Mon, Jan 27, 2020 at 4:00 PM Piotr Dymacz wrote:
>
> Hi Peter,
>
> On 27.01.2020 19:57, Peter Geis wrote:
> > On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler
> > wrote:
> >>
> >> Just a quick one:
> >>
> >> > > So, no matter what we do, there is no easy way forward.
> >> >
> >> > We could
Hi Peter,
On 27.01.2020 19:57, Peter Geis wrote:
On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler
wrote:
Just a quick one:
> > So, no matter what we do, there is no easy way forward.
>
> We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
> board names from supported
Hi Adrian,
On 27.01.2020 19:35, Adrian Schmutzler wrote:
Just a quick one:
> So, no matter what we do, there is no easy way forward.
We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
board names from supported devices lists in ath79 images and make the
target a brand new,
On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler
wrote:
>
> Just a quick one:
>
> > > So, no matter what we do, there is no easy way forward.
> >
> > We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
> > board names from supported devices lists in ath79 images and make the
> >
Just a quick one:
> > So, no matter what we do, there is no easy way forward.
>
> We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
> board names from supported devices lists in ath79 images and make the
> target a brand new, without any concerns about soon-to-be obsolete
Hi Adrian,
On 21.01.2020 15:10, Adrian Schmutzler wrote:
[...]
I'm in the middle of migrating some devices from soon-to-be-obsolete
ar71xx to ath79 target and was wondering about status of the eth0/eth1
vs. LAN/WAN assignment issue.
To start with the end: I've decided to stop working on
n
> > Behalf Of Piotr Dymacz
> > Sent: Dienstag, 21. Januar 2020 00:34
> > To: m...@adrianschmutzler.de; 'David Bauer' ;
> > gch981...@gmail.com
> > Cc: openwrt-devel@lists.openwrt.org
> > Subject: Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet
> &g
wrt.org
> Subject: Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet
>
> Hi Adrian, David, Chuanhong,
>
> On 07.09.2019 12:15, m...@adrianschmutzler.de wrote:
> > Hi,
> >
> >> > However, this will obviously swap eth0/eth1 on EVERY upgrade, not ju
Hi Adrian, David, Chuanhong,
On 07.09.2019 12:15, m...@adrianschmutzler.de wrote:
Hi,
> However, this will obviously swap eth0/eth1 on EVERY upgrade, not just
when coming from ar71xx.
> So, does anyone have an idea how to limit this to run only when updated
from ar71xx?
I was thinking about
Hi,
> > However, this will obviously swap eth0/eth1 on EVERY upgrade, not just
> when coming from ar71xx.
> > So, does anyone have an idea how to limit this to run only when updated
> from ar71xx?
>
> I was thinking about the same. As we have no information about the
> previously installed
Hello Adrian,
On 9/5/19 5:00 PM, Adrian Schmutzler wrote:
> Hi,
>
> if I remember correctly, there is still no mechanism to fix eth0/eth1 for
> devices where those have been swapped from ar71xx to ath79.
>
> In principle, this can be done with a relatively small piece of code (not
> tested):
Hi,
if I remember correctly, there is still no mechanism to fix eth0/eth1 for
devices where those have been swapped from ar71xx to ath79.
In principle, this can be done with a relatively small piece of code (not
tested):
diff --git
20 matches
Mail list logo
