Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Alex deVries <adevries@linuxcare.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] SuckyIO support
Date: Tue, 19 Dec 2000 18:56:32 -0800	[thread overview]
Message-ID: <200012200256.SAA16519@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Tue, 19 Dec 2000 10:46:40 PST." <3A3F82E0.C0FB63D6@linuxcare.com>

Alex deVries wrote:
...
> I've taken mkp's initial work on superio.c and added some stuff, but in
> the end am confused by where we actually get the interrupt number from
> the card.  There's no such register in function 1 (where the interrupts
> ultimately end up) and both registers on function 0 and 2 return 0,
> which I don't think is right.

Why are you reading this out of a register? Which register?

IIRC, function 0 and 2 *should* return 0 in INTERRUPT_PIN configuration
register and thus the INTERRUPT_LINE configuration as well.
But since IOSAPIC driver (when invoked by LBA PCI code) munges the
INTERRUPT_LINE contents and puts the virtualized IRQ number in 
dev->irq for the drivers consumption, superio driver should
not be reading these configuration registers.

> I'd thought that PDC would have set this up.

PDC should only sets up the PCI INTERRUPT_LINE config register values
to indicate which IOSAPIC input *line* they are using. parisc-linux has
to map this value to an IRQ region and virtualize the dev->irq value.

> There's not much I can do at this point until we can have some of
> Grant's attention.

If what I wrote above doesn't make any sense, tell me where to
to find the code you are talking about and I can look at it.

grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

  reply	other threads:[~2000-12-20  2:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-19  9:42 [parisc-linux] SuckyIO support Matthew Wilcox
2000-12-19 15:46 ` Alex deVries
2000-12-20  2:56   ` Grant Grundler [this message]
2000-12-20  6:37     ` Alex deVries
2000-12-20 13:05       ` Alan Cox
2000-12-20 17:30         ` Grant Grundler
2000-12-20 20:47           ` Alan Cox
2000-12-20 21:12             ` Grant Grundler
2000-12-20 15:50     ` Matthew Wilcox
2000-12-20 16:54       ` Alex deVries
2000-12-20 18:24       ` Grant Grundler
2000-12-24  9:05         ` Matthew Wilcox
2000-12-26  7:16           ` Grant Grundler
2000-12-26 10:53             ` Matthew Wilcox
2000-12-26 20:18               ` Grant Grundler
2000-12-23  9:15 ` Matthew Wilcox
2000-12-27 20:27   ` Alex deVries

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=200012200256.SAA16519@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=adevries@linuxcare.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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