RE: IRQ sharing with newbus

1999-06-04 Thread Ladavac Marino
> -Original Message- > From: Garrett Wollman [SMTP:woll...@khavrinen.lcs.mit.edu] > Sent: Wednesday, June 02, 1999 9:13 PM > To: Bruce Evans > Cc: d...@nlsystems.com; woll...@khavrinen.lcs.mit.edu; > curr...@freebsd.org; new...@atdot.dotat.org > Subject:

Re: IRQ sharing with newbus

1999-06-02 Thread Garrett Wollman
< said: >> But the sio non-multiport stuff should be able to use RF_TIMESHARE. -- >> If I'm not using my serial port, I should be able to use my >> infrared > Preemptive timesharing would be hard to implement reasonably for irqs. > A uniform timeslice would have to be 86 usec to work properly

Re: IRQ sharing with newbus

1999-06-02 Thread Matthew N. Dodd
On Wed, 2 Jun 1999, Wilko Bulte wrote: > > For EISA, it should be possible to add RF_SHAREABLE to the > > bus_alloc_resource call (assuming that EISA interrupts are shareable like > > pci interrupts). > > IRRC (it's been years) EISA cards can, but don't have to, support shared > interrupts. I thin

Re: IRQ sharing with newbus

1999-06-02 Thread Wilko Bulte
As Doug Rabson wrote ... > On Tue, 1 Jun 1999, Matthew N. Dodd wrote: > > > On Tue, 1 Jun 1999, Mark Newton wrote: > > > So, guys -- What is the officially blessed way of sharing IRQs under > > > newbus? > > > > If you find out, let me know since the EISA code suffers the same problem > > (though

Re: IRQ sharing with newbus

1999-06-02 Thread Matthew N. Dodd
On Wed, 2 Jun 1999, Doug Rabson wrote: > The EISA bus code needs a new maintainer (who could put back such > things as resource reporting). Are you interested? You seem to be one > of the few people who actively uses this bus. I'm still fairly far behind on the learning curve with respect to the n

Re: IRQ sharing with newbus

1999-06-02 Thread Doug Rabson
On Tue, 1 Jun 1999, Matthew N. Dodd wrote: > On Tue, 1 Jun 1999, Doug Rabson wrote: > > For EISA, it should be possible to add RF_SHAREABLE to the > > bus_alloc_resource call (assuming that EISA interrupts are shareable > > like pci interrupts). > > The observed behavior suggests that RF_SHAREABL

Re: IRQ sharing with newbus

1999-06-01 Thread Bruce Evans
>> I don't think the sio multiport stuff needs to use RF_SHAREABLE - the >> master device knows how to field interrupts for the slaves (at least thats >> how I understood it). > >But the sio non-multiport stuff should be able to use RF_TIMESHARE. -- >If I'm not using my serial port, I should be abl

Re: IRQ sharing with newbus

1999-06-01 Thread Garrett Wollman
< said: > I don't think the sio multiport stuff needs to use RF_SHAREABLE - the > master device knows how to field interrupts for the slaves (at least thats > how I understood it). But the sio non-multiport stuff should be able to use RF_TIMESHARE. -- If I'm not using my serial port, I should be

Re: IRQ sharing with newbus

1999-06-01 Thread Matthew N. Dodd
On Tue, 1 Jun 1999, Doug Rabson wrote: > For EISA, it should be possible to add RF_SHAREABLE to the > bus_alloc_resource call (assuming that EISA interrupts are shareable > like pci interrupts). The observed behavior suggests that RF_SHAREABLE is not being honored. dpt99: DPT PM2022A/9X FW Rev. 0

Re: IRQ sharing with newbus

1999-06-01 Thread Doug Rabson
On Tue, 1 Jun 1999, Matthew N. Dodd wrote: > On Tue, 1 Jun 1999, Mark Newton wrote: > > So, guys -- What is the officially blessed way of sharing IRQs under > > newbus? > > If you find out, let me know since the EISA code suffers the same problem > (though the drivers do a bit better job detectin

Re: IRQ sharing with newbus

1999-06-01 Thread Doug Rabson
On Wed, 2 Jun 1999, Bruce Evans wrote: > >Under newbus, of course, things look slightly different, so I tried > >this: > > > >device sio2at isa? port 0x280 flags 0x0201 irq 5 > >device sio3at isa? port 0x288 flags 0x0201 > >device sio4at isa? port 0x290 flags 0x0201 > > [ ... ] >

Re: IRQ sharing with newbus

1999-06-01 Thread Bruce Evans
>Under newbus, of course, things look slightly different, so I tried >this: > >device sio2at isa? port 0x280 flags 0x0201 irq 5 >device sio3at isa? port 0x288 flags 0x0201 >device sio4at isa? port 0x290 flags 0x0201 > [ ... ] >device sio9at isa? port 0x2b8 flags 0x0201 > >Natc

Re: IRQ sharing with newbus

1999-06-01 Thread Matthew N. Dodd
On Tue, 1 Jun 1999, Mark Newton wrote: > So, guys -- What is the officially blessed way of sharing IRQs under > newbus? If you find out, let me know since the EISA code suffers the same problem (though the drivers do a bit better job detecting the condition, and just fail to attach instead of pani

IRQ sharing with newbus

1999-06-01 Thread Mark Newton
I've blown the dust off an old ISA multiport serial card. In the old days, I used to make it work with BSD by including "options COM_MULTIPORT" and using the following config file directives: device sio2at isa? port 0x280 tty flags 0x0201 irq 5 vector siointr device sio3at isa? port 0