linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Jeglinski <jeglin@4pi.com>
To: LinuxPPC-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: usb wheel mouse, XF4.0
Date: Wed, 29 Nov 2000 09:07:55 -0500	[thread overview]
Message-ID: <p04330100b64abb5a279d@[192.168.0.1]> (raw)
In-Reply-To: <3A24C62F.D69C7558@pop.agri.ch>


Well, then is there any way for any user to control how the
interrupts are dished out (assigned), say for example by moving cards
around in the slots? Can the kernel be patched to "hardwire" the
assignment of interrupts? (I'm talking a customs patch that only I
apply, not a general patch for everyone).

Or is this entirely an initialization problem deep in the kernel
code? Is there any timeline for fixing it or is it a part of the
longer-term PCI cleanup I've read about?

I am relatively limited in how I can move cards around as my earlier
post reporting my slot summary will attest to,

<http://lists.linuxppc.org/listarcs/linuxppc-dev/200011/msg00187.html>,


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.


Stefan Jeglinski

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

  reply	other threads:[~2000-11-29 14:07 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 [this message]
2000-11-29 17:08         ` Benjamin Herrenschmidt
2000-11-29 17:14         ` Benjamin Herrenschmidt
2000-12-01  7:09           ` Michel Lanners
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='p04330100b64abb5a279d@[192.168.0.1]' \
    --to=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).