[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <kCnyFRBTNPaksjpFGz3Vnx92t6yIivNcqixk5m2h238c@mailpile>
Date: Fri, 01 Nov 2019 09:55:41 -0000
From: Karl Palsson <karlp@...ak.net.au>
To: "Maxime Ripard" <mripard@...nel.org>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"wens@...e.org" <wens@...e.org>
Subject: Re: [PATCH 3/3] ARM: dts: sun8i: add FriendlyARM NanoPi Duo2-IoT Box
Maxime Ripard <mripard@...nel.org> wrote:
> On Thu, Oct 31, 2019 at 11:12:16PM +0000, Karl Palsson wrote:
> > The IoT-Box is a dock for the NanoPi Duo2, adding two USB host ports, a
> > 10/100 ethernet port, a variety of pin headers for i2c and uarts, and a
> > quad band 2G GSM module, a SIM800C.
> >
> > Full documentation and schematics available from vendor:
> > http://wiki.friendlyarm.com/wiki/index.php/NanoPi_Duo2_IoT-Box
> >
> > Signed-off-by: Karl Palsson <karlp@...ak.net.au>
>
> It seems like it's something that can be connected /
> disconnected at will?
>
> If so, then it should be an overlay, not a full blown DTS.
Fine with me, I wasn't sure on the best procedure for things like
this. It's not something you plug / unplug at run time, you'd
tend to just always have this, or not. Is it best to just have
user space distributions handle selecting the overlay then? and
they maintain the overlay file?
I'd considered overlays something for _per user_ customization,
but I'm perfectly happy if it it's intended to be used for per
product customization too if that's the right method.
Sincerely,
Karl Palsson
Download attachment "OpenPGP-digital-signature.html" of type "application/pgp-signature" (1176 bytes)
Powered by blists - more mailing lists