Re: Re: Native NetBSD audio driver

2004-03-03 Thread wine
> 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 understand the desire to extract common code from drivers that have largely been cut and paste from the OSS driver's boilerpl

Re: Native NetBSD audio driver

2004-03-03 Thread Yorick Hardy
I thought to begin with the OSS and NetBSD drivers since I am most familiar with these. The intention was to integrate these drivers in such a way that it will be easier (although probably not trivial) to then bring the other drivers in. Although short sighted, I intended to first consider the dif

Re: Re: Native NetBSD audio driver

2004-03-02 Thread chmorgan
e combined, although I've worked a bit on audio drivers I'm drawing mostly a blank. Thanks, Chris > > From: Yorick Hardy <[EMAIL PROTECTED]> > Date: 2004/03/02 Tue AM 04:38:41 EST > To: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED] > Subject: Re: Native NetBSD audio drive

Re: Native NetBSD audio driver

2004-03-02 Thread Eric Pouech
James Gregory a écrit : On Thu, 2004-02-26 at 08:59, Alexandre Julliard wrote: Robert Reif <[EMAIL PROTECTED]> writes: I think it might be worthwhile considering restructuring the audio drivers into hardware independent wave, direct sound, midi and mixer sections and a hardware dependent low

Re: Native NetBSD audio driver

2004-03-02 Thread Eric Pouech
Alexandre Julliard a écrit : Yorick Hardy <[EMAIL PROTECTED]> writes: 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

Re: Native NetBSD audio driver

2004-03-02 Thread Alexandre Julliard
Yorick Hardy <[EMAIL PROTECTED]> writes: > 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. Any such solution n

Re: Native NetBSD audio driver

2004-03-02 Thread Yorick Hardy
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. 1) I created the directory dlls/winmm/drvcommon (perhaps there is a better name ?) 2) moved dlls/winmm/wineoss/oss.c and dlls/winmm/winenbsd/nbsd.c to th

Re: Native NetBSD audio driver

2004-02-26 Thread Yorick Hardy
I was thinking to look at the integration of the oss and NetBSD drivers this weekend (following Eric and Dimi's suggestion). Should I rather wait until some restructuring is done? The inclusion of the NetBSD audio driver is not urgent since oss already works quite well, and it stagnated on my hard

Re: Native NetBSD audio driver

2004-02-25 Thread James Gregory
On Thu, 2004-02-26 at 08:59, Alexandre Julliard wrote: > Robert Reif <[EMAIL PROTECTED]> writes: > > > I think it might be worthwhile considering restructuring the audio > > drivers into hardware independent wave, direct sound, midi > > and mixer sections and a hardware dependent low level > >

Re: Native NetBSD audio driver

2004-02-25 Thread Alexandre Julliard
Robert Reif <[EMAIL PROTECTED]> writes: > I think it might be worthwhile considering restructuring the audio > drivers into hardware independent wave, direct sound, midi > and mixer sections and a hardware dependent low level > implementation for oss, alsa, ... Yes we should definitely do some

Re: Native NetBSD audio driver

2004-02-23 Thread Robert Reif
I think it might be worthwhile considering restructuring the audio drivers into hardware independent wave, direct sound, midi and mixer sections and a hardware dependent low level implementation for oss, alsa, ... The basic structure of all the drivers is similar enough to abstracted out the ha

Re: Native NetBSD audio driver

2004-02-23 Thread Joerg Mayer
On Mon, Feb 23, 2004 at 06:50:33PM -0500, Dimitrie O. Paun wrote: > I think quite the opposite is true: having an almost identical > driver in the tree simply obscures the matter more. The two will > diverge in time, and the NetBSD one will slowly bitrot. Now that > the two are the closest it's the

Re: Native NetBSD audio driver

2004-02-23 Thread Dimitrie O. Paun
On Mon, 23 Feb 2004, Yorick Hardy wrote: > a separate winenbsd driver will have to do in the mean time, and > provides a starting point to compare the drivers in case someone > else is also interested. I think quite the opposite is true: having an almost identical driver in the tree simply obscur

Re: Native NetBSD audio driver

2004-02-23 Thread Yorick Hardy
Good catch, thanks. I will resubmit tonight. >> diff -urN /home/yorick/software/wine/wine/dlls/Makefile.in >> ./dlls/Makefile.in >> --- /home/yorick/software/wine/wine/dlls/Makefile.in Sat Feb 14 19:20:00 >> 2004 >> +++ ./dlls/Makefile.in Sat Feb 21 23:43:35 2004 >> @@ -1745,6 +1749,7 @@ >>

Re: Native NetBSD audio driver

2004-02-22 Thread Eric Pouech
Yorick Hardy a écrit : This patch adds the audio driver winenbsd using the native NetBSD audio system as an alternative to OSS. On the one hand this is useful to directly make use of the features of the NetBSD audio system instead of using emulation, on the other hand it is another driver to mainta