Re: pcic setup / wi0 timeout

From: M. Warner Losh (imp_at_bsdimp.com)
Date: 05/29/03

  • Next message: Dirk-Willem van Gulik: "Re: pcic setup / wi0 timeout" 
    Date: Wed, 28 May 2003 18:36:03 -0600 (MDT)
To: dirkx@webweaving.org

    In message: <20030529022852.V22309-100000@foem>
                Dirk-Willem van Gulik <dirkx@webweaving.org> writes:
    : > In message: <20030528235747.W22309-100000@foem>
    : > Dirk-Willem van Gulik <dirkx@webweaving.org> writes:
    : > : pcic0: <Ricoh RL5C475 PCI-CardBus Bridge> at device 18.0 on pci0
    : > : pcic0: PCI Memory allocated: 0x88000000
    : > : pcic0: No PCI interrupt routed, trying ISA.
    : >
    : > You lose. W/o a pci interrupt router, you can't use the cardbus
    : > bridge.
    :
    : Good - so who/what should set up a PCI router ? the Bios ?

    It depends. Really old machines routed interrupts to all PCI slots
    and assigned devices found there an interrupt. Newer old machines
    expect the PCI bridge driver of the OS to cope. Newer old machines
    provide a BIOS interface to route them (which we can use). Newer
    machines with ACPI have ACPI to do the routing. You might want to do
    a boot verbose, but I'm not sure how much that would help. PCIBIOS
    should have something like:

    bios32: Found BIOS32 Service Directory header at 0xc00f8270
    bios32: Entry = 0xfd770 (c00fd770) Rev = 0 Len = 1
    pcibios: PCI BIOS entry at 0xfd770+0x11e
    pnpbios: Found PnP BIOS data at 0xc00f82c0
    pnpbios: Entry = f0000:a95c Rev = 1.0

    etc

    Warner
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

  • Next message: Dirk-Willem van Gulik: "Re: pcic setup / wi0 timeout"

    Relevant Pages

    • Re: IRQ assignment in Windows 2K/XP/2003...
      ... board) are required to use the same PCI slot interrupt line ... PCI configuration header has to be different (they both don't request ... So, no driver, Windows PnP manager, or BIOS problems were the ... the bridge wasn't "directly" involved with the routing of the ...
      (microsoft.public.development.device.drivers)
    • Re: A question about hot-pluggable PCI.
      ... I program a hard-coded window into the PCI bridge behind CardBus. ... It turns out interrupt routing is the problem. ... When I added the following, I found drivers attaching to devices inside the ...
      (freebsd-hackers)
    • Re: A question about hot-pluggable PCI.
      ... I program a hard-coded window into the PCI bridge behind CardBus. ... It turns out interrupt routing is the problem. ... ...whereas normally the code was 'routing' IRQ 6 to INTA on the bridge. ...
      (freebsd-hackers)
    • Re: IRQ assignment in Windows 2K/XP/2003...
      ... I discovered in the PCI bridge spec ... board) are required to use the same PCI slot interrupt line ... So, no driver, Windows PnP manager, or BIOS problems were the ...
      (microsoft.public.development.device.drivers)
    • Re: can someone explain...[ PCI interrupts]
      ... interrupts for PCI devices are roughly split up into two categories: INTx interrupt lines and MSI interrupts. ... Each processor contains a local APIC that can receive messages from other APICs and send messages to other local APICs. ... Basically, an IRQ value is a cookie useful for binding a device interrupt tuple or an ISA IRQ) to a x86 interrupt tuple. ...
      (freebsd-current)