From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>, mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] via-cuda (CUDA_COMBINED_FORMAT_IIC)
Date: Wed, 30 Aug 2000 20:42:02 +0100 [thread overview]
Message-ID: <200008301941.UAA13718@hyperion.valhalla.net> (raw)
On Wed, Aug 30, 2000, Geert Uytterhoeven
> The generic i2c subsystem works (at least `used to work') on PPC as well. I
> once wrote an i2c `driver' (something that can read from and write to 2 signal
> lines, very very complex :-)
Well, today I wish I could get at SDA/SCL - because I think I would have a
working solution to my need (to read the TDA7433).
Maybe it's complex - or at least tedious - because of working within the OS
- but it is also specified by the i2c spec - so a solvable problem.
All the time on this patch has been spent second-guessing what the CUDA does
with its command packets... and at the end I still can't read the chip (lots
of info from the SPDs & other devices ;-)
CUDA is also on m68k? (I see some conditionals in the 2.4.0 stuff for
CONFIG_MAC)
I really would be very grateful if anyone has any more sources of info on
the command packets contents for it (CUDA)...
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-30 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 19:42 Iain Sandoe [this message]
2000-08-30 20:52 ` [PATCH] via-cuda (CUDA_COMBINED_FORMAT_IIC) David A. Gatwood
-- strict thread matches above, loose matches on Subject: below --
2000-08-30 21:03 Iain Sandoe
2000-08-30 9:37 Iain Sandoe
2000-08-30 8:37 Iain Sandoe
2000-08-30 9:22 ` Michel Lanners
2000-08-30 11:44 ` Geert Uytterhoeven
2000-08-29 23:53 Iain Sandoe
2000-08-30 5:59 ` Michel Lanners
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=200008301941.UAA13718@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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.