Am 12.06.2014 09:55, schrieb Linus Walleij:

On Wed, Jun 4, 2014 at 8:09 AM, Michael Lawnick [off-list ref] wrote:

quoted

Am 03.06.2014 13:18, schrieb Linus Walleij:

quoted

On Mon, Jun 2, 2014 at 4:29 PM, Michael Lawnick [off-list ref] wrote:

quoted

Am 02.06.2014 14:16, schrieb Linus Walleij:

quoted

quoted

Is this really so useful on embedded systems?

I was under the impression that this method was something used
on say PC desktops with temperature monitors and EEPROMs
on some I2C link on the PCB, usage entirely optional and fun
for userspace hacks.

We use it for dynamic instantiating whole subsystems with multiplexers,
sensors, controllers in an embedded system. The device list is taken from
an
I2C eeprom which gets read on hotplug.

Does this mean that you have stored the names (strings) that are used
by the Linux kernel for identifying the devices into your EEPROM?

That means that you have made the kernel-internal device driver names
an ABI which is unfortunate :-/

This is one of the reasons to why we insist on device tree: OS neutral
hardware description.

The eeprom contains a device tree that is dynamically merged.

That is a kind of way of saying "yes we made the kernel-internal
driver named an ABI" I guess?

Sorry, I fear I don't get you. Could you please rephrase?
Of course it might be that I'm missing some fundamental idea of device 
tree. The mechanism we use started with K2.6 where device tree usage on 
MIPS wasn't that intensive. Anyway the original idea of removing 
i2c_table now moved towards non-mandatory usage.

-- 
KR
Michael