From: Takashi Iwai <tiwai@suse.de>
To: David Olofson <david@olofson.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Status of Echo/Event support
Date: Mon, 09 Dec 2002 15:13:01 +0100 [thread overview]
Message-ID: <s5hk7ij8emq.wl@alsa2.suse.de> (raw)
In-Reply-To: <200212060215.gB62FY48018703@mail.space2u.com>
Hi David,
At Fri, 6 Dec 2002 03:15:32 +0100,
David Olofson wrote:
>
>
> Hi!
>
> I still have that Echo/Event Layla audio interface lying around. I
> don't have any use for it whatsoever as it is now, since I don't use
> Windoze at all any more (except occasionally, for some minor projects
> at work) and I can't use Layla with Linux.
>
> So, I have to make a decision: Either I look at Echo's C++ source and
> hack an ALSA driver - or I get rid of my Layla, and get a Delta 1010
> or something. I'll look at their code and see how I feel about it...
>
> As you might have guessed, there is *one* thing against:
>
> Why did it take so damn long to releas that code!?
well, afaik, both Jaroslav and I haven't check this soundcard, because
we have no this hardware.
so, perhaps the answer is that no one is working on it yet.
> The fact that I still have a Layla card now is part coincidence, part
> me being too lazy to get rid of it... Now, I'm basically wondering if
> anyone still wants to hear about Echo. I must admit that I still have
> hard feelings personally - but that might also have to do with the
> major hardware and driver issues I had before I got the thing to work
> under Windoze.
>
>
> Anyway, what I'm wondering is basically two things:
>
> * Is anyone else already working on a driver already?
>
> * Does anyone care? That is, does anyone else around
> here own - or have access to - one of these units?
> (Maybe I should ask in a somewhat more public place?)
>
> * I have some 18 years of programming experience
> (mostly to-the-metal stuff), some kernel hacking
> experience, but no ALSA coding experience. Any
> rough estimate how much time I'd need to add Echo
> support to ALSA?
when i write a new driver, it would take
- ca. 1 week if there is an OSS driver,
- ca. 2 weeks if it's a normal PCI (or ISA) device and there is enough
technical info, and
- more for exotic environment :)
until the first beta release. a test version may be ealier, though.
recently i wrote a small howto for writing an alsa-driver. please
check the archive of alsa-devel ml.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-12-09 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 2:15 Status of Echo/Event support David Olofson
2002-12-09 14:13 ` Takashi Iwai [this message]
[not found] ` <200212091420.gB9EKUEO013443@mail.space2u.com>
2002-12-09 14:45 ` Takashi Iwai
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=s5hk7ij8emq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=david@olofson.net \
/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