Looping in busybox people.
On Tue, May 5, 2015 at 2:22 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
> 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 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?
Typically the following patch to mdev.c makes the devices
appear:
recursive_action("/sys/class",
ACTION_RECURSE | ACTION_FOLLOWLINKS,
fileAction, dirAction, temp, 0);
+ recursive_action("/sys/bus/iio",
+ ACTION_RECURSE | ACTION_FOLLOWLINKS,
+ fileAction, dirAction, temp, 0);
That is not just a little bit annoying. Who is doing the wrong thing?
* Busybox does the wrong thing by just inspecting
/sys/class for coldplug mdev -s
* IIO does the wrong thing by not registering a class
device (I think Greg said he doesn't like these...)
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
