Port-ofppc archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: FirePower (was Re: TODO list for ofppc)

On 24-Jan-2008 Izumi Tsutsui wrote:
> extent_alloc_region: extent `ofwpci io-space' (0x0 - 0x3f7fffff)
> extent_alloc_region: start 0x80010000, end 0x80fffffe
> panic: extent_alloc_region: region lies outside extent
> Stopped in pid 0.1 (system) at  netbsd:cpu_Debugger+0x10:       lwz     r0,
> r1,
> 0x14
> ---

Ahh.. now this panic I understand.  Its angry because I hardcoded the extent
for iomem for the 7044.  We are *definately* going to need per-model
information to do the io extents.

Here is the procedure to find out the proper io extent:

disable PCI_NETBSD_CONFIGURE and enable PCI_CONF_DUMP. Let the machine boot,
and for any device that has a sane set of BARs, record where they live.  That
should give you an idea of what the correct io range is.  You can test by then
re-enabling PCI_NETBSD_CONFIGURE, and leaving PCI_CONF_DUMP in.

> other-bus-reg            07 e2 2e e0 bf ff ff f0 00 00 00 01 
> aix-chip-id              244d0081 
> aix-id&type              41 d0 00 00 00 08 00 01 
> reg                      00000001 00000020 00000002 
>                          00000001 000000a0 00000002 
>                          00000001 000004d0 00000002 
> interrupts               00000002 
>                          0000000d 
> compatible               pnpPNP,0
> device_type              interrupt-controller
> name                     interrupt-controller

Yeah..  probably just need to add that compatible id to the code in
powerpc/pci_machdep_ofw that looks for it.

Tim Rightnour <root%garbled.net@localhost>
NetBSD: Free multi-architecture OS http://www.netbsd.org/
Genecys: Open Source 3D MMORPG: http://www.genecys.org/

Home | Main Index | Thread Index | Old Index