From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Ajay Jain <ajay050@gmail.com>
Cc: alsa-devel@lists.sf.net
Subject: Re: Sound Driver Querry
Date: Fri, 29 Dec 2006 13:01:09 +0000 [thread overview]
Message-ID: <1167397269.11374.59.camel@localhost.localdomain> (raw)
In-Reply-To: <b92b327b0612290416u49fa792axd5737a79bed3498e@mail.gmail.com>
On Fri, 2006-12-29 at 17:46 +0530, Ajay Jain wrote:
> > What arm cpu are you using ?
>
> We are using an ARM926-EJS. The interface between the code chip and
> the cpu, is by our own proprietary I2C controller. Is it possible for
> us to integrate this?
Yes, providing you create a Linux i2c driver for you controller.
> BTW, the patch you just mentioned, is that not in the main line
> 2.6.latest? We are using a 2.6.14, so is it possible to backport it?
>
It is, although I would recommend upgrading your kernel version as
2.6.14 is quite old.
> > OSS audio is deprecated in the Linux 2.6 kernel.
> Ok, but we have a working & robust AC97 WM9712 driver for the same. It
> would be much more convenient for us if we have something similar in
> OSS. So is this guy (the WM8751), supported in any form in the OSS?
Sorry, afaik no.
Liam
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-29 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 7:10 Sound Driver Querry Ajay Jain
2006-12-29 11:57 ` Liam Girdwood
2006-12-29 12:16 ` Ajay Jain
2006-12-29 13:01 ` Liam Girdwood [this message]
2006-12-29 13:11 ` James Courtier-Dutton
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=1167397269.11374.59.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=ajay050@gmail.com \
--cc=alsa-devel@lists.sf.net \
/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