In message <[EMAIL PROTECTED]> Mike Smith writes:
: > However, I think the point is moot because in current I've fixed it to
: > clip the ranges properly.
:
: That's definitely what I intended. I guess I should fix the typos in
: that file too, eh?
Yes. Were they mine or yours :-)
Warner
To
> : > : requests for the register window to be based at 0xf400.
> : >
> : > Actually, for most people, just ignoring the error is enough to make
> : > it work.
> :
> : This bothers me. Are bridges ignoring their mapping registers?
>
> It would appaer that they are. It hurts my brain that
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > : As a workaround for you, though, try adjusting the memory that the driver
: > : requests for the register window to be based at 0xf400.
: >
: > Actually, for most people, just ignoring the error is enough to make
: > it work.
:
: This
> : As a workaround for you, though, try adjusting the memory that the driver
> : requests for the register window to be based at 0xf400.
>
> Actually, for most people, just ignoring the error is enough to make
> it work.
This bothers me. Are bridges ignoring their mapping registers?
--
In message <[EMAIL PROTECTED]> John McCullough writes:
: As I'm still learning, I hope my questions aren't too annoying,
:
: to do this would I have the kernel route to a different IRQ (say 10)
: instead of 255 by default?
You can't :-(. That's a bug in the code.
The questions aren't stupid.
Warner Losh wrote:
>In message <[EMAIL PROTECTED]> John McCullough writes:
>: pcib2: routed slot 15 INTA to irq 255
>: pccbb: Unable to map IRQ...
>: panic: resouce_list_release:can't find resource
>: Debugger("panic")
>
>This is a bug in pcibus issue. IRQ 255 should be treated as
>unallocated,
In message <[EMAIL PROTECTED]> John McCullough writes:
: pcib2: routed slot 15 INTA to irq 255
: pccbb: Unable to map IRQ...
: panic: resouce_list_release:can't find resource
: Debugger("panic")
This is a bug in pcibus issue. IRQ 255 should be treated as
unallocated, so please route.
: Is this
Warner Losh wrote:
>In message <[EMAIL PROTECTED]> John McCullough writes:
>: I'd like to get card bus working, however under 5.0-current my pcmcia
>: controller is failing to load with the message:
>:
>: pccbb0: at device 15.0 on pci2
>: pcib2: device pccbb0 requested unsupported memory randg
In message <[EMAIL PROTECTED]> Mike Smith writes:
: This is a bug in the way that the pccbb code allocates the register
: window when it hasn't been set up. The "real" fix actually requires the
: PCI code to configure the cardbus controller, but we don't do that yet
: (we desperately need to,
In message <[EMAIL PROTECTED]> John McCullough writes:
: I'd like to get card bus working, however under 5.0-current my pcmcia
: controller is failing to load with the message:
:
: pccbb0: at device 15.0 on pci2
: pcib2: device pccbb0 requested unsupported memory randge
: 0x1000-0x
> I'd like to get card bus working, however under 5.0-current my pcmcia
> controller is failing to load with the message:
>
> pccbb0: at device 15.0 on pci2
> pcib2: device pccbb0 requested unsupported memory randge
> 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf)
>
I'd like to get card bus working, however under 5.0-current my pcmcia
controller is failing to load with the message:
pccbb0: at device 15.0 on pci2
pcib2: device pccbb0 requested unsupported memory randge
0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf)
pccbb0: Could
12 matches
Mail list logo
