Subject: Re: SmartFirmware interrupts (was: Current EFIKA status?)
To: Matt Sealey <firstname.lastname@example.org>
From: Frank Wille <email@example.com>
Date: 10/15/2007 00:39:15
Matt Sealey wrote:
> only thing stopping you from having a port is to STOP relying on the
> Open Firmware client interface for abstraction and implement the
> interrupt controller.
Hm. Which information does SmartFirmware provide about it? The only thing I
found was "8259-IRQ at f1000cb4". This is for the ISA interrupts?
Maybe it's because I'm just a beginner, but, are there any other interrupt
controllers (in the north bridge?)? And how do I know about their registers
Or how about the interrupts of PCI devices? Other OF implementations have
properties like "interrupt-map", "#interrupt-cells", "AAPL,interrupts", etc.
But in SmartFirmware there is nothing. How do I know which interrupt a
device was assigned to?
> Too much time has been wasted on trying to expose a
> network device or a block device from the device tree... the OpenBSD
> port to Pegasos was not this complicated, even in the slightest.
I had a look at the OpenBSD port. It definitely accesses the Marvell
registers directly, e.g. c78, c7c, cf8, cfc, 118, 11c. Base address of the
chip seems to be f1000000.
_ Frank Wille (firstname.lastname@example.org)
_ // http://sun.hasenbraten.de/~frank/
\X/ Phx @ #AmigaGer