On 11/12/2015 15:02:43 CET, John Crispin wrote:
On 11/12/2015 14:48, Vittorio G (VittGam) wrote:
We cannot use board.json data here: this code is called before mounting
the rootfs, in the preinit.
we can. i just spoke with jow and we will add a codepath to failsafe to
probe board.json
Is thi
On 11/12/2015 14:48, Vittorio G (VittGam) wrote:
> Hi,
>
> On 11/12/2015 14:32:45 CET, John Crispin wrote:
>> hardcoding the board id here is not a good idea. we should rather use
>> the board.json data to probe if a switch is registered. if not we dont
>> apply the hack. i'll ask jow to tell us
Hi,
On 11/12/2015 14:32:45 CET, John Crispin wrote:
hardcoding the board id here is not a good idea. we should rather use
the board.json data to probe if a switch is registered. if not we dont
apply the hack. i'll ask jow to tell us how to probe for a switch.
We cannot use board.json data here
On 05/12/2015 12:04, Vittorio G (VittGam) wrote:
> The failsafe VLAN workaround is not needed on HT-TM02 (RT5350); it actually
> breaks
> failsafe since this router has only one port and it is 4 and not 0.
>
> Anyway, it seems that the workaround is still needed for other routers (see
> https:/
The failsafe VLAN workaround is not needed on HT-TM02 (RT5350); it actually
breaks
failsafe since this router has only one port and it is 4 and not 0.
Anyway, it seems that the workaround is still needed for other routers (see
https://patchwork.ozlabs.org/patch/424017/ for a previous attempt at r
