From owner-freebsd-arm@FreeBSD.ORG Mon Nov 20 00:21:25 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 F1DFE16A47C for ; Mon, 20 Nov 2006 00:21:25 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EB2943F80 for ; Mon, 20 Nov 2006 00:17:58 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id kAK0HxO6044231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 19 Nov 2006 16:17:59 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4560F437.5060402@errno.com> Date: Sun, 19 Nov 2006 16:17:59 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.7 (X11/20060920) MIME-Version: 1.0 To: freebsd-arm@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Gateworks 2348 support now in HEAD 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, 20 Nov 2006 00:21:26 -0000 I just committed the code to make 2348 boards usable. But there are some caveats. 1. The npe (wired ethernet) support requires Intel firmware that we cannot distribute (yet); you must obtain it from the Intel web site if you don't otherwise have it (e.g. in a Gateworks Linux distribution). 2. The compact flash ide support needs a change to sys/dev/ata/ata-all.c; roll back that file to rev 1.274. 3. If you want to use ath cards in the minipci slots you'll need to use a newer hal than what is in CVS. I believe the tarball at http://www.freebsd.org/~sam/ath_hal-20060909.tgz will work but am not sure. I'm working on getting a known-good version together. This stuff has mostly been tested booting with an NFS-mounted root filesystem. I've placed instructions on how I do this at: http://www.freebsd.org/~sam/README-gateworks I believe most of the important stuff is working. The main thing missing is read/write to flash. We're also not fully setup for booting from compact flash (because redboot does not grok ufs filesystems) but that's not a big deal as there are several ways to deal with this. There's still a lot of room for improvement. It'd be nice if someone could add the PMC support to help in doing performance tuning. Sam From owner-freebsd-arm@FreeBSD.ORG Mon Nov 20 05:04:21 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 E314E16A47C for ; Mon, 20 Nov 2006 05:04:21 +0000 (UTC) (envelope-from context@osioc.net) Received: from ip-236.net-81-220-79.rev.numericable.fr (ip-236.net-81-220-79.rev.numericable.fr [81.220.79.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 481F243D80 for ; Mon, 20 Nov 2006 05:03:52 +0000 (GMT) (envelope-from context@osioc.net) Message-ID: <000e01c70c61$4a2554b0$00000000@Celeron600> From: "bar code" To: freebsd-arm@freebsd.org Date: Mon, 20 Nov 2006 06:03:59 +0100 MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_000A_01C70C69.ABE9BCB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: MSN WiseNut edit 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, 20 Nov 2006 05:04:22 -0000 ------=_NextPart_000_000A_01C70C69.ABE9BCB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Lady or Starrating hot Stuff from in bon in jovirating Wizard in am. = Meets Girl tv Oregon in. Ice am Dragon of Interview Renowned fantasy writer discusses his latest. Progress couldnt be font which provide Breaking News is. Tool Really or know. Altavista of aol in ask Clusty Gigablast Lycos of = msn Wisenut is. More is than ago then is it will not in show up. Can right click desktop = select requires get. Again dont tab so cant let use. Boards Movie Showtimes Office Trailers = Imdbprocom. Ask Clusty Gigablast or Lycos msn Wisenut edit category. Medium repository of mail tool. Out action apologize! End Infomore in Newsmore am Soon Goes. Erase necessary simple am apply them gracefully probably? Cinderella = Dancing or Dean bringing. End Infomore in Newsmore am Soon Goes. Context device recording or using cannot appear aa. Korating Onegai = Twins Amvrating nge. Watson of pes Fear is Only that were uploaded. Details Currently out in = action apologize pagelast? Games Console a Platforms a Atari dmoz is. Network too is does is mean am answers. Installed correctly want example = a Rightclick Windows. Endthe definitive guide Londons? Meets Girl tv Oregon in. Hotelscom of Hotwire hsn of. Just follow = pointer a open Display Properties dialog is box can. Not show up here or Sponsors ad of ltd or on how. Just follow pointer a = open Display Properties dialog is box can. Youve a couple am Adding new = regarding in. ------=_NextPart_000_000A_01C70C69.ABE9BCB0-- From owner-freebsd-arm@FreeBSD.ORG Mon Nov 20 09:53:23 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 823B816A415 for ; Mon, 20 Nov 2006 09:53:23 +0000 (UTC) (envelope-from brewer.doug@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id A86D043D55 for ; Mon, 20 Nov 2006 09:53:07 +0000 (GMT) (envelope-from brewer.doug@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so956808uge for ; Mon, 20 Nov 2006 01:53:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=iaPZ2wjj5jLYeHCT4T3I8Gr/GyTNxxnuQsSIkkl7ncXiXFMdI+CUVMXo4zrwkKn2dAzIOh9lZPRQNHAWff+as0WDI4APf2XcO7+DtraruICxDl62HV0c4wgX/cLxNIjmPHmcf2yJRAuMHQ01hCGDYQIhcnYZPwiXDGgJGvaGEUI= Received: by 10.78.170.17 with SMTP id s17mr5002437hue.1164016401034; Mon, 20 Nov 2006 01:53:21 -0800 (PST) Received: by 10.78.140.7 with HTTP; Mon, 20 Nov 2006 01:53:20 -0800 (PST) Message-ID: Date: Mon, 20 Nov 2006 17:53:20 +0800 From: "Doug Brewer" To: mlfbsd@ci0.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD/arm image question 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, 20 Nov 2006 09:53:23 -0000 Olivier Houchard wrote: > Hi Doug, > > The real target is "make trampoline", which will generate kernel.tramp, > kernel.tramp.bin, kernel.gz.tramp and kernel.gz.tramp.bin. > kernel.gz.tramp.bin will be I think what look the most like zImage, as it's > a raw binary, able to uncompress the gzipped kernel embedded. > Unfortunately, you can't, afaik, do it with the "buildkernel/installkernel" > method, so you'll have to use the old config + make depend all method. Thanks for the reply. I tried to build the config file KB920X, I still got errors: ... echo "#define KERNNAME \"kernel.tmp\"" >opt_kernname.h sed s/0xc0000000/0x20000000/ ldscript.arm > ldscript.arm.tramp sed s/" + SIZEOF_HEADERS"// ldscript.arm.tramp > ldscript.arm.tramp.noheader /crossarm/usr/bin/objcopy --strip-symbol '$d' --strip-symbol '$a' -g --strip-symbol '$t' kernel.debug kernel.tmp eval $(stat -s kernel.tmp) && echo "#define KERNSIZE $st_size" >>opt_kernname.h /crossarm/usr/bin/gcc -O -nostdlib -I. -Xlinker -T -Xlinker ldscript.arm.tramp ../../../arm/arm/elf_trampoline.c ../../../arm/arm/inckern.S ../../../arm/arm/cpufunc_asm_arm7tdmi.S ../../../arm/arm/cpufunc_asm_arm8.S ../../../arm/arm/cpufunc_asm_arm9.S ../../../arm/arm/cpufunc_asm_sa1.S ../../../arm/arm/cpufunc_asm_arm10.S ../../../arm/arm/cpufunc_asm_xscale.S ../../../arm/arm/cpufunc_asm.S -o kernel.tramp ../../../arm/arm/elf_trampoline.c:25:23: sys/cdefs.h: No such file or directory ../../../arm/arm/elf_trampoline.c:26: error: syntax error before string constant ../../../arm/arm/elf_trampoline.c:28:23: sys/param.h: No such file or directory ../../../arm/arm/elf_trampoline.c:29:23: sys/elf32.h: No such file or directory ../../../arm/arm/elf_trampoline.c:30:25: sys/inflate.h: No such file or directory In file included from ../../../arm/arm/elf_trampoline.c:31: ./machine/elf.h:41:29: sys/elf_generic.h: No such file or directory .... Would you tell me how to fix this? Thanks in advance. > > Cheers, > > Olivier Warm regards, Doug. From owner-freebsd-arm@FreeBSD.ORG Mon Nov 20 22:04:05 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 F208016A416 for ; Mon, 20 Nov 2006 22:04:05 +0000 (UTC) (envelope-from Danovitsch@vitsch.net) Received: from amsfep12-int.chello.nl (amsfep17-int.chello.nl [213.46.243.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CBE843D49 for ; Mon, 20 Nov 2006 22:03:44 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Tuinhuisje.Vitsch.net ([62.195.87.223]) by amsfep12-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20061120220401.UCYW1928.amsfep12-int.chello.nl@Tuinhuisje.Vitsch.net>; Mon, 20 Nov 2006 23:04:01 +0100 Received: from self (f23025.upc-f.chello.nl [80.56.23.25]) (authenticated bits=0) by Tuinhuisje.Vitsch.net (8.13.1/8.13.1) with ESMTP id kAKM3iOx061057; Mon, 20 Nov 2006 23:03:49 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: "M. Warner Losh" Date: Mon, 20 Nov 2006 23:03:52 +0100 User-Agent: KMail/1.9.1 References: <7380637.post@talk.nabble.com> <20061116.093638.63053940.imp@bsdimp.com> In-Reply-To: <20061116.093638.63053940.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_IZiYFkN+IcqicJ4" Message-Id: <200611202303.52817.Danovitsch@vitsch.net> Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 20 Nov 2006 22:04:06 -0000 --Boundary-00=_IZiYFkN+IcqicJ4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Warner (and the list), On Thursday 16 November 2006 17:36, M. Warner Losh wrote: > In message: <7380637.post@talk.nabble.com> > > Zuy writes: > : How I'm soldering board based on AT91RM9200 with 16mb SDRAM and othe > : standartpPeripherals(USB, SD, UART ...). I'm going to run FreeBSD on this > : board, but unfortunately I do not know how to start. > : I havn't found any files connected with AT91RM9200 in FreeBSD6.0 Stable > : source files directory. > : I found from this board that freebsd works on at91rm9200. > > Yes. It does. FreeBSD-current has the most up to date tested code > for this platform. FreeBSD 6.2 will contain the tools you need to > build it, as well as a slightly less advanced version (the freeze date > for 6.2 was a while ago). 6.3 is likely to have even more advanced > support. ... > Here's the broad outlines. ... followed by a very nice ARM-introduction :) ... > Feel free to ask questions. the more people that ask, the bigger my > collection of email on the topic gets, and the easier it will be for > me to synthesize a tutorial. Also, if there are areas that I've been > vague, please don't hesitate to let me know. This email got me to dust-off the KB9202B board my company bought a while back for a project that hasn't started (yet). With your email it was quite easy to get the board to work. I now use the original Kwikbyte boot loader to load the kernel with tftp. After that the kernel mounts root over NFS and everything works like a charm. If I am going to use this board in the project it was intended for, we will need USB support, so I took a shot at getting USB working... o updated hints.at91rm9200 (ohci controller is on ASB) crash in usbd_transfer() because of missing device->bus->buffer_dmatag o allocate dma tags in ohci_atmelarm_attach() (inspired by ohci_pci.c) o destroy dma tags in ohc_atmelarm_detach() --Boundary-00=_IZiYFkN+IcqicJ4 Content-Type: text/plain; charset="iso-8859-1"; name="daan_usb_patch.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="daan_usb_patch.diff" --- sys/arm/at91/ohci_atmelarm.c.org Mon Nov 20 16:32:05 2006 +++ sys/arm/at91/ohci_atmelarm.c Mon Nov 20 17:45:03 2006 @@ -28,7 +28,9 @@ #include #include #include +#include #include +#include #include #include #include @@ -99,6 +101,30 @@ } device_set_ivars(sc->sc_ohci.sc_bus.bdev, &sc->sc_ohci.sc_bus); + /* Allocate a parent dma tag for DMA maps */ + err = bus_dma_tag_create(bus_get_dma_tag(dev), 1, 0, + BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, NULL, + BUS_SPACE_MAXSIZE_32BIT, USB_DMA_NSEG, BUS_SPACE_MAXSIZE_32BIT, 0, + NULL, NULL, &sc->sc_ohci.sc_bus.parent_dmatag); + if (err) { + device_printf(dev, "Could not allocate parent DMA tag (%d)\n", + err); + err = ENXIO; + goto error; + } + + /* Allocate a dma tag for transfer buffers */ + err = bus_dma_tag_create(sc->sc_ohci.sc_bus.parent_dmatag, 1, 0, + BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, NULL, + BUS_SPACE_MAXSIZE_32BIT, USB_DMA_NSEG, BUS_SPACE_MAXSIZE_32BIT, 0, + busdma_lock_mutex, &Giant, &sc->sc_ohci.sc_bus.buffer_dmatag); + if (err) { + device_printf(dev, "Could not allocate transfer tag (%d)\n", + err); + err = ENXIO; + goto error; + } + err = bus_setup_intr(dev, sc->sc_ohci.irq_res, INTR_TYPE_BIO, ohci_intr, sc, &sc->sc_ohci.ih); if (err) { @@ -158,6 +184,12 @@ bus_teardown_intr(dev, sc->sc_ohci.irq_res, sc->sc_ohci.ih); sc->sc_ohci.ih = NULL; } + + if (sc->sc_ohci.sc_bus.parent_dmatag != NULL) + bus_dma_tag_destroy(sc->sc_ohci.sc_bus.parent_dmatag); + if (sc->sc_ohci.sc_bus.buffer_dmatag != NULL) + bus_dma_tag_destroy(sc->sc_ohci.sc_bus.buffer_dmatag); + if (sc->sc_ohci.sc_bus.bdev) { device_delete_child(dev, sc->sc_ohci.sc_bus.bdev); sc->sc_ohci.sc_bus.bdev = NULL; --- sys/arm/at91/kb920x_machdep.c.org Mon Nov 20 16:24:03 2006 +++ sys/arm/at91/kb920x_machdep.c Mon Nov 20 19:08:39 2006 @@ -167,14 +167,14 @@ * initialization is done. However, the AT91 resource allocation * system doesn't know how to use pmap_mapdev() yet. */ -#if 0 +#if 1 { /* * Add the ohci controller, and anything else that might be * on this chip select for a VA/PA mapping. */ AT91RM92_OHCI_BASE, - AT91RM92_OHCI_BASE, + AT91RM92_OHCI_PA_BASE, AT91RM92_OHCI_SIZE, VM_PROT_READ|VM_PROT_WRITE, PTE_NOCACHE, --- sys/arm/at91/hints.at91rm9200.org Mon Nov 20 16:33:33 2006 +++ sys/arm/at91/hints.at91rm9200 Mon Nov 20 22:29:20 2006 @@ -64,5 +64,5 @@ # USB host (ohci) #??? maybe this needs to be on asb instead of apb -hint.ohci.at="apb" +hint.ohci.at="asb" hint.ohci.maddr="0x00300000" --- sys/arm/at91/at91rm92reg.h.org Mon Nov 20 22:52:56 2006 +++ sys/arm/at91/at91rm92reg.h Mon Nov 20 19:13:26 2006 @@ -337,6 +337,7 @@ #define AT91RM92_TC1C2_BASE 0xffa4080 #define AT91RM92_OHCI_BASE 0xdfe00000 +#define AT91RM92_OHCI_PA_BASE 0x00300000 #define AT91RM92_OHCI_SIZE 0x00100000 #define AT91C_MASTER_CLOCK 60000000 --- sys/arm/conf/KB920X.org Fri Nov 17 16:06:37 2006 +++ sys/arm/conf/KB920X Mon Nov 20 22:05:16 2006 @@ -82,3 +82,18 @@ # device at91_twi # TWI: Two Wire Interface device at91_spi # SPI: device spibus + + +device usb +device ohci + +#device ugen + +#device scbus +#device da +#device umass + +device axe +#device bpf + + --Boundary-00=_IZiYFkN+IcqicJ4-- From owner-freebsd-arm@FreeBSD.ORG Mon Nov 20 22:13:19 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 2EFE116A492 for ; Mon, 20 Nov 2006 22:13:19 +0000 (UTC) (envelope-from Danovitsch@vitsch.net) Received: from amsfep12-int.chello.nl (amsfep17-int.chello.nl [213.46.243.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3962243D5D for ; Mon, 20 Nov 2006 22:12:56 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Tuinhuisje.Vitsch.net ([62.195.87.223]) by amsfep12-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20061120221306.VAUS1928.amsfep12-int.chello.nl@Tuinhuisje.Vitsch.net>; Mon, 20 Nov 2006 23:13:06 +0100 Received: from self (f23025.upc-f.chello.nl [80.56.23.25]) (authenticated bits=0) by Tuinhuisje.Vitsch.net (8.13.1/8.13.1) with ESMTP id kAKMCnCQ061082; Mon, 20 Nov 2006 23:12:54 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: "M. Warner Losh" Date: Mon, 20 Nov 2006 23:12:57 +0100 User-Agent: KMail/1.9.1 References: <7380637.post@talk.nabble.com> <20061116.093638.63053940.imp@bsdimp.com> <200611202303.52817.Danovitsch@vitsch.net> In-Reply-To: <200611202303.52817.Danovitsch@vitsch.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611202312.58007.Danovitsch@vitsch.net> Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 20 Nov 2006 22:13:19 -0000 On Monday 20 November 2006 23:03, Daan Vreeken [PA4DAN] wrote: > Hi Warner (and the list), > > On Thursday 16 November 2006 17:36, M. Warner Losh wrote: > > In message: <7380637.post@talk.nabble.com> > > > > Zuy writes: > > : How I'm soldering board based on AT91RM9200 with 16mb SDRAM and othe > > : standartpPeripherals(USB, SD, UART ...). I'm going to run FreeBSD on > > : this board, but unfortunately I do not know how to start. > > : I havn't found any files connected with AT91RM9200 in FreeBSD6.0 Stable > > : source files directory. > > : I found from this board that freebsd works on at91rm9200. > > > > Yes. It does. FreeBSD-current has the most up to date tested code > > for this platform. FreeBSD 6.2 will contain the tools you need to > > build it, as well as a slightly less advanced version (the freeze date > > for 6.2 was a while ago). 6.3 is likely to have even more advanced > > support. > > ... > > > Here's the broad outlines. > > ... followed by a very nice ARM-introduction :) ... > > > Feel free to ask questions. the more people that ask, the bigger my > > collection of email on the topic gets, and the easier it will be for > > me to synthesize a tutorial. Also, if there are areas that I've been > > vague, please don't hesitate to let me know. > > This email got me to dust-off the KB9202B board my company bought a while > back for a project that hasn't started (yet). With your email it was quite > easy to get the board to work. I now use the original Kwikbyte boot loader > to load the kernel with tftp. After that the kernel mounts root over NFS > and everything works like a charm. > If I am going to use this board in the project it was intended for, we will > need USB support, so I took a shot at getting USB working... Stupid me, I pressed [ctrl+enter] while typing this email instead of [enter], so a piece of the intended story didn't make it into the first email :-s The conclusion : I've got USB to work. What I changed : > o updated hints.at91rm9200 (ohci controller is on ASB) o I've added a mapping for the OHCI controller in kb920x_machdep.c that maps the controller to 0xdfe00000 (just below where the IO region is mapped) After enabling the ohci controller it crashed in usbd_transfer() because of missing device->bus->buffer_dmatag so I added : > o allocate dma tags in ohci_atmelarm_attach() > (inspired by ohci_pci.c) > o destroy dma tags in ohc_atmelarm_detach() With these changes USB is now working on the board I have here. I have succesfully read the entire content of a memory stick inside a digital camera with it. There are some problems though (not sure yet where they come from). I have a if_axe device here that doesn't want to work. (Will investigate further). Also, I'm not sure if I need to tell the kernel more about the VA/PA mapping I have added and wheter or not there is a better way/place to do the mapping. Any comments are appreciated. If time permits I'll try to implement a driver for the USB Device Port as it could also come in handy when we're going to use these boards. btw: This work is sponsored by Vitsch Electronics. -- Daan From owner-freebsd-arm@FreeBSD.ORG Tue Nov 21 11:14:56 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 689EF16A47B for ; Tue, 21 Nov 2006 11:14:56 +0000 (UTC) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (cognet.ci0.org [80.65.224.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1B8B43DD2 for ; Tue, 21 Nov 2006 11:13:47 +0000 (GMT) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.7/8.13.4) with ESMTP id kALBTRqx087077; Tue, 21 Nov 2006 12:29:28 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.7/8.13.4/Submit) id kALBTQuL087076; Tue, 21 Nov 2006 12:29:27 +0100 (CET) (envelope-from mlfbsd) Date: Tue, 21 Nov 2006 12:29:26 +0100 From: Olivier Houchard To: "Daan Vreeken [PA4DAN]" Message-ID: <20061121112926.GA87021@ci0.org> References: <7380637.post@talk.nabble.com> <20061116.093638.63053940.imp@bsdimp.com> <200611202303.52817.Danovitsch@vitsch.net> <200611202312.58007.Danovitsch@vitsch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200611202312.58007.Danovitsch@vitsch.net> User-Agent: Mutt/1.4.1i Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 21 Nov 2006 11:14:56 -0000 Hi Daan, On Mon, Nov 20, 2006 at 11:12:57PM +0100, Daan Vreeken [PA4DAN] wrote: > On Monday 20 November 2006 23:03, Daan Vreeken [PA4DAN] wrote: > > Hi Warner (and the list), > > > > On Thursday 16 November 2006 17:36, M. Warner Losh wrote: > > > In message: <7380637.post@talk.nabble.com> > > > > > > Zuy writes: > > > : How I'm soldering board based on AT91RM9200 with 16mb SDRAM and othe > > > : standartpPeripherals(USB, SD, UART ...). I'm going to run FreeBSD on > > > : this board, but unfortunately I do not know how to start. > > > : I havn't found any files connected with AT91RM9200 in FreeBSD6.0 Stable > > > : source files directory. > > > : I found from this board that freebsd works on at91rm9200. > > > > > > Yes. It does. FreeBSD-current has the most up to date tested code > > > for this platform. FreeBSD 6.2 will contain the tools you need to > > > build it, as well as a slightly less advanced version (the freeze date > > > for 6.2 was a while ago). 6.3 is likely to have even more advanced > > > support. > > > > ... > > > > > Here's the broad outlines. > > > > ... followed by a very nice ARM-introduction :) ... > > > > > Feel free to ask questions. the more people that ask, the bigger my > > > collection of email on the topic gets, and the easier it will be for > > > me to synthesize a tutorial. Also, if there are areas that I've been > > > vague, please don't hesitate to let me know. > > > > This email got me to dust-off the KB9202B board my company bought a while > > back for a project that hasn't started (yet). With your email it was quite > > easy to get the board to work. I now use the original Kwikbyte boot loader > > to load the kernel with tftp. After that the kernel mounts root over NFS > > and everything works like a charm. > > If I am going to use this board in the project it was intended for, we will > > need USB support, so I took a shot at getting USB working... > > Stupid me, I pressed [ctrl+enter] while typing this email instead of [enter], > so a piece of the intended story didn't make it into the first email :-s > > The conclusion : I've got USB to work. !! That's great news ! Thanks a lot for doing this. > What I changed : > > o updated hints.at91rm9200 (ohci controller is on ASB) > o I've added a mapping for the OHCI controller in kb920x_machdep.c that > maps the controller to 0xdfe00000 (just below where the IO region is > mapped) > > After enabling the ohci controller it crashed in usbd_transfer() because of > missing device->bus->buffer_dmatag so I added : > > o allocate dma tags in ohci_atmelarm_attach() > > (inspired by ohci_pci.c) > > o destroy dma tags in ohc_atmelarm_detach() > > With these changes USB is now working on the board I have here. I have > succesfully read the entire content of a memory stick inside a digital camera > with it. There are some problems though (not sure yet where they come from). > I have a if_axe device here that doesn't want to work. (Will investigate > further). > Not working as in failed to probe/attach, or fail to transfer ? If it is fail to transfer, a common issue on arm is the lack of proper use of bus_dmamap_sync(), because arm is the only arch which really needs those (I don't know the USB code enough to tell if it's the problem here, but it's an usual suspect). > Also, I'm not sure if I need to tell the kernel more about the VA/PA mapping I > have added and wheter or not there is a better way/place to do the mapping. > Any comments are appreciated. Given the static nature of the OHCI controller, I think it's OK to do as you did, that's KVA we won't use anyway. > If time permits I'll try to implement a driver for the USB Device Port as it > could also come in handy when we're going to use these boards. > That would be great. > btw: This work is sponsored by Vitsch Electronics. > We'll make sure it appears in the commit log. Thanks a lot ! Olivier > -- > Daan > _______________________________________________ > 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 Tue Nov 21 17:23:02 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 CBE5616D5FA for ; Tue, 21 Nov 2006 17:21:31 +0000 (UTC) (envelope-from Danovitsch@vitsch.net) Received: from amsfep14-int.chello.nl (amsfep17-int.chello.nl [213.46.243.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F0B143E7B for ; Tue, 21 Nov 2006 17:17:10 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Tuinhuisje.Vitsch.net ([62.195.87.223]) by amsfep14-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20061121171728.JIBD7165.amsfep14-int.chello.nl@Tuinhuisje.Vitsch.net>; Tue, 21 Nov 2006 18:17:28 +0100 Received: from self (f23025.upc-f.chello.nl [80.56.23.25]) (authenticated bits=0) by Tuinhuisje.Vitsch.net (8.13.1/8.13.1) with ESMTP id kALHHHq6064165; Tue, 21 Nov 2006 18:17:22 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: Olivier Houchard Date: Tue, 21 Nov 2006 18:17:23 +0100 User-Agent: KMail/1.9.1 References: <7380637.post@talk.nabble.com> <200611202312.58007.Danovitsch@vitsch.net> <20061121112926.GA87021@ci0.org> In-Reply-To: <20061121112926.GA87021@ci0.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611211817.23949.Danovitsch@vitsch.net> Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 21 Nov 2006 17:23:02 -0000 Hi Olivier, On Tuesday 21 November 2006 12:29, you wrote: > Hi Daan, > > On Mon, Nov 20, 2006 at 11:12:57PM +0100, Daan Vreeken [PA4DAN] wrote: > > On Monday 20 November 2006 23:03, Daan Vreeken [PA4DAN] wrote: > > > Hi Warner (and the list), > > > > > > On Thursday 16 November 2006 17:36, M. Warner Losh wrote: > > > > In message: <7380637.post@talk.nabble.com> > > > > > > > > Zuy writes: > > > > : How I'm soldering board based on AT91RM9200 with 16mb SDRAM and > > > > : othe standartpPeripherals(USB, SD, UART ...). I'm going to run > > > > : FreeBSD on this board, but unfortunately I do not know how to > > > > : start. > > > > : I havn't found any files connected with AT91RM9200 in FreeBSD6.0 > > > > : Stable source files directory. > > > > : I found from this board that freebsd works on at91rm9200. > > > > > > > > Yes. It does. FreeBSD-current has the most up to date tested code > > > > for this platform. FreeBSD 6.2 will contain the tools you need to > > > > build it, as well as a slightly less advanced version (the freeze > > > > date for 6.2 was a while ago). 6.3 is likely to have even more > > > > advanced support. > > > > > > ... > > > > > > > Here's the broad outlines. > > > > > > ... followed by a very nice ARM-introduction :) ... > > > > > > > Feel free to ask questions. the more people that ask, the bigger my > > > > collection of email on the topic gets, and the easier it will be for > > > > me to synthesize a tutorial. Also, if there are areas that I've been > > > > vague, please don't hesitate to let me know. > > > > > > This email got me to dust-off the KB9202B board my company bought a > > > while back for a project that hasn't started (yet). With your email it > > > was quite easy to get the board to work. I now use the original > > > Kwikbyte boot loader to load the kernel with tftp. After that the > > > kernel mounts root over NFS and everything works like a charm. > > > If I am going to use this board in the project it was intended for, we > > > will need USB support, so I took a shot at getting USB working... > > > > Stupid me, I pressed [ctrl+enter] while typing this email instead of > > [enter], so a piece of the intended story didn't make it into the first > > email :-s > > > > The conclusion : I've got USB to work. > > !! > That's great news ! > Thanks a lot for doing this. > > > What I changed : > > > o updated hints.at91rm9200 (ohci controller is on ASB) > > > > o I've added a mapping for the OHCI controller in kb920x_machdep.c that > > maps the controller to 0xdfe00000 (just below where the IO region is > > mapped) > > > > After enabling the ohci controller it crashed in usbd_transfer() because > > of > > > > missing device->bus->buffer_dmatag so I added : > > > o allocate dma tags in ohci_atmelarm_attach() > > > (inspired by ohci_pci.c) > > > o destroy dma tags in ohc_atmelarm_detach() > > > > With these changes USB is now working on the board I have here. I have > > succesfully read the entire content of a memory stick inside a digital > > camera with it. There are some problems though (not sure yet where they > > come from). I have a if_axe device here that doesn't want to work. (Will > > investigate further). > > Not working as in failed to probe/attach, or fail to transfer ? If it is > fail to transfer, a common issue on arm is the lack of proper use of > bus_dmamap_sync(), because arm is the only arch which really needs those (I > don't know the USB code enough to tell if it's the problem here, but it's > an usual suspect). The device does attach, here is the dmesg snippet : axe0: on uhub0 axe0: vendor 0x0b95 product 0x1720, rev 2.00/0.01, addr 2 axe0: Ethernet address: 00:50:fc:bd:17:ac axe0: if_start running deferred for Giant The reported mac address is the same as when I plug the device into an i386 machine, so it looks as if byte-ordering is also done where needed upto here. I have added some printf's to the rxeof and txeof functions but they don't get printed. Playing around with ifconfig gives the following : # ifconfig axe0 axe0: flags=108802 mtu 1500 ether 00:50:fc:bd:17:ac # ifconfig axe0 axe0: flags=108802 mtu 1500 ether 00:50:fc:bd:17:ac (at least it's consistent :) # ifconfig axe0 up axe0: getting interface handle failed # ifconfig axe0 doon axe_rxeof() called axe0: getting interface handle failed # ifconfig axe0 up axe0: getting interface handle failed # ifconfig axe0 down axe_rxeof() called axe0: getting interface handle failed # ifconfig axe0 up axe0: getting interface handle failed # axe0: at uhub0 port 1 (addr 2) disconnected axe_rxeof() called And unplugging the device after this crashes the board. While typing this email I've been testing some more. Just now and then ukphy also attaches when I plug in the device : axe0: on uhub0 axe0: vendor 0x0b95 product 0x1720, rev 2.00/0.01, addr 2 miibus1: on axe0 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto axe0: Ethernet address: 00:50:fc:bd:17:ac axe0: if_start running deferred for Giant After that, assigning an ip address to the interface seems to work and the link LED even lights up. Starting a "ping" even shows txeof() being called. (Still no rxeof() though). Unplugging the device in this state works as it should. Another couple of plug & unplug's show : axe0: on uhu0 axe0: vendor 0x0b95 product 0x1720, rev 2.00/0.01, addr 2 axe0: MII without any PHY! device_attach: axe0 attach returned 6 axe0: at uhub0 port 1 (addr 2) disconnected axe0: on uhub0 axe0: vendor 0x0b95 product 0x1720, rev 2.00/0.01, addr 2 miibus1: on axe0 ukphy1: on miibus1 ukphy1: ifmedia_set: no match for 0x0/0xfffffff panic: ifmedia_set KDB: enter: panic [thread pid 22 tid 100025 ] Stopped at kdb_enter+0x3c: ldrb r15, [r15, r15, ror r15]! db> So it seems that if_axe itself at least attaches without a problem, but the interaction with mii seems to be purely random. Apart from that I have another problem with this KB9202B board. I use the original boot loader that was provided by Kwikbyte and load the kernel using TFTP. I would really like to keep using TFTP for it's speed, but for some reason not all kernels I have created are bootable... I suspect this to be a problem in the boot loader. When I change the configuration of my kernel (add a device, or remove one) all of a sudden the kernel won't boot. The boot loader doesn't complain during the TFTP-transfer, but after typing "e 0x20000000" to execute, the board hangs without a single letter being output on the serial console. Has anyone else seen this problem? Is there a way to fix the TFTP problems I am seeing? (Or did I really mess up with compiling?) > > Also, I'm not sure if I need to tell the kernel more about the VA/PA > > mapping I have added and wheter or not there is a better way/place to do > > the mapping. Any comments are appreciated. > > Given the static nature of the OHCI controller, I think it's OK to do as > you did, that's KVA we won't use anyway. Ok. Great. > > If time permits I'll try to implement a driver for the USB Device Port as > > it could also come in handy when we're going to use these boards. > > That would be great. > > > btw: This work is sponsored by Vitsch Electronics. > > We'll make sure it appears in the commit log. Thanks a lot ! > > Olivier -- Daan From owner-freebsd-arm@FreeBSD.ORG Tue Nov 21 17:42:31 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 C20DF16B620 for ; Tue, 21 Nov 2006 17:42:31 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 295D243D68 for ; Tue, 21 Nov 2006 17:42:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kALHaIo2079056; Tue, 21 Nov 2006 10:36:19 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 21 Nov 2006 10:37:00 -0700 (MST) Message-Id: <20061121.103700.1152757768.imp@bsdimp.com> To: Danovitsch@vitsch.net From: "M. Warner Losh" In-Reply-To: <200611211817.23949.Danovitsch@vitsch.net> References: <200611202312.58007.Danovitsch@vitsch.net> <20061121112926.GA87021@ci0.org> <200611211817.23949.Danovitsch@vitsch.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 21 Nov 2006 10:36:19 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 21 Nov 2006 17:42:31 -0000 In message: <200611211817.23949.Danovitsch@vitsch.net> "Daan Vreeken [PA4DAN]" writes: : Apart from that I have another problem with this KB9202B board. I use the : original boot loader that was provided by Kwikbyte and load the kernel using : TFTP. I would really like to keep using TFTP for it's speed, but for some : reason not all kernels I have created are bootable... : I suspect this to be a problem in the boot loader. When I change the : configuration of my kernel (add a device, or remove one) all of a sudden the : kernel won't boot. The boot loader doesn't complain during the TFTP-transfer, : but after typing "e 0x20000000" to execute, the board hangs without a single : letter being output on the serial console. : Has anyone else seen this problem? : Is there a way to fix the TFTP problems I am seeing? : (Or did I really mess up with compiling?) kwikbyte's tftp boot code sucks. I fixed a lot of bugs with it and you can find the results in bootiic :-) In fact, I started with kwikbyte's boot loader and have made the original one fit in about ~5k instead of 16k. I've also added some functionality to it and it takes up 8k or so. Warner From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 14:05:03 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 4006616A403 for ; Wed, 22 Nov 2006 14:05:03 +0000 (UTC) (envelope-from Danovitsch@vitsch.net) Received: from amsfep15-int.chello.nl (amsfep17-int.chello.nl [213.46.243.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 667F643D72 for ; Wed, 22 Nov 2006 14:04:28 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Tuinhuisje.Vitsch.net ([62.195.87.223]) by amsfep15-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20061122140455.VQCJ1751.amsfep15-int.chello.nl@Tuinhuisje.Vitsch.net>; Wed, 22 Nov 2006 15:04:55 +0100 Received: from self (f23025.upc-f.chello.nl [80.56.23.25]) (authenticated bits=0) by Tuinhuisje.Vitsch.net (8.13.1/8.13.1) with ESMTP id kAME4lGP067549; Wed, 22 Nov 2006 15:04:48 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: "M. Warner Losh" Date: Wed, 22 Nov 2006 15:04:51 +0100 User-Agent: KMail/1.9.1 References: <200611202312.58007.Danovitsch@vitsch.net> <200611211817.23949.Danovitsch@vitsch.net> <20061121.103700.1152757768.imp@bsdimp.com> In-Reply-To: <20061121.103700.1152757768.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611221504.51893.Danovitsch@vitsch.net> Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 22 Nov 2006 14:05:03 -0000 On Tuesday 21 November 2006 18:37, you wrote: > In message: <200611211817.23949.Danovitsch@vitsch.net> > > "Daan Vreeken [PA4DAN]" writes: > : Apart from that I have another problem with this KB9202B board. I use the > : original boot loader that was provided by Kwikbyte and load the kernel > : using TFTP. I would really like to keep using TFTP for it's speed, but > : for some reason not all kernels I have created are bootable... > : I suspect this to be a problem in the boot loader. When I change the > : configuration of my kernel (add a device, or remove one) all of a sudden > : the kernel won't boot. The boot loader doesn't complain during the > : TFTP-transfer, but after typing "e 0x20000000" to execute, the board > : hangs without a single letter being output on the serial console. > : Has anyone else seen this problem? > : Is there a way to fix the TFTP problems I am seeing? > : (Or did I really mess up with compiling?) > > kwikbyte's tftp boot code sucks. I fixed a lot of bugs with it and > you can find the results in bootiic :-) In fact, I started with > kwikbyte's boot loader and have made the original one fit in about ~5k > instead of 16k. I've also added some functionality to it and it takes > up 8k or so. > > Warner Changing the boot loader indeed solved the problems I was seeing. It's also nice to have a progress indicator while downloading and to actually see errors when things go wrong :) Thanks, Daan From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 14:26:32 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 D535D16A407 for ; Wed, 22 Nov 2006 14:26:32 +0000 (UTC) (envelope-from Danovitsch@vitsch.net) Received: from amsfep20-int.chello.nl (amsfep20-int.chello.nl [62.179.120.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16B1643D58 for ; Wed, 22 Nov 2006 14:26:00 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Tuinhuisje.Vitsch.net ([62.195.87.223]) by amsfep20-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20061122142627.FWYU7198.amsfep20-int.chello.nl@Tuinhuisje.Vitsch.net>; Wed, 22 Nov 2006 15:26:27 +0100 Received: from self (f23025.upc-f.chello.nl [80.56.23.25]) (authenticated bits=0) by Tuinhuisje.Vitsch.net (8.13.1/8.13.1) with ESMTP id kAMEQJhf067602; Wed, 22 Nov 2006 15:26:19 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: Olivier Houchard Date: Wed, 22 Nov 2006 15:26:24 +0100 User-Agent: KMail/1.9.1 References: <7380637.post@talk.nabble.com> <200611202312.58007.Danovitsch@vitsch.net> <20061121112926.GA87021@ci0.org> In-Reply-To: <20061121112926.GA87021@ci0.org> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_Q4FZFhGJxDJPQNe" Message-Id: <200611221526.24471.Danovitsch@vitsch.net> Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 22 Nov 2006 14:26:32 -0000 --Boundary-00=_Q4FZFhGJxDJPQNe Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Tuesday 21 November 2006 12:29, you wrote: > Hi Daan, > > On Mon, Nov 20, 2006 at 11:12:57PM +0100, Daan Vreeken [PA4DAN] wrote: > > On Monday 20 November 2006 23:03, Daan Vreeken [PA4DAN] wrote: > > > Hi Warner (and the list), > > > > > > On Thursday 16 November 2006 17:36, M. Warner Losh wrote: > > > > In message: <7380637.post@talk.nabble.com> > > > > > > > > Zuy writes: > > > > : How I'm soldering board based on AT91RM9200 with 16mb SDRAM and > > > > : othe standartpPeripherals(USB, SD, UART ...). I'm going to run > > > > : FreeBSD on this board, but unfortunately I do not know how to > > > > : start. > > > > : I havn't found any files connected with AT91RM9200 in FreeBSD6.0 > > > > : Stable source files directory. > > > > : I found from this board that freebsd works on at91rm9200. > > > > > > > > Yes. It does. FreeBSD-current has the most up to date tested code > > > > for this platform. FreeBSD 6.2 will contain the tools you need to > > > > build it, as well as a slightly less advanced version (the freeze > > > > date for 6.2 was a while ago). 6.3 is likely to have even more > > > > advanced support. > > > > > > ... > > > > > > > Here's the broad outlines. > > > > > > ... followed by a very nice ARM-introduction :) ... > > > > > > > Feel free to ask questions. the more people that ask, the bigger my > > > > collection of email on the topic gets, and the easier it will be for > > > > me to synthesize a tutorial. Also, if there are areas that I've been > > > > vague, please don't hesitate to let me know. > > > > > > This email got me to dust-off the KB9202B board my company bought a > > > while back for a project that hasn't started (yet). With your email it > > > was quite easy to get the board to work. I now use the original > > > Kwikbyte boot loader to load the kernel with tftp. After that the > > > kernel mounts root over NFS and everything works like a charm. > > > If I am going to use this board in the project it was intended for, we > > > will need USB support, so I took a shot at getting USB working... > > > > Stupid me, I pressed [ctrl+enter] while typing this email instead of > > [enter], so a piece of the intended story didn't make it into the first > > email :-s > > > > The conclusion : I've got USB to work. > > !! > That's great news ! > Thanks a lot for doing this. > > > What I changed : > > > o updated hints.at91rm9200 (ohci controller is on ASB) > > > > o I've added a mapping for the OHCI controller in kb920x_machdep.c that > > maps the controller to 0xdfe00000 (just below where the IO region is > > mapped) > > > > After enabling the ohci controller it crashed in usbd_transfer() because > > of > > > > missing device->bus->buffer_dmatag so I added : > > > o allocate dma tags in ohci_atmelarm_attach() > > > (inspired by ohci_pci.c) > > > o destroy dma tags in ohc_atmelarm_detach() > > > > With these changes USB is now working on the board I have here. I have > > succesfully read the entire content of a memory stick inside a digital > > camera with it. There are some problems though (not sure yet where they > > come from). I have a if_axe device here that doesn't want to work. (Will > > investigate further). > > Not working as in failed to probe/attach, or fail to transfer ? If it is > fail to transfer, a common issue on arm is the lack of proper use of > bus_dmamap_sync(), because arm is the only arch which really needs those (I > don't know the USB code enough to tell if it's the problem here, but it's > an usual suspect). I have been debugging the usb problems some more. Your were right in your assumption (thanks for the pointer) about lack of calls to bus_dmamap_sync(). In usbdi.c bus_dmamap_sync() does get used for transfers that move data from PC to USB and it is used for transfers that move data from USB to PC. But someone forgot that control transfers consist of possibly two data chunks : the request itself and optionally a buffer of data that should be transfered to or from the USB device. On requests to the control endpoint without additional data bus_dmamap_sync() didn't get called. For some reason my first tests with umass worked (due to enough cache poisening I guess). The attached patch adds a call to bus_dmamap_sync() to usbdi.c and now all devices I have tried work out of the box. I have successfully transfered large files using the if_axe driver and I have mounted several different umass devices. And once again: This work was sponsored by Vitsch Electronics. -- Daan --Boundary-00=_Q4FZFhGJxDJPQNe Content-Type: text/x-diff; charset="iso-8859-1"; name="daan_usbdi_patch.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="daan_usbdi_patch.diff" --- usbdi.c.org Wed Nov 22 11:40:46 2006 +++ usbdi.c Wed Nov 22 15:16:37 2006 @@ -377,6 +377,13 @@ xfer->buffer != xfer->allocbuf) memcpy(xfer->allocbuf, xfer->buffer, xfer->length); bus_dmamap_sync(tag, dmap->map, BUS_DMASYNC_PREWRITE); + } else { + /* + * Even if we have no data portion we still need to sync the + * dmamap for the request data in the SETUP packet + */ + if (xfer->rqflags & URQ_REQUEST) + bus_dmamap_sync(tag, dmap->map, BUS_DMASYNC_PREWRITE); } err = pipe->methods->transfer(xfer); if (err != USBD_IN_PROGRESS && err) { --Boundary-00=_Q4FZFhGJxDJPQNe-- From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 14:42:32 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 4CC3216A4AB for ; Wed, 22 Nov 2006 14:42:32 +0000 (UTC) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (cognet.ci0.org [80.65.224.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A67B43D6A for ; Wed, 22 Nov 2006 14:41:35 +0000 (GMT) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.7/8.13.4) with ESMTP id kAMEvwTF097276; Wed, 22 Nov 2006 15:57:58 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.7/8.13.4/Submit) id kAMEvv3S097275; Wed, 22 Nov 2006 15:57:57 +0100 (CET) (envelope-from mlfbsd) Date: Wed, 22 Nov 2006 15:57:57 +0100 From: Olivier Houchard To: "Daan Vreeken [PA4DAN]" Message-ID: <20061122145757.GA97202@ci0.org> References: <7380637.post@talk.nabble.com> <200611202312.58007.Danovitsch@vitsch.net> <20061121112926.GA87021@ci0.org> <200611221526.24471.Danovitsch@vitsch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200611221526.24471.Danovitsch@vitsch.net> User-Agent: Mutt/1.4.1i Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 22 Nov 2006 14:42:32 -0000 On Wed, Nov 22, 2006 at 03:26:24PM +0100, Daan Vreeken [PA4DAN] wrote: > On Tuesday 21 November 2006 12:29, you wrote: > > Hi Daan, > > > > On Mon, Nov 20, 2006 at 11:12:57PM +0100, Daan Vreeken [PA4DAN] wrote: > > > On Monday 20 November 2006 23:03, Daan Vreeken [PA4DAN] wrote: > > > > Hi Warner (and the list), > > > > > > > > On Thursday 16 November 2006 17:36, M. Warner Losh wrote: > > > > > In message: <7380637.post@talk.nabble.com> > > > > > > > > > > Zuy writes: > > > > > : How I'm soldering board based on AT91RM9200 with 16mb SDRAM and > > > > > : othe standartpPeripherals(USB, SD, UART ...). I'm going to run > > > > > : FreeBSD on this board, but unfortunately I do not know how to > > > > > : start. > > > > > : I havn't found any files connected with AT91RM9200 in FreeBSD6.0 > > > > > : Stable source files directory. > > > > > : I found from this board that freebsd works on at91rm9200. > > > > > > > > > > Yes. It does. FreeBSD-current has the most up to date tested code > > > > > for this platform. FreeBSD 6.2 will contain the tools you need to > > > > > build it, as well as a slightly less advanced version (the freeze > > > > > date for 6.2 was a while ago). 6.3 is likely to have even more > > > > > advanced support. > > > > > > > > ... > > > > > > > > > Here's the broad outlines. > > > > > > > > ... followed by a very nice ARM-introduction :) ... > > > > > > > > > Feel free to ask questions. the more people that ask, the bigger my > > > > > collection of email on the topic gets, and the easier it will be for > > > > > me to synthesize a tutorial. Also, if there are areas that I've been > > > > > vague, please don't hesitate to let me know. > > > > > > > > This email got me to dust-off the KB9202B board my company bought a > > > > while back for a project that hasn't started (yet). With your email it > > > > was quite easy to get the board to work. I now use the original > > > > Kwikbyte boot loader to load the kernel with tftp. After that the > > > > kernel mounts root over NFS and everything works like a charm. > > > > If I am going to use this board in the project it was intended for, we > > > > will need USB support, so I took a shot at getting USB working... > > > > > > Stupid me, I pressed [ctrl+enter] while typing this email instead of > > > [enter], so a piece of the intended story didn't make it into the first > > > email :-s > > > > > > The conclusion : I've got USB to work. > > > > !! > > That's great news ! > > Thanks a lot for doing this. > > > > > What I changed : > > > > o updated hints.at91rm9200 (ohci controller is on ASB) > > > > > > o I've added a mapping for the OHCI controller in kb920x_machdep.c that > > > maps the controller to 0xdfe00000 (just below where the IO region is > > > mapped) > > > > > > After enabling the ohci controller it crashed in usbd_transfer() because > > > of > > > > > > missing device->bus->buffer_dmatag so I added : > > > > o allocate dma tags in ohci_atmelarm_attach() > > > > (inspired by ohci_pci.c) > > > > o destroy dma tags in ohc_atmelarm_detach() > > > > > > With these changes USB is now working on the board I have here. I have > > > succesfully read the entire content of a memory stick inside a digital > > > camera with it. There are some problems though (not sure yet where they > > > come from). I have a if_axe device here that doesn't want to work. (Will > > > investigate further). > > > > Not working as in failed to probe/attach, or fail to transfer ? If it is > > fail to transfer, a common issue on arm is the lack of proper use of > > bus_dmamap_sync(), because arm is the only arch which really needs those (I > > don't know the USB code enough to tell if it's the problem here, but it's > > an usual suspect). > > I have been debugging the usb problems some more. Your were right in your > assumption (thanks for the pointer) about lack of calls to bus_dmamap_sync(). > In usbdi.c bus_dmamap_sync() does get used for transfers that move data from > PC to USB and it is used for transfers that move data from USB to PC. But > someone forgot that control transfers consist of possibly two data chunks : > the request itself and optionally a buffer of data that should be transfered > to or from the USB device. > On requests to the control endpoint without additional data bus_dmamap_sync() > didn't get called. For some reason my first tests with umass worked (due to > enough cache poisening I guess). > The attached patch adds a call to bus_dmamap_sync() to usbdi.c and now all > devices I have tried work out of the box. > I have successfully transfered large files using the if_axe driver and I have > mounted several different umass devices. > That's great to hear ! Hopefully I'll be able to look at this tonight. Thanks a lot ! > And once again: > This work was sponsored by Vitsch Electronics. > It's noted. Olivier > -- > Daan From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 16:50:56 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 D9BD616A412 for ; Wed, 22 Nov 2006 16:50:56 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 779C843D5A for ; Wed, 22 Nov 2006 16:50:26 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAMGmc2i001464; Wed, 22 Nov 2006 09:48:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 22 Nov 2006 09:49:21 -0700 (MST) Message-Id: <20061122.094921.-2076632274.imp@bsdimp.com> To: Danovitsch@vitsch.net From: "M. Warner Losh" In-Reply-To: <200611221504.51893.Danovitsch@vitsch.net> References: <200611211817.23949.Danovitsch@vitsch.net> <20061121.103700.1152757768.imp@bsdimp.com> <200611221504.51893.Danovitsch@vitsch.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 22 Nov 2006 09:48:39 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: At91rm9200 how to start with FreeBSD 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, 22 Nov 2006 16:50:56 -0000 In message: <200611221504.51893.Danovitsch@vitsch.net> "Daan Vreeken [PA4DAN]" writes: : On Tuesday 21 November 2006 18:37, you wrote: : > In message: <200611211817.23949.Danovitsch@vitsch.net> : > : > "Daan Vreeken [PA4DAN]" writes: : > : Apart from that I have another problem with this KB9202B board. I use the : > : original boot loader that was provided by Kwikbyte and load the kernel : > : using TFTP. I would really like to keep using TFTP for it's speed, but : > : for some reason not all kernels I have created are bootable... : > : I suspect this to be a problem in the boot loader. When I change the : > : configuration of my kernel (add a device, or remove one) all of a sudden : > : the kernel won't boot. The boot loader doesn't complain during the : > : TFTP-transfer, but after typing "e 0x20000000" to execute, the board : > : hangs without a single letter being output on the serial console. : > : Has anyone else seen this problem? : > : Is there a way to fix the TFTP problems I am seeing? : > : (Or did I really mess up with compiling?) : > : > kwikbyte's tftp boot code sucks. I fixed a lot of bugs with it and : > you can find the results in bootiic :-) In fact, I started with : > kwikbyte's boot loader and have made the original one fit in about ~5k : > instead of 16k. I've also added some functionality to it and it takes : > up 8k or so. : > : > Warner : : Changing the boot loader indeed solved the problems I was seeing. It's also : nice to have a progress indicator while downloading and to actually see : errors when things go wrong :) Glad to see you are enjoying my handiwork. I spent a lot of time on that.. Warner From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 17:45:25 2006 Return-Path: X-Original-To: arm@FreeBSD.ORG 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 392F516A403; Wed, 22 Nov 2006 17:45:25 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B719A43D6B; Wed, 22 Nov 2006 17:44:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAMHi0Fd002183; Wed, 22 Nov 2006 10:44:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 22 Nov 2006 10:44:43 -0700 (MST) Message-Id: <20061122.104443.1324583801.imp@bsdimp.com> To: kevlo@FreeBSD.ORG, sam@errno.com From: "M. Warner Losh" In-Reply-To: <200611221257.kAMCvHLT053236@repoman.freebsd.org> References: <200611221257.kAMCvHLT053236@repoman.freebsd.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 22 Nov 2006 10:44:00 -0700 (MST) Cc: arm@FreeBSD.ORG Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 22 Nov 2006 17:45:25 -0000 In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> Kevin Lo writes: : Bring in status led support for /dev/led/gpioled on Avila. : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) Maybe it is time to start thinking of a more generic GPIO framework that the led can plug into... I've started on one in the p4 tree for the atmel PIO. It is incomplete and just an API right now (no gpio bus that devices can attach to). Care to comment? Warner From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 18:03:29 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 9CD4516A412; Wed, 22 Nov 2006 18:03:29 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB11943E5C; Wed, 22 Nov 2006 17:59:49 +0000 (GMT) (envelope-from freebsd-arm@dino.sk) Received: from [192.168.16.241] (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by bsd.dino.sk with esmtp; Wed, 22 Nov 2006 18:59:40 +0100 id 0000001F.4564900C.00000656 From: Milan Obuch To: freebsd-arm@freebsd.org Date: Wed, 22 Nov 2006 18:58:55 +0100 User-Agent: KMail/1.9.4 References: <200611221257.kAMCvHLT053236@repoman.freebsd.org> <20061122.104443.1324583801.imp@bsdimp.com> In-Reply-To: <20061122.104443.1324583801.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611221858.55805.freebsd-arm@dino.sk> Cc: kevlo@freebsd.org, freebsd-arm@freebsd.org Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 22 Nov 2006 18:03:29 -0000 On Wednesday 22 November 2006 18:44, M. Warner Losh wrote: > In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> > > Kevin Lo writes: > : Bring in status led support for /dev/led/gpioled on Avila. > : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) > > Maybe it is time to start thinking of a more generic GPIO framework > that the led can plug into... > > I've started on one in the p4 tree for the atmel PIO. It is > incomplete and just an API right now (no gpio bus that devices can > attach to). Care to comment? > > Warner I did some work based on older code from some FreeBSD based work with some influence from OpenBSD. It uses gpio bus, gpio controller and gpio control primitives. Currently it works with WRAP's geode controller and another LPC SuperI/O GPIO controller. If you could tell me how to access your work (no experience with p4 tree) I will be able to integrate them together. Or I can use your work as an improvement. Either way, I would like to get my work put into official repository, but it needs some refinement. Regards, Milan -- This address is used only for mailing list response. Do not send any personal messages to it, use milan in address instead. From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 18:04:12 2006 Return-Path: X-Original-To: freebsd-arm@FreeBSD.ORG 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 0182016A492 for ; Wed, 22 Nov 2006 18:04:12 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76EA543EBF for ; Wed, 22 Nov 2006 18:00:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAMHunI5002360; Wed, 22 Nov 2006 10:56:50 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 22 Nov 2006 10:57:33 -0700 (MST) Message-Id: <20061122.105733.1564840155.imp@bsdimp.com> To: Danovitsch@vitsch.net From: "M. Warner Losh" In-Reply-To: <200611221526.24471.Danovitsch@vitsch.net> References: <200611202312.58007.Danovitsch@vitsch.net> <20061121112926.GA87021@ci0.org> <200611221526.24471.Danovitsch@vitsch.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 22 Nov 2006 10:56:51 -0700 (MST) Cc: freebsd-arm@FreeBSD.ORG Subject: Re: At91rm9200 how to start with FreeBSD 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, 22 Nov 2006 18:04:12 -0000 committed, thanks! Warner From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 19:13:21 2006 Return-Path: X-Original-To: arm@FreeBSD.ORG 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 5F7B116A47B; Wed, 22 Nov 2006 19:13:21 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8139043D55; Wed, 22 Nov 2006 19:12:50 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (libe0ybn7xe8lth5@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id kAMJDD6a063441; Wed, 22 Nov 2006 11:13:13 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id kAMJDA2w063440; Wed, 22 Nov 2006 11:13:10 -0800 (PST) (envelope-from jmg) Date: Wed, 22 Nov 2006 11:13:10 -0800 From: John-Mark Gurney To: "M. Warner Losh" Message-ID: <20061122191310.GN9291@funkthat.com> Mail-Followup-To: "M. Warner Losh" , kevlo@FreeBSD.ORG, sam@errno.com, arm@FreeBSD.ORG, Poul-Henning Kamp References: <200611221257.kAMCvHLT053236@repoman.freebsd.org> <20061122.104443.1324583801.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061122.104443.1324583801.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: arm@FreeBSD.ORG, kevlo@FreeBSD.ORG, Poul-Henning Kamp Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 19:13:21 -0000 Warner Losh wrote this message on Wed, Nov 22, 2006 at 10:44 -0700: > In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> > Kevin Lo writes: > : Bring in status led support for /dev/led/gpioled on Avila. > : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) > > Maybe it is time to start thinking of a more generic GPIO framework > that the led can plug into... > > I've started on one in the p4 tree for the atmel PIO. It is > incomplete and just an API right now (no gpio bus that devices can > attach to). Care to comment? What happened to the work that phk, you and I worked on at BSDcan? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 20:58:02 2006 Return-Path: X-Original-To: arm@FreeBSD.ORG 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 33C2E16A417; Wed, 22 Nov 2006 20:58:02 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 331A743D46; Wed, 22 Nov 2006 20:57:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 2CC9A170C1; Wed, 22 Nov 2006 20:58:00 +0000 (UTC) To: John-Mark Gurney From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 22 Nov 2006 11:13:10 PST." <20061122191310.GN9291@funkthat.com> Date: Wed, 22 Nov 2006 20:58:00 +0000 Message-ID: <49211.1164229080@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: arm@FreeBSD.ORG, kevlo@FreeBSD.ORG Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 22 Nov 2006 20:58:02 -0000 In message <20061122191310.GN9291@funkthat.com>, John-Mark Gurney writes: >Warner Losh wrote this message on Wed, Nov 22, 2006 at 10:44 -0700: >> In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> >> Kevin Lo writes: >> : Bring in status led support for /dev/led/gpioled on Avila. >> : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) >> >> Maybe it is time to start thinking of a more generic GPIO framework >> that the led can plug into... >> >> I've started on one in the p4 tree for the atmel PIO. It is >> incomplete and just an API right now (no gpio bus that devices can >> attach to). Care to comment? > >What happened to the work that phk, you and I worked on at BSDcan? Nothing much. It's still pending in the todo list :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 21:35:18 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 D7C8E16A4A0; Wed, 22 Nov 2006 21:35:18 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D609442D7; Wed, 22 Nov 2006 21:20:12 +0000 (GMT) (envelope-from freebsd-arm@dino.sk) Received: from [192.168.16.241] (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by bsd.dino.sk with esmtp; Wed, 22 Nov 2006 22:20:33 +0100 id 00000078.4564BF21.00000B39 From: Milan Obuch To: freebsd-arm@freebsd.org Date: Wed, 22 Nov 2006 22:20:18 +0100 User-Agent: KMail/1.9.4 References: <49211.1164229080@critter.freebsd.dk> In-Reply-To: <49211.1164229080@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611222220.19638.freebsd-arm@dino.sk> Cc: kevlo@freebsd.org, Poul-Henning Kamp , freebsd-arm@freebsd.org Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 22 Nov 2006 21:35:19 -0000 On Wednesday 22 November 2006 21:58, Poul-Henning Kamp wrote: > In message <20061122191310.GN9291@funkthat.com>, John-Mark Gurney writes: > >Warner Losh wrote this message on Wed, Nov 22, 2006 at 10:44 -0700: > >> In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> > >> > >> Kevin Lo writes: > >> : Bring in status led support for /dev/led/gpioled on Avila. > >> : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) > >> > >> Maybe it is time to start thinking of a more generic GPIO framework > >> that the led can plug into... > >> > >> I've started on one in the p4 tree for the atmel PIO. It is > >> incomplete and just an API right now (no gpio bus that devices can > >> attach to). Care to comment? > > > >What happened to the work that phk, you and I worked on at BSDcan? > > Nothing much. It's still pending in the todo list :-( Is it accessible anywhere? Regards, Milan -- This address is used only for mailing list response. Do not send any personal messages to it, use milan in address instead. From owner-freebsd-arm@FreeBSD.ORG Wed Nov 22 22:06:31 2006 Return-Path: X-Original-To: arm@FreeBSD.ORG 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 E094D16A403; Wed, 22 Nov 2006 22:06:31 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1127E43D97; Wed, 22 Nov 2006 22:05:34 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAMM3CLl005631; Wed, 22 Nov 2006 15:03:13 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 22 Nov 2006 15:03:53 -0700 (MST) Message-Id: <20061122.150353.1589020890.imp@bsdimp.com> To: gurney_j@resnet.uoregon.edu From: "M. Warner Losh" In-Reply-To: <20061122191310.GN9291@funkthat.com> References: <200611221257.kAMCvHLT053236@repoman.freebsd.org> <20061122.104443.1324583801.imp@bsdimp.com> <20061122191310.GN9291@funkthat.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 22 Nov 2006 15:03:15 -0700 (MST) Cc: arm@FreeBSD.ORG, kevlo@FreeBSD.ORG, phk@phk.freebsd.dk Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 22 Nov 2006 22:06:32 -0000 In message: <20061122191310.GN9291@funkthat.com> John-Mark Gurney writes: : Warner Losh wrote this message on Wed, Nov 22, 2006 at 10:44 -0700: : > In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> : > Kevin Lo writes: : > : Bring in status led support for /dev/led/gpioled on Avila. : > : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) : > : > Maybe it is time to start thinking of a more generic GPIO framework : > that the led can plug into... : > : > I've started on one in the p4 tree for the atmel PIO. It is : > incomplete and just an API right now (no gpio bus that devices can : > attach to). Care to comment? : : What happened to the work that phk, you and I worked on at BSDcan? This is a subset of that. Warner From owner-freebsd-arm@FreeBSD.ORG Thu Nov 23 04:31:35 2006 Return-Path: X-Original-To: arm@FreeBSD.org 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 658D216A403 for ; Thu, 23 Nov 2006 04:31:35 +0000 (UTC) (envelope-from kevlo@FreeBSD.org) Received: from ns.kevlo.org (ns.kevlo.org [203.74.190.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37C7643D49 for ; Thu, 23 Nov 2006 04:31:02 +0000 (GMT) (envelope-from kevlo@FreeBSD.org) Received: from [127.0.0.1] (kevlo@ns.kevlo.org [203.74.190.123]) (authenticated bits=0) by ns.kevlo.org (8.13.4/8.13.4) with ESMTP id kANCTopa024197 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 23 Nov 2006 12:29:55 GMT From: Kevin Lo To: "M. Warner Losh" In-Reply-To: <20061122.104443.1324583801.imp@bsdimp.com> References: <200611221257.kAMCvHLT053236@repoman.freebsd.org> <20061122.104443.1324583801.imp@bsdimp.com> Content-Type: text/plain Date: Thu, 23 Nov 2006 12:31:20 +0800 Message-Id: <1164256280.5038.14.camel@monet> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Cc: arm@FreeBSD.org Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 23 Nov 2006 04:31:35 -0000 M. Warner Losh wrote: > In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> > Kevin Lo writes: > : Bring in status led support for /dev/led/gpioled on Avila. > : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) > > Maybe it is time to start thinking of a more generic GPIO framework > that the led can plug into... I like the idea :-) Having an API for gpio drivers makes life easier when writing a driver. > I've started on one in the p4 tree for the atmel PIO. It is > incomplete and just an API right now (no gpio bus that devices can > attach to). Care to comment? Since OpenBSD implemented in their gpio(4) driver, how about improving your work based on OpenBSD's gpio driver? > Warner Kevin From owner-freebsd-arm@FreeBSD.ORG Thu Nov 23 06:41:55 2006 Return-Path: X-Original-To: arm@FreeBSD.org 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 133C416A407; Thu, 23 Nov 2006 06:41:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5055843D49; Thu, 23 Nov 2006 06:41:21 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAN6dL79010291; Wed, 22 Nov 2006 23:39:21 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 22 Nov 2006 23:40:05 -0700 (MST) Message-Id: <20061122.234005.723205711.imp@bsdimp.com> To: kevlo@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <1164256280.5038.14.camel@monet> References: <200611221257.kAMCvHLT053236@repoman.freebsd.org> <20061122.104443.1324583801.imp@bsdimp.com> <1164256280.5038.14.camel@monet> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 22 Nov 2006 23:39:22 -0700 (MST) Cc: arm@FreeBSD.org Subject: Re: cvs commit: src/sys/arm/conf AVILA src/sys/arm/xscale/ixp425 avila_led.c files.avila ixp425.c 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, 23 Nov 2006 06:41:55 -0000 In message: <1164256280.5038.14.camel@monet> Kevin Lo writes: : M. Warner Losh wrote: : > In message: <200611221257.kAMCvHLT053236@repoman.freebsd.org> : > Kevin Lo writes: : > : Bring in status led support for /dev/led/gpioled on Avila. : > : 1.1 +114 -0 src/sys/arm/xscale/ixp425/avila_led.c (new) : > : > Maybe it is time to start thinking of a more generic GPIO framework : > that the led can plug into... : : I like the idea :-) Having an API for gpio drivers makes life : easier when writing a driver. : : > I've started on one in the p4 tree for the atmel PIO. It is : > incomplete and just an API right now (no gpio bus that devices can : > attach to). Care to comment? : : Since OpenBSD implemented in their gpio(4) driver, how about improving : your work based on OpenBSD's gpio driver? I think it needs a little refinement still. There's two parts. I did the API, but not the internal kernel framework... Warner From owner-freebsd-arm@FreeBSD.ORG Fri Nov 24 00:42:56 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 C690316A412 for ; Fri, 24 Nov 2006 00:42:56 +0000 (UTC) (envelope-from daimon@dev-random.org) Received: from sharp.org (sharp.org [161.58.2.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7699243D45 for ; Fri, 24 Nov 2006 00:42:18 +0000 (GMT) (envelope-from daimon@dev-random.org) Received: from betty.wa.sharp.org (sharp.org [161.58.2.117]) by sharp.org (8.12.11.20060614/8.12.9) with ESMTP id kAO0gsTl061928 for ; Thu, 23 Nov 2006 17:42:55 -0700 (MST) Received: from betty.wa.sharp.org (2d30ffc1ee241b6ab4b50c9e48679bcd@localhost [127.0.0.1]) by betty.wa.sharp.org (8.13.6/8.13.3) with ESMTP id kAO0g9vb002965; Thu, 23 Nov 2006 16:42:16 -0800 (PST) (envelope-from daimon@dev-random.org) Received: (from djs@localhost) by betty.wa.sharp.org (8.13.6/8.13.6/Submit) id kAO0NBMT002584; Thu, 23 Nov 2006 16:23:11 -0800 (PST) (envelope-from daimon@dev-random.org) X-Authentication-Warning: betty.wa.sharp.org: djs set sender to daimon@dev-random.org using -f Date: Thu, 23 Nov 2006 16:23:10 -0800 From: David Sharp To: Doug Brewer Message-ID: <20061124002310.GA2324@mail.secure.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-arm@freebsd.org Subject: Re: Question about "make trampoline" on FreeBSD 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, 24 Nov 2006 00:42:57 -0000 doug, i am replying to freebsd-arm as well. perhaps someone with more clue than myself can point out a better way to do this. david. my method is something like: cd /usr/src && make TARGET_ARCH=arm buildworld setenv MAKEOBJDIRPREFIX /usr/obj/arm setenv MACHINE_ARCH arm setenv MACHINE arm setenv CPUTYPE setenv GROFF_BIN_PATH /usr/obj/arm/usr/src/tmp/legacy/usr/bin setenv GROFF_FONT_PATH /usr/obj/arm/usr/src/tmp/legacy/usr/share/groff_font setenv GROFF_TMAC_PATH /usr/obj/arm/usr/src/tmp/legacy/usr/share/tmac setenv _SHLIBDIRPREFIX /usr/obj/arm/usr/src/tmp setenv INSTALL "sh /usr/src/tools/install.sh" setenv PATH /usr/obj/arm/usr/src/tmp/legacy/usr/sbin:/usr/obj/arm/usr/src/tmp/legacy/usr/bin:/usr/obj/arm/usr/src/tmp/legacy/usr/games:/usr/obj/arm/usr/src/tmp/usr/sbin:/usr/obj/arm/usr/src/tmp/usr/bin:/usr/obj/arm/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin cd /usr/src/sys/arm/conf config KB920X cd ../compile/KB920X make cleandepend && make depend && make && make trampoline to be sure, i have not actually tried recently to make this to work on a KB920X board. my own boards however work well. both SD boot/root and tftp boot nfs root work. however, SD root is pretty slow. takes about 2 min to boot a full multiuser system from reset to login:. /etc/rc.d/root and /etc/rc.d/mountcritlocal account for about half of the boot time. also, to get make buildworld to work it was necessary to disable some things in /etc/make.conf. the one i use looks like: WITHOUT_ACPI=YES WITHOUT_ASSERT_DEBUG=YES WITHOUT_ATM=YES WITHOUT_AUDIT=YES WITHOUT_BIND=YES WITHOUT_BIND_DNSSEC=YES WITHOUT_BIND_LIBS_LWRES=YES WITHOUT_BIND_MTREE=YES WITHOUT_BIND_ETC=YES WITHOUT_BIND_NAMED=YES WITHOUT_BIND_UTILS=YES WITHOUT_BLUETOOTH=YES #WITHOUT_BOOT=YES WITHOUT_CALENDAR=YES #WITHOUT_CPP=YES #WITHOUT_CVS=YES #WITHOUT_CXX=YES WITHOUT_DICT=YES #WITHOUT_DYNAMICROOT=YES WITHOUT_EXAMPLES=YES WITHOUT_FORTH=YES WITHOUT_FORTRAN=YES #WITHOUT_FP_LIBC=YES WITHOUT_GAMES=YES WITHOUT_GCOV=YES #WITHOUT_GNU=YES WITHOUT_GPIB=YES WITHOUT_GROFF=YES WITHOUT_HTML=YES WITHOUT_I4B=YES #WITHOUT_INET6=YES WITHOUT_INFO=YES WITHOUT_IPFILTER=YES WITHOUT_IPX=YES WITHOUT_NCP=YES WITHOUT_LIB32=YES #WITHOUT_LIBPTHREAD=YES #WITHOUT_LIBTHR=YES WITHOUT_LOCALES=YES WITHOUT_LPR=YES WITHOUT_MAILWRAPPER=YES WITHOUT_MAN=YES WITHOUT_NETCAT=YES WITHOUT_NIS=YES WITHOUT_NLS=YES WITHOUT_NLS_CATALOGS=YES WITHOUT_NS_CACHING=YES WITHOUT_OBJC=YES #WITHOUT_CRYPT=YES # WITHOUT_OPENSSL=YES # WITHOUT_OPENSSH=YES # WITHOUT_KERBEROS=YES #WITHOUT_PAM=YES #WITHOUT_PF=YES # WITHOUT_AUTHPF=YES WITHOUT_PROFILE=YES WITHOUT_RCMDS=YES WITHOUT_RCS=YES WITHOUT_RESCUE=YES WITHOUT_SENDMAIL=YES #WITHOUT_SETUID_LOGIN=YES WITHOUT_SHAREDOCS=YES WITHOUT_SYSCONS=YES #WITHOUT_TCSH=YES #WITHOUT_TOOLCHAIN=YES # WITHOUT_GDB=YES WITHOUT_USB=YES WITHOUT_WPA_SUPPLICANT_EAPOL=YES On 2006.11.23 22:29:32 +0000, Doug Brewer wrote: > Hello David, > > I saw your message on freebsd-arm@, I have a problem about making > trampoline on FreeBSD. > Would you tell me the procedures about how to make trampoline ? Thanks. > > My steps are: > > 1. cd /usr/src && make TARGET=arm TARGET_ARCH=arm kernel-toolchain > 2. make buildenv && cd sys/arm/conf && config KB920X > From owner-freebsd-arm@FreeBSD.ORG Fri Nov 24 00:59:56 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 4E27C16A403 for ; Fri, 24 Nov 2006 00:59:56 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A947A43D49 for ; Fri, 24 Nov 2006 00:59:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAO0vBHl026865; Thu, 23 Nov 2006 17:57:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 23 Nov 2006 17:57:56 -0700 (MST) Message-Id: <20061123.175756.-1398301896.imp@bsdimp.com> To: daimon@dev-random.org From: "M. Warner Losh" In-Reply-To: <20061124002310.GA2324@mail.secure.net> References: <20061124002310.GA2324@mail.secure.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 23 Nov 2006 17:57:11 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: Question about "make trampoline" on FreeBSD 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, 24 Nov 2006 00:59:56 -0000 In message: <20061124002310.GA2324@mail.secure.net> David Sharp writes: : doug, : : i am replying to freebsd-arm as well. perhaps someone with more clue than myself : can point out a better way to do this. : : david. : : : my method is something like: : : cd /usr/src && make TARGET_ARCH=arm buildworld good so far. I always add TARGET=arm too. : setenv MAKEOBJDIRPREFIX /usr/obj/arm : setenv MACHINE_ARCH arm : setenv MACHINE arm : setenv CPUTYPE : setenv GROFF_BIN_PATH /usr/obj/arm/usr/src/tmp/legacy/usr/bin : setenv GROFF_FONT_PATH /usr/obj/arm/usr/src/tmp/legacy/usr/share/groff_font : setenv GROFF_TMAC_PATH /usr/obj/arm/usr/src/tmp/legacy/usr/share/tmac : setenv _SHLIBDIRPREFIX /usr/obj/arm/usr/src/tmp : setenv INSTALL "sh /usr/src/tools/install.sh" : : setenv PATH /usr/obj/arm/usr/src/tmp/legacy/usr/sbin:/usr/obj/arm/usr/src/tmp/legacy/usr/bin:/usr/obj/arm/usr/src/tmp/legacy/usr/games:/usr/obj/arm/usr/src/tmp/usr/sbin:/usr/obj/arm/usr/src/tmp/usr/bin:/usr/obj/arm/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin the above is the hard way of saying "make TARGET=arm TARGET_ARCH=arm buildenv" : cd /usr/src/sys/arm/conf : config KB920X : cd ../compile/KB920X : make cleandepend && make depend && make && make trampoline This works. I have some changes in one of my tree that cause make kernel.tramp (err, make trampoline) to happen automatically, and for both kernel.gz and kernel.gz.tramp to be installed. Once that's integrated, a simple 'make buildkernel : to be sure, i have not actually tried recently to make this to work : on a KB920X board. my own boards however work well. both SD : boot/root and tftp boot nfs root work. however, SD root is pretty : slow. takes about 2 min to boot a full multiuser system from reset : to login:. /etc/rc.d/root and /etc/rc.d/mountcritlocal account for : about half of the boot time. SD root isn't that slow. I get from power on to login prompt in 1 minute on the machines at work as well as the KB9202 boards. Over NFS root it takes about the same amount of time. Maybe there's something weird in your setup... No doubt this could be optimized, and I'll be looking at optimizing the boot time in the near future. : also, to get make buildworld to work it was necessary to disable some : things in /etc/make.conf. the one i use looks like: Yea, I have custom scripts that build everything, but only install a very limited subset. Warner From owner-freebsd-arm@FreeBSD.ORG Fri Nov 24 01:32:38 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 50BC816A500 for ; Fri, 24 Nov 2006 01:32:38 +0000 (UTC) (envelope-from daimon@dev-random.org) Received: from sharp.org (sharp.org [161.58.2.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id A99FA43D45 for ; Fri, 24 Nov 2006 01:31:59 +0000 (GMT) (envelope-from daimon@dev-random.org) Received: from betty.wa.sharp.org (sharp.org [161.58.2.117]) by sharp.org (8.12.11.20060614/8.12.9) with ESMTP id kAO1WX1B067660 for ; Thu, 23 Nov 2006 18:32:36 -0700 (MST) Received: from betty.wa.sharp.org (4f3b6570af64739501d50041ff5fd1f9@localhost [127.0.0.1]) by betty.wa.sharp.org (8.13.6/8.13.3) with ESMTP id kAO1VwRY004113; Thu, 23 Nov 2006 17:31:58 -0800 (PST) (envelope-from daimon@dev-random.org) Received: (from djs@localhost) by betty.wa.sharp.org (8.13.6/8.13.6/Submit) id kAO1VuDT004112; Thu, 23 Nov 2006 17:31:56 -0800 (PST) (envelope-from daimon@dev-random.org) X-Authentication-Warning: betty.wa.sharp.org: djs set sender to daimon@dev-random.org using -f Date: Thu, 23 Nov 2006 17:31:56 -0800 From: David Sharp To: "M. Warner Losh" Message-ID: <20061124013156.GI2324@mail.secure.net> References: <20061124002310.GA2324@mail.secure.net> <20061123.175756.-1398301896.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061123.175756.-1398301896.imp@bsdimp.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-arm@freebsd.org Subject: Re: Question about "make trampoline" on FreeBSD 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, 24 Nov 2006 01:32:38 -0000 On 2006.11.23 17:57:56 +0000, M. Warner Losh wrote: > SD root isn't that slow. I get from power on to login prompt in 1 > minute on the machines at work as well as the KB9202 boards. Over NFS > root it takes about the same amount of time. Maybe there's something > weird in your setup... NFS is quite a bit faster than SD for me, so as you suggest my hw is prolly broken. i think i got all the pullups in the right place. it has not failed to load but is just slow to read/write. perhaps another sd card might fix things. are the ...bus width to 1 messages normal? Timecounter "AT91RM9200 timer" frequency 32768 Hz quality 1000 Timecounters tick every 7.812 msec at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 SD CARD: 500695040 bytes at91_mci0: Setting controller bus width to 1 mmcsd0: on mmc0 mmc0: setting transfer rate to 30.000MHz at91_mci0: Setting controller bus width to 1 Trying to mount root from ufs:mmcsd0s1a From owner-freebsd-arm@FreeBSD.ORG Fri Nov 24 01:53:56 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org 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 A2C3A16A412 for ; Fri, 24 Nov 2006 01:53:56 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E826D43D4C for ; Fri, 24 Nov 2006 01:53:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAO1qVNZ027414; Thu, 23 Nov 2006 18:52:31 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 23 Nov 2006 18:53:16 -0700 (MST) Message-Id: <20061123.185316.-1717446433.imp@bsdimp.com> To: daimon@dev-random.org From: "M. Warner Losh" In-Reply-To: <20061124013156.GI2324@mail.secure.net> References: <20061124002310.GA2324@mail.secure.net> <20061123.175756.-1398301896.imp@bsdimp.com> <20061124013156.GI2324@mail.secure.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 23 Nov 2006 18:52:31 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: Question about "make trampoline" on FreeBSD 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, 24 Nov 2006 01:53:56 -0000 In message: <20061124013156.GI2324@mail.secure.net> David Sharp writes: : On 2006.11.23 17:57:56 +0000, M. Warner Losh wrote: : > SD root isn't that slow. I get from power on to login prompt in 1 : > minute on the machines at work as well as the KB9202 boards. Over NFS : > root it takes about the same amount of time. Maybe there's something : > weird in your setup... : : NFS is quite a bit faster than SD for me, so as you suggest my hw is : prolly broken. i think i got all the pullups in the right place. it : has not failed to load but is just slow to read/write. perhaps : another sd card might fix things. are the ...bus width to 1 messages : normal? : : Timecounter "AT91RM9200 timer" frequency 32768 Hz quality 1000 : Timecounters tick every 7.812 msec : at91_mci0: Setting controller bus width to 1 : at91_mci0: Setting controller bus width to 1 : at91_mci0: Setting controller bus width to 1 : at91_mci0: Setting controller bus width to 1 : at91_mci0: Setting controller bus width to 1 : at91_mci0: Setting controller bus width to 1 : SD CARD: 500695040 bytes : at91_mci0: Setting controller bus width to 1 : mmcsd0: on mmc0 : mmc0: setting transfer rate to 30.000MHz : at91_mci0: Setting controller bus width to 1 : Trying to mount root from ufs:mmcsd0s1a Yes. the bus width messages are normal, but I should likely add support for 4bit too. It isn't that hard, I just haven't had a chance to do it. Warner