From: Apostolos Dimitromanolakis <apostolos@aei.ca>
To: TG Kang <tg@egosys.net>, alsa-devel@lists.sourceforge.net
Subject: Re: [Fwd: ALSA request]
Date: Wed, 07 Jul 2004 18:18:37 -0400 [thread overview]
Message-ID: <40EC76BD.2070905@aei.ca> (raw)
In-Reply-To: <40EBDCC2.7040807@boosthardware.com>
Hi,
We appreciate your interest in supporting writing Linux drives for your
products. There are 2 ways to have your products supported:
1. Your company writes a driver following the ALSA driver specification
for the sound cards you are interested in supporting. Then the code of
the driver will become part of the ALSA drivers that are included in
every linux distribution automatically. This means that the source code
of the driver will become part of the ALSA project and can benefit for
further improvements by the open-source community.
2. Your company releases information on programming the chips of the
sound card to the ALSA developers (through the alsa-devel mailing list
for example) and the developers of ALSA take care of writing a driver
for you automatically. This means no work on your part other than
providing help to the developers with the datasheets of the chips,
specific interconnections between them and answering any questions that
arise. Again the code will become part of the ALSA project and will be
included in all future kernel releases.
In the case of your company I think the 2nd way will be the best as
there is already partial support for some Egosys based soundcards in
Linux and the developers that wrote those drivers can finish the gaps
with some more information from your part.
Apostolos
> Subject:
> ALSA request
> From:
> "TG Kang" <tg@egosys.net>
> Date:
> Wed, 7 Jul 2004 16:59:22 +0900
> To:
> <pshirkey@boosthardware.com>
>
> To:
> <pshirkey@boosthardware.com>
>
>
>
> Hi,
> My company, Ego Systems Inc., is beginning to consider making our
> products compatible to ALSA. So far, we haven't made much effort to
> put our products into the Linux world for some reasons.
> We produce soundcards and audio interfaces targeted to both
> professional and regular consumers. If you don't have much information
> on this company and its products, looking at www.esi-pro.com
> <http://www.esi-pro.com> will help.
> Now that the demand from inside and outside of this company arises, we
> are seriously willing to hook our products with linux/ALSA.
> I've read the 'Getting support for your hardware' section on ALSA
> website carefully, and got aware of what ALSA developers want from
> manufacturers.
>
> Now, please give us more detailed procedure we need to take.
> If you are not the proper contact point regarding this request, please
> forward it to a proper person.
>
> Personally, as one of the Linux 'freaks', I hope every Linux user can
> feel free to use our products.
>
> Best regards,
>
> /*
> *
> * Kang, Taegoo
> *
> * R&D dept. / Software Engineer
> * Ego Systems Inc.
> *
> * phone: +82-2-2164-9832
> *
> * www.esi-pro.com <http://www.esi-pro.com>
> *
> */
>
>
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-07-07 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 11:21 [Fwd: ALSA request] Patrick Shirkey
2004-07-07 11:55 ` James Courtier-Dutton
2004-07-07 19:39 ` Daniel Wagner
2004-07-07 22:18 ` Apostolos Dimitromanolakis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 15:22 Peter Zubaj
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=40EC76BD.2070905@aei.ca \
--to=apostolos@aei.ca \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tg@egosys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.