From: ndno72-omap@yahoo.com
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: "beagleboard@googlegroups.com" <beagleboard@googlegroups.com>,
"linux-omap@vger.kernel.orgList" <linux-omap@vger.kernel.org>
Subject: Re: No audio support for BeagleBoard in Latest GIT tree?
Date: Tue, 27 Jan 2009 02:37:30 -0800 (PST) [thread overview]
Message-ID: <636109.62555.qm@web81102.mail.mud.yahoo.com> (raw)
In-Reply-To: 20090127115540.b7c5e004.jarkko.nikula@nokia.com
> > 2) The BeagleBoard uses the twl4030 device for its audio (among other things);
> for our OMAP3 custom board, we're not using that, we're going to continue use
> the AIC33 codec (like what we used on our Davinci custom board). Is adding
> support for the AIC33 codec as simple as enabling that option in the OMAP3 GIT
> kernel configuration under ALSA? Or do I have to do a lot of porting? If so,
> what is the best approach, i.e. porting the AIC33 initialization/driver code for
> mthe Davinci GIT kernel into OMAP3 GIT kernel?
>
> With ALSA System on Chip (ASoC) porting is pretty simple. There is
> already driver for AIC33 (sound/soc/codecs/tlv320aic3x.c), ASoC OMAP
> platfrom drivers (sound/soc/omap) and also machine drivers using AIC33
> (sound/soc/omap/n810.c and sound/soc/davinci/davinci-evm.c).
>
> So what you need is basically to write your own machine driver using
> mostly copy-paste approach.
>
> > 3) Is OSS audio API no longer supported? Our existing application uses the
> OSS audio API; the latest kernel seems to only support ALSA; is OSS emulation
> (on top of ALSA) working and/or reliable?
>
> At least some few OSS applications I have tried were working fine with
> OSS emulation.
>
Thanks for the advice and pointers. Hopefully, when I get my hands dirty in a few weeks and I get into troubles, people like you on this board can help.
Regards,
Andy
prev parent reply other threads:[~2009-01-27 10:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 19:30 [PATCH] ARM: OMAP: board-omap3beagle: set i2c-3 to 100kHz Koen Kooi
2009-01-15 19:54 ` Koen Kooi
2009-01-23 8:00 ` Koen Kooi
2009-01-23 9:52 ` David Brownell
2009-01-23 10:48 ` Koen Kooi
2009-01-24 15:06 ` Jason Kridner
2009-01-24 20:30 ` David Brownell
2009-01-24 21:09 ` Koen Kooi
2009-01-24 22:33 ` David Brownell
[not found] ` <bd7b27490901250616q2363c5b4wf422d32831bd3638@mail.gmail.com>
2009-01-27 9:18 ` No audio support for BeagleBoard in Latest GIT tree? ndno72-omap
2009-01-27 9:38 ` Peter Ujfalusi
2009-01-27 10:35 ` ndno72-omap
2009-01-27 10:51 ` Peter Ujfalusi
2009-01-27 11:08 ` Arun KS
2009-01-27 9:55 ` Jarkko Nikula
2009-01-27 10:37 ` ndno72-omap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=636109.62555.qm@web81102.mail.mud.yahoo.com \
--to=ndno72-omap@yahoo.com \
--cc=beagleboard@googlegroups.com \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox