On Mon, May 4, 2015 at 6:39 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > The generic_buffer.c > test app (now under tools/iio) should do the job for testing > this. The purpose of that one is to act as an example > of the chardev (buffered) interface and as documentation > as the docs always got out of date when we kept them seperately. > (yeah I'm lazy). Aha and that test app like iio_event_monitor needs proper device creation in /dev/iio:device0 etc ... And then I notice that busybox' mdev doesn't really auto-create devices for anything else than what appears below /sys/class/*, /sys/bus/* is not scanned for device, yippie-ay. I guess you have udev for creating your devices on test systems and a full distro-type userspace? I wonder how people solve this for IIO on stripped-down systems, static devices? Is mdev even doing the right thing by just looking under /sys/class? I'm so confused by this, sorry Jonathan just airing some frustration :/ Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
