[alsa-devel] ESI MAYA44 PCI datasheet request
oponek at gmail.com
Tue Aug 21 22:17:56 CEST 2007
I decided to send a changed letter (thank's for your comments) and if ESI
refuses to give the datasheet to all of the ALSA developers, we will start
to look for the best programmer. I changed the firmware demand and added
info about GPL license. Changed letter:
In reply to the letter sent 14.07.2007:
2007/8/14, ESI UK Support <uksupport at esi-audio.com>:
ESI do not provide and have no plans for Linux drivers for our products
ESI are happy to provide /share information to an Individual developer
within the Linux community
That is able and capable to develope drivers
and wishes to develope drivers
I would like to ask you to share the information about ESI MAYA44 PCI card
needed to write drivers on behalf of the ALSA development team. ALSA team
needs all the information that you give your programmers to create drivers
for the device. We would like to ask you for:
- a full datasheet containing IO port layout, register descriptions and
- source code for current windows drivers would be very helpful but isn't
- ESI MAYA44 PCI firmware (if needed) and the permission for the firmware to
be distributed with ALSA.
There are many peope that are willing to write the driver for MAYA44 and
because of the way Open-Source software and drivers are developed, in the
interest of it's quality, it is important that the information about the
card are accesable for all of the ALSA developers. We ask for your permision
to place that information on the ALSA server for developers. Thanks to that
any qualified person will have acces to it. Many other companies provided
that kind of information to us this way before:
I also would like to inform you that the driver that we hope to produce will
be open-sourced and licensed under the GNU GPL as the whole ALSA project.
I am sure that adding this card to the list of the suported cards under the
linux operating system will cause the number of satisfied ESI card users to
increase. Thank you for your co-operation.
2007/8/21, Ash Willis <ashwillis at programmer.net>:
> Hi Piotr,
> In general, I think this is good. Some points though...
> * I don't think you should demand firmware source. Asking for that
> might be seen as quite invasive. It might be a bonus to have, but
> I don't see anyone hacking on it. Their firmware works, It's a
> driver that we need. Does this card even use firmware? I guess...
> * Linking to a mirror probably isn't too smart if they think their
> infos are going to distributed all over the web. Sorry, that was
> my fault. I'm an idiot. I think the correct link should be
> * I would offer a fall back. I would propose that the approach you
> have mentioned is in their best interest however if they are
> unwilling to distribute the information freely, then the next best
> thing would be to find one developer that is able, willing and
> possesses the hardware. That's not ideal. I would prefer the second
> approach to no driver at all, as would you, I'm sure. However, I
> don't speak for anyone else when I say that.
> * I'm sure they know the ins and outs of open source but you should
> confirm with them the terms of this arrangement. NDAs are basically
> incompatible with this whole thing because, usually, releasing the
> source will breach the NDA. Make sure they know that the driver
> being produced is open source and licensed under the GNU GPL.
More information about the Alsa-devel