From owner-freebsd-arm@FreeBSD.ORG Fri Nov 2 03:24:06 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 AE6A2DE3 for ; Fri, 2 Nov 2012 03:24:06 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 86A028FC0A for ; Fri, 2 Nov 2012 03:24:05 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qA23O4bn084486; Fri, 2 Nov 2012 03:24:04 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id inxpakwk7ndag9r6hvh4unyha6; Fri, 02 Nov 2012 03:24:04 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: BeagleBone SD card problems Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <5092667B.2030908@thieprojects.ch> Date: Thu, 1 Nov 2012 20:24:04 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <5C5E2EAA-DEE7-4F79-9F23-A614DE32EBF9@kientzle.com> References: <5092667B.2030908@thieprojects.ch> To: Werner Thie X-Mailer: Apple Mail (2.1283) 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: Fri, 02 Nov 2012 03:24:06 -0000 On Nov 1, 2012, at 5:09 AM, Werner Thie wrote: > Hi all >=20 > just got my fingers wet with a Rev A6 Beaglebone. Being a long time = user of FreeBSD I found of course Tim Kientzle's project on github. = Setting up a VM and the building of an image was a nobrainer, mahalo and = kudos to Tim! >=20 > When experimentally adding a swap file I encountered the following = message repeatedly on console: >=20 > dd if=3D/dev/zero of=3D/usr/swap0 bs=3D1024k count=3D512 >=20 > ti_mmchs0: Error: current cmd NULL, already done? Don't know for sure that it is a problem, actually. I think of this message more as a gentle reminder: Someone needs to study the driver and go through the hardware docs carefully to figure out whether this particular case indicates a flaw in the driver or is just an expected case that can be safely ignored. While you're in there , you might look at what's involved in converting the driver to use DMA and whether there are any other performance optimizations we should be trying. Tim