> >> radeonfb: EDID probed
> >> Parsing EDID data for panel info
> >> Setting up default mode based on panel info
> >> radeonfb (:00:0a.0): ATI Radeon Y`
> >
> >Hm, what's that Y`?
>
> Thats the final message in the radeonfb driver ater initializing everything.
>printk ("radeonfb (%s
On Tue, 2008-04-22 at 16:21 +0200, Christian Ehrhardt wrote:
>
> >> radeonfb: EDID probed
> >> Parsing EDID data for panel info
> >> Setting up default mode based on panel info
> >> radeonfb (:00:0a.0): ATI Radeon Y`
> >
> >Hm, what's that Y`?
>
> Thats the final message in the radeonfb
n issue where my graphic card could not initialize because the pci
resource space was not big enough.
The related mail thread about the backgrounds of this has the subject "pci
issue - wrong detection of pci ressources"
Signed-off-by: Christian Ehrhardt <[EMAIL PROTECTED]>
---
[diffstat]
ssue where my graphic card could not initialize because the pci
resource space was not big enough.
The related mail thread about the backgrounds of this has the subject "pci
issue - wrong detection of pci ressources"
After these values were fixed another modification that came up in the
where my graphic card could not initialize because the pci
resource space was not big enough.
The related mail thread about the backgrounds of this has the subject "pci
issue - wrong detection of pci ressources"
After these values were fixed another modification that came up in the mail
On Mon, 2008-04-21 at 13:55 +0200, Christian Ehrhardt wrote:
> Benjamin Herrenschmidt wrote:
> >> Yes you're right. Early at the pci initialization are errors of the
> >> allocation for pi ressources.
> >> And that are exactly the ressources failing later, so that pci
> >> initialization seem to
Hello, I wrote:
Ah, that's what happens -- BAR0 in functions 0/1 takes up the whole
265 MiB of the PCI memory space (128+128), so no place is left for other
memory BARs.
What's interesting, the Sequoia/Rainier board user manual says that PCI
memory is 0x8000 thru 0xbfff (i.e. 1
Christian Ehrhardt wrote:
+else {
+printk(KERN_ERR"%s - continue with start 0x%0lx on %p\n", __func__,
(this->end + 1), this->sibling);
+}
new->start = this->end + 1;
this = this->sibling;
And here. Yet it's not clear why you call resource's 'end' 'start'.
Sergei Shtylyov wrote:
Hello.
Christian Ehrhardt wrote:
Cheers,
Ben.
For comparison I defined DEBUG in the good kernel (arch=ppc) and that
is what the initialization prints (pci ...:0a:1 is the secondary head
of the same graphic card an it's not an issue if thats not allocated):
[...]
Hello.
Christian Ehrhardt wrote:
Cheers,
Ben.
For comparison I defined DEBUG in the good kernel (arch=ppc) and that is
what the initialization prints (pci ...:0a:1 is the secondary head of
the same graphic card an it's not an issue if thats not allocated):
good case:
PCI: Probing PCI hardw
Benjamin Herrenschmidt wrote:
Yes you're right. Early at the pci initialization are errors of the allocation
for pi ressources.
And that are exactly the ressources failing later, so that pci initialization
seem to be the reason for my problem.
Was there any simple solution (e.g. just somehow in
> Yes you're right. Early at the pci initialization are errors of the
> allocation for pi ressources.
> And that are exactly the ressources failing later, so that pci initialization
> seem to be the reason for my problem.
> Was there any simple solution (e.g. just somehow increase memory reserve
Johan Borkhuis wrote:
Hello Christian,
Christian Ehrhardt wrote:
Hi,
I tried to use a radeon r200 based graphic card on a sequoia ppc
(440epx) board. I wondered about the initialization of radeonfb that
failed with
__ioremap(): phys addr 0x0 is RAM lr c029cf80
radeonfb (:00:0a.0)
On Sat, 2008-04-19 at 10:48 +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2008-04-18 at 14:07 +0200, Christian Ehrhardt wrote:
> > => Region 2 is not detected with our kernel, this later break things
> > like radeonfb initialization.
>
> I'll need some information here:
>
> - Your device-tree (
On Fri, 2008-04-18 at 14:07 +0200, Christian Ehrhardt wrote:
> => Region 2 is not detected with our kernel, this later break things
> like radeonfb initialization.
I'll need some information here:
- Your device-tree (is that the base sequoia one ?)
- Enable DEBUG in arch/powerpc/kernel/pci-commo
Christian Ehrhardt wrote:
I tried to use a radeon r200 based graphic card on a sequoia ppc
(440epx) board. I wondered about the initialization of radeonfb that
failed with
__ioremap(): phys addr 0x0 is RAM lr c029cf80
radeonfb (:00:0a.0): cannot map MMIO
radeonfb: probe of
Hello Christian,
Christian Ehrhardt wrote:
Hi,
I tried to use a radeon r200 based graphic card on a sequoia ppc
(440epx) board. I wondered about the initialization of radeonfb that
failed with
__ioremap(): phys addr 0x0 is RAM lr c029cf80
radeonfb (:00:0a.0): cannot map MMIO
r
Hi,
I tried to use a radeon r200 based graphic card on a sequoia ppc (440epx)
board. I wondered about the initialization of radeonfb that failed with
__ioremap(): phys addr 0x0 is RAM lr c029cf80
radeonfb (:00:0a.0): cannot map MMIO
radeonfb: probe of :00:0a.0 fail
18 matches
Mail list logo
