Hi,
> Le 21 janv. 2023 à 02:23, Christian Marangi a écrit :
>
> Yes CI test will catch that and will just fail. Now I think I have to
> ask someone to reboot buildbot again for the new subtarget... Or it will be
> picked automatically?
It needs a restart.
Cheers,
Thibaut
_
On Sat, Jan 21, 2023 at 02:23:08AM +0100, Christian Marangi wrote:
> On Fri, Jan 20, 2023 at 05:17:43PM -0800, Brian Norris wrote:
> > On Fri, Jan 20, 2023 at 6:11 AM Christian Marangi
> > wrote:
> > > added the changed to my staging repo and testing them here
> > > https://github.com/openwrt/ope
On Fri, Jan 20, 2023 at 05:17:43PM -0800, Brian Norris wrote:
> On Fri, Jan 20, 2023 at 6:11 AM Christian Marangi
> wrote:
> > added the changed to my staging repo and testing them here
> > https://github.com/openwrt/openwrt/pull/11843.
> >
> > Merged the fstools requirement. If CI tests doesn't
On Fri, Jan 20, 2023 at 6:11 AM Christian Marangi wrote:
> added the changed to my staging repo and testing them here
> https://github.com/openwrt/openwrt/pull/11843.
>
> Merged the fstools requirement. If CI tests doesn't have problems, i
> will merge this in master.
I see you've merged them to
On Thu, Jan 12, 2023 at 09:32:22PM -0800, Brian Norris wrote:
> TP-Link and ASUS OnHub devices are very similar, sharing many of the
> same characteristics and much of their Device Tree. They both run a
> version of ChromeOS for their factory firmware, and so installation
> instructions look very s
TP-Link and ASUS OnHub devices are very similar, sharing many of the
same characteristics and much of their Device Tree. They both run a
version of ChromeOS for their factory firmware, and so installation
instructions look very similar to Google Wifi [1].
Things I've tested, and are working:
* E
