All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pieter Palmers <pieter.palmers@student.kuleuven.ac.be>
To: "\"Z嶵ulon (by way of Z嶵ulon <>)\"" <zeb@zebulon.org.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Terratec Aureon Space
Date: Mon, 19 May 2003 21:29:23 +0200	[thread overview]
Message-ID: <3EC93093.1090003@student.kuleuven.ac.be> (raw)
In-Reply-To: 200305170831.13014.zeb@zebulon.org.uk

Ze'bulon (by way of Ze'bulon <>) wrote:

>>only if we get enough technical information...
>>
>>at least we need to know the wire connection between codec and ice1724
>>chips, especially 61, 62 and 63 pins of Wolfson chip and GPIO pins of
>>ice1724 chip.
>>    
>>
>
>Would it be possible to find it by analysing the circuits on the card itself
> ?
>  
>
Chances are that this is possible. I did it for the maxistudio isis.
You'll need a multimeter with a beep function and some common sense
knowledge of which connections are most likely.
Most PCI cards are 4 layer PCB's with power and ground distribution on
the inner layer. This means that the signal traces are on the outside of
the board, so you can use a magnifying glass to trace them. Using a
digital camera with proper lighting works even better. You make a
picture of the piece of board you want to analyze (of both sides of
course), with a good resolution. This gives you a more 'stable' view of
the traces.

Pieter




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

  parent reply	other threads:[~2003-05-19 19:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17  6:31 Terratec Aureon Space Zébulon
2003-05-19  9:23 ` Takashi Iwai
2003-05-19 19:29 ` Pieter Palmers [this message]
     [not found] <5.1.0.14.2.20030831014515.021b7850@192.168.10.1>
     [not found] ` <s5hfzjgrhiz.wl@alsa2.suse.de>
2003-09-06 10:22   ` Dennis van der Meer
2003-09-08  8:52     ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2003-08-31 10:04 Dennis van der Meer
2003-05-28 22:20 Dennis van der Meer
     [not found] ` <s5h65nnnrnx.wl@alsa2.suse.de>
     [not found]   ` <5.1.0.14.2.20030603193926.01638eb0@192.168.10.1>
     [not found]     ` <s5hk7c2m4h8.wl@alsa2.suse.de>
2003-06-04 17:56       ` Dennis van der Meer
2003-06-04 18:30         ` Takashi Iwai
2003-06-06 22:31           ` Dennis van der Meer
2003-05-15 16:26 Zébulon
2003-05-16  9:33 ` Takashi Iwai
2003-05-16 10:33   ` Liam Girdwood
2003-05-16 10:41     ` Takashi Iwai
2003-05-16 16:50       ` Zébulon

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=3EC93093.1090003@student.kuleuven.ac.be \
    --to=pieter.palmers@student.kuleuven.ac.be \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=zeb@zebulon.org.uk \
    /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.