From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: App database, libsynth Date: Thu, 17 Jul 2003 20:07:25 +0400 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <3F16C9BD.2090301@aknet.ru> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org Hello. Ryan Underwood wrote: > The design is simple to me. The programmer of the > application need do nothing but SynthOpen the correct > devices, and then SynthWrite the data to them. Sounds good. It would probably be a good idea to provide an optional way to query user's time and request the timer events from user. It may be that the user's time is different than the real time. dosemu uses the real time, but AFAIK dosbox uses the emulated time (CPU-emu relative). It may also be possible that the real card's sampling rate is not very precise (the pcsp driver rounds the sampling rate rather cruely), in which case you'll have one more timing source with which you also have to keep in sync. Last time I dealt with all that mess, it wasn't very simple (see linux_sound.c :) > Plan to support the following synths in the library, all > can be either hardware or emulated: How are you accessing the hardware btw? ioperm() ? > or DMA and such are not candidates. Yes, DMA is out of question, that's for sure. > The OPL-chip has an internal IRQ but it can be triggered > or cleared by simply writing to the OPL's port. AFAIK it is not even connected to any of the PIC wires, but why can't you provide an optional way to notify the user about an IRQ? Simply calling the user's registered call-back function might just do the trick, so why not?