public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Anderson Briglia <anderson.briglia@indt.org.br>
To: ext Daniel Petrini <d.pensator@gmail.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: quick test OMAP ALSA driver on H2
Date: Tue, 15 Aug 2006 10:44:03 -0400	[thread overview]
Message-ID: <44E1DDB3.8040808@indt.org.br> (raw)
In-Reply-To: <9268368b0608150400t43fc9dfev71a0b9d366eb8286@mail.gmail.com>

Hi Jian,

ext Daniel Petrini wrote:
> Did you tried aplay and other applications from alsa-utils?
> In my tests I always walked through that path.

I compiled a kernel for H2 with ALSA driver (using the latest linux-omap git tree) and did
some tests (just played a wav file) using aplay. The sound was played properly.
You can check if the device is present using "aplay -l" command.

root@arm:~/sound# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: TSC2101 [H2 TSC2101], device 0: OMAP PCM [omap alsa pcm]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Regards,

Anderson Briglia

>> Hi everyone,
>>
>> I managed to get a H2 board and booted an ALSA enabled kernel on it. The
>> kernel boot log shows "H2 TSC2101" as the #0 ALSA device. To do a quick
>> test, I have manually created a pcm device node:
>> /dev/snd/pcmC0D0 116, 16, c
> 
> 
> [...]
> 
>> Regards,
>>
>> Jian
> 

  reply	other threads:[~2006-08-15 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 11:00 quick test OMAP ALSA driver on H2 Daniel Petrini
2006-08-15 14:44 ` Anderson Briglia [this message]
2006-08-15 16:12   ` Zhang, Jian
2006-08-15 18:18     ` David Cohen
2006-08-15 18:28     ` Anderson Briglia
2006-08-15 19:39       ` Zhang, Jian
2006-08-18  2:18         ` lamikr
  -- strict thread matches above, loose matches on Subject: below --
2006-08-14 20:45 Zhang, Jian

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=44E1DDB3.8040808@indt.org.br \
    --to=anderson.briglia@indt.org.br \
    --cc=d.pensator@gmail.com \
    --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