Thread: Commands on EEPROM
View Single Post
kimmoli's Avatar
kimmoli is offline kimmoli
2014-02-04 , 20:01
Posts: 562 | Thanked: 2,744 times | Joined on Dec 2013 @ Espoo, Finland
#16
Originally Posted by kjokinie View Post
Idea there was to have some pre-defined key-value pairs to initiate actions inside kernel and tohd. Simple exaple would be vdd=1, meaning "enable the VDD". Or have some other string for i2c device parameters that the toh-core driver would register onto the bus then (so that corresponding driver would automatically probe).
at dayjob, we use something like this to set additional Linux environment variables from external configuration memory.

Originally Posted by kjokinie View Post
The user data was meant for any application running in userspace to just read and do anything they need to according to that.
Is the UDATA somewhere accessible, could not find that the driver makes it visible in sysfs?

And atm to get the automatic rpm download/install, the NFC is the only way?

Originally Posted by kjokinie View Post
I'm very interested to see what kind of uses you guys come up with it.

I will anyway have a eeprom on my TOHs, maybe use to store some TOH identity or TOH dependent configurations, e.g. if oled toh would have different settings (brightness/font etc) this is stores on eeprom. or serial number, hw version information, sensor calibration data.
__________________
TOH ideas, concepts and creations since 2013 toholed tohuart toheink Heebo tohIRi i2ctool tohmm LeTOH FMTOH
 

The Following 2 Users Say Thank You to kimmoli For This Useful Post: