[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux1394-devel
Subject:    Re: [PATCH 3/4] firewire: core: allow source filter for
From:       Alaney_Dória <27978 () alunos ! isel ! ipl ! pt>
Date:       2009-12-16 20:47:25
Message-ID: 4B29475D.4020000 () alunos ! isel ! ipl ! pt
[Download RAW message or body]

On 16-12-2009 16:03, Stefan Richter wrote:
> Clemens Ladisch wrote:
>    
>> Stefan Richter wrote:
>>      
>>> Regarding a kernel audio driver:
>>>
>>> Device control (and hence device discovery) needs to stay in userspace
>>> because there are simply too many different device types.  So, the audio
>>> streaming kernel component in which the FFADO folks are interested in
>>> might end up not having to deal with FCP at all.
>>>        
>> At the moment I'm writing a driver for my specific device (AudioFire2)
>> because I want to get the Firewire streaming stuff working first, and
>> this test driver _is_ using FCP.  (But as long as I'm testing, I'm not
>> too concerned about conflicts.)
>>      
> Ah, I see.
>
>    
>> A userspace/kernel device handling interface for FFADO does not exist at
>> the moment, and FFADO needs to be rewritten (in an unknown amount) to
>> support this.  I don't know if there are any plans for this and what
>> time this would take;
>>      
> The status is that there was a GSoC project which produced some kernel
> code, but
>    a) an architectural discussion of the kernel--userspace division
>       did not yet happen on either ffado-devel or linux1394-devel,
>    b) I for one have not yet looked at the code in detail, not even
>       compiled it yet.
> http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/linux_foundation/t124022664340
> http://repo.or.cz/w/firewire-audio.git
>
> There was also an ALSA-AMDTP project in Linux 2.4 days which never made
> it onto the radar of mainline Linux or mainline FFADO though:
> http://mlanalsa.sourceforge.net/
>    

     Well I'm working on that, to give OGT support to FFado, but right 
now I don't have much time till end of January 2010, and
     that's why I was asking about the VIA firewire chipset because I 
was thinking to buy a Asus P55 MB. For more details, just
    write me.


>    
>> it's possible that I complete a self-contained
>> driver for all Echo devices before FFADO + kernel driver can be made to
>> work.
>>      
> Definitely, because there aren't that many people who know all the
> involved problem spaces enough /and/ have as much time on their hand as
> will be required for that.
>
>    
>> In any case, the firedtv driver needs better FCP handling now.
>>      
> When the firedtv driver was originally submitted via the Linux Driver
> Project, I thought that its adaptation to Juju (including proper FCP
> handling in Juju) would happen much quicker.  However, once more it
> turned out that things don't get magically done all by themselves. :-)
>    


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
mailing list linux1394-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-devel
[prev in list] [next in list] [prev in thread] [next in thread]