From: Charles 'Buck' Krasic <krasic@cs.ubc.ca>
To: linux-omap-open-source@linux.omap.com
Cc: maemo-developers@maemo.org, lamikr@c.jyu.fi
Subject: [PATCH] board-nokia-770.c: Add missing alsa platform driver code
Date: Thu, 15 Jun 2006 18:35:21 -0700 [thread overview]
Message-ID: <44920AD9.4030200@cs.ubc.ca> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I checked the mailing list archive, and I do not see any answer
regarding Mika's alsa patch for alsa and the 770.
Since Nokia released the 2.0 beta for 770, I hoped Nokia would have
ALSA support enabled, but it seems not.
So I went ahead and rebuilt the Nokia 2.6.16-omap1 kernel with Mika's
ALSA patch
(http://linux.omap.com/pipermail/linux-omap-open-source/2006-April/006868.html),
installed the kernel, and booted. Low and behold the OMAP_ALSA card
appears in /proc/asound/cards on the 770!
After this, I build the libasound2 package in scratchbox (using ubuntu
breezy package) and alsa-utils. libasound2 built and installed ok on
the 770. alsa-utils would build, but not install because of package
dependencies. So anyway, I just copied the aplay binary to the
770. So, it seems to play some wav files, but not at the correct
speed; i.e. a 44100 Hz .wav file sounds very slow on the 770. I
found a 22 KHz wav and it sounded almost right. So I'm guessing the
770 is playing at 16KHz.
Can any Nokia people comment, will we have ALSA in 2.0? I for one
would be really happy to see it.
- -- Buck
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEkgrZPrrWIMa4SMsRAtY7AJ91hyW6s9uulFna70h9vUx/J5eeygCgrt02
lL87GqV5242tn5CaS3a1xgs=
=HJqg
-----END PGP SIGNATURE-----
next reply other threads:[~2006-06-16 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 1:35 Charles 'Buck' Krasic [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-05 23:20 [PATCH] board-nokia-770.c: Add missing alsa platform driver code lamikr
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=44920AD9.4030200@cs.ubc.ca \
--to=krasic@cs.ubc.ca \
--cc=lamikr@c.jyu.fi \
--cc=linux-omap-open-source@linux.omap.com \
--cc=maemo-developers@maemo.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