From owner-freebsd-arm@FreeBSD.ORG Tue Mar 24 12:00:13 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE9CC1065701 for ; Tue, 24 Mar 2009 12:00:13 +0000 (UTC) (envelope-from antab@freebsd.org) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by mx1.freebsd.org (Postfix) with ESMTP id 400648FC18 for ; Tue, 24 Mar 2009 12:00:13 +0000 (UTC) (envelope-from antab@freebsd.org) Received: from dumb.farm.antab.is (farm.antab.is [80.101.60.195]) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id n2OC0CMM036710 for ; Tue, 24 Mar 2009 13:00:12 +0100 (CET) (envelope-from antab@freebsd.org) Resent-Message-Id: <200903241200.n2OC0CMM036710@smtp-vbr19.xs4all.nl> Resent-To: freebsd-arm@freebsd.org From: Arnar Mar Sig To: "M. Warner Losh" In-Reply-To: <20090323.214024.-2077496443.imp@bsdimp.com> Resent-From: Arnar Mar Sig References: <164b4c9c0903231301p754eebb7k84ea2b22d7b60dc1@mail.gmail.com> <8BC7AFF2-E0E1-4498-82E8-29C3F64C5E2E@FreeBSD.org> <20090323.214024.-2077496443.imp@bsdimp.com> Message-Id: <9C3FADC8-1707-46FA-8BD9-EF7731916B61@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Resent-Date: Tue, 24 Mar 2009 13:00:11 +0100 Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 24 Mar 2009 12:57:53 +0100 X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Subject: Re: Atmel at91sam9261-ek support. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 12:00:15 -0000 On Mar 24, 2009, at 4:40 AM, M. Warner Losh wrote: > In message: <8BC7AFF2-E0E1-4498-82E8-29C3F64C5E2E@FreeBSD.org> > Arnar Mar Sig writes: > : > - a new smc driver (static memory controller) > : Looks like the at91sam9261 uses the same SMC core as at32ap700x, we > : should look into using the same driver for both archs. I already > have > : at32_smc in p4 to do bus managment and attach childs but no setup > code > > Part of the problem here is going to be each SoC is going to have a > different set of errata for the silicon.... Yes i know. Dosen't look like they are having problems with it in linux land, and aren't there driver in the tree that deal with bugs in some chip revisions? After a quick look over at32ap700x and at91sam9261ek errata it dosen't look like there are any show stopper bugs for not using the same smc driver on both archs. Difference between them are: at32ap700x has 6 chips selects while at91sam9261ek has 8 "Special" functions (CompactFlash, SmartMedia, NAND..) are set in different registers not belonging to SMC (same for both archs but different registers) Arnar Mar Sig