Date: Sun, 24 May 2015 18:58:03 -0600 From: Ian Lepore <ian@freebsd.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Oleksandr Tymoshenko <gonzo@FreeBSD.org>, "freebsd-arm@freebsd.org List" <freebsd-arm@freebsd.org> Subject: Re: panic: arm_unmask_irq [was: Re: TI platforms code update: switching to vendor FDT data] Message-ID: <1432515483.1200.22.camel@freebsd.org> In-Reply-To: <DED4D218-842A-4CD2-8BB1-8114B68A748A@xcllnt.net> References: <C9791C97-D5B1-433A-9AC0-CA2707C6137F@freebsd.org> <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> <DED4D218-842A-4CD2-8BB1-8114B68A748A@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2015-05-24 at 17:54 -0700, Marcel Moolenaar wrote: > > On May 24, 2015, at 5:41 PM, Ian Lepore <ian@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1432515483.1200.22.camel>