Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Ronald Stewart <ronaldjstewart@gmail.com>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Hi ALSA Team - serious technical question from Ron
Date: Sat, 10 Jun 2006 02:23:25 +0700	[thread overview]
Message-ID: <4489CAAD.4010900@boosthardware.com> (raw)
In-Reply-To: <4c84399f0606042324o10e15f92t3320621c2f9064f9@mail.gmail.com>

Hi Ronald,

I have forwarded this email the the alsa-devel mailing list.

Cheers.


Ronald Stewart wrote:
> Hello,
> I originally wrote this to the websmaster before I saw your email 
> addresses.
> I just want to let you guys know that I really believe that what I am
> inquiring about and trying to accomplish will really help Linux Audio
> across the board.
> If there is anyway I could get a conversation going with any of you
> about the state of ALSA in regards to my hardware (ie previous codec
> development)
> and share with you where we are at today along with preparing you with all
> the information you would need to succeed as well as where we are
> going with our vison.  Also I read what is required for HW / firmware
> but I think I can really excel in that category for the ALSA team and
> ready some dev boards for you or any other requirements that are
> needed.
> Any way, would love some feedback and hopefully you guys aren't too hard 
> on me.
> Thanks and here is the original email to webmaster:
> 
> Hey guys,
> 
> Can someone point me to the correct email address to ask this question?
> 
> I built a portable linux based multitrack studio/field recorder but we 
> have yet
> to get 24 bit audio sampling achieved on our prototypes.  Now we use a Soc
> utilizing the Intel PXA270 and we have disabled the ac97 codec on board and
> we are connecting the PXA to an AKM 4620A codec.  However, I was wondering
> how much development has occured for this if at all.
> Anyway I have many questions.  I decided over a year ago when I began that
> we would always be a Linux based product, for all the right reasons and now
> I could really use some help finishing this for producing the retail 
> versions.
> 
> Here is what it looks like!
> 
> Thanks and if anyone could assist me getting just a conversation going 
> about the
> current landscape I would really appreciate it.
> 
> Thank you
> 
> Ronald Stewart
> 
> ------------------------------------------------------------------------
> 


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://lau.linuxaudio.org - The Linux Audio Users guide
========================================

"Anything your mind can see you can manifest physically, then it will 
become reality" - Macka B

       reply	other threads:[~2006-06-09 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4c84399f0606042324o10e15f92t3320621c2f9064f9@mail.gmail.com>
2006-06-09 19:23 ` Patrick Shirkey [this message]
2006-06-10  3:43   ` Hi ALSA Team - serious technical question from Ron Lee Revell
2006-06-12 10:52   ` Liam Girdwood
2006-06-12 16:23     ` Ronald Stewart
2006-06-12 16:53       ` Liam Girdwood

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=4489CAAD.4010900@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ronaldjstewart@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