From owner-freebsd-arm@freebsd.org Sat Jan 14 13:33:30 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F45BCAF568 for ; Sat, 14 Jan 2017 13:33:30 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 924BD1D67 for ; Sat, 14 Jan 2017 13:33:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 9d3f49dc; Sat, 14 Jan 2017 14:33:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=8DxIvwqbWhrYzZijfOlMeRivnKk=; b=qc16v/bg8eposMFKgVsiDYrqN3M9 YOvVfS6HO6s8YU0SNWyKn8cR7yvQsKziER/dniC1rvrqEgl6rbSEWgPIaKvPFky+ MtFquRgBcDQFeseQZPo9MAkHtfuuHA3AIIO9GXImLWXvYTIYNKNBtwbY7nG6D2hd /iay4YRm7LPGkPw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=oiGBJp/3kWMluW3ELsN8Z+quEx7kEuWxTx1oNhpJ/ahZHBmRrOhE+imG L4xXwYZzEQh8n0wjpMC5NkEhzKVXFmUjbhrCHUcgLFVe6Tr2yLi4vMgQRljMoc/n fNREexH7PyQFIYB0q2tT0jWZEB2ayZxxVGuCSo5wax+wOmV6dOU= Received: from knuckles.blih.net (ip-54.net-82-216-203.roubaix.rev.numericable.fr [82.216.203.54]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 3bfd2abd TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 14 Jan 2017 14:33:27 +0100 (CET) Date: Sat, 14 Jan 2017 14:33:26 +0100 From: Emmanuel Vadot To: Mark Millard Cc: freebsd-arm Subject: Re: Is a83t development still active? (My context: BPI-M3) Message-Id: <20170114143326.5c99aeee0283d86fec722412@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 13:33:30 -0000 Hi Mark, On Fri, 13 Jan 2017 14:40:26 -0800 Mark Millard 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