From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Christof Petig <christof@petig-baender.de>,
Conrad H Ziesler <cziesler@umich.edu>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: ibook sound, limping mixer
Date: Wed, 10 Jan 2001 14:29:47 +0000 [thread overview]
Message-ID: <20010110143207.0568BDB9FD@atlas.valhalla.net> (raw)
on Wed, Jan 10, 2001, Christof Petig wrote:
> Conrad H Ziesler wrote:
>> in case this is of any use to anyone:
> Yes, I'm very interested. Since I actually started looking into the
> specs and sources, but did not find the time to start coding the same.
so am I (of course). I've taken a copy over to my devl area - and I will
figure out how to include it into the next stage of dmasound devl soon.
>> since the dac3550a has write-only i2c registers, its pretty hard to debug
>> the i2c interface. probably if someone puts an oscilloscope probe on the
>> i2c bus signals it should all become clear.
>>
> I would recommend a logic analyzer or better an i2c analyzer. I have an
> oscilloscope but I would not dare to try reading i2c signals by hand.
well, I have a storage scope (which would possibly do it) [I don't run to a
logic analyser]
- but more fundamental problem - no iBook - if someone in the UK (unless
someone from elsewhere is prepared to ship one) wants to lend one - I'll see
what I can do... it's not a machine I can justify buying at the moment.
[my test set is G3/Beige, Lombard, 9600/233, and, when I get the disk
re-partitioned G4/500].
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-10 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 14:29 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 8:48 ibook sound, limping mixer Christof Petig
2001-01-09 21:29 Conrad H Ziesler
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=20010110143207.0568BDB9FD@atlas.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=christof@petig-baender.de \
--cc=cziesler@umich.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).