On Monday 24 March 2003 08:35, David Olofson wrote:
> On Friday 21 March 2003 21.47, Paul Davis wrote:
> > agreed. its a rather tricky design however, because on a lot of
> > hardware, you have to defer most of the driver initialization until
> > the firmware load is complete. the h/w won't even ta
On Friday 21 March 2003 21.47, Paul Davis wrote:
[...]
> >a better interface is a generic firmware loading API (or as
> > generic as one can be made, anyway) with a userspace firmware
> > loader.
>
> agreed. its a rather tricky design however, because on a lot of
> hardware, you have to defer most
>it is however quite dangerous for a driver to do so.
why?
>a better interface is a generic firmware loading API (or as generic as one
>can be made, anyway) with a userspace firmware loader.
agreed. its a rather tricky design however, because on a lot of
hardware, you have to defer most of the
On Fri, 21 Mar 2003, David Olofson wrote:
> On Thursday 20 March 2003 23.08, Paul Davis wrote:
> > >Anyway, I believe this goes for a bunch of other cards as well, so
> > > no news here, really.
> > there are plans to try to generalize the "firmware" loading for
> > ALSA drivers to load stuff from
At Thu, 20 Mar 2003 17:08:23 -0500,
Paul Davis wrote:
>
> >Anyway, I believe this goes for a bunch of other cards as well, so no
> >news here, really.
>
> there are plans to try to generalize the "firmware" loading for ALSA
> drivers to load stuff from a regular file. the wavefront driver does
>
On Thursday 20 March 2003 23.08, Paul Davis wrote:
> >Anyway, I believe this goes for a bunch of other cards as well, so
> > no news here, really.
>
> there are plans to try to generalize the "firmware" loading for
> ALSA drivers to load stuff from a regular file. the wavefront
> driver does this.
On Thursday 20 March 2003 22.54, Mark Rages wrote:
[...]
> Did you all know there is an alsa-devel mailing list?
Yep - and I've been wondering what we're doing on LAD... :-)
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality!
>Anyway, I believe this goes for a bunch of other cards as well, so no
>news here, really.
there are plans to try to generalize the "firmware" loading for ALSA
drivers to load stuff from a regular file. the wavefront driver does
this. not many people know that a linux driver can call
open/close/r
On Tue, Mar 18, 2003 at 11:51:30PM +0100, David Olofson wrote:
> On Tuesday 18 March 2003 21.24, Paul Davis wrote:
> [...CVS, bugzilla etc...]
> > with all due respect, you are talking about somewhere between
> > 1-5000 lines of code that would take someone experienced about 3
> > days to get to 60
On Thursday 20 March 2003 19.29, Ranjit Singh wrote:
> >My only interest is in th interface components useful in making a
> > device driver.
>
> Sure. I was just curious as to whether there was scope at a later
> to date to play with the DSP code.
Even if Echo would release the required info, ther
On Thursday 20 March 2003 16.57, Ranjit Singh wrote:
> >> We're effectively talking about a driver for the Motorola DSP
> >> onboard (I can't remember what the no is.)
> >
> >No, that stuff is "secret". The microcode is available only as raw
> >binaries, and the driver's job is to talk to the micro
>My only interest is in th interface components useful in making a device
>driver.
Sure. I was just curious as to whether there was scope at a later to date to
play with the DSP code.
I've looked at the source again (cheers, David ;) and I can see what David
means, in that for each device (Dar
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ranjit
Singh
Sent: Thursday, March 20, 2003 7:57 AM
To: [EMAIL PROTECTED]
Subject: Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux
>>> We're effectively talking about a driver for th
>> We're effectively talking about a driver for the Motorola DSP
>> onboard (I can't remember what the no is.)
>No, that stuff is "secret". The microcode is available only as raw
>binaries, and the driver's job is to talk to the microcode; not the
>hardware directly. So, we're talking about Li
On Tue, 2003-03-18 at 23:49, Ranjit Singh wrote:
> We're effectively talking about a driver for the Motorola DSP onboard (I can't
> remember what the no is.) We first need to get it to C code- isn't that what
> the CPP used to do?
Some "lesser" C++ compilers do. GCC does things the right way (
On Wednesday 19 March 2003 00.49, Ranjit Singh wrote:
[...]
> We're effectively talking about a driver for the Motorola DSP
> onboard (I can't remember what the no is.)
No, that stuff is "secret". The microcode is available only as raw
binaries, and the driver's job is to talk to the microcode; n
: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux
On Tuesday 18 March 2003 22.25, Brad Arant wrote:
[...]
> Then lets get it to that point so we can make drivers for the older
> Echo a non-issue.
Older and newer isn't an issue at all it seems, as they're virtually
identical fro
> with all due respect, you are talking about somewhere between 1-5000
> lines of code that would take someone experienced about 3 days to get
> to 60% functionality. once it reaches that point, ALSA will happily
> take it on, and you get CVS and the ALSA mailing lists to use.
Fair enough, I d
On Tuesday 18 March 2003 22.25, Brad Arant wrote:
[...]
> Then lets get it to that point so we can make drivers for the older
> Echo a non-issue.
Older and newer isn't an issue at all it seems, as they're virtually
identical from the driver POV. All cards are 24 bit internally, and
the DMA subsy
On Tuesday 18 March 2003 21.24, Paul Davis wrote:
[...CVS, bugzilla etc...]
> with all due respect, you are talking about somewhere between
> 1-5000 lines of code that would take someone experienced about 3
> days to get to 60% functionality. once it reaches that point, ALSA
> will happily take it
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Paul Davis
Sent: Tuesday, March 18, 2003 12:24 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux
>with all due respect, you are talking ab
>> I have downloaded the C++ sample code from the echo site. Has anybody
>> developed it beyond that point? I will go ahead and set up a web site for
>> the management of the development. Are there any suggestions as to the tools
>
>> we will need to collaborate?
>
>Well, base would be CVS and
> I have downloaded the C++ sample code from the echo site. Has anybody
> developed it beyond that point? I will go ahead and set up a web site for
> the management of the development. Are there any suggestions as to the tools
> we will need to collaborate?
Well, base would be CVS and bugzilla
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ranjit
Singh
Sent: Tuesday, March 18, 2003 6:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux
..
>I think we could both learn some new things :)
As we
> I am a broadcast engineer by profession, but a hacker by hobby. I maintain
> the PostgreSQL RPMset, the nspostgres AOLserver database driver, and do a
> little bit of coding. I wouldn't consider myself fluent in C++, however.
> But I enjoy learning new things
Well, that sounds perfect to
On Monday 17 March 2003 19:00, Ranjit Singh wrote:
> Lamar, since you're on Internet Radio and that, maybe you'd like to do the
> testing from an engineer's perspective? (ie with stability and throughput
> as your main goals.) Do you have any coding experience?
I am a broadcast engineer by profess
Sorry not to respond sooner, can't work out the Konqueror history thing= it
doesn't even sort by date, for crying out loud.. ;)
I downloaded the Event code as well, although not sure where it is on the
machines, since I've converted eveything to Linux. Since the code was put out
publically, can
On Saturday 15 March 2003 08:23, Brad Arant wrote:
> If anyone can forward some specs to these cards I would be glad to see what
> I can do.
> If also have a Darla 24 (No-SPDIF) that I can test with. If anybody has
> other cards in this family that would like to test and have been waiting
> for dr
PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David
Olofson
Sent: Saturday, March 15, 2003 4:52 AM
To: [EMAIL PROTECTED]
Subject: Re: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux
On Friday 14 March 2003 03.13, Ranjit Singh wrote:
> Hi,
>
>I was wondering whether there'd bee
On Friday 14 March 2003 03.13, Ranjit Singh wrote:
> Hi,
>
>I was wondering whether there'd been any progress on this?
Nope, not yet; not around here anyway. I've heard from a few others
who started messing with it, but AFAIK, no one is actually hacking
right now.
>I have a Darla card,
Hi,
I was wondering whether there'd been any progress on this?
I have a Darla card, and would love to get it working under Linux. I have
experience of assembler (since 1983) if that would be of any help..
Regards,
Ranjit.
> I have a short, simple question:
>
> Would anyone around here care for ALSA drivers for
the Echo
> (formerly Event/Echo) line of studio audio
interfaces?
>
>
> (We're talking about the original Darla/Gina/Layla,
as well as the
> new 24 bit interfaces.)
>
> I have an old 20 bit Layla. I h
Echo Darla/Gina/Layla/... on Linux
I have a short, simple question:
Would anyone around here care for ALSA drivers for the Echo
(formerly Event/Echo) line of studio audio interfaces?
[...]
> I have a short, simple question:
>
> Would anyone around here care for ALSA drivers for the Echo
> (formerly Event/Echo) line of studio audio interfaces?
>
>
> (We're talking about the original Darla/Gina/Layla, as well as the
> new 24 bit interfaces.)
>
> I have an old 20 bit La
I have a short, simple question:
Would anyone around here care for ALSA drivers for the Echo
(formerly Event/Echo) line of studio audio interfaces?
(We're talking about the original Darla/Gina/Layla, as well as the
new 24 bit interfaces.)
I have an old 20 bit Layla. I have the
35 matches
Mail list logo
