From: Alison Chaiken <[email protected]> [email protected] writes: > happy New Year for all,
>From me as well! > Why you are using readdir() and recursive_action()? recursive_action does it > for you. Because the function didn't produce the desired result without it, ahem. What I have in the back of my mind is that some boards have more than one I2C controller chip. Some will have one controller chip on SOC and one on the motherboard. How must the function be implemented to support that case? Unfortunately, I have only targets with one I2C controller on-SOC with which to perform tests. >Can you give an example of "nextfile" ? /sys/bus/i2c/drivers contains the following directories: dummy egalax_ts ov5642 sgtl5000 A simple recursive_action without explicitly opening these directories produces no results. Probably there is a way to invoke it so that the readdir isn't needed, but I didn't discover it. Assuming that there is such such a way, I wonder if it would cover the multi-controller case? I need to study the I2C driver to learn how sysfs is laid out in that situation. >you can not free fileName, GCC message: >warning: attempt to free a non-heap object [-Wfree-nonheap-object] Thanks, Souf: my toolchain produced a much more obscure error message whose meaning I could not discern. Best wishes, Alison Alison Chaiken (1): I2C bus fake enumeration applet lsi2c util-linux/lsi2c.c | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 util-linux/lsi2c.c -- 1.8.5.2 _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
