What is the plan for combining these audio drivers? One thing that is common to each driver are the functions that handle the wave headers, adding, removing etc.
I'm also weary of any kind of combination that includes OSS as OSS is depreciated and has been replaced by Alsa.
I'm also concerned with the arts, jack and nas drivers being left out of this merge. While many of the audio drivers have a lot in common there are a LOT of subtle differences that are necessary for things to work correctly. Maybe Eric and others could comment on what they see as being able to be combined, although I've worked a bit on audio drivers I'm drawing mostly a blank.
Thanks, Chris
From: Yorick Hardy yha@na.rau.ac.za Date: 2004/03/02 Tue AM 04:38:41 EST To: wine-devel@winehq.org CC: yha@na.rau.ac.za Subject: Re: Native NetBSD audio driver
I started now with the integration of the OSS and NetBSD audio drivers. Before I get too far, I would like to hear suggestions/criticisms.
- I created the directory dlls/winmm/drvcommon (perhaps there is a better name ?)
- moved dlls/winmm/wineoss/oss.c and dlls/winmm/winenbsd/nbsd.c to the single integrated file dlls/winmm/drvcommon/drv.c.
- renamed the files dlls/winmm/wineoss/oss.h and dlls/winmm/winenbsd/nbsd.h to dlls/winmm/wineoss/drv.h and dlls/winmm/winenbsd/drv.h respectively.
- Update the respective Makefile.in to use the integrated dlls/winmm/drvcommon/drv.c
The idea is that eventually winenbsd and wineoss only have the drv.h and the spec file. drv.h will define all driver specific names/functions. I must stress that I am only concerned with the OSS and NetBSD drivers at the moment.
Is this too much? Or can someone suggest a better solution?
Kind regards,
-- Yorick Hardy Tel: +2711 489 3640 | Fax: +2711 489 2067 | Office: C-Ring 517 Auckland Park Campus | Rand Afrikaans University | South Africa Department of Applied Mathematics : http://general.rau.ac.za/apm Standard Bank Academy for Information Technology : http://csweb.rau.ac.za