Date: Sat, 14 Jan 2017 14:33:26 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Mark Millard <markmi@dsl-only.net> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Is a83t development still active? (My context: BPI-M3) Message-ID: <20170114143326.5c99aeee0283d86fec722412@bidouilliste.com> In-Reply-To: <D371F8AA-B1DA-41F1-97B0-4EEB5D61A3BA@dsl-only.net> References: <D371F8AA-B1DA-41F1-97B0-4EEB5D61A3BA@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mark, On Fri, 13 Jan 2017 14:40:26 -0800 Mark Millard <markmi@dsl-only.net> wrote: > I notice looking in: > > https://svnweb.freebsd.org/base/head/sys/arm/allwinner/ > > that, while a10, a13/, a20/, a31/, a33/, a64/, and h3/ have been > getting updates, a83t/ has not had one since 2016-Oct-3 > (306646) --and that was only to remove std.* files. The only > other vintage of a83t/ goes back to 2016-May-5 (299113). > > Is a83t no longer being updated? > > === > Mark Millard > markmi at dsl-only.net > Most of the drivers works for many Allwinner SoC so even if we don't add files in the a83t directory, it doesn't mean that there is no updates. Each of thoses directories only contain file for the padconf (the pinmuxing information) and a file with the list of needed file for this SoC (if one want to compile a kernel for a specific SoC). But I admit that when I've added information on the pin interrupts I forgot to do a83t, I'll do that soon. Cheers, -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170114143326.5c99aeee0283d86fec722412>