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
| ||
|
Date: Fri, 29 Aug 2014 22:56:39 +0200 From: Andreas Werner <wernerandy@....de> To: linux-kernel@...r.kernel.org Cc: andreas.werner@....de, wernerandy@....de Subject: eeprom Board Information EEPROM I have a question regarding a driver for a Board Information EEPROM. I want to give our customer easy access to our Board Information EEPROM which is an 256byte I2C eeprom. There is a defined structure of information at the beginning of the eeprom which includes board name, serialnumber, production date, repair date and a eeprom structure ident number. The rest of the eeprom is for user defined settings where customer can write any data to. I want to have access to the eeprom without any special to and without installing anything just running linux and to a cat/echo to sysfs entries to read/write data to the eeprom. What i want to do is to create sysfs entries for the pre defined settings and on entrie where customer can access the rest of the eeprom bytes. Is drivers/misc/eeprom the right place to put those kind of driver in? Or are there any other options to write those kind of driver? Regards Andy -- 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