bk 2.4.1pre2 Lombard PCI allocation fails.

bk 2.4.1pre2 Lombard PCI allocation fails.

[Iain Sandoe]

Hi,

as the title says...
The machine boots and (seems) OK.

FWIW: I boot this machine with BootX [1.2.2] (and always have, without
problem, until this time).

relevant DMESG below.
ciao,
Iain.

========

Linux version 2.4.1-pre2 (iain-s@athena) (gcc version 2.95.2 19991024
(release/franzo)) #1 Mon Jan 15 05:27:33 GMT 2001
Registered 1 feature controller(s)
PMU driver initialized for 1999 PowerBook G3
Found Grackle (MPC106) PCI host bridge at 0x80000000. Firmware bus number:
0->0
[...]
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Fixup mem res, dev: 0.e, res_start: 80882000->80882000
Fixup mem res, dev: 0.10, res_start: 80800000->80800000
Fixup mem res, dev: 0.11, res_start: 81000000->81000000
Fixup mem res, dev: 0.11, res_start: 81fff000->81fff000
Fixup mem res, dev: 0.13, res_start: 80880000->80880000
PCI: Resource 80882000-80882fff (f=200, d=0, p=0)
PCI: Resource 00000c00-00000cff (f=101, d=0, p=0)
PCI: Resource 80800000-8087ffff (f=200, d=0, p=0)
PCI: Resource 81000000-81ffffff (f=200, d=0, p=0)
PCI: Resource 81fff000-81ffffff (f=200, d=0, p=0)
PCI: Cannot allocate resource region 2 of device 00:11.0
PCI: Resource 80880000-80880fff (f=200, d=0, p=0)
PCI: Resource 00000c00-00000cff (f=101, d=1, p=1)
PCI: Cannot allocate resource region 1 of device 00:11.0
  got res[10000000:10000fff] for resource 2 of ATI Technologies Inc 3D Rage
LT Pro
Registered "pmu" backlight controller, level: 1/15
======

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: bk 2.4.1pre2 Lombard PCI allocation fails.

[Michael Schmitz]

> as the title says...
> The machine boots and (seems) OK.
>
> FWIW: I boot this machine with BootX [1.2.2] (and always have, without
> problem, until this time).
> PCI: Cannot allocate resource region 2 of device 00:11.0
> PCI: Resource 80880000-80880fff (f=200, d=0, p=0)
> PCI: Resource 00000c00-00000cff (f=101, d=1, p=1)
> PCI: Cannot allocate resource region 1 of device 00:11.0
>   got res[10000000:10000fff] for resource 2 of ATI Technologies Inc 3D Rage
> LT Pro

BootX uses the MacOS PCI mappings which are bogus for the Rage LT Pro.
Though I'm certain Geert's old PCI resource allocation patch worked fine
in spite of this. There was some message about resource conflict but that
was fixed by the kernel.

What's the PCI resourced for the card after the kernel has finished
booting?

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: bk 2.4.1pre2 Lombard PCI allocation fails.

[Geert Uytterhoeven]

On Mon, 15 Jan 2001, Michael Schmitz wrote:
> > as the title says...
> > The machine boots and (seems) OK.
> >
> > FWIW: I boot this machine with BootX [1.2.2] (and always have, without
> > problem, until this time).
> > PCI: Cannot allocate resource region 2 of device 00:11.0
> > PCI: Resource 80880000-80880fff (f=200, d=0, p=0)
> > PCI: Resource 00000c00-00000cff (f=101, d=1, p=1)
> > PCI: Cannot allocate resource region 1 of device 00:11.0
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The conflict for the overlapping MMIO region.

> >   got res[10000000:10000fff] for resource 2 of ATI Technologies Inc 3D Rage
> > LT Pro

Fixed by the kernel, and reassigned to 0x10000000.

> BootX uses the MacOS PCI mappings which are bogus for the Rage LT Pro.
> Though I'm certain Geert's old PCI resource allocation patch worked fine
> in spite of this. There was some message about resource conflict but that
> was fixed by the kernel.
>
> What's the PCI resourced for the card after the kernel has finished
> booting?

