From: "jeff" <jeff_lee@coventive.com>
To: "David Kesselring" <dkesselr@mmc.atmel.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: sound drivers
Date: Thu, 2 Oct 2003 21:49:56 +0800 [thread overview]
Message-ID: <04a701c388ec$10b9b050$c117a8c0@jefflee> (raw)
In-Reply-To: Pine.GSO.4.44.0310020901500.8498-100000@ares.mmc.atmel.com
In here, we can use madplay to play MP3, vplay to run WAV file, etc.
Yes, we get the kernel source from linux-mips.org but we porting the ALSA
driver base on many others code. For example, we will refer the VIA
, StrongARM, ESS.... source code and combine to VR4181A ALSA
driver. BUT..... Capture still can't work :-(
Regards,
Jeff
----- Original Message -----
From: "David Kesselring" <dkesselr@mmc.atmel.com>
To: "jeff" <jeff_lee@coventive.com>
Cc: <linux-mips@linux-mips.org>
Sent: Thursday, October 02, 2003 9:06 PM
Subject: Re: sound drivers
> I just beginning to develop drivers for our SOC that includes a 5kf and
> our own custom dsp for audio playback. The target market is the settop. Am
> I correct in thinking that all audio drivers (mpeg,mp3,pcm) should be
> integrated with ALSA? When you say "still can't work" are you getting it
> compile with the linux-mips.org sources or something else?
> Thanks,
> David
>
> On Thu, 2 Oct 2003, jeff wrote:
>
> > What CPU are you using ?
> > We are under development about ALSA on VR4181A but still can't work.
> > Only playback is OK. Capture is failed.
> >
> > Regards,
> >
> > Jeff
> > ----- Original Message -----
> > From: "David Kesselring" <dkesselr@mmc.atmel.com>
> > To: <linux-mips@linux-mips.org>
> > Sent: Wednesday, October 01, 2003 11:27 PM
> > Subject: sound drivers
> >
> >
> > > Has anyone used alsa on mips? I need to impement a sound driver for
our
> > > dsp. It seems like all sound drivers should be developed for alsa. Is
that
> > > true? I've tried to build alsa and its' drivers but ran into a cross
> > > compile problem.
> > > Thanks,
> > >
> > > David Kesselring
> > >
> >
> >
>
> David Kesselring
> Atmel MMC
> dkesselr@mmc.atmel.com
> 919-462-6587
>
WARNING: multiple messages have this Message-ID (diff)
From: "jeff" <jeff_lee@coventive.com>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: sound drivers
Date: Thu, 2 Oct 2003 21:49:56 +0800 [thread overview]
Message-ID: <04a701c388ec$10b9b050$c117a8c0@jefflee> (raw)
Message-ID: <20031002134956.4yaVqzRxY5DOJiM6umIOHgMbJ9bDFbUpH1Q0wiqr360@z> (raw)
In-Reply-To: Pine.GSO.4.44.0310020901500.8498-100000@ares.mmc.atmel.com
In here, we can use madplay to play MP3, vplay to run WAV file, etc.
Yes, we get the kernel source from linux-mips.org but we porting the ALSA
driver base on many others code. For example, we will refer the VIA
, StrongARM, ESS.... source code and combine to VR4181A ALSA
driver. BUT..... Capture still can't work :-(
Regards,
Jeff
----- Original Message -----
From: "David Kesselring" <dkesselr@mmc.atmel.com>
To: "jeff" <jeff_lee@coventive.com>
Cc: <linux-mips@linux-mips.org>
Sent: Thursday, October 02, 2003 9:06 PM
Subject: Re: sound drivers
> I just beginning to develop drivers for our SOC that includes a 5kf and
> our own custom dsp for audio playback. The target market is the settop. Am
> I correct in thinking that all audio drivers (mpeg,mp3,pcm) should be
> integrated with ALSA? When you say "still can't work" are you getting it
> compile with the linux-mips.org sources or something else?
> Thanks,
> David
>
> On Thu, 2 Oct 2003, jeff wrote:
>
> > What CPU are you using ?
> > We are under development about ALSA on VR4181A but still can't work.
> > Only playback is OK. Capture is failed.
> >
> > Regards,
> >
> > Jeff
> > ----- Original Message -----
> > From: "David Kesselring" <dkesselr@mmc.atmel.com>
> > To: <linux-mips@linux-mips.org>
> > Sent: Wednesday, October 01, 2003 11:27 PM
> > Subject: sound drivers
> >
> >
> > > Has anyone used alsa on mips? I need to impement a sound driver for
our
> > > dsp. It seems like all sound drivers should be developed for alsa. Is
that
> > > true? I've tried to build alsa and its' drivers but ran into a cross
> > > compile problem.
> > > Thanks,
> > >
> > > David Kesselring
> > >
> >
> >
>
> David Kesselring
> Atmel MMC
> dkesselr@mmc.atmel.com
> 919-462-6587
>
next prev parent reply other threads:[~2003-10-02 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 15:27 sound drivers David Kesselring
2003-10-02 1:56 ` jeff
2003-10-02 1:56 ` jeff
2003-10-02 13:06 ` David Kesselring
2003-10-02 13:49 ` jeff [this message]
2003-10-02 13:49 ` jeff
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='04a701c388ec$10b9b050$c117a8c0@jefflee' \
--to=jeff_lee@coventive.com \
--cc=dkesselr@mmc.atmel.com \
--cc=linux-mips@linux-mips.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