Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Jan 2018 16:17:09 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc:        John Baldwin <jhb@freebsd.org>, Emmanuel Vadot <manu@bidouilliste.com>,  src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org,  svn-src-head@freebsd.org
Subject:   Re: svn commit: r328257 - in head/sys: arm/broadcom/bcm2835 dts/arm modules
Message-ID:  <CANCZdfpRTtt_KTuyN99bsNjfQcE8pmVbTTzMoc-9yT=X5eckRg@mail.gmail.com>
In-Reply-To: <90380.1516662352@critter.freebsd.dk>
References:  <201801220710.w0M7AUm9091853@repo.freebsd.org> <88258.1516630050@critter.freebsd.dk> <20180122153003.664e1613bbf70ab49c5c1541@bidouilliste.com> <52374125.OgxafgljNu@ralph.baldwin.cx> <89102.1516649067@critter.freebsd.dk> <CANCZdfp6t6KrTkp=O7Z9crnAUZhFMr%2BW-92t9S480=OytJdpfg@mail.gmail.com> <89478.1516652693@critter.freebsd.dk> <CANCZdfqwXb%2Bw1BxcruV2bhYruJ4JoQ5j0FqoM%2Bf4gz7%2BKpKQFA@mail.gmail.com> <90380.1516662352@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 22, 2018 at 4:05 PM, Poul-Henning Kamp <phk@phk.freebsd.dk>
wrote:

> --------
> In message <CANCZdfqwXb+w1BxcruV2bhYruJ4JoQ5j0FqoM+
> f4gz7+KpKQFA@mail.gmail.com>
> , Warner Losh writes:
>
> >This represents a partial understanding of what's required. It's base
> level
> >only. Don't mistake it for full understanding of what needs to be done.
>
> I would love not to, but learning "what needs to be done" have so
> far eluded me, apart from some people pointing out that "somebody
> should write XYZ" for severely underdocumented values of XYZ.
>
> And now I *really* think this thread should end...


I'm happy to point you at such docs as there are and answer as many
questions on this. It's not ideal, but it's what we have. We've made the
decision to use the FDT standard, which forces us down certain paths. When
I wrote the pinmux / pinctl stuff for Atmel, it took me about two days to
complete, most of that was understanding what needed to be done.

Part of the problem is that the original RPi port pre-dated a lot of these
efforts, and the followon ports have been incremental efforts to add in
missing bits incrementally w/o regard to modernizing, but no one has gone
back and put in the effort to modernize. You're running up against that
issue right now, if you want to help revitalize the rpi port.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpRTtt_KTuyN99bsNjfQcE8pmVbTTzMoc-9yT=X5eckRg>