Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Philipp Rumpf <prumpf@suse.de>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Thoughts on arch/parisc/irq.c
Date: Thu, 26 Aug 1999 10:13:14 -0700	[thread overview]
Message-ID: <199908261713.KAA12239@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Thu, 26 Aug 1999 17:26:26 PDT." <19990826172626.K19314@suse.de>

Philipp Rumpf:
> the Dino documentations says bits 5-31 are HPA but as long as 5-10 are 0 we
> don't have to care.

FYI - All PA device addresses are 4k page aligned.
I've seen devices alias within a page but the IODC can only
report the number of 4k pages a devices uses - ergo 4K aligned.

> 
> > ie a value 0-31). The location of this register is NOT
> > defined by PA I/O architecture - or at least not well defined.
> > Is this a real problem or not?
> 
> No.  You just do
> gsc_writel(0xfffe0000 + dev->irq, dev->hpa + DEVICE_SPECIFIC_OFFSET);
> right after request_irq(dev->irq, ...);

Ok - this is another SMP issue...I'll hardcode 0xfffe0000 for now. 

Platform	Processor HPA
--------	-------------
712/80		0xfffbe000
715/100		0xfffbe000
B132L		0xfffbe000
B180L		0xfffbe000
C200+		0xfffa0000

> > Another tidbit: I know of only one device which can use "6-bit"
> > (0-63) EIRR vectors. GSC and PCI devices which are capable of mastering
> > their own interrupt transactions can also use 6-bits. 6-bits is
> > obviously only supportable running a 64-bit kernel binary.
> 
> Is it ok with you if we worry about SMP and PA2.0 boxes later ?

Absolutely. I brought this up so it doesn't have to get redesigned
by whoever feels like tackling those issues.  Note the subject line.
I'm just not into doing thing two or three times in a row.

grant

> 
> 	Philipp Rumpf

Grant Grundler
Communications Infrastructure Computer Operations
+1.408.447.7253

  parent reply	other threads:[~1999-08-26 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37C432D3.C9BC0D7F@thepuffingroup.com>
1999-08-26  0:49 ` [parisc-linux] Thoughts on arch/parisc/irq.c Grant Grundler
1999-08-26  1:16   ` Alan Cox
1999-08-26  2:13     ` Grant Grundler
1999-08-26 12:06       ` Alan Cox
1999-08-26 15:26       ` Philipp Rumpf
1999-08-26 16:43         ` LaMont Jones
1999-08-26 17:13         ` Grant Grundler [this message]
1999-08-26 17:48           ` Alex deVries
1999-08-26 18:12           ` Philipp Rumpf
1999-08-26 15:16   ` Philipp Rumpf
     [not found] <199908261629.JAA12121@milano.cup.hp.com>
1999-08-26 16:38 ` Alan Cox

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=199908261713.KAA12239@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=prumpf@suse.de \
    /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