Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 May 2010 21:16:53 +0200
From:      Rafal Jaworowski <raj@semihalf.com>
To:        Andreas Tobler <andreast-list@fgznet.ch>
Cc:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: iic/i2c debugging on PowerMac
Message-ID:  <C2885CB4-252F-4354-8BF3-3865C5CCD63E@semihalf.com>
In-Reply-To: <4BF58342.7010707@fgznet.ch>
References:  <4BF58342.7010707@fgznet.ch>

next in thread | previous in thread | raw e-mail | index | archive | help

On 2010-05-20, at 20:45, Andreas Tobler wrote:

> Hi,
>=20
> I'm trying to access (read/write) an i2c device on my G5. The problem =
is, I do not know the right i2c address although I have it from the =
device-tree, it's 0x15e.
>=20
> I read about the i2c utilitiy which requires the iic driver compiled =
into the kernel. Done that and it seems it is there:
>=20
> unin0
>    iichb0 pnpinfo name=3Di2c compat=3Dkeywest-i2c
>      iicbus0
>        iic0 at addr=3D0
>        fcu0 pnpinfo name=3Dfan compat=3Dfcu at addr=3D0x15e
>=20
> But I do not have this device entry in /dev. Trying to create one does =
not work.
> mknod /dev/iic0 c 103 0
> mknod: /dev/iic0: No such file or directory
>=20
> This is a netboot environment, might this be the cause of not being =
able to create the device?
> Or do I have another issue?

This shouldn't be related to the boot method.

Do you see any failure output during iic attach (there should be a diag =
error)? If not try to intstrument the iic_probe() routine and see what =
happens.

Rafal




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C2885CB4-252F-4354-8BF3-3865C5CCD63E>