17 Feb, 2007

1 commit

  • I'm currently working on a port to a CPCI board with a MPC5200. When
    testing the PCI interrupt routing, I discovered the following: Even devices
    which don't use interrupts (-> PCI Spec.: Interrupt Pin Register is zero),
    get an interrupt assigned (this is at least true for most of the
    PPC-targets I looked at).

    The cause is pretty obvious in drivers/pci/setup-irq.c. I guess at least
    in an ideal world with correctly designed hardware, the code should rather
    look as in the patch below.

    Of course it doesn't hurt anybody to have an unuseable IRQ assigned to a
    PCI-to-PCI-bridge (or something alike), but to me it seems a bit strange.
    Please correct me, if I'm mislead.

    The patch below is tested on the above mentioned CPCI-MPC5200 board and is
    compiler tested with the latest git-repository kernel on x86.

    Cc: "Eric W. Biederman"
    Cc: Thomas Gleixner
    Cc: Ingo Molnar
    Cc: Linus Torvalds
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Andreas Block
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds