| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4A8491E3.4070907@gmail.com> Date: Fri, 14 Aug 2009 01:21:23 +0300 From: Kari Laine <klaine8@...il.com> To: linux-kernel@...r.kernel.org, klaine8@...il.com Subject: I2C -bus programming Dear List, this is my first post here and I am not sure if this is a suitable topic here. Anyway I have a Velleman K8000 IO-card and it uses I2C over parallel port to communicate. when I modprobe i2c-parport it does not complain. I tested without card connected and it complained so it seems to find the card. modprobe pcf8591 modprobe i2c-core modprobe i2c-dev I am not sure I am doing it right. Should i2c-core probed first ? anyway now I have /dev/i2c-0 /dev/i2c-1 Now I don't know whether these i2c-devices refer to this Velleman board or some other i2c-device which happen to be in the computer... If these devices probably refer to Velleman - then how I can refer different i2c-devices on the board. I am totally new to this i2c thing (reading spec at the moment but it does not help much with Linux). I would be very greatfull if some could point me the way - thanks. Best Regards Kari Laine -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists