linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: iain@sandoe.co.uk
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] via-cuda (CUDA_COMBINED_FORMAT_IIC)
Date: Wed, 30 Aug 2000 07:59:37 +0200 (CEST)	[thread overview]
Message-ID: <200008300559.HAA00748@piglet.grunz.lu> (raw)
In-Reply-To: <200008292353.AAA19158@hyperion.valhalla.net>


Hi Iain,

On  30 Aug, this message from Iain Sandoe echoed through cyberspace:
> Unfortunately, the one chip I *really* want to probe (the TDA7433 on the
> audio card -  i2c address 0x8a) doesn't seem to give a proper response... so
> if anyone knows more about this - I'd be interested.

Hmm, are you sure it is actually attached to the CUDA's I2C bus? The
7x00/8x00 series have a video input chip on an I2C bus as well, but not
on CUDA... it's on PlanB, which includes its own I2C implementation. I
don't know about the sound chips in those boxes, however. My first bet
would be looking around AWACS if there is no I2C bus hidden there
somewhere.

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-30  5:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 23:53 [PATCH] via-cuda (CUDA_COMBINED_FORMAT_IIC) Iain Sandoe
2000-08-30  5:59 ` Michel Lanners [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-30  8:37 Iain Sandoe
2000-08-30  9:22 ` Michel Lanners
2000-08-30 11:44   ` Geert Uytterhoeven
2000-08-30  9:37 Iain Sandoe
2000-08-30 19:42 Iain Sandoe
2000-08-30 20:52 ` David A. Gatwood
2000-08-30 21:03 Iain Sandoe

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=200008300559.HAA00748@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=iain@sandoe.co.uk \
    --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).