Josh Green wrote:
>
> Patrick Shirkey wrote:
>
> > Abramo Bagnara wrote:
>
> >
>
> >>
> >>SuSE support was invaluable, its lack for so many months has made
> >>everything harder and slower for ALSA.
> >>
> >>
> >
> > That is very good news :)
> >
> >
>
> Is it?? My understanding from what Ab
Patrick Shirkey wrote:
> Abramo Bagnara wrote:
>
>>
>>SuSE support was invaluable, its lack for so many months has made
>>everything harder and slower for ALSA.
>>
>>
>
> That is very good news :)
>
>
Is it?? My understanding from what Abramo said was that SuSE support
used to be availab
Abramo Bagnara wrote:
>
> Paul Davis wrote:
> >
> > >To be more specific I'm referring to a function(?) called type share as
> > >opposed to type hw. PD mentioned last week that Abramo had implemented
> > >it a while ago and mentioned that it did this for cards that do not have
> > >support for m
>To be more specific I'm referring to a function(?) called type share as
>opposed to type hw. PD mentioned last week that Abramo had implemented
>it a while ago and mentioned that it did this for cards that do not have
>support for multiopen.
>
>He also said that AFAHK Abramo is the only person wh
Paul Davis wrote:
>
> >To be more specific I'm referring to a function(?) called type share as
> >opposed to type hw. PD mentioned last week that Abramo had implemented
> >it a while ago and mentioned that it did this for cards that do not have
> >support for multiopen.
> >
> >He also said that A
>> keep in mind that this is likely to be no more efficient (and possibly
>> less) than using esd or artsd. it still involves un-optimized IPC with
>> a server process.
>
>How can you affirm that is a mistery for me: async notification, poll
>and shared memory will make the difference (a big diffe