linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: bh40@calva.net
Cc: jeglin@4pi.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: usb wheel mouse, XF4.0
Date: Fri, 1 Dec 2000 08:09:21 +0100 (CET)	[thread overview]
Message-ID: <200012010709.IAA00844@piglet.grunz.lu> (raw)
In-Reply-To: <19341024104634.3912@192.168.1.2>


Hi all,

On  29 Nov, this message from Benjamin Herrenschmidt echoed through cyberspace:
>>In addition, yesterday I speculated that the dual IRQ 23 might help
>>explain why I was having 2.2.18preX boot problems with the aic7xxx.
>>This can't really be the case because one of the slot summary tests
>>was to remove the USB card (and all others). There was no difference,
>>so my boot issue remains a separate one with its odd workaround.
>
> Ok, I found the problem, I think, with the interrupt. I'm still
> investigating, but what it looks like is that the OF tree puts the
> AAPL,interrupt property in the pci-bridge node, not in the sub-nodes.

I remember seeing this documented somewhere in the kernel sources, I
think.

Also, another 'shot in the dark': might we have a bug in the PCI-bridge
code, that (erronously) rotates interrupts? On Intel machines, the 4 PCI
interrupt lines are BIOS-wired to some IRQs, and are rotated one
position while passing to the next PCI slot. They are also, IIRC,
rotated by each PCI bridge. This _could_ make the USB card be configured
for the wrong interrupt, maybe the adjacent slot: SCSI controller....

Just a thought...

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "

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

  reply	other threads:[~2000-12-01  7:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseld orf.de>
2000-11-28 19:55 ` usb wheel mouse, XF4.0 Stefan Jeglinski
2000-11-28 20:23   ` Michael Schmitz
2000-11-29  8:33   ` Timothy A. Seufert
2000-11-29  9:02     ` Andreas Tobler
2000-11-29 14:07       ` Stefan Jeglinski
2000-11-29 17:08         ` Benjamin Herrenschmidt
2000-11-29 17:14         ` Benjamin Herrenschmidt
2000-12-01  7:09           ` Michel Lanners [this message]
2000-11-29 13:45     ` christopher.murtagh
     [not found] <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseldorf.de >
2000-11-29  8:15 ` Timothy A. Seufert
2000-11-29  9:30   ` Michael Schmitz
2000-11-29 13:10   ` Benjamin Herrenschmidt
     [not found] <Pine.LNX.4.10.10011282109440.2086-100000@zirkon.biophys.uni-duessel dorf.de>
2000-11-28 22:32 ` Stefan Jeglinski
2000-11-28 23:15   ` Michael Schmitz
     [not found] <F269nW0kKIBXEHt3V5g00007774@hotmail.com>
2000-11-28 19:31 ` Stefan Jeglinski
2000-11-28 19:39   ` Michael Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200012010709.IAA00844@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=bh40@calva.net \
    --cc=jeglin@4pi.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).