From owner-freebsd-arm@FreeBSD.ORG Fri Jan 6 19:51:05 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44F86106564A for ; Fri, 6 Jan 2012 19:51:05 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 2BBEC8FC0A for ; Fri, 6 Jan 2012 19:51:05 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta02.emeryville.ca.mail.comcast.net with comcast id JKX71i0040EPchoA2KqycJ; Fri, 06 Jan 2012 19:50:58 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta01.emeryville.ca.mail.comcast.net with comcast id JKV61i0144NgCEG8MKV7RL; Fri, 06 Jan 2012 19:29:08 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q06Jp1s9023090; Fri, 6 Jan 2012 12:51:02 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Mattia Rossi In-Reply-To: <4F05503D.4030303@swin.edu.au> References: <4F05503D.4030303@swin.edu.au> Content-Type: text/plain Date: Fri, 06 Jan 2012 12:51:01 -0700 Message-Id: <1325879461.25037.87.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org Subject: Re: SDIO driver for OpenRD Ultimate/ Dreamplug 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, 06 Jan 2012 19:51:05 -0000 On Thu, 2012-01-05 at 18:24 +1100, Mattia Rossi wrote: > Hi all, > > I've tried to compile and use the SDIO driver found here: > http://people.freebsd.org/~raj/misc/mv_sdio.c > > and here: > http://freebsd.1045724.n5.nabble.com/SD-MMC-driver-for-OpenRD-Board-td4384370.html > > but it causes the kernel to panic. > I'm not able to find the cause of the problem. > It would be great if anyone could help me to get this going :-) > [snip] > mmc0: Probing bus > mv_gpio_intr_handler(): No handler for Pin 34 > sdio0: Card inserted > sdio0: Previous removal has not been detected properly > mmc0: detached > [snip] > GPIO: gpio@10100 { > #gpio-cells = <3>; > compatible = "mrvl,gpio"; > reg = <0x10100 0x20>; > gpio-controller = <1>; > pin-count = <50>; > interrupts = <35 36 37 38 39 40 41>; > interrupt-parent = <&PIC>; > I'll start by saying I don't know much about FDT (I only first heard of it a couple weeks ago, and it's now high on my "learn more about this" list)... I notice the backtrace shows signs of the crash being interrupt-related, and boot output included a complaint about "no handler for pin 34", and the FDT gpio block lists a bunch of pins in the interrupts= line but not 34. Could it be as easy as adding 34 to that list? -- Ian