From owner-freebsd-arm@FreeBSD.ORG Sun Dec 16 01:04:37 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8613F4ED for ; Sun, 16 Dec 2012 01:04:37 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 8BE2D8FC14 for ; Sun, 16 Dec 2012 01:04:36 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id qBG14ZRQ067089 for ; Sat, 15 Dec 2012 18:04:35 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id qBG14CrC060819; Sat, 15 Dec 2012 18:04:12 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: SAM9G45 (was: sheevaplug boot from nandfs hangs) From: Ian Lepore To: ticso@cicely.de In-Reply-To: <20121216000839.GS16564@cicely7.cicely.de> References: <1355364418.87661.489.camel@revolution.hippie.lan> <1355595537.1198.72.camel@revolution.hippie.lan> <20121216000839.GS16564@cicely7.cicely.de> Content-Type: text/plain; charset="us-ascii" Date: Sat, 15 Dec 2012 18:04:12 -0700 Message-ID: <1355619852.1198.98.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2012 01:04:37 -0000 On Sun, 2012-12-16 at 01:08 +0100, Bernd Walter wrote: > On Sat, Dec 15, 2012 at 11:18:57AM -0700, Ian Lepore wrote: > > Wow, this is all very familiar. I had this exact situation a couple > > months ago as I was trying to get freebsd running on my pico-sam9g45 > > You have a SAM9G45 running? > Yeah, this board: http://www.mini-box.com/pico-SAM9G45-X The mci driver is stuck in "1 sector at a time" mode (slow) because all the workarounds for the rm9200 errata seem to interfere with the new less-buggy mci hardware. I think I just need to write a new driver from scratch for the new hardware rev. I've also got ehci working for it. I did some pretty ugly stuff in the at91 directory to get it going. I was just hacking to get it working, then I was going to work with Warner to clean up what I had done and get it committed, but both his and my lives got busy and nothing much has happened for 2 months now. But it does sit here on my desk running just fine (and notably not ever crashing or anything). Pretty much I've been using it when I need to see a freebsd 10 manpage, but not much else. :) I heard a rumor that the hardware guys at work are taking a look at using a G45 for an upcoming project. If that happens, that'll ensure a better mci driver gets written. If you need a patchset and are willing to deal with the ugly half-baked nature of what I've got, just let me know. -- Ian