Francois Gouget wrote:
I have been thinking about how to share more more code between the
drivers. My understanding is that we cannot modify the winmm-driver
protocol because we have to conform to the standard Windows API,
mostly so that winmm can be reused with as little modifications as
possi
Now maybe I'm mis-evaluating the amount of code that could be shared
beyond this wine_bytes_to_mmtime() function and this is not worth it.
Does anyone have a more informed opinion on the matter?
the better way would be to merge all wine MM drivers into a single one. This
would solve most of the
On Fri, 18 Mar 2005, Robert Reif wrote:
[...]
Does that mean we could do the same wor winealsa, winearts, etc?
Yes, I am going to do winealsa next now that I have an alsa system.
I haven't really looked at the others yet but will do them if someone
doesn't beat me to it ;-)
Cool. I think I'll let
Francois Gouget wrote:
On Thu, 17 Mar 2005, Robert Reif wrote:
Fall back to default header prepare and unprepare functions.
A driver only needs to support prepare and unprepare functions
when it is doing something special like allocating a DMA buffer for
each header. Since we don't do anything spe
On Thu, 17 Mar 2005, Robert Reif wrote:
Fall back to default header prepare and unprepare functions.
A driver only needs to support prepare and unprepare functions
when it is doing something special like allocating a DMA buffer for
each header. Since we don't do anything special, just fall back
to
