o:openwrt-devel-
> boun...@lists.openwrt.org]
> >> On Behalf Of Rafal Milecki
> >> Sent: Mittwoch, 8. Juli 2020 17:10
> >> To: openwrt-devel@lists.openwrt.org
> >> Cc: Rafał Miłecki ; Adrian Schmutzler
> >> ; Petr Štetiar ; Moritz
> >> Warning ;
Štetiar ; Moritz
Warning ; Paul Spooren
Subject: [PATCH] build: put DT "compatible" value as "board_name" in
profiles.json
From: Rafał Miłecki
The purpose of "board_name" in JSON is matchine OpenWrt running device
with JSON profile entry. Right now it gets filled for d
; Warning ; Paul Spooren
> Subject: [PATCH] build: put DT "compatible" value as "board_name" in
> profiles.json
>
> From: Rafał Miłecki
>
> The purpose of "board_name" in JSON is matchine OpenWrt running device
> with JSON profile entry. Right n
'Petr Štetiar' ; 'Moritz
> Warning' ; 'Daniel Golle'
> Subject: Re: [PATCH] build: put DT "compatible" value as "board_name" in
> profiles.json
>
> On 08.07.2020 21:41, m...@adrianschmutzler.de wrote:
> >> -Original
z
> Subject: Re: [PATCH] build: put DT "compatible" value as "board_name" in
> profiles.json
>
> On 2020-07-09 10:49, Daniel Golle wrote:
> > On Wed, Jul 08, 2020 at 11:32:43PM +0200, Rafał Miłecki wrote:
> >> On 08.07.2020 21:34, Paul Spoore
On 2020-07-09 10:49, Daniel Golle wrote:
On Wed, Jul 08, 2020 at 11:32:43PM +0200, Rafał Miłecki wrote:
On 08.07.2020 21:34, Paul Spooren wrote:
> I think there is a policy for new DT devices to use the compatible string as
profile.
>
> Multiple targets contain the following line in the target
On Wed, Jul 08, 2020 at 11:32:43PM +0200, Rafał Miłecki wrote:
> On 08.07.2020 21:34, Paul Spooren wrote:
> > I think there is a policy for new DT devices to use the compatible string
> > as profile.
> >
> > Multiple targets contain the following line in the target Makefile, which
> > automatica
Subject: Re: [PATCH] build: put DT "compatible" value as "board_name" in
profiles.json
I think the question is therefore more on how to deal with devices that do
not use DT? If we use a per device rootfs a line could be added to /etc/os-
release containing something like OPEN
On 08.07.2020 21:34, Paul Spooren wrote:
I think there is a policy for new DT devices to use the compatible string as
profile.
Multiple targets contain the following line in the target Makefile, which
automatically adds the profile name as supported device:
SUPPORTED_DEVICES := $(subst _,$(co
e: [PATCH] build: put DT "compatible" value as "board_name" in
> profiles.json
>
> TL;DR: I think the issue is solved for devices using DT, the problem are the
> other targets with custom solutions.
>
> I think there is a policy for new DT devices to use the com
TL;DR: I think the issue is solved for devices using DT, the problem are
the other targets with custom solutions.
I think there is a policy for new DT devices to use the compatible
string as profile.
Multiple targets contain the following line in the target Makefile,
which automatically adds
From: Rafał Miłecki
The purpose of "board_name" in JSON is matchine OpenWrt running device
with JSON profile entry. Right now it gets filled for devices using DT.
Other targets will require custom solutions or just speciyfing that
value manually.
Signed-off-by: Rafał Miłecki
---
include/image.
12 matches
Mail list logo
