svn commit: r328257 - in head/sys: arm/broadcom/bcm2835 dts/arm modules

[Emmanuel Vadot]

On Sat, 27 Jan 2018 12:13:57 -0800
Adrian Chadd <adrian.chadd at gmail.com> wrote:

> Hi,
> 
> Find the middle ground. Don't dissuade the developer too much.

 This is what happened two years ago when I started hacking on the
allwinner SoCs :

 - I asked what should be done for bringing a new board
 - andrew@ told me that we first need to switch to upstream dts and
update drivers.
 - Guess what, I did that.

> Here's an example:
> 
> Make the driver follow DTS, allow a tunable/kenv check for it to
> override whether it needs to be in the DTS or not (the "keep phk happy
> for now" compromise) and have it default to obeying the device tree.
> 
> That way phk is kept happy and the defaults are the same as normal-ish
> ARM /and/ you have a springboard to experiment with extending FDT
> overlays at runtime for people who wish to do so.

 I don't care about keeping phk@ (or any other developer) happy, we
have a standard, let's stick to it.

> (I personally hate having to edit the dts/recompile/reboot for every
> test hardware change; it makes breadboarding things up kinda
> hilariously annoying.)

 Use overlays then. And if you don't want to reboot provide patch for
loading overlays at runtime.

> -adrian


-- 
Emmanuel Vadot <manu at bidouilliste.com> <manu at freebsd.org>