Date: Fri, 02 Mar 2007 11:22:46 -0700 (MST) From: Warner Losh <imp@bsdimp.com> To: gurney_j@resnet.uoregon.edu Cc: freebsd-arm@freebsd.org Subject: Re: IIC support? Message-ID: <20070302.112246.21920579.imp@bsdimp.com> In-Reply-To: <20070302175913.GQ73385@funkthat.com> References: <45E83CAB.1090005@bulinfo.net> <20070302175913.GQ73385@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Krassimir Slavchev wrote this message on Fri, Mar 02, 2007 at 17:03 +0200: > > I have problems to access the iic eeprom from userland. Even after set > > SCAN_IICBUS in iicbus.c nothing has been detected. I have made some > > tests from the bootloader to read/write from/to the eeprom and they work. > > Is there any known problems with TWI or any differences between board > > settings? > > You can load the iic driver, and attempt to access the device through > iic's ioctl interface... As Warner mentioned, iic isn't really self > enumerating, so it requires you to privde the address of the device > that you are accessing... HEre's what I ahve at work: # ID Eeprom hint.icee.0.at="iicbus0" hint.icee.0.addr=0x80 hint.icee.0.type=8 hint.icee.0.size=2048 hint.icee.0.rd_sz=256 hint.icee.0.wr_sz=16 # Config Eeprom hint.icee.1.at="iicbus0" hint.icee.1.addr=0xa6 hint.icee.1.type=16 hint.icee.1.size=32768 hint.icee.1.rd_sz=256 hint.icee.1.wr_sz=16
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070302.112246.21920579.imp>