Date: Mon, 12 Mar 2018 10:48:33 -0400 From: Ralph Smith <ralph@ralphsmith.org> To: Shamim Shahriar <shamim.shahriar@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: PPS or /dev/ppsN on Raspberry Pi 3 Message-ID: <5F567062-88EF-4707-B8A7-2B5841C23E38@ralphsmith.org> In-Reply-To: <9d27f6ff-d317-aa24-4f22-b06624fd6d1d@gmail.com> References: <819975e8-56a8-677b-e5f5-003ff2091553@gmail.com> <20180312011202.GA60784@bluezbox.com> <9d27f6ff-d317-aa24-4f22-b06624fd6d1d@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Look for /dev/gpiopps*
You may also need to load gpiopps.ko
Ralph
> On Mar 12, 2018, at 3:38 AM, Shamim Shahriar <shamim.shahriar@gmail.com> w=
rote:
>=20
>> On 12/03/2018 01:12, Oleksandr Tymoshenko wrote:
>> sysctl -b hw.fdt.dtb | dtc -I dtb -O dts | grep pps
> Hello Gonzo
>=20
> I made a little change (pps numbers) on your example and put that in place=
. After reboot, if I run the command above, I can see the two pps devices
> # sysctl -b hw.fdt.dtb | dtc -I dtb -O dts | grep pps
> pps@1 {
> compatible =3D "pps-gpio";
> pps@0 {
> compatible =3D "pps-gpio";
>=20
> However, there is no /dev/pps yet on the system. Is there something I need=
to do in addition to get the pps drivers in place?
>=20
> Regards
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5F567062-88EF-4707-B8A7-2B5841C23E38>