From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Qeury regarding EAC driver for omap 24xx
Date: Wed, 6 Jun 2007 16:02:49 +0300 [thread overview]
Message-ID: <20070606160249.568fac54.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <4666ADE7.5050904@gmail.com>
On Wed, 06 Jun 2007 16:51:51 +0400
"ext Dmitry Krivoschekov" <dmitry.krivoschekov@gmail.com> wrote:
> > Hopefully we see gradually those drivers ported into ASoC platform and
> > codec drivers in order to get some change to get them into mainline.
> >
> yes, it would be great to port sound/arm/omap stuff to ASoC framework,
> do you have any plans (or maybe already working) on this?
>
Unfortunately not in near future.
Jarkko
prev parent reply other threads:[~2007-06-06 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:02 Qeury regarding EAC driver for omap 24xx Pharaoh .
2007-06-06 12:04 ` Jarkko Nikula
2007-06-06 12:33 ` Pharaoh .
2007-06-06 12:51 ` Dmitry Krivoschekov
2007-06-06 13:02 ` Jarkko Nikula [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=20070606160249.568fac54.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=dmitry.krivoschekov@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