From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 19 09:01:07 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E7EE16A4CF for ; Wed, 19 Jan 2005 09:01:07 +0000 (GMT) Received: from home.dino.sk (home.dino.sk [213.215.74.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D9B143D54 for ; Wed, 19 Jan 2005 09:01:05 +0000 (GMT) (envelope-from bsd@dino.sk) Received: from [127.0.0.1] ([127.0.0.1]) by home.dino.sk with esmtp; Wed, 19 Jan 2005 10:00:59 +0100 id 0000E90D.41EE21CB.00004828 From: Milan Obuch To: freebsd-hackers@freebsd.org Date: Wed, 19 Jan 2005 10:00:51 +0100 User-Agent: KMail/1.6.2 References: <200501141015.37516.bsd@dino.sk> <200501171314.31179.bsd@dino.sk> <20050119004340.GT19624@funkthat.com> In-Reply-To: <20050119004340.GT19624@funkthat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501191000.51574.bsd@dino.sk> Subject: Re: Geode integrated peripherals support? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 09:01:07 -0000 On Wednesday 19 January 2005 01:43, John-Mark Gurney wrote: > Milan Obuch wrote this message on Mon, Jan 17, 2005 at 13:14 +0100: > > On Monday 17 January 2005 12:55, Bruce M Simpson wrote: > > > On Sun, Jan 16, 2005 at 03:01:17PM +0100, Milan Obuch wrote: > > > > ACCESS.bus support (i2c bus compatible) and LPC bus bridge (for > > > > expansion). The first one is present in OpenBSD. I am currently > > > > studying that and FreeBSD kernel sources to try port it, however, any > > > > help would be great. No idea on LPC, through... > > > > > > There's some i2c support in FreeBSD already, whether or not this > > > applies to the i2c hardware in the Geode I don't know. iic(4) would be > > > a good place to start. > > > > I think so. However, I built kernel with device iic, iicbus, iicbb, but > > nothing shows. As said, I am doing my 'homework' now - astudying sources, > > but, as usual, any help appreciated. > > Well, as having used the i2c code, I know it works... You probably > need to look at the hardware spec, and figure out if you need to write > a iicbb device driver (one that directly controls the SCL/SDA lines), or > a higher level one, that has hardware that can issue i2c reads and wrights > directly... > > I recently d/l'd the ACCESS.bus spec myself, since I have a firewire/usb2.0 > card that says it's an ACCESS.bus card, but not quite (the subrev is > wrong for access.bus), and didn't realize that ACCESS.bus was so close > to i2c.. There might need to be a layer written on top of i2c to make > it appear as an access.bus and do access.bus type things.. Great, could we cooperate? I know there are two modes - bit banging software i2c bus and real hardware controller. Which one would be easier to begin with? With geode, both are possible. Pins designed for ACCESS.bus (at least the second, there are two buses integrated) can be used as GPIO pins. Actually the first thing I need to get working is simple LM75 sensor reading, which is just i2c device, so nothing else (higher level access.bus layer) is necessary for me. Regards, Milan