Alsa Driver on Coldfire

Alsa Driver on Coldfire

[Simon Dunn]

Hi

I've been given the job of writing a sound card driver using the alsa  
architecture for a
development platform that uses a coldfire chip.

The first thing I came across was a chunky 'if !M68K' in sound/Kconfig,  
which excludes all
the alsa components.  I can't find any reason for this in the mailing list  
archives or
on the web in general, so I'm wondering if anybody knows why the M68K  
architecture is
excluded?

Cheers
Simon

-- 

Simon Dunn, Software Engineer
MPC Data Limited
e-mail: sdunn@mpc-data.co.uk
web: www.mpc-data.co.uk
tel: +44 (0) 1225 710600
fax: +44 (0) 1225 710601
ddi: +44 (0) 1225 710631

MPC Data Limited is a company registered in England and Wales with company  
number 05507446
Registered Address: County Gate, County Way, Trowbridge, Wiltshire, BA14  
7FJ
VAT no: 850625238

The information in this email and in the attached documents is  
confidential and may be legally privileged. Any unauthorized review,  
copying, disclosure or distribution is prohibited and may be unlawful. It  
is intended solely for the addressee. Access to this email by anyone else  
is unauthorized. If you are not the intended recipient, please contact the  
sender by reply email and destroy all copies of the original message. When  
addressed to our clients any opinions or advice contained in this email is  
subject to the terms and conditions expressed in the governing contract.

Re: Alsa Driver on Coldfire

[Takashi Iwai]

At Fri, 18 Apr 2008 11:02:56 +0100,
Simon Dunn wrote:
> 
> Hi
> 
> I've been given the job of writing a sound card driver using the alsa  
> architecture for a
> development platform that uses a coldfire chip.
> 
> The first thing I came across was a chunky 'if !M68K' in sound/Kconfig,  
> which excludes all
> the alsa components.  I can't find any reason for this in the mailing list  
> archives or
> on the web in general, so I'm wondering if anybody knows why the M68K  
> architecture is
> excluded?

I don't remember exact reason, too.  It was so when ALSA was merged,
IIRC.


Takashi

Re: Alsa Driver on Coldfire

[Mark Brown]

On Fri, Apr 18, 2008 at 12:22:35PM +0200, Takashi Iwai wrote:
> Simon Dunn wrote:

> > I've been given the job of writing a sound card driver using the alsa  
> > architecture for a
> > development platform that uses a coldfire chip.

> > on the web in general, so I'm wondering if anybody knows why the M68K  
> > architecture is
> > excluded?

> I don't remember exact reason, too.  It was so when ALSA was merged,
> IIRC.

I think I'd formed the impression from somewhere or other (probably
related to Debian m68k) that it was that there were no relevant drivers
for m68k that had been ported to ALSA so there wasn't much point
building it.  I could be misremembering, though.

With regard to ColdFire I'm guessing that this is an embedded system?
If so you might want to have a look at working with the ASoC framework
(see sound/soc and Documentation/sound/alsa/soc).

Re: Alsa Driver on Coldfire

[Simon Dunn]

On Fri, 18 Apr 2008 12:23:41 +0100, Mark Brown  
<broonie@opensource.wolfsonmicro.com> wrote:

>> I don't remember exact reason, too.  It was so when ALSA was merged,
>> IIRC.
>
> I think I'd formed the impression from somewhere or other (probably
> related to Debian m68k) that it was that there were no relevant drivers
> for m68k that had been ported to ALSA so there wasn't much point
> building it.  I could be misremembering, though.
>
> With regard to ColdFire I'm guessing that this is an embedded system?
> If so you might want to have a look at working with the ASoC framework
> (see sound/soc and Documentation/sound/alsa/soc).

Thanks for the info guys, I couldn't see any reason why alsa would be
excluded.  Oh and thanks for the tip re the system on chip, I'll have
a look into that though the kernel version we're working with is
2.6.10 and doesn't include it 'off the shelf'.

Can't imagine it would be too difficult to merge across unless anyone
knows different?

Cheers
Simon


-- 

Simon Dunn, Software Engineer
MPC Data Limited
e-mail: sdunn@mpc-data.co.uk
web: www.mpc-data.co.uk
tel: +44 (0) 1225 710600
fax: +44 (0) 1225 710601
ddi: +44 (0) 1225 710631

MPC Data Limited is a company registered in England and Wales with company  
number 05507446
Registered Address: County Gate, County Way, Trowbridge, Wiltshire, BA14  
7FJ
VAT no: 850625238

The information in this email and in the attached documents is  
confidential and may be legally privileged. Any unauthorized review,  
copying, disclosure or distribution is prohibited and may be unlawful. It  
is intended solely for the addressee. Access to this email by anyone else  
is unauthorized. If you are not the intended recipient, please contact the  
sender by reply email and destroy all copies of the original message. When  
addressed to our clients any opinions or advice contained in this email is  
subject to the terms and conditions expressed in the governing contract.

Re: Alsa Driver on Coldfire

[Mark Brown]

On Fri, Apr 18, 2008 at 04:47:40PM +0100, Simon Dunn wrote:
> On Fri, 18 Apr 2008 12:23:41 +0100, Mark Brown 

> excluded.  Oh and thanks for the tip re the system on chip, I'll have
> a look into that though the kernel version we're working with is
> 2.6.10 and doesn't include it 'off the shelf'.

> Can't imagine it would be too difficult to merge across unless anyone
> knows different?

Tedious more than hard - there was a change in the ALSA APIs from using
typedefs to using 'struct foo' which creates a lot of code churn but is
not at all difficult to deal with.  Other than that things should be
pretty straightforward.