From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 3 Sep 2010 20:11:11 -0400 To: 9p-st@imu.li, 9fans@9fans.net Message-ID: <7d86ad3ab98383f438bc9498f3c56619@brasstown.quanstro.net> In-Reply-To: <257739.47cbc5b4.ijDr.mx@tumtum.plumbweb.net> References: <257739.47cbc5b4.ijDr.mx@tumtum.plumbweb.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] kw IC Topicbox-Message-UUID: 4ec8b8b0-ead6-11e9-9d60-3106f5b1d025 On Fri Sep 3 19:09:18 EDT 2010, 9p-st@imu.li wrote: > I'm working on a audio driver for kw (openrd) as a warmup for other more > useful drivers (do something easy before something hard), and I've come > to the point where to do anything more requires talking to the audio > codec. According to various linux patches, this is done over I²C. Has > anyone done anything with I²C, is it used for anything else? The kirkwood > functional specification does not mention it (at least so far as I can > see in the copy I have). Elseways I'll scrounge around some more. > if i read the marvell specification correctly, it uses i²s, not i²c. wikipedia has a pointer to the phillips specification. the main thing they have in common is that they both pass at least one of ron's "how to tell if a specification sucks" tests. :-) - erik