From owner-freebsd-arm@FreeBSD.ORG Mon May 25 00:58:05 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E859179 for ; Mon, 25 May 2015 00:58:05 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) by mx1.freebsd.org (Postfix) with SMTP id 3953516E for ; Mon, 25 May 2015 00:58:04 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Mon, 25 May 2015 00:58:22 +0000 (UTC) Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t4P0w34q009191; Sun, 24 May 2015 18:58:03 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1432515483.1200.22.camel@freebsd.org> Subject: Re: panic: arm_unmask_irq [was: Re: TI platforms code update: switching to vendor FDT data] From: Ian Lepore To: Marcel Moolenaar Cc: Oleksandr Tymoshenko , "freebsd-arm@freebsd.org List" Date: Sun, 24 May 2015 18:58:03 -0600 In-Reply-To: References: <72E1D87A-1CEF-4719-907E-CF8E9D720FD1@xcllnt.net> <3741A6A7-1185-4E5A-9E98-22F5A6C730DC@freebsd.org> <3B662B61-1778-4791-A09F-A9162D3D7191@xcllnt.net> <1432514469.1200.19.camel@freebsd.org> Content-Type: text/plain; charset="iso-8859-13" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2015 00:58:05 -0000 On Sun, 2015-05-24 at 17:54 -0700, Marcel Moolenaar wrote: > > On May 24, 2015, at 5:41 PM, Ian Lepore wrote: > > > > "ti,aintc" is the compat string from the old fdt data, the new one that > > teh driver now recognizes would be "ti,am33xx-intc¡. > > Noticed that too. Trying to boot now and see if I can recover > the BBB. > > It would have been nice if we would match our own device type > for a while longer... > > -- > Marcel Moolenaar > marcel@xcllnt.net > That would probably work for the interrupt controller, but would fail completely for many other devices. We did a pretty bad thing when we started making up our own fdt data long ago. It turns out how we structure our drivers is necessarily dictated by the linux developers who write fdt data. The data they decide to include and how they structure it leaves us little choice. -- Ian