Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: ALSA-devel <alsa-devel@alsa-project.org>
Subject: Re: ASoC v2 on PowerPC
Date: Fri, 05 Oct 2007 10:30:38 -0500	[thread overview]
Message-ID: <4706589E.5000404@freescale.com> (raw)
In-Reply-To: <9e4733910710050826h25d29827radec93e9eef17782@mail.gmail.com>

Jon Smirl wrote:

>> A lot of the i.MX code just sits in BSPs and is never forwarded to the main
>> repositories.
> 
> Aren't you fixing that?

No, I work on PowerPC only, and only some 8xxx chips.  The i.MX stuff is a 
completely different group, and I only know one person who works on it, and 
she's in India.

> I started looking at v2 because of the posts about modularizing it and
> using open firmware to identify and load the codecs. There doesn't
> seem to be that much difference.

My brain can only handle so much at one time. :-)

> We are on 5200 because it is cheaper and 5200 has all the peripherals
> we need. Now that I am writing code for it I see that BestComm adds a
> lot of complexity. Hopefully I can get i2s working on it, I'd hate to
> switch CPUs after doing all this work.

You might want to direct some questions to the linuxppc-dev@ozlabs.org.  Also, 
if you have an IRC client, you can find a bunch of us on irc.freenode.net, 
channel #mklinux.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

      reply	other threads:[~2007-10-05 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 17:12 ASoC v2 on PowerPC Jon Smirl
2007-10-05 11:07 ` Liam Girdwood
2007-10-05 12:55   ` Jon Smirl
2007-10-05 14:03     ` Timur Tabi
2007-10-05 15:26       ` Jon Smirl
2007-10-05 15:30         ` Timur Tabi [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=4706589E.5000404@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jonsmirl@gmail.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