I expect it to be 0x10000000.

BTW, this also means we can start using the secondary aperture as well in
2.4.0. Gives us an additional 4 kB of frame buffer on little-endian boxes.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: bk 2.4.1pre2 Lombard PCI allocation fails.

[Benjamin Herrenschmidt]

>Fixed by the kernel, and reassigned to 0x10000000.
>
>> BootX uses the MacOS PCI mappings which are bogus for the Rage LT Pro.
>> Though I'm certain Geert's old PCI resource allocation patch worked fine
>> in spite of this. There was some message about resource conflict but that
>> was fixed by the kernel.
>>
>> What's the PCI resourced for the card after the kernel has finished
>> booting?
>
>I expect it to be 0x10000000.
>
>BTW, this also means we can start using the secondary aperture as well in
>2.4.0. Gives us an additional 4 kB of frame buffer on little-endian boxes.

Well, unfortunately, 0x10000000 is bogus on most cases. (I didn't check
with Grackle, but for example on UniNorth based machines, this address is
not routed to PCI).

Our PCI code still have no knowledge of which physical ranges can
actually be allocated for each bus. That should be implemented via proper
root bus resources, but I've not yet been able to find a good solution
for that (mostly because we would need more resources than the current
pci_bus structure provides in some cases where the bridge can decode
several discontiguous regions). Maybe We could fake this, my knowledge of
the linux resource mecanism is not perfect.

Matt Porter is coming with a better solution based on some platform
callbacks that would take care of such things are re-assigning a given
device. Those callbacks could then take care of doing proper allocation
depending on the host bridge setup. (See our discussion about the enable
device hook)

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: bk 2.4.1pre2 Lombard PCI allocation fails.

[Iain Sandoe]

>>Fixed by the kernel, and reassigned to 0x10000000.
>>
>>> BootX uses the MacOS PCI mappings which are bogus for the Rage LT Pro.
>>> Though I'm certain Geert's old PCI resource allocation patch worked fine
>>> in spite of this. There was some message about resource conflict but that
>>> was fixed by the kernel.
>>>
>>> What's the PCI resourced for the card after the kernel has finished
>>> booting?
>>
>>I expect it to be 0x10000000.
>>
>>BTW, this also means we can start using the secondary aperture as well in
>>2.4.0. Gives us an additional 4 kB of frame buffer on little-endian boxes.

indeed:

00:11.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4c49
(rev dc)
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
 Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
 Latency: 8 min, 32 set, cache line size 08
 Interrupt: pin A routed to IRQ 24
 Region 0: Memory at 81000000 (32-bit, non-prefetchable)
 Region 1: I/O ports at <ignored> [disabled]
 Region 2: Memory at 10000000 (32-bit, non-prefetchable)
 Capabilities: [5c] Power Management version 1
  Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

> Well, unfortunately, 0x10000000 is bogus on most cases. (I didn't check
> with Grackle, but for example on UniNorth based machines, this address is
> not routed to PCI).

How can I find out whether the area is bogus?

> Our PCI code still have no knowledge of which physical ranges can
> actually be allocated for each bus. That should be implemented via proper
> root bus resources, but I've not yet been able to find a good solution
> for that (mostly because we would need more resources than the current
> pci_bus structure provides in some cases where the bridge can decode
> several discontiguous regions). Maybe We could fake this, my knowledge of
> the linux resource mecanism is not perfect.

If I yaboot it will the problem go away?
(hadn't worried yet - this is the first prob. I've had with it)

and this machine seems to be in a grey-area where either method will work...

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: bk 2.4.1pre2 Lombard PCI allocation fails.

[Michael Schmitz]

> > > PCI: Cannot allocate resource region 1 of device 00:11.0
>          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> The conflict for the overlapping MMIO region.
>
> > >   got res[10000000:10000fff] for resource 2 of ATI Technologies Inc 3D Rage
> > > LT Pro
>
> Fixed by the kernel, and reassigned to 0x10000000.

OK, I misread that error message. Now you just need to supply a valid new
region :-) (How did the 2.3.99 code differ in that respect?)

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/