From: Andrew Lunn <andrew@lunn.ch>
To: Paul Spooren <mail@aparcar.org>
Cc: devicetree@vger.kernel.org, jason@lakedaemon.net,
gregory.clement@bootlin.com, linux-kernel@vger.kernel.org,
daniel@makrotopia.org, freifunk@adrianschmutzler.de,
robh+dt@kernel.org, kaloz@openwrt.org,
linux-arm-kernel@lists.infradead.org,
sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH 0/5] arm: dts: linksys: rename codename to model
Date: Wed, 8 Apr 2020 02:09:51 +0200 [thread overview]
Message-ID: <20200408000951.GE310042@lunn.ch> (raw)
In-Reply-To: <004a2ef9c1e04f9ffbb9c3cc9907ca656a406713.camel@aparcar.org>
On Tue, Apr 07, 2020 at 01:38:17PM -1000, Paul Spooren wrote:
> Hi Andrew,
>
> thank you very much for the quick response!
> Are you okay with adding the new compatible string as first element of
> the list? This would already simplify the OpenWrt build system.
That should be fine. OF will keep searching from first till last for a
match.
> What about the changed labels? Are they considered ABI too?
You mean LED names. I would consider those ABI. People can have
scripts which configure the LEDs how they want, blinking heartbeat,
etc.
> Regarding file names, I'm new to ABI policies. Within OpenWrt this is
> all done via a single line patch, I'm not familiar with any other
> installers/bootloaders.
Well, it would break how i boot my wrt1900ac. I tftpboot it, grabbing
both the kernel and the DB blob from my TFTP server. If the blob
changes names, i would need to modify my uboot configuration.
I don't know if Debian has full support for any of these boards, but
if i remember correctly, flash-kernel has a database of machine names
and DTB file names. My wrt1900ac is quite happy running Debian, but i
don't have it booting the Debian way, because i use it for kernel
hacking. But maybe there are people out there that do.
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-04-08 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 21:08 [PATCH 0/5] arm: dts: linksys: rename codename to model Paul Spooren
2020-04-07 21:08 ` [PATCH 1/5] arm: dts: linksys: rename rango to wrt3200acm Paul Spooren
2020-04-07 21:08 ` [PATCH 2/5] arm: dts: linksys: rename mamba to wrt1900ac Paul Spooren
2020-04-07 21:08 ` [PATCH 3/5] arm: dts: linksys: rename cobra to wrt1900ac-v2 Paul Spooren
2020-04-07 21:08 ` [PATCH 4/5] arm: dts: linksys: rename caiman to wrt1200ac Paul Spooren
2020-04-07 21:08 ` [PATCH 5/5] arm: dts: linksys: rename shelby to wrt1900acs Paul Spooren
2020-04-07 21:08 ` [PATCH 0/5] arm: dts: linksys: rename codename to model Paul Spooren
2020-04-07 22:46 ` Andrew Lunn
2020-04-07 23:38 ` Paul Spooren
2020-04-08 0:07 ` Florian Fainelli
[not found] ` <VI1PR02MB5325621D39BF0FFAFE3993C4A0C00@VI1PR02MB5325.eurprd02.prod.outlook.com>
2020-04-08 16:23 ` Daniel Golle
2020-04-10 9:49 ` Paul Spooren
2020-04-08 0:09 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200408000951.GE310042@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=freifunk@adrianschmutzler.de \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=kaloz@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@aparcar.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).