Re: Re-install Warp 4.52



On Tue, 6 Dec 2005 17:18:26 UTC, Daniela Engert <dani%ngrt.de@xxxxxxxxx>
wrote:

> There's no need at all for a software mapping from MSI messages to IRQs.
> This is done by the LAPIC (built into every CPU) and assorted,
> platform specific hardware.

Even better ! I did not know about the LAPIC stuff, so thanks
for the pointer.

So currently I only see two problems: It appears to me that
the PSD_IRQ_xxx functions would only allow up to 32 interrupts
(bit masks in ULONGs). O.K., it's more than we have now, but
256 would be better ;-).
The other are these $%&(/@ drivers, that don't like high
interrupt numbers. I'm realy wondering, how many these are.
We currently know the following for sure:

COM.SYS
SBLIVExx.SYS
CMEDIAxx.SYS
UNIAUD32.SYS

I suspect some more audio drivers, (i.e. all that used the
Tropez or PciAudio source code from the DDK as template).

I will fix SBLIVE and CMEDIA and maybe UNIAUD (If someone
manages to upload compileable source code to the Netlabs
repository).


--
Ruediger "Rudi" Ihle [S&T Systemtechnik GmbH, Germany]
http://www.s-t.de
Please remove all characters left of the "R" in my email address

.



Relevant Pages

  • Re: Run-time error 453
    ... The source code is machine code. ... Nobody ever talks about using DOS Interrupts ... Everyone talks about API. ...
    (microsoft.public.vb.general.discussion)
  • Re: Dahm Locks
    ... certain the ALLOW and DISALLOW were in the original code, ... interrupts had less to do with I/O interrupts than with disabling ... The DISALLOW is to (from the source code comment): ... ensure that locking TTL and identifying the owner of TTL is an atomic ...
    (comp.sys.unisys)
  • Re: Question on interrupt stats and probe
    ... I am very to new to kernel dev, have a question on collecting data on ... If I were to dump a list of all interrupts that get ... the point in the kernel source, where I can see all the interrutps) ... If you want to know how it's done, I would track down the source code ...
    (comp.os.linux.development.system)
  • Re: Atmel AVR, too slow encoder tics counting
    ... > You may want to check your LCD output routines. ... I didn`t disable interrupts myself in any code. ... there were no "cli" instructions in source code. ...
    (comp.arch.embedded)