All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug <nostar@comcast.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: EZ8 ADAT I/O card (ICE1712 chipset)
Date: Thu, 05 Feb 2004 03:50:30 -0500	[thread overview]
Message-ID: <402203D6.3030308@comcast.net> (raw)
In-Reply-To: <401A62AD.2050302@comcast.net>

Here is what I have done to the ice1712.c file in order to add support 
for my EZ8 card.  It's a temporary hack (emphesis on 'hack') until I add 
code to reliably identify the ez8 from the hoontech (both cards share 
the same subvendorid).

/* EZ8 Hack */
int ez8=0;
MODULE_PARM(ez8, "i");

I added this at the end of all ofthe MODULE_PARM() definitions.

On line 2505, I made this change:

for (tbl = card_tables+(ez8 ? 1 : 0); *tbl; tbl++) { /* EZ8 Hack */

Just a quick and dirty way to skip over the hoontech card_table entry so 
that my EZ8 is recognized as a generic device, while still correctly 
detecting my Delta 1010LT card when ez8=1 is added as argument to the 
snd-ice1712 module.  Module functions normally if ez8 is not added to 
command line (or is set to 0).  This would not work if an ez8 and 
hoontech were used together.

This, of course, is only a temporary fix for my own use, while I work on 
code to correctly differentiate between the ez8 and the hoontech card. 
In addition, there are a few EZ8 specific features that don't seem to be 
implemented with the generic driver.  Since ADAT is fully functional, 
though, I now will spend much more time using the card/driver (with 
ardour/jack) and less finishing support.  I don't think there will be 
any objection here, since I think I am the only linux using EZ8/EZBus 
owner on the planet :)

Does anyone have the ICE1712 chip documentation?  How were the drivers 
for the other ice1712 based cards written?  Were the manufacturers 
contacted and data released under some sort of non-disclosure agreement? 
   I dont get why documentation for a chip is kept so secretive, I mean 
rtl8xxx ethernet tranceiver chip docs, for example, are all over the 
place, that seems like the same thing to me.  I would really like to 
have the documetation so that I can study the ice1712 driver line by 
line and understand what exactly is being done on-board the chip.  I 
just like that kind of stuff, I know there is enough info in the 
existing source for the other cards to figure out how to implement my needs.

-- 
http://nostar.isa-geek.com/



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-02-05  8:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 13:57 EZ8 ADAT I/O card (ICE1712 chipset) Doug
2004-02-05  8:50 ` Doug [this message]
2004-02-05 11:41   ` Takashi Iwai
2004-02-05 20:41     ` Doug
2004-04-01  4:05     ` Doug McLain
2004-04-09 17:59       ` Doug McLain
2004-04-13 10:01         ` Takashi Iwai
2004-04-13 15:54           ` Takashi Iwai
2004-04-14  2:21             ` Doug McLain
  -- strict thread matches above, loose matches on Subject: below --
2004-01-30  9:05 Doug

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=402203D6.3030308@comcast.net \
    --to=nostar@comcast.net \
    --cc=alsa-devel@lists.sourceforge.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.