From owner-freebsd-arm@FreeBSD.ORG Sun Feb 25 07:17:02 2007 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 1050516A400 for ; Sun, 25 Feb 2007 07:17:02 +0000 (UTC) (envelope-from xride@x12.dk) Received: from swip.net (mailfe07.tele2.dk [212.247.154.195]) by mx1.freebsd.org (Postfix) with ESMTP id A2C7513C481 for ; Sun, 25 Feb 2007 07:17:01 +0000 (UTC) (envelope-from xride@x12.dk) X-Cloudmark-Score: 0.000000 [] Received: from x12.dk (account mu12272@get2net.dk [83.72.97.231] verified) by mailfe07.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 422936854 for freebsd-arm@freebsd.org; Sun, 25 Feb 2007 08:16:55 +0100 Received: by x12.dk (Postfix, from userid 666) id 1047A50845; Sun, 25 Feb 2007 08:16:55 +0100 (CET) Date: Sun, 25 Feb 2007 08:16:54 +0100 From: Soeren Straarup To: freebsd-arm@freebsd.org Message-ID: <20070225071654.GE81938@x12.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: BEEP PHY BEEP X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 07:17:02 -0000 Hi list I've gotten so far with the mb9200 board that i can get the loader to load via xmodem.. I just can't seem to get the phy setup right. The phy is a Davicom DM9161EP, I can only find a datasheet for the DM9161, not the EP version. When i read the PHYAD1 i get 0x181 as the datasheet says. But from usign the register/bit teh datasheet say I don't get any link. /Soeren -- Soeren Straarup | aka OZ2DAK aka Xride FreeBSD committer | FreeBSD since 2.2.6-R If a program is not working right, then send a patch From owner-freebsd-arm@FreeBSD.ORG Sun Feb 25 13:46:45 2007 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 0EDB616A400; Sun, 25 Feb 2007 13:46:45 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id 832BA13C442; Sun, 25 Feb 2007 13:46:44 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 4D35CF845; Sun, 25 Feb 2007 15:46:40 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55772-03-2; Sun, 25 Feb 2007 15:46:37 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 44D38F846; Sun, 25 Feb 2007 15:46:34 +0200 (EET) Message-ID: <45E1933A.6090505@bulinfo.net> Date: Sun, 25 Feb 2007 15:46:34 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: Subject: kernel panic on ARM (interrupt filtering related)? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 13:46:45 -0000 at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x1380010 ODSR: 0 panic: All system interrupt ISRs must be type INTR_FAST KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x3c: ldrb r15, [r15, r15, ror r15]! db>bt Tracing pid 0 tid 0 td 0xc01b3b38 db_trace_thread() at db_trace_thread+0x10 scp=0xc0138dc4 rlv=0xc0004a0c (db_stack_trace+0x100) rsp=0xc023c9bc rfp=0xc023c9d8 db_stack_trace() at db_stack_trace+0x10 scp=0xc000491c rlv=0xc00043b0 (db_command+0x254) rsp=0xc023c9dc rfp=0xc023ca78 r5=0x00000000 r4=0x00000000 db_command() at db_command+0x10 scp=0xc000416c rlv=0xc00044bc (db_command_loop+0x58) rsp=0xc023ca7c rfp=0xc023ca88 r6=0xc01b78f0 r5=0x600000d3 r4=0xc023ca94 db_command_loop() at db_command_loop+0x10 scp=0xc0004474 rlv=0xc0006b08 (db_trap+0xf8) rsp=0xc023ca8c rfp=0xc023cba8 db_trap() at db_trap+0x10 scp=0xc0006a20 rlv=0xc007567c (kdb_trap+0xb8) rsp=0xc023cbac rfp=0xc023cbd0 r4=0x000000c0 kdb_trap() at kdb_trap+0x10 scp=0xc00755d4 rlv=0xc014653c (undefinedinstruction+0x25c) rsp=0xc023cbd4 rfp=0xc023cc48 r10=0x00000000 r8=0xc00752e4 r7=0xc01b3b38 r6=0xe7ffffff r5=0xc023cc4c r4=0x00000000 undefinedinstruction() at undefinedinstruction+0x10 scp=0xc01462f0 rlv=0xc013ab30 (exception_exit) rsp=0xc023cc4c rfp=0xc023cca4 r10=0xc0815200 r8=0xc01b3b38 r7=0x00000100 r6=0xc023ccbc r5=0xe0000004 r4=0x00000001 kdb_enter() at kdb_enter+0x10 scp=0xc00752b8 rlv=0xc0053498 (panic+0xc0) rsp=0xc023cca8 rfp=0xc023ccb4 panic() at panic+0x14 scp=0xc00533ec rlv=0xc014b5d0 (at91_setup_intr+0x48) rsp=0xc023ccc8 rfp=0xc023cd0c at91_setup_intr() at at91_setup_intr+0x10 scp=0xc014b598 rlv=0xc00719f4 (bus_setup_intr+0xd0) rsp=0xc023cd10 rfp=0xc023cd5c r10=0xc0815200 r9=0xc0815204 r8=0x00000000 r7=0xc014d5b4 r6=0xc07c7d00 r5=0x00000010 r4=0xc07c7b80 bus_setup_intr() at bus_setup_intr+0x10 scp=0xc0071934 rlv=0xc014d3d0 (at91_pio_attach+0x12c) rsp=0xc023cd60 rfp=0xc023cd94 r10=0x00000000 r9=0x200e7ffc r8=0xc07c7b80 r7=0xc0815200 r6=0x00000060 r5=0x00000000 r4=0xc0815210 at91_pio_attach() at at91_pio_attach+0x10 scp=0xc014d2b4 rlv=0xc0070034 (device_attach+0x70) rsp=0xc023cd98 rfp=0xc023cdac r10=0xfffff80f r8=0x2022b19c r7=0xc07c7d00 r6=0x00000000 r5=0xc07c7b80 r4=0xc07c7b80 device_attach() at device_attach+0x10 scp=0xc006ffd4 rlv=0xc006ffb4 (device_probe_and_attach+0xfc) rsp=0xc023cdb0 rfp=0xc023cdcc r5=0xc07c7c80 r4=0xc07c7b80 device_probe_and_attach() at device_probe_and_attach+0x10 scp=0xc006fec8 rlv=0xc0070a94 (bus_generic_attach+0x24) rsp=0xc023cdd0 rfp=0xc023cde4 r7=0xc07c7d00 r6=0x00000020 r5=0xc07c7c80 r4=0xc07c7b80 bus_generic_attach() at bus_generic_attach+0x10 scp=0xc0070a80 rlv=0xc014b294 (at91_attach+0x254) rsp=0xc023cde8 rfp=0xc023ce0c r4=0x0000007c at91_attach() at at91_attach+0x10 scp=0xc014b050 rlv=0xc0070034 (device_attach+0x70) rsp=0xc023ce10 rfp=0xc023ce24 r7=0xc01b41e0 r6=0x00000000 r5=0xc07c7d00 r4=0xc07c7d00 device_attach() at device_attach+0x10 scp=0xc006ffd4 rlv=0xc006ffb4 (device_probe_and_attach+0xfc) rsp=0xc023ce28 rfp=0xc023ce44 r5=0xc07c6100 r4=0xc07c7d00 device_probe_and_attach() at device_probe_and_attach+0x10 scp=0xc006fec8 rlv=0xc0070a94 (bus_generic_attach+0x24) rsp=0xc023ce48 rfp=0xc023ce5c r7=0xc01b41e0 r6=0x00000000 r5=0xc07c6100 r4=0xc07c7d00 bus_generic_attach() at bus_generic_attach+0x10 scp=0xc0070a80 rlv=0xc013c94c (nexus_attach+0x20) rsp=0xc023ce60 rfp=0xc023ce74 r4=0xc07c6100 nexus_attach() at nexus_attach+0x10 scp=0xc013c93c rlv=0xc0070034 (device_attach+0x70) rsp=0xc023ce78 rfp=0xc023ce8c r4=0xc07c6100 device_attach() at device_attach+0x10 scp=0xc006ffd4 rlv=0xc006ffb4 (device_probe_and_attach+0xfc) rsp=0xc023ce90 rfp=0xc023ceac r5=0xc01b41e4 r4=0xc07c6100 device_probe_and_attach() at device_probe_and_attach+0x10 scp=0xc006fec8 rlv=0xc0072144 (root_bus_configure+0x2c) rsp=0xc023ceb0 rfp=0xc023cec4 r7=0xc01b41e0 r6=0xc01b41e8 r5=0xc01b41e4 r4=0xc07c6100 root_bus_configure() at root_bus_configure+0x10 scp=0xc0072128 rlv=0xc013393c (configure+0x10) rsp=0xc023cec8 rfp=0xc023ced4 r4=0xc017173c configure() at configure+0x10 scp=0xc013393c rlv=0xc002a8e4 (mi_startup+0x100) rsp=0xc023ced8 rfp=0xc023cef4 mi_startup() at mi_startup+0x10 scp=0xc002a7f4 rlv=0xc00001b0 (virt_done+0x10) rsp=0xc023cef8 rfp=0x00000000 r7=0x20000110 r6=0x00000004 r5=0x2000011c r4=0x200001f0 From owner-freebsd-arm@FreeBSD.ORG Sun Feb 25 14:23:53 2007 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 320AF16A400; Sun, 25 Feb 2007 14:23:53 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id D0F8E13C474; Sun, 25 Feb 2007 14:23:52 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id BAF26F90B; Sun, 25 Feb 2007 16:23:48 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57307-10; Sun, 25 Feb 2007 16:23:46 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 02D0DF909; Sun, 25 Feb 2007 16:23:45 +0200 (EET) Message-ID: <45E19BF1.1070500@bulinfo.net> Date: Sun, 25 Feb 2007 16:23:45 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: Paolo Pisati References: <45E1933A.6090505@bulinfo.net> <20070225141000.GB44753@tin.it> In-Reply-To: <20070225141000.GB44753@tin.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: kernel panic on ARM (interrupt filtering related)? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 14:23:53 -0000 Yes. It works! Best Regards Paolo Pisati wrote: > On Sun, Feb 25, 2007 at 03:46:34PM +0200, Krassimir Slavchev wrote: > >> at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 >> at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x1380010 ODSR: 0 >> panic: All system interrupt ISRs must be type INTR_FAST >> > > try this: > > http://people.freebsd.org/~piso/at91.diff > > bye, > P. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-arm@FreeBSD.ORG Sun Feb 25 14:30:27 2007 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 EB3B516A400 for ; Sun, 25 Feb 2007 14:30:27 +0000 (UTC) (envelope-from piso@newluxor.wired.org) Received: from mail.oltrelinux.com (krisma.oltrelinux.com [194.242.226.43]) by mx1.freebsd.org (Postfix) with ESMTP id A972A13C4A7 for ; Sun, 25 Feb 2007 14:30:27 +0000 (UTC) (envelope-from piso@newluxor.wired.org) Received: from newluxor.wired.org (ip-91-186.sn1.eutelia.it [62.94.91.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.oltrelinux.com (Postfix) with ESMTP id 8E17311AEB6; Sun, 25 Feb 2007 15:10:08 +0100 (CET) Received: (from piso@localhost) by newluxor.wired.org (8.13.8/8.13.8/Submit) id l1PEA1AG045093; Sun, 25 Feb 2007 15:10:01 +0100 (CET) (envelope-from piso) Date: Sun, 25 Feb 2007 15:10:00 +0100 From: Paolo Pisati To: Krassimir Slavchev Message-ID: <20070225141000.GB44753@tin.it> References: <45E1933A.6090505@bulinfo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E1933A.6090505@bulinfo.net> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at krisma.oltrelinux.com Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: kernel panic on ARM (interrupt filtering related)? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 14:30:28 -0000 On Sun, Feb 25, 2007 at 03:46:34PM +0200, Krassimir Slavchev wrote: > > at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 > at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x1380010 ODSR: 0 > panic: All system interrupt ISRs must be type INTR_FAST try this: http://people.freebsd.org/~piso/at91.diff bye, P. From owner-freebsd-arm@FreeBSD.ORG Sun Feb 25 17:17:49 2007 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 716F316A400 for ; Sun, 25 Feb 2007 17:17:49 +0000 (UTC) (envelope-from xride@x12.dk) Received: from swip.net (mailfe04.tele2.dk [212.247.154.99]) by mx1.freebsd.org (Postfix) with ESMTP id 1225D13C461 for ; Sun, 25 Feb 2007 17:17:48 +0000 (UTC) (envelope-from xride@x12.dk) X-Cloudmark-Score: 0.000000 [] Received: from x12.dk (account mu12272@get2net.dk [83.72.97.231] verified) by mailfe04.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 421293724 for freebsd-arm@freebsd.org; Sun, 25 Feb 2007 18:17:46 +0100 Received: by x12.dk (Postfix, from userid 666) id 3E99650844; Sun, 25 Feb 2007 18:17:45 +0100 (CET) Date: Sun, 25 Feb 2007 18:17:45 +0100 From: Soeren Straarup To: freebsd-arm@freebsd.org Message-ID: <20070225171745.GF81938@x12.dk> References: <20070225071654.GE81938@x12.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070225071654.GE81938@x12.dk> User-Agent: Mutt/1.4.2.2i Subject: Datasheet, was BEEP PHY BEEP X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 17:17:49 -0000 On Sun, Feb 25, 2007 at 08:16:54AM +0100, Soeren Straarup wrote: > Hi list > > I've gotten so far with the mb9200 board that i can get the loader to load > via xmodem.. I just can't seem to get the phy setup right. > The phy is a Davicom DM9161EP, I can only find a datasheet for the DM9161, > not the EP version. > When i read the PHYAD1 i get 0x181 as the datasheet says. > But from usign the register/bit teh datasheet say I don't get any link. > http://www.datasheetcatalog.com/datasheets_pdf/D/M/9/1/DM9161E.shtml That is the datasheet, On page 21 it should the registers in short form. /Soeren -- Soeren Straarup | aka OZ2DAK aka Xride FreeBSD committer | FreeBSD since 2.2.6-R If a program is not working right, then send a patch From owner-freebsd-arm@FreeBSD.ORG Sun Feb 25 17:46:37 2007 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 0E31516A400; Sun, 25 Feb 2007 17:46:37 +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 AD0CE13C428; Sun, 25 Feb 2007 17:46:36 +0000 (UTC) (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 l1PHhdcx059069; Sun, 25 Feb 2007 10:43:41 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 25 Feb 2007 10:43:42 -0700 (MST) Message-Id: <20070225.104342.-1581794529.imp@bsdimp.com> To: krassi@bulinfo.net From: "M. Warner Losh" In-Reply-To: <45E1933A.6090505@bulinfo.net> References: <45E1933A.6090505@bulinfo.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]); Sun, 25 Feb 2007 10:43:42 -0700 (MST) Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: kernel panic on ARM (interrupt filtering related)? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 17:46:37 -0000 In message: <45E1933A.6090505@bulinfo.net> Krassimir Slavchev writes: : : at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 : at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x1380010 ODSR: 0 : panic: All system interrupt ISRs must be type INTR_FAST I think this is fallout from the Filter patches. Warner : KDB: enter: panic : [thread pid 0 tid 0 ] : Stopped at kdb_enter+0x3c: ldrb r15, [r15, r15, ror r15]! : db>bt : Tracing pid 0 tid 0 td 0xc01b3b38 : db_trace_thread() at db_trace_thread+0x10 : scp=0xc0138dc4 rlv=0xc0004a0c (db_stack_trace+0x100) : rsp=0xc023c9bc rfp=0xc023c9d8 : db_stack_trace() at db_stack_trace+0x10 : scp=0xc000491c rlv=0xc00043b0 (db_command+0x254) : rsp=0xc023c9dc rfp=0xc023ca78 : r5=0x00000000 r4=0x00000000 : db_command() at db_command+0x10 : scp=0xc000416c rlv=0xc00044bc (db_command_loop+0x58) : rsp=0xc023ca7c rfp=0xc023ca88 : r6=0xc01b78f0 r5=0x600000d3 : r4=0xc023ca94 : db_command_loop() at db_command_loop+0x10 : scp=0xc0004474 rlv=0xc0006b08 (db_trap+0xf8) : rsp=0xc023ca8c rfp=0xc023cba8 : db_trap() at db_trap+0x10 : scp=0xc0006a20 rlv=0xc007567c (kdb_trap+0xb8) : rsp=0xc023cbac rfp=0xc023cbd0 : r4=0x000000c0 : kdb_trap() at kdb_trap+0x10 : scp=0xc00755d4 rlv=0xc014653c (undefinedinstruction+0x25c) : rsp=0xc023cbd4 rfp=0xc023cc48 : r10=0x00000000 r8=0xc00752e4 : r7=0xc01b3b38 r6=0xe7ffffff r5=0xc023cc4c r4=0x00000000 : undefinedinstruction() at undefinedinstruction+0x10 : scp=0xc01462f0 rlv=0xc013ab30 (exception_exit) : rsp=0xc023cc4c rfp=0xc023cca4 : r10=0xc0815200 r8=0xc01b3b38 : r7=0x00000100 r6=0xc023ccbc r5=0xe0000004 r4=0x00000001 : kdb_enter() at kdb_enter+0x10 : scp=0xc00752b8 rlv=0xc0053498 (panic+0xc0) : rsp=0xc023cca8 rfp=0xc023ccb4 : panic() at panic+0x14 : scp=0xc00533ec rlv=0xc014b5d0 (at91_setup_intr+0x48) : rsp=0xc023ccc8 rfp=0xc023cd0c : at91_setup_intr() at at91_setup_intr+0x10 : scp=0xc014b598 rlv=0xc00719f4 (bus_setup_intr+0xd0) : rsp=0xc023cd10 rfp=0xc023cd5c : r10=0xc0815200 r9=0xc0815204 : r8=0x00000000 r7=0xc014d5b4 r6=0xc07c7d00 r5=0x00000010 : r4=0xc07c7b80 : bus_setup_intr() at bus_setup_intr+0x10 : scp=0xc0071934 rlv=0xc014d3d0 (at91_pio_attach+0x12c) : rsp=0xc023cd60 rfp=0xc023cd94 : r10=0x00000000 r9=0x200e7ffc : r8=0xc07c7b80 r7=0xc0815200 r6=0x00000060 r5=0x00000000 : r4=0xc0815210 : at91_pio_attach() at at91_pio_attach+0x10 : scp=0xc014d2b4 rlv=0xc0070034 (device_attach+0x70) : rsp=0xc023cd98 rfp=0xc023cdac : r10=0xfffff80f r8=0x2022b19c : r7=0xc07c7d00 r6=0x00000000 r5=0xc07c7b80 r4=0xc07c7b80 : device_attach() at device_attach+0x10 : scp=0xc006ffd4 rlv=0xc006ffb4 (device_probe_and_attach+0xfc) : rsp=0xc023cdb0 rfp=0xc023cdcc : r5=0xc07c7c80 r4=0xc07c7b80 : device_probe_and_attach() at device_probe_and_attach+0x10 : scp=0xc006fec8 rlv=0xc0070a94 (bus_generic_attach+0x24) : rsp=0xc023cdd0 rfp=0xc023cde4 : r7=0xc07c7d00 r6=0x00000020 : r5=0xc07c7c80 r4=0xc07c7b80 : bus_generic_attach() at bus_generic_attach+0x10 : scp=0xc0070a80 rlv=0xc014b294 (at91_attach+0x254) : rsp=0xc023cde8 rfp=0xc023ce0c : r4=0x0000007c : at91_attach() at at91_attach+0x10 : scp=0xc014b050 rlv=0xc0070034 (device_attach+0x70) : rsp=0xc023ce10 rfp=0xc023ce24 : r7=0xc01b41e0 r6=0x00000000 : r5=0xc07c7d00 r4=0xc07c7d00 : device_attach() at device_attach+0x10 : scp=0xc006ffd4 rlv=0xc006ffb4 (device_probe_and_attach+0xfc) : rsp=0xc023ce28 rfp=0xc023ce44 : r5=0xc07c6100 r4=0xc07c7d00 : device_probe_and_attach() at device_probe_and_attach+0x10 : scp=0xc006fec8 rlv=0xc0070a94 (bus_generic_attach+0x24) : rsp=0xc023ce48 rfp=0xc023ce5c : r7=0xc01b41e0 r6=0x00000000 : r5=0xc07c6100 r4=0xc07c7d00 : bus_generic_attach() at bus_generic_attach+0x10 : scp=0xc0070a80 rlv=0xc013c94c (nexus_attach+0x20) : rsp=0xc023ce60 rfp=0xc023ce74 : r4=0xc07c6100 : nexus_attach() at nexus_attach+0x10 : scp=0xc013c93c rlv=0xc0070034 (device_attach+0x70) : rsp=0xc023ce78 rfp=0xc023ce8c : r4=0xc07c6100 : device_attach() at device_attach+0x10 : scp=0xc006ffd4 rlv=0xc006ffb4 (device_probe_and_attach+0xfc) : rsp=0xc023ce90 rfp=0xc023ceac : r5=0xc01b41e4 r4=0xc07c6100 : device_probe_and_attach() at device_probe_and_attach+0x10 : scp=0xc006fec8 rlv=0xc0072144 (root_bus_configure+0x2c) : rsp=0xc023ceb0 rfp=0xc023cec4 : r7=0xc01b41e0 r6=0xc01b41e8 : r5=0xc01b41e4 r4=0xc07c6100 : root_bus_configure() at root_bus_configure+0x10 : scp=0xc0072128 rlv=0xc013393c (configure+0x10) : rsp=0xc023cec8 rfp=0xc023ced4 : r4=0xc017173c : configure() at configure+0x10 : scp=0xc013393c rlv=0xc002a8e4 (mi_startup+0x100) : rsp=0xc023ced8 rfp=0xc023cef4 : mi_startup() at mi_startup+0x10 : scp=0xc002a7f4 rlv=0xc00001b0 (virt_done+0x10) : rsp=0xc023cef8 rfp=0x00000000 : r7=0x20000110 r6=0x00000004 : r5=0x2000011c r4=0x200001f0 : : : _______________________________________________ : 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 Sun Feb 25 17:52:33 2007 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 8916F16A403; Sun, 25 Feb 2007 17:52:33 +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 4B02513C467; Sun, 25 Feb 2007 17:52:33 +0000 (UTC) (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 l1PHplqE059163; Sun, 25 Feb 2007 10:51:47 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 25 Feb 2007 10:51:49 -0700 (MST) Message-Id: <20070225.105149.1575282293.imp@bsdimp.com> To: krassi@bulinfo.net From: "M. Warner Losh" In-Reply-To: <20070225.104342.-1581794529.imp@bsdimp.com> References: <45E1933A.6090505@bulinfo.net> <20070225.104342.-1581794529.imp@bsdimp.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]); Sun, 25 Feb 2007 10:51:49 -0700 (MST) Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: kernel panic on ARM (interrupt filtering related)? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 17:52:33 -0000 In message: <20070225.104342.-1581794529.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <45E1933A.6090505@bulinfo.net> : Krassimir Slavchev writes: : : : : at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 : : at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x1380010 ODSR: 0 : : panic: All system interrupt ISRs must be type INTR_FAST : : I think this is fallout from the Filter patches. And I see piso@ has fixed it... Warner From owner-freebsd-arm@FreeBSD.ORG Tue Feb 27 09:04:31 2007 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 A96B316A403 for ; Tue, 27 Feb 2007 09:04:31 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1D4AB13C48D for ; Tue, 27 Feb 2007 09:04:30 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so101863nfc for ; Tue, 27 Feb 2007 01:04:29 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=RmAcJZDRKikNFSOCAqxJqJ7inI0liyidcD4d6wBRHVZ6fyxYB2/MYBiYRQmMActur1NLpoQoz8O5bwjclreNsnbNco33x8NdZYAeoIy2bWQiF5cGlUhnIa3b0tyMQVPxR4U77cKh4kn5fYWGVrlv4e/xpvnibr4iM3IO39O+oSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=FJ/RlwNLdTR546U4DgHJUSzTYpj6wxb8qp+geo1OCdVXy9z/jvHQwBb1RvgwHPbTJpnbH3b4uDFgo0/o4kfskFbRneaOBZXWA6VGKCwctxu6pk/1zezaQ4rwyOinBxYTK/WkHx4nbM45XP5ZB+oW8rzvDsdwhO5AhqKMKBv9VN0= Received: by 10.49.20.15 with SMTP id x15mr565502nfi.1172565449066; Tue, 27 Feb 2007 00:37:29 -0800 (PST) Received: from ?192.168.0.21? ( [87.166.94.114]) by mx.google.com with ESMTP id e8sm4412489muf.2007.02.27.00.37.28; Tue, 27 Feb 2007 00:37:28 -0800 (PST) From: Pascal Hofstee To: freebsd-arm@FreeBSD.org Content-Type: text/plain Date: Tue, 27 Feb 2007 09:37:27 +0100 Message-Id: <1172565447.1394.20.camel@chekov> Mime-Version: 1.0 X-Mailer: Evolution 2.9.91 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: __aeabi_read_tp missing symbol 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, 27 Feb 2007 09:04:31 -0000 Hi, I just finished writing a small application for my job on FreeBSD/i386 making sure everything compiles WARNS=9 clean. Now comes the task to move this code over to our embedded platform which is an Intel XScale (Linksys NSLU2) at the moment i have not been able to test out cognet@'s FreeBSD/arm work yet .. so we're using a Linux (Debian/Etch) to do our embedded development on, so i apologise if this tunrs out to be a Linux problem and i am asking the wrong people for assistence :) The problem i am encountering is that during the link stage i get a lot of the following link errors: datastream.o: In function `deleteSynchronisedData': ...../datastream.c:909: undefined reference to `__aeabi_read_tp' Googling so far has taught me that this is GCC's work and well the following: `-mtp=NAME' Specify the access model for the thread local storage pointer. The valid models are `soft', which generates calls to `__aeabi_read_tp', `cp15', which fetches the thread pointer from `cp15' directly (supported in the arm6k architecture), and `auto', which uses the best available method for the selected processor. The default setting is `auto'. Obviously GCC is of the opinion that it should use the "soft" access model for thread local storage (which i am indeed using a lot in this source file). But somehow the link stage fails to find these symbols. Where should these symbols be coming from normally and how would i go about fixing my link stage ... It seems as if the compiler is of the opinion that TLS is supported. Once again i know this is currently on a Linux platform but i have much bigger trust in the FreeBSD community to provide sensible answers in this regard. -- Pascal Hofstee From owner-freebsd-arm@FreeBSD.ORG Tue Feb 27 11:49:08 2007 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 403C316A400 for ; Tue, 27 Feb 2007 11:49:08 +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 58CC213C4B3 for ; Tue, 27 Feb 2007 11:49:06 +0000 (UTC) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.8/8.13.8) with ESMTP id l1RBxmuD017694; Tue, 27 Feb 2007 12:59:48 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.8/8.13.8/Submit) id l1RBxmfc017693; Tue, 27 Feb 2007 12:59:48 +0100 (CET) (envelope-from mlfbsd) Date: Tue, 27 Feb 2007 12:59:47 +0100 From: Olivier Houchard To: Pascal Hofstee Message-ID: <20070227115947.GA17619@ci0.org> References: <1172565447.1394.20.camel@chekov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1172565447.1394.20.camel@chekov> User-Agent: Mutt/1.4.1i Cc: freebsd-arm@freebsd.org Subject: Re: __aeabi_read_tp missing symbol 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, 27 Feb 2007 11:49:08 -0000 Hi Pascal, On Tue, Feb 27, 2007 at 09:37:27AM +0100, Pascal Hofstee wrote: > Hi, > > I just finished writing a small application for my job on FreeBSD/i386 > making sure everything compiles WARNS=9 clean. Now comes the task to > move this code over to our embedded platform which is an Intel XScale > (Linksys NSLU2) at the moment i have not been able to test out cognet@'s > FreeBSD/arm work yet .. so we're using a Linux (Debian/Etch) to do our > embedded development on, so i apologise if this tunrs out to be a Linux > problem and i am asking the wrong people for assistence :) > > The problem i am encountering is that during the link stage i get a lot > of the following link errors: > > datastream.o: In function `deleteSynchronisedData': > ...../datastream.c:909: undefined reference to `__aeabi_read_tp' > Yes it is definitively a linux problem :-) See below. > Googling so far has taught me that this is GCC's work and well the > following: > > `-mtp=NAME' > Specify the access model for the thread local storage pointer. > The valid models are `soft', which generates calls to > `__aeabi_read_tp', `cp15', which fetches the thread pointer from > `cp15' directly (supported in the arm6k architecture), and `auto', > which uses the best available method for the selected processor. > The default setting is `auto'. > > Obviously GCC is of the opinion that it should use the "soft" access model for > thread local storage (which i am indeed using a lot in this source file). But > somehow the link stage fails to find these symbols. > > Where should these symbols be coming from normally and how would i go about > fixing my link stage ... It seems as if the compiler is of the opinion that > TLS is supported. > > Once again i know this is currently on a Linux platform but i have much bigger > trust in the FreeBSD community to provide sensible answers in this regard. > Latest revisions of gcc/binutils have support for TLS. And using EABI is the right thing to do on linux. You're just using the wrong libc, eabi_read_tp and friends come from the glibc. If changing your glibc is not an option, you'll have to play with -mabi, and set it to something else than eabi, however if you need TLS I think you're doomed with this version of gcc, you'll have to find a matching glibc. I could be wrong on this one, I'm not a linux/arm specialist. Cheers, Olivier > -- > Pascal Hofstee > > _______________________________________________ > 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 Wed Feb 28 01:34:44 2007 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 6EE4E16C20A for ; Wed, 28 Feb 2007 01:34:44 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187]) by mx1.freebsd.org (Postfix) with ESMTP id 00C2113C4C7 for ; Wed, 28 Feb 2007 01:34:41 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by mu-out-0910.google.com with SMTP id g7so1730829muf for ; Tue, 27 Feb 2007 17:34:35 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=NoCBOVI4rRDofYK3H77EuFAa8RqABc+W6tT4p4dzYZWSxDQUJDTqdVN7RixsjuVcdnuCK+xDTOkzS83vsz/BWtL1nJYJuhPQ2ugMb8evrgjncMq9mPGg0t7p15d8OK+5zUwYig3i19dUHh+YZF0Gm8cf7YegqPdk0txPNTLKbS8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=jsJFAdoOHYZ76ZOJrX6HA0uTRe9U7wPL4z2PxJyCO+Sj3W4ALPthvrHQBsa/rAPQkJyB1m+AOhuea7NxOnJr3Q53ggTAs/OmvP6j6ZGJNz3yJEjFWD+YrEJasfnUtDFsB6+VHnV+Ts6kK62Lj+cmBo47nFE3X0GTo9POfXjk3kc= Received: by 10.82.116.15 with SMTP id o15mr2539939buc.1172626475309; Tue, 27 Feb 2007 17:34:35 -0800 (PST) Received: from ?192.168.0.21? ( [87.166.94.114]) by mx.google.com with ESMTP id y6sm8388552mug.2007.02.27.17.34.34; Tue, 27 Feb 2007 17:34:34 -0800 (PST) From: Pascal Hofstee To: Olivier Houchard In-Reply-To: <20070227115947.GA17619@ci0.org> References: <1172565447.1394.20.camel@chekov> <20070227115947.GA17619@ci0.org> Content-Type: text/plain Date: Wed, 28 Feb 2007 02:34:32 +0100 Message-Id: <1172626472.1394.29.camel@chekov> Mime-Version: 1.0 X-Mailer: Evolution 2.9.91 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org Subject: Re: __aeabi_read_tp missing symbol 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, 28 Feb 2007 01:34:44 -0000 On Tue, 2007-02-27 at 12:59 +0100, Olivier Houchard wrote: > Hi Pascal, [snip] > Yes it is definitively a linux problem :-) > See below. [snip] > Latest revisions of gcc/binutils have support for TLS. And using EABI is the > right thing to do on linux. You're just using the wrong libc, eabi_read_tp and > friends come from the glibc. If changing your glibc is not an option, you'll > have to play with -mabi, and set it to something else than eabi, however if > you need TLS I think you're doomed with this version of gcc, you'll have to > find a matching glibc. > > I could be wrong on this one, I'm not a linux/arm specialist. I did some additional digging on my own and (since i am using a Debian/Etch to currently do my "native compiling" on) decided to have a closer look at the Debian support pages where i noticed that Debian claims to fully support LE ARM .. and that there are unofficial images for BE ARM and EABI ARM support. That made me draw the conclusion that most likely my "armv5el" (if i recall correctly) Debian/Etch simply doesn't support the EABI interface. I however spent most of today to successfully rewrite the parts of my code that used TLS to now use a mechanism involving pthread_(set|get)specific instead. So the thing is a moot point for me now anyway. Thanks for the feedback though ... and i'll be seeing wether or not i can put some time into trying out a FreeBSD/arm cross-compile build to see if i can get that build to boot on one of our NSLU2s sometime during the next couple of weeks ... If you could put up an updated set of instructions somewhere on how to go about this (you gave some pointers during an IRC chat a while ago) that would be awesome ... I'll gladly provide feedback :) -- Pascal Hofstee From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 07:45:15 2007 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 A41B816A4E5 for ; Wed, 28 Feb 2007 07:45:15 +0000 (UTC) (envelope-from dave@dogwood.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 19B2C13C58D for ; Wed, 28 Feb 2007 07:45:06 +0000 (UTC) (envelope-from dave@dogwood.com) Received: by py-out-1112.google.com with SMTP id f47so34829pye for ; Tue, 27 Feb 2007 23:45:05 -0800 (PST) Received: by 10.35.32.9 with SMTP id k9mr449063pyj.1172648705352; Tue, 27 Feb 2007 23:45:05 -0800 (PST) Received: from Gecko.dogwood.com ( [66.91.140.187]) by mx.google.com with ESMTP id c12sm1463685nzc.2007.02.27.23.45.04; Tue, 27 Feb 2007 23:45:05 -0800 (PST) X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 27 Feb 2007 21:45:01 -1000 To: freebsd-arm@freebsd.org From: David Cornejo Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> Subject: building ports for ARM 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, 28 Feb 2007 07:45:16 -0000 Aloha, Is there some generic way to cross-compile ports for the ARM? Some ports seem to be ok by overriding the CC/LD/etc. definitions, but others attempt to build stuff using compiled binaries... dave c From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 10:07:31 2007 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 9CE1F16A402 for ; Wed, 28 Feb 2007 10:07: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 5EF9813C47E for ; Wed, 28 Feb 2007 10:07:31 +0000 (UTC) (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 l1SA5D3m084455; Wed, 28 Feb 2007 03:05:14 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 28 Feb 2007 03:05:16 -0700 (MST) Message-Id: <20070228.030516.-432837530.imp@bsdimp.com> To: dave@dogwood.com From: "M. Warner Losh" In-Reply-To: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> References: <45e53301.5e2ca738.28ab.2d6c@mx.google.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, 28 Feb 2007 03:05:14 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: building ports for ARM 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, 28 Feb 2007 10:07:31 -0000 In message: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> David Cornejo writes: : Is there some generic way to cross-compile ports for the ARM? Some : ports seem to be ok by overriding the CC/LD/etc. definitions, but : others attempt to build stuff using compiled binaries... No. There's some things that can be done to make this process easier. However, there are four kinds of ports: simple, host tools needed and no cross support, with broken cross support, with working cross support. Only the first and the last can work. The last works by telling config to use its cross config to build. The first works by telling it to use ALL tools for cross build. I have a bunch of patches to install the cross tools into /usr/arm-freebsd so that autoconfig for the working ports can work, and a string of CC=, LD=, etc can work for the simple ports. I've not had time to integrate those into the tree yet. I also have some half-assed patches to ports as of about 4.8 that can help a little, but that don't apply cleanly to present ports... Warner From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 10:12:29 2007 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 0AC2816A414 for ; Wed, 28 Feb 2007 10:12:29 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id 7AD4F13C48E for ; Wed, 28 Feb 2007 10:12:26 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id DF99B33CBB; Wed, 28 Feb 2007 12:12:23 +0200 (SAST) Date: Wed, 28 Feb 2007 12:12:23 +0200 From: John Hay To: David Cornejo Message-ID: <20070228101223.GA28669@zibbi.meraka.csir.co.za> References: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@freebsd.org Subject: Re: building ports for ARM 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, 28 Feb 2007 10:12:29 -0000 On Tue, Feb 27, 2007 at 09:45:01PM -1000, David Cornejo wrote: > Aloha, > > Is there some generic way to cross-compile ports for the ARM? Some > ports seem to be ok by overriding the CC/LD/etc. definitions, but > others attempt to build stuff using compiled binaries... I gave up after a while and just set up a diskless arm that nfs mount one of our servers and use that to build packages of the ports that I need. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 10:20:46 2007 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 DCFF016A400 for ; Wed, 28 Feb 2007 10:20:46 +0000 (UTC) (envelope-from dave@dogwood.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id A696C13C49D for ; Wed, 28 Feb 2007 10:20:46 +0000 (UTC) (envelope-from dave@dogwood.com) Received: by py-out-1112.google.com with SMTP id f47so51006pye for ; Wed, 28 Feb 2007 02:20:46 -0800 (PST) Received: by 10.35.110.13 with SMTP id n13mr303385pym.1172658046143; Wed, 28 Feb 2007 02:20:46 -0800 (PST) Received: from Gecko.dogwood.com ( [66.91.140.187]) by mx.google.com with ESMTP id 16sm2064277nzo.2007.02.28.02.20.42; Wed, 28 Feb 2007 02:20:45 -0800 (PST) X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 28 Feb 2007 00:20:37 -1000 To: "M. Warner Losh" From: David Cornejo In-Reply-To: <20070228.030516.-432837530.imp@bsdimp.com> References: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> <20070228.030516.-432837530.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: <45e5577d.5a052323.3f11.ffffad26@mx.google.com> Cc: freebsd-arm@freebsd.org Subject: Re: building ports for ARM 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, 28 Feb 2007 10:20:46 -0000 was afraid of this, with one of the netgate avila boards, some ports are taking days to compile due to swapping. barring cross-compiling, does anyone have a binary package repository, or might be interested in one? dave c At 12:05 AM 2/28/2007, M. Warner Losh wrote: >In message: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> > David Cornejo writes: >: Is there some generic way to cross-compile ports for the ARM? Some >: ports seem to be ok by overriding the CC/LD/etc. definitions, but >: others attempt to build stuff using compiled binaries... > >No. > >There's some things that can be done to make this process easier. >However, there are four kinds of ports: simple, host tools needed and >no cross support, with broken cross support, with working cross >support. > >Only the first and the last can work. The last works by telling >config to use its cross config to build. The first works by telling >it to use ALL tools for cross build. > >I have a bunch of patches to install the cross tools into >/usr/arm-freebsd so that autoconfig for the working ports can work, >and a string of CC=, LD=, etc can work for the simple ports. I've not >had time to integrate those into the tree yet. I also have some >half-assed patches to ports as of about 4.8 that can help a little, >but that don't apply cleanly to present ports... > >Warner From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 10:48:58 2007 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 7046916A400 for ; Wed, 28 Feb 2007 10:48:58 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id E443813C4A5 for ; Wed, 28 Feb 2007 10:48:57 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 3449433CB7; Wed, 28 Feb 2007 12:24:59 +0200 (SAST) Date: Wed, 28 Feb 2007 12:24:59 +0200 From: John Hay To: freebsd-arm@freebsd.org Message-ID: <20070228102459.GB28669@zibbi.meraka.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: redboot based boot loader for kernels? 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, 28 Feb 2007 10:48:58 -0000 Hi, Does anyone have or is busy with an app that one can load in the redboot flash, that will load the kernel from the active partition of a compact flash? I know one can load the kernel in the redboot flash, but that makes remote upgrading more difficult. The way I have done with our wrap and soekris boards, is to create 2 slices on the CF. When upgrading, you just format and install on the non-active slice, change the active bit and reboot. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 11:39:42 2007 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 59E6016A401 for ; Wed, 28 Feb 2007 11:39:42 +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 8749B13C491 for ; Wed, 28 Feb 2007 11:39:40 +0000 (UTC) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.8/8.13.8) with ESMTP id l1SBoc7T030736; Wed, 28 Feb 2007 12:50:38 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.8/8.13.8/Submit) id l1SBobdd030735; Wed, 28 Feb 2007 12:50:37 +0100 (CET) (envelope-from mlfbsd) Date: Wed, 28 Feb 2007 12:50:37 +0100 From: Olivier Houchard To: John Hay Message-ID: <20070228115037.GA30703@ci0.org> References: <20070228102459.GB28669@zibbi.meraka.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070228102459.GB28669@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.4.1i Cc: freebsd-arm@freebsd.org Subject: Re: redboot based boot loader for kernels? 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, 28 Feb 2007 11:39:42 -0000 On Wed, Feb 28, 2007 at 12:24:59PM +0200, John Hay wrote: > Hi, > > Does anyone have or is busy with an app that one can load in the > redboot flash, that will load the kernel from the active partition > of a compact flash? I know one can load the kernel in the redboot > flash, but that makes remote upgrading more difficult. The way I > have done with our wrap and soekris boards, is to create 2 slices > on the CF. When upgrading, you just format and install on the > non-active slice, change the active bit and reboot. > > John Hi John, The problem is, it's very difficult to do so in a generic way. RedBoot doesn't export any facility to read from flash, so for each board, such a loader would require an IDE driver to read from CF, etc. As far as I know, nobody is working on it. Would being able to update the kernel located in the onboard flash from FreeBSD be an acceptable solution for you ? Olivier From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 12:58:18 2007 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 3D91816A400 for ; Wed, 28 Feb 2007 12:58:18 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id A5EEC13C481 for ; Wed, 28 Feb 2007 12:58:17 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id BBD3C33CB8; Wed, 28 Feb 2007 14:58:15 +0200 (SAST) Date: Wed, 28 Feb 2007 14:58:15 +0200 From: John Hay To: Olivier Houchard Message-ID: <20070228125815.GA35515@zibbi.meraka.csir.co.za> References: <20070228102459.GB28669@zibbi.meraka.csir.co.za> <20070228115037.GA30703@ci0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070228115037.GA30703@ci0.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@freebsd.org Subject: Re: redboot based boot loader for kernels? 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, 28 Feb 2007 12:58:18 -0000 Hi Olivier, On Wed, Feb 28, 2007 at 12:50:37PM +0100, Olivier Houchard wrote: > On Wed, Feb 28, 2007 at 12:24:59PM +0200, John Hay wrote: > > Hi, > > > > Does anyone have or is busy with an app that one can load in the > > redboot flash, that will load the kernel from the active partition > > of a compact flash? I know one can load the kernel in the redboot > > flash, but that makes remote upgrading more difficult. The way I > > have done with our wrap and soekris boards, is to create 2 slices > > on the CF. When upgrading, you just format and install on the > > non-active slice, change the active bit and reboot. > > The problem is, it's very difficult to do so in a generic way. RedBoot doesn't > export any facility to read from flash, so for each board, such a loader would > require an IDE driver to read from CF, etc. As far as I know, nobody is > working on it. > Would being able to update the kernel located in the onboard flash from > FreeBSD be an acceptable solution for you ? Yes that would also be great. At the moment I have ROOTDEVNAME=\"ufs:ad0s1a\" in my kernel config file and twiddle that to the correct slice, but maybe one can make something a little more intelligent that look for the active slice. The board I have is an Avila 2348. I proably should have mentioned that in the first email. :-/ John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 15:29:46 2007 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 49F9216A407 for ; Wed, 28 Feb 2007 15:29:46 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from qsrv02sl.mx.bigpond.com (qsrv02sl.mx.bigpond.com [144.140.93.182]) by mx1.freebsd.org (Postfix) with ESMTP id D0A0C13C494 for ; Wed, 28 Feb 2007 15:29:45 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from oaamta02sl.mx.bigpond.com ([144.132.228.157]) by omta02sl.mx.bigpond.com with ESMTP id <20070228132243.RYUF21976.omta02sl.mx.bigpond.com@oaamta02sl.mx.bigpond.com> for ; Wed, 28 Feb 2007 13:22:43 +0000 Received: from areilly.bpa.nu ([144.132.228.157]) by oaamta02sl.mx.bigpond.com with ESMTP id <20070228132243.BDRP19608.oaamta02sl.mx.bigpond.com@areilly.bpa.nu> for ; Wed, 28 Feb 2007 13:22:43 +0000 Received: (qmail 40956 invoked by uid 501); 28 Feb 2007 13:19:53 -0000 Date: Thu, 1 Mar 2007 00:19:53 +1100 From: Andrew Reilly To: David Cornejo Message-ID: <20070228131953.GA40908@duncan.reilly.home> References: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> <20070228.030516.-432837530.imp@bsdimp.com> <45e5577d.5a052323.3f11.ffffad26@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45e5577d.5a052323.3f11.ffffad26@mx.google.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-arm@freebsd.org Subject: Re: building ports for ARM 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, 28 Feb 2007 15:29:46 -0000 On Wed, Feb 28, 2007 at 12:20:37AM -1000, David Cornejo wrote: > was afraid of this, with one of the netgate avila boards, some ports > are taking days to compile due to swapping. > > barring cross-compiling, does anyone have a binary package > repository, or might be interested in one? Have you tried qemu's ARM emulation, on a beasty host? (Not that I have, but that's what I'm planning to try...) Cheers, -- Andrew From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 16:01:06 2007 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 7F13516A400 for ; Wed, 28 Feb 2007 16:01:06 +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 5990E13C494 for ; Wed, 28 Feb 2007 16:01:06 +0000 (UTC) (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 l1SG13Aa043657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Feb 2007 08:01:05 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45E5A73E.20503@errno.com> Date: Wed, 28 Feb 2007 08:01:02 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.9 (X11/20070208) MIME-Version: 1.0 To: John Hay References: <20070228102459.GB28669@zibbi.meraka.csir.co.za> In-Reply-To: <20070228102459.GB28669@zibbi.meraka.csir.co.za> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org Subject: Re: redboot based boot loader for kernels? 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, 28 Feb 2007 16:01:06 -0000 John Hay wrote: > Hi, > > Does anyone have or is busy with an app that one can load in the > redboot flash, that will load the kernel from the active partition > of a compact flash? I know one can load the kernel in the redboot > flash, but that makes remote upgrading more difficult. The way I > have done with our wrap and soekris boards, is to create 2 slices > on the CF. When upgrading, you just format and install on the > non-active slice, change the active bit and reboot. A certain someone promised to add read/write support for the flash. When that happens another option is to write the new kernel to flash before rebooting. Otherwise we need a redboot image that grok's ufs or a secondary bootstrap that can be written to flash that knows how to boot from cf (I recall the latter might be in the obsd thecus work). Sam From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 16:42:52 2007 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 C751616A400 for ; Wed, 28 Feb 2007 16:42:52 +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 8391D13C428 for ; Wed, 28 Feb 2007 16:42:52 +0000 (UTC) (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 l1SGadEb092713; Wed, 28 Feb 2007 09:36:40 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 28 Feb 2007 09:36:44 -0700 (MST) Message-Id: <20070228.093644.-1975969471.imp@bsdimp.com> To: mlfbsd@ci0.org From: "M. Warner Losh" In-Reply-To: <20070228115037.GA30703@ci0.org> References: <20070228102459.GB28669@zibbi.meraka.csir.co.za> <20070228115037.GA30703@ci0.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, 28 Feb 2007 09:36:40 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: redboot based boot loader for kernels? 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, 28 Feb 2007 16:42:52 -0000 In message: <20070228115037.GA30703@ci0.org> Olivier Houchard writes: : On Wed, Feb 28, 2007 at 12:24:59PM +0200, John Hay wrote: : > Hi, : > : > Does anyone have or is busy with an app that one can load in the : > redboot flash, that will load the kernel from the active partition : > of a compact flash? I know one can load the kernel in the redboot : > flash, but that makes remote upgrading more difficult. The way I : > have done with our wrap and soekris boards, is to create 2 slices : > on the CF. When upgrading, you just format and install on the : > non-active slice, change the active bit and reboot. : > : > John : : Hi John, : : The problem is, it's very difficult to do so in a generic way. RedBoot doesn't : export any facility to read from flash, so for each board, such a loader would : require an IDE driver to read from CF, etc. As far as I know, nobody is : working on it. : Would being able to update the kernel located in the onboard flash from : FreeBSD be an acceptable solution for you ? The other option is to load boot2, or its kin, from flash and have that load the kernel from CF... Warner From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 16:44:33 2007 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 71D3416A401 for ; Wed, 28 Feb 2007 16:44:33 +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 AC5F413C481 for ; Wed, 28 Feb 2007 16:44:32 +0000 (UTC) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.8/8.13.8) with ESMTP id l1SGtTTo033441; Wed, 28 Feb 2007 17:55:29 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.8/8.13.8/Submit) id l1SGtTrt033440; Wed, 28 Feb 2007 17:55:29 +0100 (CET) (envelope-from mlfbsd) Date: Wed, 28 Feb 2007 17:55:28 +0100 From: Olivier Houchard To: "M. Warner Losh" Message-ID: <20070228165528.GA33406@ci0.org> References: <20070228102459.GB28669@zibbi.meraka.csir.co.za> <20070228115037.GA30703@ci0.org> <20070228.093644.-1975969471.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070228.093644.-1975969471.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Cc: freebsd-arm@freebsd.org Subject: Re: redboot based boot loader for kernels? 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, 28 Feb 2007 16:44:33 -0000 On Wed, Feb 28, 2007 at 09:36:44AM -0700, M. Warner Losh wrote: > In message: <20070228115037.GA30703@ci0.org> > Olivier Houchard writes: > : On Wed, Feb 28, 2007 at 12:24:59PM +0200, John Hay wrote: > : > Hi, > : > > : > Does anyone have or is busy with an app that one can load in the > : > redboot flash, that will load the kernel from the active partition > : > of a compact flash? I know one can load the kernel in the redboot > : > flash, but that makes remote upgrading more difficult. The way I > : > have done with our wrap and soekris boards, is to create 2 slices > : > on the CF. When upgrading, you just format and install on the > : > non-active slice, change the active bit and reboot. > : > > : > John > : > : Hi John, > : > : The problem is, it's very difficult to do so in a generic way. RedBoot doesn't > : export any facility to read from flash, so for each board, such a loader would > : require an IDE driver to read from CF, etc. As far as I know, nobody is > : working on it. > : Would being able to update the kernel located in the onboard flash from > : FreeBSD be an acceptable solution for you ? > > The other option is to load boot2, or its kin, from flash and have > that load the kernel from CF... > Well the problem is still that we have to teach boot2 to use every CF. Olivier From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 16:44:59 2007 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 CEE5216A402 for ; Wed, 28 Feb 2007 16:44:59 +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 8146413C48E for ; Wed, 28 Feb 2007 16:44:59 +0000 (UTC) (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 l1SGfocN092741; Wed, 28 Feb 2007 09:41:50 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 28 Feb 2007 09:41:55 -0700 (MST) Message-Id: <20070228.094155.660269855.imp@bsdimp.com> To: sam@errno.com From: "M. Warner Losh" In-Reply-To: <45E5A73E.20503@errno.com> References: <20070228102459.GB28669@zibbi.meraka.csir.co.za> <45E5A73E.20503@errno.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, 28 Feb 2007 09:41:50 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: redboot based boot loader for kernels? 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, 28 Feb 2007 16:44:59 -0000 In message: <45E5A73E.20503@errno.com> Sam Leffler writes: : John Hay wrote: : > Hi, : > : > Does anyone have or is busy with an app that one can load in the : > redboot flash, that will load the kernel from the active partition : > of a compact flash? I know one can load the kernel in the redboot : > flash, but that makes remote upgrading more difficult. The way I : > have done with our wrap and soekris boards, is to create 2 slices : > on the CF. When upgrading, you just format and install on the : > non-active slice, change the active bit and reboot. : : A certain someone promised to add read/write support for the flash. That would be me... My day job has been crazy and my new son isn't yet sleeping through the night. : When that happens another option is to write the new kernel to flash : before rebooting. Otherwise we need a redboot image that grok's ufs or : a secondary bootstrap that can be written to flash that knows how to : boot from cf (I recall the latter might be in the obsd thecus work). The at91 boot2 groks ufs and only needs a function that can read the sectors from the underlying media to grok new media. Of course, it inherited most of that from the i386 boot2. Warner From owner-freebsd-arm@FreeBSD.ORG Thu Mar 1 03:16:31 2007 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 0EB2216A401 for ; Thu, 1 Mar 2007 03:16:31 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id C923813C441 for ; Thu, 1 Mar 2007 03:16:30 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id l212ktd5045884; Wed, 28 Feb 2007 21:46:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id l212ktZq066431; Wed, 28 Feb 2007 21:46:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id DB9357303E; Wed, 28 Feb 2007 21:46:54 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070301024654.DB9357303E@freebsd-current.sentex.ca> Date: Wed, 28 Feb 2007 21:46:54 -0500 (EST) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 03:16:31 -0000 TB --- 2007-03-01 01:35:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-03-01 01:35:00 - starting HEAD tinderbox run for arm/arm TB --- 2007-03-01 01:35:00 - cleaning the object tree TB --- 2007-03-01 01:35:52 - checking out the source tree TB --- 2007-03-01 01:35:52 - cd /tinderbox/HEAD/arm/arm TB --- 2007-03-01 01:35:52 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-03-01 01:49:54 - building world (CFLAGS=-O2 -pipe) TB --- 2007-03-01 01:49:54 - cd /src TB --- 2007-03-01 01:49:54 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 1 01:49:55 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/ipsec.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/bpf.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/pfkey.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/inet6.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/ipx.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -o netstat if.o inet.o main.o mbuf.o mcast.o mroute.o route.o unix.o atalk.o netgraph.o mroute6.o ipsec.o bpf.o pfkey.o inet6.o ipx.o -lkvm -lmemstat -lnetgraph -lutil -lipx mcast.o(.text+0x1ec): In function `ifmalist_dump_af': : undefined reference to `addr2ascii' *** Error code 1 Stop in /src/usr.bin/netstat. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-03-01 02:46:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-03-01 02:46:54 - ERROR: failed to build world TB --- 2007-03-01 02:46:54 - tinderbox aborted TB --- 0.42 user 1.66 system 4314.17 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-arm@FreeBSD.ORG Thu Mar 1 09:33:57 2007 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 1E1EF16A400 for ; Thu, 1 Mar 2007 09:33:57 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id D261B13C467 for ; Thu, 1 Mar 2007 09:33:56 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 71616178B5A for ; Thu, 1 Mar 2007 11:33:55 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12636-05 for ; Thu, 1 Mar 2007 11:33:52 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id B33E8178B4F for ; Thu, 1 Mar 2007 11:33:52 +0200 (EET) Message-ID: <45E69E00.50300@bulinfo.net> Date: Thu, 01 Mar 2007 11:33:52 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Subject: PHY IDs? 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, 01 Mar 2007 09:33:57 -0000 Hello, What is the reason for ignoring PHYs with nonzero ID in ate_miibus_readreg()? My PHY is at 0x10: ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 miibus0: on ate0 rlphy0: PHY 16 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ate0: Ethernet address: 00:ff:01:00:00:43 ate0: [ITHREAD] From owner-freebsd-arm@FreeBSD.ORG Thu Mar 1 10:39:39 2007 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 0D05E16A404 for ; Thu, 1 Mar 2007 10:39:39 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id A28AD13C481 for ; Thu, 1 Mar 2007 10:39:38 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id A1D3D178C4A for ; Thu, 1 Mar 2007 12:39:37 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17884-02 for ; Thu, 1 Mar 2007 12:39:34 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id A6612178C46 for ; Thu, 1 Mar 2007 12:39:34 +0200 (EET) Message-ID: <45E6AD66.8050702@bulinfo.net> Date: Thu, 01 Mar 2007 12:39:34 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Subject: kernel panic(USB related)? 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, 01 Mar 2007 10:39:39 -0000 ohci0: mem 0x300000-0x3fffff irq 23 on atmelarm0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] Enable ohci_clk Enable mck Enable plla Enable main Turning PC 0x800 on Done PCSR is now: 0x1fffffc! Enable uhpck Enable pllb Enable main Turning PLLB 0x102f3e05 on Done! Turning SC 0x10 on Done SCSR is now: 0x215! vm_fault(0xc01f4e80, 300000, 2, 0) -> 1 Fatal kernel mode data abort: 'Translation Fault (S)' trapframe: 0xc0220ccc FSR=00000005, FAR=00300004, spsr=600000d3 r0 =00000000, r1 =00300000, r2 =00000004, r3 =00000000 r4 =c084d000, r5 =00000000, r6 =00000001, r7 =ffffffff r8 =00000000, r9 =00000002, r10=c080a100, r11=c0220d54 r12=c01f0670, ssp=c0220d18, slr=c01803f8, pc =c0163dd8 [thread pid 0 tid 0 ] Stopped at generic_bs_w_4: str r3, [r1, r2] db> bt Tracing pid 0 tid 0 td 0xc01f4ce8 db_trace_thread() at db_trace_thread+0x10 scp=0xc0168018 rlv=0xc00145a4 (db_command_loop+0x724) rsp=0xc02209d4 rfp=0xc02209f8 r10=0x00000000 r9=0xc01f2e14 r8=0xc01f3648 r7=0xc0220a0c r6=0x00000010 r5=0x00000000 r4=0xc01f4ce8 db_command_loop() at db_command_loop+0x694 scp=0xc0014514 rlv=0xc0014198 (db_command_loop+0x318) rsp=0xc02209fc rfp=0xc0220ab0 r6=0x00000000 r5=0xc0220a08 r4=0xc01d9b40 db_command_loop() at db_command_loop+0x10 scp=0xc0013e90 rlv=0xc00164cc (X_db_symbol_values+0x18c) rsp=0xc0220ab4 rfp=0xc0220bd0 r10=0xc01f8ab4 r9=0xc01f8aac r8=0x00000005 r7=0x00000000 r6=0xc0220ccc r5=0x000000c0 r4=0xc0220abc X_db_symbol_values() at X_db_symbol_values+0x114 scp=0xc0016454 rlv=0xc0099440 (kdb_trap+0xbc) rsp=0xc0220bd4 rfp=0xc0220c00 r4=0x000000c0 kdb_trap() at kdb_trap+0x10 scp=0xc0099394 rlv=0xc0173fd0 (sysarch+0x1e4) rsp=0xc0220c04 rfp=0xc0220c20 r10=0xc0220ccc r9=0xc01f4e80 r8=0xc0220ef8 r7=0xc01f4ce8 r6=0x00300004 r5=0x00000005 r4=0xc0220ccc sysarch() at sysarch+0xd4 scp=0xc0173ec0 rlv=0xc0174534 (data_abort_handler+0x4e0) rsp=0xc0220c24 rfp=0xc0220cc8 r6=0x00300000 r5=0xc0220c48 r4=0xc01f4afc data_abort_handler() at data_abort_handler+0x10 scp=0xc0174064 rlv=0xc016a020 (address_exception_entry+0x50) rsp=0xc0220ccc rfp=0xc0220d54 r10=0xc080a100 r9=0x00000002 r8=0x00000000 r7=0xffffffff r6=0x00000001 r5=0xe0000004 r4=0xc084d000 at91_pmc_clock_disable() at at91_pmc_clock_disable+0x3850 scp=0xc01802a4 rlv=0xc0093e24 (device_attach+0x238) rsp=0xc0220d58 rfp=0xc0220d9c r10=0xc018d40c r9=0xc018da28 r8=0x00000000 r7=0xc080a100 r6=0xc0092090 r5=0x80000000 r4=0xc07acc00 device_attach() at device_attach+0x10 scp=0xc0093bfc rlv=0xc0094a00 (bus_generic_attach+0x20) rsp=0xc0220da0 rfp=0xc0220db4 r10=0x00000017 r9=0x00000000 r8=0xc07acc00 r7=0xc080a100 r6=0x00000000 r5=0xc01f0654 r4=0xc080a100 bus_generic_attach() at bus_generic_attach+0x10 scp=0xc00949f0 rlv=0xc017a2c0 (bus_dma_get_range_nb+0x3bc) rsp=0xc0220db8 rfp=0xc0220df4 r4=0x00000000 bus_dma_get_range_nb() at bus_dma_get_range_nb+0x18 scp=0xc0179f1c rlv=0xc0093e24 (device_attach+0x238) rsp=0xc0220df8 rfp=0xc0220e3c r10=0xc018d40c r9=0xc018da28 r8=0x00000000 r7=0xc07acc00 r6=0xc0092090 r5=0x80000000 r4=0xc07ab100 device_attach() at device_attach+0x10 scp=0xc0093bfc rlv=0xc0094a00 (bus_generic_attach+0x20) rsp=0xc0220e40 rfp=0xc0220e54 r10=0xc018d40c r9=0xc018da28 r8=0x00000000 r7=0xc07ab100 r6=0xc0092090 r5=0x80000000 r4=0xc07acc00 bus_generic_attach() at bus_generic_attach+0x10 scp=0xc00949f0 rlv=0xc016be3c (dev_mem_md_init+0x154) rsp=0xc0220e58 rfp=0xc0220e6c r4=0xc07ab100 dev_mem_md_init() at dev_mem_md_init+0x144 scp=0xc016be2c rlv=0xc0093e24 (device_attach+0x238) rsp=0xc0220e70 rfp=0xc0220eb4 r4=0xc07ab14c device_attach() at device_attach+0x10 scp=0xc0093bfc rlv=0xc0095f60 (root_bus_configure+0x2c) rsp=0xc0220eb8 rfp=0xc0220ecc r10=0x00000000 r9=0x0000056c r8=0xc01f539c r7=0xc01f5390 r6=0xc01f5398 r5=0xc01f5394 r4=0xc07ab100 root_bus_configure() at root_bus_configure+0x10 scp=0xc0095f44 rlv=0xc004f098 (mi_startup+0xd8) rsp=0xc0220ed0 rfp=0xc0220ef4 r4=0xc01abbf0 mi_startup() at mi_startup+0x10 scp=0xc004efd0 rlv=0xc00001b0 (btext+0xd0) rsp=0xc0220ef8 rfp=0x00000000 r10=0xfffff80f r8=0x2020ef2c r7=0x20000110 r6=0x00000004 r5=0x2000011c r4=0x200001f0 db> From owner-freebsd-arm@FreeBSD.ORG Thu Mar 1 16:10:34 2007 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 450E616A405 for ; Thu, 1 Mar 2007 16:10:34 +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 F338613C4A3 for ; Thu, 1 Mar 2007 16:10:33 +0000 (UTC) (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 l21G99BA007984; Thu, 1 Mar 2007 09:09:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 01 Mar 2007 09:09:14 -0700 (MST) Message-Id: <20070301.090914.179959647.imp@bsdimp.com> To: krassi@bulinfo.net From: "M. Warner Losh" In-Reply-To: <45E69E00.50300@bulinfo.net> References: <45E69E00.50300@bulinfo.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, 01 Mar 2007 09:09:10 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: PHY IDs? 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, 01 Mar 2007 16:10:34 -0000 In message: <45E69E00.50300@bulinfo.net> Krassimir Slavchev writes: : Hello, : : What is the reason for ignoring PHYs with nonzero ID in : ate_miibus_readreg()? I had a board that would, I thought, reply to all PHY addresses. Turns out that something else was wrong and I've removed this test from my current sources. Warner : My PHY is at 0x10: : : ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 : miibus0: on ate0 : rlphy0: PHY 16 on miibus0 : rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto : ate0: Ethernet address: 00:ff:01:00:00:43 : ate0: [ITHREAD] From owner-freebsd-arm@FreeBSD.ORG Fri Mar 2 15:03:16 2007 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 18F2B16A406 for ; Fri, 2 Mar 2007 15:03:16 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id CBE3D13C4B6 for ; Fri, 2 Mar 2007 15:03:15 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 6DC6E17A70C for ; Fri, 2 Mar 2007 17:03:14 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33122-03 for ; Fri, 2 Mar 2007 17:03:11 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 7FBE917A70A for ; Fri, 2 Mar 2007 17:03:09 +0200 (EET) Message-ID: <45E83CAB.1090005@bulinfo.net> Date: Fri, 02 Mar 2007 17:03:07 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Subject: IIC support? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 15:03:16 -0000 Hello, I have problems to access the iic eeprom from userland. Even after set SCAN_IICBUS in iicbus.c nothing has been detected. I have made some tests from the bootloader to read/write from/to the eeprom and they work. Is there any known problems with TWI or any differences between board settings? Best Regards From owner-freebsd-arm@FreeBSD.ORG Fri Mar 2 17:19:44 2007 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 7637716A403 for ; Fri, 2 Mar 2007 17:19:44 +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 1B20313C46B for ; Fri, 2 Mar 2007 17:19:43 +0000 (UTC) (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 l22HHiPg028793; Fri, 2 Mar 2007 10:17:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 02 Mar 2007 10:17:44 -0700 (MST) Message-Id: <20070302.101744.115917142.imp@bsdimp.com> To: krassi@bulinfo.net From: Warner Losh In-Reply-To: <45E83CAB.1090005@bulinfo.net> References: <45E83CAB.1090005@bulinfo.net> X-Mailer: Mew version 3.3 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]); Fri, 02 Mar 2007 10:17:44 -0700 (MST) Cc: freebsd-arm@FreeBSD.org Subject: Re: IIC support? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 17:19:44 -0000 > I have problems to access the iic eeprom from userland. Even after set > SCAN_IICBUS in iicbus.c nothing has been detected. I have made some > tests from the bootloader to read/write from/to the eeprom and they work. > Is there any known problems with TWI or any differences between board > settings? The IIC bus is not a self enumerating bus. Bad things happen when you go out and try to 'probe' it, although often you can get away with that. FreeBSD takes a conservative approach. You need hints for each iic device on bus that you have on your board. Warner From owner-freebsd-arm@FreeBSD.ORG Fri Mar 2 18:17:41 2007 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 8D63416A400 for ; Fri, 2 Mar 2007 18:17:41 +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 5002913C441 for ; Fri, 2 Mar 2007 18:17:39 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (3n7bj5spgi33kad7@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l22HxFuc090145; Fri, 2 Mar 2007 09:59:15 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l22HxDWk090143; Fri, 2 Mar 2007 09:59:13 -0800 (PST) (envelope-from jmg) Date: Fri, 2 Mar 2007 09:59:13 -0800 From: John-Mark Gurney To: Krassimir Slavchev Message-ID: <20070302175913.GQ73385@funkthat.com> Mail-Followup-To: Krassimir Slavchev , freebsd-arm@freebsd.org References: <45E83CAB.1090005@bulinfo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E83CAB.1090005@bulinfo.net> 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: freebsd-arm@freebsd.org Subject: Re: IIC support? 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: Fri, 02 Mar 2007 18:17:41 -0000 Krassimir Slavchev wrote this message on Fri, Mar 02, 2007 at 17:03 +0200: > I have problems to access the iic eeprom from userland. Even after set > SCAN_IICBUS in iicbus.c nothing has been detected. I have made some > tests from the bootloader to read/write from/to the eeprom and they work. > Is there any known problems with TWI or any differences between board > settings? You can load the iic driver, and attempt to access the device through iic's ioctl interface... As Warner mentioned, iic isn't really self enumerating, so it requires you to privde the address of the device that you are accessing... -- 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 Fri Mar 2 18:26:08 2007 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 C627616A404 for ; Fri, 2 Mar 2007 18:26:08 +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 853A013C474 for ; Fri, 2 Mar 2007 18:26:08 +0000 (UTC) (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 l22IMkjn029213; Fri, 2 Mar 2007 11:22:46 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 02 Mar 2007 11:22:46 -0700 (MST) Message-Id: <20070302.112246.21920579.imp@bsdimp.com> To: gurney_j@resnet.uoregon.edu From: Warner Losh In-Reply-To: <20070302175913.GQ73385@funkthat.com> References: <45E83CAB.1090005@bulinfo.net> <20070302175913.GQ73385@funkthat.com> X-Mailer: Mew version 3.3 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]); Fri, 02 Mar 2007 11:22:46 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: IIC support? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 18:26:08 -0000 > Krassimir Slavchev wrote this message on Fri, Mar 02, 2007 at 17:03 +0200: > > I have problems to access the iic eeprom from userland. Even after set > > SCAN_IICBUS in iicbus.c nothing has been detected. I have made some > > tests from the bootloader to read/write from/to the eeprom and they work. > > Is there any known problems with TWI or any differences between board > > settings? > > You can load the iic driver, and attempt to access the device through > iic's ioctl interface... As Warner mentioned, iic isn't really self > enumerating, so it requires you to privde the address of the device > that you are accessing... HEre's what I ahve at work: # ID Eeprom hint.icee.0.at="iicbus0" hint.icee.0.addr=0x80 hint.icee.0.type=8 hint.icee.0.size=2048 hint.icee.0.rd_sz=256 hint.icee.0.wr_sz=16 # Config Eeprom hint.icee.1.at="iicbus0" hint.icee.1.addr=0xa6 hint.icee.1.type=16 hint.icee.1.size=32768 hint.icee.1.rd_sz=256 hint.icee.1.wr_sz=16