* [parisc-linux] Dino and Lasi
@ 1999-06-28 5:26 Alex deVries
1999-06-28 17:03 ` Grant Grundler
0 siblings, 1 reply; 3+ messages in thread
From: Alex deVries @ 1999-06-28 5:26 UTC (permalink / raw)
To: parisc-linux
Okay, I've committed some small changes to dino and lasi that can easily
be backed out.
some questions:
- what IRQ are we going to run LASI on? Is that something we just pick
and hard code?
- I changed lasi.c and dino.c to only use readl() and writel(), and not
readb and writew, etc. Was this a mistake?
- We really really need the IRQ bottom halfs setup. Any takers?
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [parisc-linux] Dino and Lasi
1999-06-28 5:26 [parisc-linux] Dino and Lasi Alex deVries
@ 1999-06-28 17:03 ` Grant Grundler
1999-06-28 17:56 ` Alan Cox
0 siblings, 1 reply; 3+ messages in thread
From: Grant Grundler @ 1999-06-28 17:03 UTC (permalink / raw)
To: Alex deVries; +Cc: parisc-linux
Alex deVries wrote:
>
>
> Okay, I've committed some small changes to dino and lasi that can easily
> be backed out.
>
> some questions:
>
> - what IRQ are we going to run LASI on? Is that something we just pick
> and hard code?
Isn't LASI a PA (ie GSC bus) device?
If so, it can use any EIRR bit/HPA pair supported by the PA processor code.
It needs to register an ISR with PA interrupt code and get the EIRR/HPA
pair (commonly called EIM value).
Same is true for Dino.
> - I changed lasi.c and dino.c to only use readl() and writel(), and not
> readb and writew, etc. Was this a mistake?
For Dino, I think so. On a reads, it shouldn't matter unless the
reads have side effects (eg. clears the byte register). On writes
too many byte enables will be set.
BTW, I assume you are talking about PCI MMIO/Port/Cfg space accessor
functions.
> - We really really need the IRQ bottom halfs setup. Any takers?
What do you mean "bottom half"?
dino_isr() to map DINO EIM registers to PCI IRQ lines (and thus
PCI device ISRs)?
grant
Grant Grundler
+1.408.447.7253
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [parisc-linux] Dino and Lasi
1999-06-28 17:03 ` Grant Grundler
@ 1999-06-28 17:56 ` Alan Cox
0 siblings, 0 replies; 3+ messages in thread
From: Alan Cox @ 1999-06-28 17:56 UTC (permalink / raw)
To: Grant Grundler; +Cc: adevries, parisc-linux
> What do you mean "bottom half"?
> dino_isr() to map DINO EIM registers to PCI IRQ lines (and thus
> PCI device ISRs)?
The Linux bottom halves are closest in 'other unixen' to the software interrupt
code run after the IRQ return.
Linux services any pending bottom halves after the irq completes but before
returning to the scheduled task/scheduler. Its used for deferring processing
from interrupt paths
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1999-06-28 18:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-06-28 5:26 [parisc-linux] Dino and Lasi Alex deVries
1999-06-28 17:03 ` Grant Grundler
1999-06-28 17:56 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox