From: Philip Balister <philip@balister.org>
To: "Carlos, John J DA CIV USA ATC" <john.carlos@atc.army.mil>
Cc: Linux-Omap-Open-Source <linux-omap-open-source@linux.omap.com>
Subject: Re: kernel 2.6.18 dsp gateway problems and tlv320aic23 problem osk591 2
Date: Tue, 31 Oct 2006 10:23:52 -0500 [thread overview]
Message-ID: <45476A88.7010504@balister.org> (raw)
In-Reply-To: <22CECCE071A8DC4CAB2412DC44CBEDF107A5A7AD@apgrb1atc-0058e.atc.army.mil>
I can run aplay /dev/urandom on my OSK. This emits an appropriate hiss
and I can adjust the volume with alsamixer.
I built my kernel using this recipe from OE:
http://www.openembedded.org/repo/org.openembedded.dev/packages/linux/linux-omap1_2.6.18-omap1.bb
defconfig is here. I use the eabi version.
http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/linux/linux-omap1-2.6.18-omap1
Philip
Carlos, John J DA CIV USA ATC wrote:
> Hello all,
>
> I have two issues. I'm trying to get audio codec to work. On kernel
> 2.6.17.13 with dsp patch the dsp gateway stuff works but I can't get audio
> support to compile without errors and it locks the kernel when trying to
> load.
>
> I tried kernel 2.6.18 with omap-1 patch. The dsp module will not load to
> many undefined externals (is there a patch for this) Also the audio codec
> modules all compile with no errors but when I modprobe tlv320aic23.ko for
> the i2c support for the codec the kernel still locks up. Has anyone been
> able to get audio support working on osk5912 in either of the two kernel
> versions I mentioned.
>
> Thanks,
> John
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
prev parent reply other threads:[~2006-10-31 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 11:55 kernel 2.6.18 dsp gateway problems and tlv320aic23 problem osk591 2 Carlos, John J DA CIV USA ATC
2006-10-31 15:23 ` Philip Balister [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=45476A88.7010504@balister.org \
--to=philip@balister.org \
--cc=john.carlos@atc.army.mil \
--cc=linux-omap-open-source@linux.omap.com \
/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