On Fri, Jan 6, 2023 at 12:39 AM Thibaut wrote:
> > Le 6 janv. 2023 à 04:48, Brian Norris a écrit
> > :
> Indeed. Coreutils seems like a better choice here.
OK. So I guess I just copy/paste it back into the openwrt tree from
the packages feed, and then later clean it out of packages.git?
> As
> Le 6 janv. 2023 à 04:48, Brian Norris a écrit :
>
> On Thu, Jan 5, 2023 at 7:12 PM Stefan Lippers-Hollmann wrote:
>> On 2023-01-06, Christian Marangi wrote:
>>> On Thu, Jan 05, 2023 at 02:03:24PM -0800, Brian Norris wrote:
On Thu, Jan 5, 2023 at 11:59 AM Brian Norris
>> [...]
Do I
On Thu, Jan 5, 2023 at 7:12 PM Stefan Lippers-Hollmann wrote:
> On 2023-01-06, Christian Marangi wrote:
> > On Thu, Jan 05, 2023 at 02:03:24PM -0800, Brian Norris wrote:
> > > On Thu, Jan 5, 2023 at 11:59 AM Brian Norris
> [...]
> > > Do I need to create some intermediate/stub package just to
Hi
On 2023-01-06, Christian Marangi wrote:
> On Thu, Jan 05, 2023 at 02:03:24PM -0800, Brian Norris wrote:
> > On Thu, Jan 5, 2023 at 11:59 AM Brian Norris
[...]
> > Do I need to create some intermediate/stub package just to express the
> > dependency, or is there some better way?
> >
>
> In
On Thu, Jan 05, 2023 at 02:03:24PM -0800, Brian Norris wrote:
> In case you are open to giving more helpful tips to a relative
> newcomer to openwrt development:
>
> On Thu, Jan 5, 2023 at 11:59 AM Brian Norris
> wrote:
> > I'll just need to
> > force a 'base64' utility into these images
>
>
In case you are open to giving more helpful tips to a relative
newcomer to openwrt development:
On Thu, Jan 5, 2023 at 11:59 AM Brian Norris
wrote:
> I'll just need to
> force a 'base64' utility into these images
This is turning out to be nontrivial. The only in-tree base64 tool is
a busybox
On Thu, Jan 5, 2023 at 11:02 AM Robert Marko wrote:
> On Thu, 5 Jan 2023 at 19:47, Brian Norris wrote:
> > On Wed, Jan 04, 2023 at 01:58:01PM +0100, Christian Marangi wrote:
> > > Also on top of that the besto solution for these special case is to
> > > parse the base64 data in userspace a
On Thu, 5 Jan 2023 at 19:47, Brian Norris wrote:
>
> Hi Christian,
>
> On Wed, Jan 04, 2023 at 01:58:01PM +0100, Christian Marangi wrote:
> > On Mon, Jan 02, 2023 at 03:25:33PM -0800, Brian Norris wrote:
> > > See the patch notes about the stock firmware for TP-Link Onhub and
> > >
Hi Christian,
On Wed, Jan 04, 2023 at 01:58:01PM +0100, Christian Marangi wrote:
> On Mon, Jan 02, 2023 at 03:25:33PM -0800, Brian Norris wrote:
> > See the patch notes about the stock firmware for TP-Link Onhub and
> > https://chromium-review.googlesource.com/243115.
> >
> > As noted there, the
On Tue, 3 Jan 2023 at 00:30, Brian Norris wrote:
>
> See the patch notes about the stock firmware for TP-Link Onhub and
> https://chromium-review.googlesource.com/243115.
>
> As noted there, the production firmware for Google OnHub devices only
> provide the *-base64 Device Tree property, and so
On Mon, Jan 02, 2023 at 03:25:33PM -0800, Brian Norris wrote:
> See the patch notes about the stock firmware for TP-Link Onhub and
> https://chromium-review.googlesource.com/243115.
>
> As noted there, the production firmware for Google OnHub devices only
> provide the *-base64 Device Tree
11 matches
Mail list logo
