Date: Fri, 17 Aug 2018 16:56:44 +0930 From: "O'Connor, Daniel" <darius@dons.net.au> To: "Dr. Rolf Jansen" <rj@obsigna.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Beaglebone Black pinmuxing Message-ID: <F3C39031-B0B7-4824-984E-EFEFF32D63A4@dons.net.au> In-Reply-To: <72D8FE35-EE57-4E40-A604-4DF9DC8FEE05@dons.net.au> References: <13360A40-3381-4AF9-8EC5-C8E9B00CCABD@dons.net.au> <56756FA3-8FD7-44A4-A2D8-054E7C86744B@obsigna.com> <3B199FD0-479D-49C5-8E6F-DDE3D447EB03@dons.net.au> <72D8FE35-EE57-4E40-A604-4DF9DC8FEE05@dons.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 17 Aug 2018, at 13:36, O'Connor, Daniel <darius@dons.net.au> wrote:
> Next step is to make an overlay version - hopefully I can look at that =
tonight :)
Another thing would be to capture the PPS signal - it is connected to =
timer 4 but I can't see how to enable it.
Naively adding status =3D "okay" to timer@48044000 {} and/or =
timer4_fck@510 {} does not result in it showing up in dmesg. I had a =
look at timer@48042000 {} which does show up in dmesg but can't see a =
likely difference to explain why one works and the other doesn't.
--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3C39031-B0B7-4824-984E-EFEFF32D63A4>