From owner-freebsd-hardware Sun Feb 14 09:11:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14792 for freebsd-hardware-outgoing; Sun, 14 Feb 1999 09:11:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14772; Sun, 14 Feb 1999 09:11:10 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id MAA14227; Sun, 14 Feb 1999 12:11:09 -0500 (EST) Date: Sun, 14 Feb 1999 12:11:09 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Nicolas Souchu cc: hardware@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Aladdin chipset SMBus support available! In-Reply-To: <19990214155232.61732@breizh.prism.uvsq.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 14 Feb 1999, Nicolas Souchu wrote: > On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote: > > > >On Sun, 14 Feb 1999, Nicolas Souchu wrote: > > > >> On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote: > >> > > >> >On Sat, 13 Feb 1999, Nicolas Souchu wrote: > >> > > >> >> Example program to fetch temperature or voltages is available at > >> >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ > >> >> There's also an example program to fetch SDRAM info over the smbus. > >> > >> I attach you the detect.c program. It's very simple and may help us > >> in knowing what I2C hardware you have on your mobo. > > > >Where's my detect.c? I think you forgot to attach it :) > > :) here it is! alpm0: rev 0x00 on pci0.3.0 alsmb0: smbus0: on alsmb0 smb0: on smbus0 {"/home/green/examples"}$ ./detect a2 found. d2 found. > > > > >> >I tried them, and there's the problem: all the ioctl()s they perform return > >> >EINTR! Has this driver been tested on many motherboards? Why should I expect > >> >an EINTR? Just wondering :) > >> > >> EINTR is odd. It just mean that the device at the address requested on the > >> I2C bus do not respond. I have to translate SMBus errors to the appropriate > >> unix ones. > > > >Hmm... wouldn't the appropriate error for something not responding be an > >ENXIO or ETIMEDOUT? EINTR seems more than a little wrong for this purpouse. > > Fix committed. > > BTW, as outlined by -pkh all this is just a first step in a huge monitoring > adventure where all still need to be _defined_ (architecture and interfaces) > and implemented. Any proposition for doing the job is wellcome, > since I just have enough time to do the hardware SMBus support. Sounds like fun.... > > Nicholas > > -- > nsouch@teaser.fr / nsouch@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message