From owner-freebsd-arm@FreeBSD.ORG Sun Jul 24 03:23:15 2011 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 777191065674; Sun, 24 Jul 2011 03:23:15 +0000 (UTC) (envelope-from jakub.klama@uj.edu.pl) Received: from mail.uj.edu.pl (mail.uj.edu.pl [149.156.89.147]) by mx1.freebsd.org (Postfix) with ESMTP id 378108FC1B; Sun, 24 Jul 2011 03:23:14 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from mbox.uj.edu.pl ([unknown] [149.156.89.248]) by mta.uoks.uj.edu.pl (Sun Java(tm) System Messaging Server 7u3-12.01 64bit (built Oct 15 2009)) with ESMTP id <0LOT007ISFQB7A40@mta.uoks.uj.edu.pl>; Sun, 24 Jul 2011 04:18:11 +0200 (CEST) Date: Sun, 24 Jul 2011 04:18:11 +0200 From: jakub.klama@uj.edu.pl To: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org, andrew@fubar.geek.nz Message-id: X-Sender: jakub.klama@uj.edu.pl User-Agent: Roundcube Webmail/0.5 Cc: Subject: LPC32x0 MMC/SD and DMA interface issues 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: Sun, 24 Jul 2011 03:23:15 -0000 Hi, During my GSoC work on LPC32x0 port, I've discovered that ARM PL180 MMC/SD controller present in SoC has completely useless PIO mode. That is, controller can't stop card clock when Rx FIFO buffer is full. This leads to permanent Rx overrun errors when CPU doesn't react to arriving data as fast as it should. Any other interrupt arriving between reading two blocks of data from SD card will make whole transfer fail. In practice, to make it work reasonably reliable in PIO mode, card clock speed should be lowered to less than 1MHz (while current SDHC cards can go with clocks of about 30MHz). I think that only possibility to make this controller working reasonable is to use DMA. On LPC32x0, there is central general-purpose DMA controller. And there is my central question: how to interface DMA controller driver with MMC/SD driver? Using direct function calls between drivers? My work from previous GSoC, Generic DMA Framework isn't ready to integrate right now, at least not that fast to do this in current GSoC timeline. Bearing in mind that it will be more or less temporary solution, will direct function calls between two drivers sufficient? Or maybe incorporate whole DMA-dealing code in MMC/SD driver? Regards, Jakub Klama From owner-freebsd-arm@FreeBSD.ORG Sun Jul 24 14:34:25 2011 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 65B781065670 for ; Sun, 24 Jul 2011 14:34:25 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4B09E8FC0A for ; Sun, 24 Jul 2011 14:34:24 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta12.emeryville.ca.mail.comcast.net with comcast id BqJe1h0021HpZEsACqMC0f; Sun, 24 Jul 2011 14:21:12 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta14.emeryville.ca.mail.comcast.net with comcast id BqMC1h0044NgCEG8aqMC1P; Sun, 24 Jul 2011 14:21:16 +0000 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 p6OEL7WT056341; Sun, 24 Jul 2011 08:21:08 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: jakub.klama@uj.edu.pl In-Reply-To: References: Content-Type: text/plain Date: Sun, 24 Jul 2011 08:21:07 -0600 Message-Id: <1311517267.1589.7.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-arm@freebsd.org Subject: Re: LPC32x0 MMC/SD and DMA interface issues 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: Sun, 24 Jul 2011 14:34:25 -0000 Have a look at the Atmel driver in sys/arm/at91/at91_mci.c. It interfaces to the mmc/sd driver code in sys/dev, and uses DMA. The driver in -current does only single-block transfers; if you add my patches from http://www.freebsd.org/cgi/query-pr.cgi?pr=155214 it will do multiblock transfers as well. The controller in the first generation Atmel SoC also doesn't stop the data clock on a receive overrun even in DMA mode, which prevents using 4-bit transfers when other memory-intensive devices are active (such as the USB host) or when interrupt latency is high. I've read that the more recent Atmel chips can do so (but I haven't gotten to work with one yet). -- Ian On Sun, 2011-07-24 at 04:18 +0200, jakub.klama@uj.edu.pl wrote: > Hi, > > During my GSoC work on LPC32x0 port, I've discovered that > ARM PL180 MMC/SD controller present in SoC has completely > useless PIO mode. That is, controller can't stop card clock > when Rx FIFO buffer is full. This leads to permanent Rx > overrun errors when CPU doesn't react to arriving data as > fast as it should. Any other interrupt arriving between > reading two blocks of data from SD card will make whole > transfer fail. In practice, to make it work reasonably > reliable in PIO mode, card clock speed should be lowered > to less than 1MHz (while current SDHC cards can go with > clocks of about 30MHz). > > I think that only possibility to make this controller > working reasonable is to use DMA. On LPC32x0, there is > central general-purpose DMA controller. > > And there is my central question: how to interface DMA > controller driver with MMC/SD driver? Using direct > function calls between drivers? My work from previous > GSoC, Generic DMA Framework isn't ready to integrate > right now, at least not that fast to do this in current > GSoC timeline. Bearing in mind that it will be more or > less temporary solution, will direct function calls > between two drivers sufficient? Or maybe incorporate > whole DMA-dealing code in MMC/SD driver? > > Regards, > Jakub Klama > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Mon Jul 25 11:07:03 2011 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 3C8511065672 for ; Mon, 25 Jul 2011 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2B85B8FC21 for ; Mon, 25 Jul 2011 11:07:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6PB7312046315 for ; Mon, 25 Jul 2011 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6PB72Nj046313 for freebsd-arm@FreeBSD.org; Mon, 25 Jul 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Jul 2011 11:07:02 GMT Message-Id: <201107251107.p6PB72Nj046313@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arm@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-arm@FreeBSD.org 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: Mon, 25 Jul 2011 11:07:03 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o arm/158950 arm arm/sheevaplug fails fsx when mmap operations are enab o arm/156814 arm OpenRD Ultimate does not boot on DB-88F6XXX or SHEEVAP o arm/156496 arm [patch] Minor bugfixes and enhancements to mmc and mmc o arm/155894 arm [patch] Enable at91 booting from SDHC (high capacity) o arm/155214 arm [patch] MMC/SD IO slow on Atmel ARM with modern large o arm/154227 arm [geli] using GELI leads to panic on ARM o arm/154189 arm lang/perl5.12 doesn't build on arm o arm/153380 arm Panic / translation fault with wlan on ARM o arm/150581 arm [irq] Unknown error generates IRQ address decoding err o arm/149288 arm mail/dovecot causes panic during configure on Sheevapl o arm/134368 arm [patch] nslu2_led driver for the LEDs on the NSLU2 p arm/134338 arm [patch] Lock GPIO accesses on ixp425 12 problems total. From owner-freebsd-arm@FreeBSD.ORG Wed Jul 27 14:08:06 2011 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 B41031065672 for ; Wed, 27 Jul 2011 14:08:06 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3A18FC1C for ; Wed, 27 Jul 2011 14:08:05 +0000 (UTC) Received: by fxe4 with SMTP id 4so506978fxe.13 for ; Wed, 27 Jul 2011 07:08:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=W7TNqenqCih6jvot6Xrgjx4u0l/YUXNdPPN2wI2My10=; b=gqN3YPsMeXOL5h0yYgqM0LDaubExUiWYgK6H4siUkkPw/y5IM9Doi4G9vHdIDTA8Y+ CKrRbQy3O1yW6IrQjC6+rKQdCOfviErNJVl6tTqoOOvzk67Nh4CUMhfceH37VzRmstOM XBO+DWt5I1w5J5ePSHSyDZS4TrbcWuUrA0Yrk= Received: by 10.223.144.194 with SMTP id a2mr38267fav.138.1311775685007; Wed, 27 Jul 2011 07:08:05 -0700 (PDT) Received: from damarion-mac.lan (93-143-24-20.adsl.net.t-com.hr [93.143.24.20]) by mx.google.com with ESMTPS id x13sm87386fah.5.2011.07.27.07.08.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jul 2011 07:08:04 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Damjan Marion In-Reply-To: <1311045159.1508.3.camel@bmcgover-laptop.beta.com> Date: Wed, 27 Jul 2011 16:08:04 +0200 Content-Transfer-Encoding: 7bit Message-Id: <6E4BB877-4039-41A8-96B7-AB36AE2774C0@gmail.com> References: <20110708120025.5C94210656D9@hub.freebsd.org> <1310178351.5681.4.camel@bmcgover-laptop.beta.com> <4E18403C.8010203@gmail.com> <1310344111.1455.3.camel@bmcgover-laptop.beta.com> <4E1A4F18.5000802@gmail.com> <1310412331.1466.41.camel@bmcgover-laptop.beta.com> <4E1B83F8.3070700@gmail.com> <1310439696.1438.6.camel@bmcgover-laptop.beta.com> <4E1C48EE.3070905@gmail.com> <1310674865.1447.71.camel@bmcgover-laptop.beta.com> <4E1FA4E0.5050703@gmail.com> <1311045159.1508.3.camel@bmcgover-laptop.beta.com> To: Brian J. McGovern X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-arm@freebsd.org Subject: Re: Suggestions for arm build for qemu? 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: Wed, 27 Jul 2011 14:08:06 -0000 On Jul 19, 2011, at 5:12 AM, Brian J. McGovern wrote: > That got it. The kernel is now booting, and I'm able to run the > applications in /rescue. The other binaries seem to be hit or miss > (signal 11s), although the C compiler can build 'hello world', so I'm > guessing that either the dynamic linker isn't set up right (/etc isn't > populated by the installworld, so I continue to add files by hand) and > its having a problem finding all the dynamic libraries it wants, or the > 64MB memory limit is a problem, and I need to get swap going. In any > event, its enough to get my hacking until Globalscale ships my board. Hi Brian, Can you share how did you setup root file system? I tried to play with qemu network settings but didn't reach far away from: Received DHCP Ack packet on smc0 from 10.0.2.2 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 Thanks, Damjan From owner-freebsd-arm@FreeBSD.ORG Wed Jul 27 23:14:29 2011 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 935A81065670 for ; Wed, 27 Jul 2011 23:14:29 +0000 (UTC) (envelope-from mcgovern@beta.com) Received: from spoon.beta.com (spoon.beta.com [199.165.180.2]) by mx1.freebsd.org (Postfix) with ESMTP id 195F18FC14 for ; Wed, 27 Jul 2011 23:14:28 +0000 (UTC) Received: from [199.165.180.39] (dhcp9.beta.com [199.165.180.39]) by spoon.beta.com (8.14.4/8.14.4) with ESMTP id p6RNEQQG025417; Wed, 27 Jul 2011 19:14:26 -0400 (EDT) (envelope-from mcgovern@beta.com) From: "Brian J. McGovern" To: Damjan Marion In-Reply-To: <6E4BB877-4039-41A8-96B7-AB36AE2774C0@gmail.com> References: <20110708120025.5C94210656D9@hub.freebsd.org> <1310178351.5681.4.camel@bmcgover-laptop.beta.com> <4E18403C.8010203@gmail.com> <1310344111.1455.3.camel@bmcgover-laptop.beta.com> <4E1A4F18.5000802@gmail.com> <1310412331.1466.41.camel@bmcgover-laptop.beta.com> <4E1B83F8.3070700@gmail.com> <1310439696.1438.6.camel@bmcgover-laptop.beta.com> <4E1C48EE.3070905@gmail.com> <1310674865.1447.71.camel@bmcgover-laptop.beta.com> <4E1FA4E0.5050703@gmail.com> <1311045159.1508.3.camel@bmcgover-laptop.beta.com> <6E4BB877-4039-41A8-96B7-AB36AE2774C0@gmail.com> Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Jul 2011 19:14:28 -0400 Message-ID: <1311808468.1465.10.camel@bmcgover-laptop.beta.com> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.5 required=5.0 tests=S25R_6,T_RP_MATCHES_RCVD autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spoon.beta.com Cc: freebsd-arm@freebsd.org Subject: Re: Suggestions for arm build for qemu? 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: Wed, 27 Jul 2011 23:14:29 -0000 On Wed, 2011-07-27 at 16:08 +0200, Damjan Marion wrote: > On Jul 19, 2011, at 5:12 AM, Brian J. McGovern wrote: > > > That got it. The kernel is now booting, and I'm able to run the > > applications in /rescue. The other binaries seem to be hit or miss > > (signal 11s), although the C compiler can build 'hello world', so I'm > > guessing that either the dynamic linker isn't set up right (/etc isn't > > populated by the installworld, so I continue to add files by hand) and > > its having a problem finding all the dynamic libraries it wants, or the > > 64MB memory limit is a problem, and I need to get swap going. In any > > event, its enough to get my hacking until Globalscale ships my board. > > Hi Brian, > > Can you share how did you setup root file system? I tried to play with > qemu network settings but didn't reach far away from: > > Received DHCP Ack packet on smc0 from 10.0.2.2 (accepted) (no root path) > DHCP/BOOTP timeout for server 255.255.255.255 > > Thanks, > > Damjan > > Sure. Happy to share what others helped with... I'm going to assume you've read through http://wiki.freebsd.org/FreeBSDMarvell, have built and the exported file system. It looks like you're getting hung up on passing the root filesystem via DHCP. I'm using the isc-dhcp server, so I had to add option root-path "dotted.quad.ip.addr:/path/to/exported root"; to the section that will give an address to the device. This will get the device to mount the NFS export as the root filesystem. Once you can boot the device, you can use the standard tools to build local filesystems if you've defined hard disks or other storage. From owner-freebsd-arm@FreeBSD.ORG Wed Jul 27 23:31:44 2011 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 9D977106566C for ; Wed, 27 Jul 2011 23:31:44 +0000 (UTC) (envelope-from mcgovern@beta.com) Received: from spoon.beta.com (spoon.beta.com [199.165.180.2]) by mx1.freebsd.org (Postfix) with ESMTP id 498DF8FC08 for ; Wed, 27 Jul 2011 23:31:43 +0000 (UTC) Received: from [199.165.180.39] (dhcp9.beta.com [199.165.180.39]) by spoon.beta.com (8.14.4/8.14.4) with ESMTP id p6RNVgAr025484 for ; Wed, 27 Jul 2011 19:31:42 -0400 (EDT) (envelope-from mcgovern@beta.com) From: "Brian J. McGovern" To: freebsd-arm@freebsd.org In-Reply-To: <20110725120003.C270310656D9@hub.freebsd.org> References: <20110725120003.C270310656D9@hub.freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Jul 2011 19:31:44 -0400 Message-ID: <1311809504.1465.16.camel@bmcgover-laptop.beta.com> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.5 required=5.0 tests=S25R_6,T_RP_MATCHES_RCVD autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spoon.beta.com Subject: OpenRD Ultimate SD card slot? 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: Wed, 27 Jul 2011 23:31:44 -0000 I'm moving ahead with real hardware. Got my OpenRD Ultimate yesterday, and already have it booting and doing a handful of useful tasks. However, I noticed that the SD card reader wasn't showing up as a device. I added in the mmc, mmcsd, and sdhci devices, rebuilt, and rebooted. Still nothing. Digging around, I found that the original OpenRD doesn't have SD, and the other devices are dependent at91_mci, which doesn't seem to be available with the Marvell family of chips... Before I dedicate a ton of time to trying to make this work on my way to getting a flash-based kernel booting and using the sd card as a filesystem, has anyone with one of these devices gotten this working? -Brian From owner-freebsd-arm@FreeBSD.ORG Thu Jul 28 01:54:23 2011 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 333151065675 for ; Thu, 28 Jul 2011 01:54:23 +0000 (UTC) (envelope-from nitw.satish@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 119C48FC13 for ; Thu, 28 Jul 2011 01:54:22 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QmFnq-0008EL-8T for freebsd-arm@freebsd.org; Wed, 27 Jul 2011 18:54:22 -0700 Date: Wed, 27 Jul 2011 18:54:22 -0700 (PDT) From: satish kondapalli To: freebsd-arm@freebsd.org Message-ID: <1311818062256-4640945.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: how to configure freeBSD kernel to mount NFS as a root file system 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: Thu, 28 Jul 2011 01:54:23 -0000 Hi, How to configure freeBSD kernel to mount NFS as a root filesystem. In case of Linux we will set the bootargs ( In kernel command line args, we will give the server ip and path of file system.) 1) In Free BSD, make installworld will install all the utils in DESTDIR, that DESTDIR we can use as the file system. am i correct? 2) If my first point is correct then how to configure my kernel DESTDIR as a root filesytem. where to give the path of DESTDIR and DESTDIR machine IP in the kernel. Thanks in advance. Sateesh -- View this message in context: http://freebsd.1045724.n5.nabble.com/how-to-configure-freeBSD-kernel-to-mount-NFS-as-a-root-file-system-tp4640945p4640945.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Thu Jul 28 09:09:30 2011 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 65821106566B for ; Thu, 28 Jul 2011 09:09:30 +0000 (UTC) (envelope-from vancorte@biologie.ens.fr) Received: from nef2.ens.fr (nef2.ens.fr [129.199.96.40]) by mx1.freebsd.org (Postfix) with ESMTP id 012508FC14 for ; Thu, 28 Jul 2011 09:09:29 +0000 (UTC) Received: from biologie.ens.fr (biologie.ens.fr [129.199.16.22]) by nef2.ens.fr (8.13.6/1.01.28121999) with ESMTP id p6S8LUl3088362 ; Thu, 28 Jul 2011 10:21:30 +0200 (CEST) X-Envelope-To: freebsd-arm@freebsd.org Received: from [129.199.16.44] (hades.ens.fr [129.199.16.44]) by biologie.ens.fr (8.14.4/jb-1.1) (authenticated bits=0) id p6S8LTRG010915 ; Thu, 28 Jul 2011 10:21:30 +0200 (CEST) Message-ID: <4E311C09.40102@biologie.ens.fr> Date: Thu, 28 Jul 2011 10:21:29 +0200 From: Arnaud User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr-FR; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: "Brian J. McGovern" References: <20110725120003.C270310656D9@hub.freebsd.org> <1311809504.1465.16.camel@bmcgover-laptop.beta.com> In-Reply-To: <1311809504.1465.16.camel@bmcgover-laptop.beta.com> X-Enigmail-Version: 1.1.2 OpenPGP: url=hkp://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.1.4 (nef2.ens.fr [129.199.96.32]); Thu, 28 Jul 2011 10:21:30 +0200 (CEST) Cc: freebsd-arm@freebsd.org Subject: Re: OpenRD Ultimate SD card slot? 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: Thu, 28 Jul 2011 09:09:30 -0000 Have a look to this thread : http://thread.gmane.org/gmane.os.freebsd.devel.arm/2890 -- Arnaud. On 28/07/2011 01:31, Brian J. McGovern wrote: > I'm moving ahead with real hardware. Got my OpenRD Ultimate yesterday, > and already have it booting and doing a handful of useful tasks. > However, I noticed that the SD card reader wasn't showing up as a > device. > > I added in the mmc, mmcsd, and sdhci devices, rebuilt, and rebooted. > Still nothing. Digging around, I found that the original OpenRD doesn't > have SD, and the other devices are dependent at91_mci, which doesn't > seem to be available with the Marvell family of chips... > > Before I dedicate a ton of time to trying to make this work on my way to > getting a flash-based kernel booting and using the sd card as a > filesystem, has anyone with one of these devices gotten this working? > > -Brian > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Thu Jul 28 12:18:59 2011 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 E40881065673 for ; Thu, 28 Jul 2011 12:18:59 +0000 (UTC) (envelope-from crest@informatik.uni-bremen.de) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [134.102.201.18]) by mx1.freebsd.org (Postfix) with ESMTP id 74D1C8FC16 for ; Thu, 28 Jul 2011 12:18:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p6SAl83M026310 for ; Thu, 28 Jul 2011 12:47:08 +0200 (CEST) Received: from mb-wlan.dhcp.crest.dn42 (dslb-092-077-000-141.pools.arcor-ip.net [92.77.0.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C11A02B for ; Thu, 28 Jul 2011 12:47:08 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: crest In-Reply-To: <1311818062256-4640945.post@n5.nabble.com> Date: Thu, 28 Jul 2011 12:47:08 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <3B2DAD3B-5405-43EC-959E-5324C5AEA62A@informatik.uni-bremen.de> References: <1311818062256-4640945.post@n5.nabble.com> To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.1084) Subject: Re: how to configure freeBSD kernel to mount NFS as a root file system 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: Thu, 28 Jul 2011 12:19:00 -0000 On 28.07.2011, at 03:54, satish kondapalli wrote: > Hi, >=20 > How to configure freeBSD kernel to mount NFS as a root filesystem.=20 > In case of Linux we will set the bootargs ( In kernel command line = args, we > will give the server ip and path of file system.) >=20 > 1) In Free BSD, make installworld will install all the utils in = DESTDIR, > that DESTDIR we can use as the file system. am i correct? Yes export $DESTDIR via NFSv3 > 2) If my first point is correct then how to configure my kernel = DESTDIR as > a root filesytem. where to give the path of DESTDIR and DESTDIR = machine IP > in the kernel. Your kernel needs to support (options NFS_ROOT). If you can't run = /boot/loader than define the rootfs in the kernel config (options = ROOTDEVNAME=3D\"ufs:/dev/ufs/rootfs\").= From owner-freebsd-arm@FreeBSD.ORG Fri Jul 29 04:23:29 2011 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 46F96106566B for ; Fri, 29 Jul 2011 04:23:29 +0000 (UTC) (envelope-from nitw.satish@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 21FD38FC19 for ; Fri, 29 Jul 2011 04:23:28 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Qmebg-00029a-Bn for freebsd-arm@freebsd.org; Thu, 28 Jul 2011 21:23:28 -0700 Date: Thu, 28 Jul 2011 21:23:28 -0700 (PDT) From: satish kondapalli To: freebsd-arm@freebsd.org Message-ID: <1311913408355-4645024.post@n5.nabble.com> In-Reply-To: <3B2DAD3B-5405-43EC-959E-5324C5AEA62A@informatik.uni-bremen.de> References: <1311818062256-4640945.post@n5.nabble.com> <3B2DAD3B-5405-43EC-959E-5324C5AEA62A@informatik.uni-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: how to configure freeBSD kernel to mount NFS as a root file system 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: Fri, 29 Jul 2011 04:23:29 -0000 Thanks Crest > Hi, > > How to configure freeBSD kernel to mount NFS as a root filesystem. > In case of Linux we will set the bootargs ( In kernel command line args, > we > will give the server ip and path of file system.) > > 1) In Free BSD, make installworld will install all the utils in DESTDIR, > that DESTDIR we can use as the file system. am i correct? Yes export $DESTDIR via NFSv3 > 2) If my first point is correct then how to configure my kernel DESTDIR > as > a root filesytem. where to give the path of DESTDIR and DESTDIR machine IP > in the kernel. Your kernel needs to support (options NFS_ROOT). If you can't run /boot/loader than define the rootfs in the kernel config (options ROOTDEVNAME=\"ufs:/dev/ufs/rootfs\"). My questions is: 1) we are not telling the NFS server ip address in above two options. where we will configure the server ip of NFS server in config options. -- View this message in context: http://freebsd.1045724.n5.nabble.com/how-to-configure-freeBSD-kernel-to-mount-NFS-as-a-root-file-system-tp4640945p4645024.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Fri Jul 29 07:25:19 2011 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 A875F1065674 for ; Fri, 29 Jul 2011 07:25:19 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 620A18FC1C for ; Fri, 29 Jul 2011 07:25:19 +0000 (UTC) Received: by yxl31 with SMTP id 31so2631666yxl.13 for ; Fri, 29 Jul 2011 00:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=3KuaagGQfoBVA3QToA16Wk8bYkSNfwYDlpoLsQNVk4U=; b=Xkznj6SycX7vELxr+G1XZ+UisNZExB9s3pggHyktsI9CI6iScDTTb1VKSas2kh0tU9 sJOJt+Wqc83zXhpa8CDbmzFFv6V4qPkNKigVrnEN/FFHA/nFgkTTyjHKU5KFm6itt03n fP3SH4QDCiosmjz7CUpxU32eLramt+cEk/wxs= MIME-Version: 1.0 Received: by 10.150.74.21 with SMTP id w21mr6748yba.396.1311922836193; Fri, 29 Jul 2011 00:00:36 -0700 (PDT) Received: by 10.151.46.18 with HTTP; Fri, 29 Jul 2011 00:00:36 -0700 (PDT) In-Reply-To: <1311913408355-4645024.post@n5.nabble.com> References: <1311818062256-4640945.post@n5.nabble.com> <3B2DAD3B-5405-43EC-959E-5324C5AEA62A@informatik.uni-bremen.de> <1311913408355-4645024.post@n5.nabble.com> Date: Fri, 29 Jul 2011 09:00:36 +0200 Message-ID: From: Monthadar Al Jaberi To: satish kondapalli Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-arm@freebsd.org Subject: Re: how to configure freeBSD kernel to mount NFS as a root file system 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: Fri, 29 Jul 2011 07:25:19 -0000 On Fri, Jul 29, 2011 at 6:23 AM, satish kondapalli wrote: > Thanks > Crest >> Hi, >> >> How to configure freeBSD kernel to mount NFS as a root filesystem. >> In case of Linux we will set the bootargs ( In kernel command line args, >> we >> will give the server ip and path of file system.) >> >> 1) In Free BSD, make installworld =A0will install all the utils in DESTD= IR, >> that DESTDIR we can use as the file system. am i correct? > > Yes export $DESTDIR via NFSv3 > >> 2) If my first point is correct then how to configure my kernel =A0DESTD= IR >> as >> a root filesytem. where to give the path of DESTDIR and DESTDIR machine = IP >> in the kernel. > > Your kernel needs to support (options NFS_ROOT). If you can't run > /boot/loader than define the rootfs in the kernel config (options > ROOTDEVNAME=3D\"ufs:/dev/ufs/rootfs\"). > > My questions is: > 1) we are not telling the NFS server ip address in above two options. whe= re > we will configure the server ip of NFS server in config options. try this: options ROOTDEVNAME=3D\"nfs:192.168.1.103:/usr/obj/rspro_nfs/root\" > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/how-to= -configure-freeBSD-kernel-to-mount-NFS-as-a-root-file-system-tp4640945p4645= 024.html > Sent from the freebsd-arm mailing list archive at Nabble.com. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > --=20 //Monthadar Al Jaberi