Hi Rodolfo, I've changed the channel to a read only attribute. There is still a compiler warning. As soon as code compiles warnings-less, I'll post a patch here. Loading i2c devices out from dts-file is now working :-)! The advantage of register and bind clients by means of dts-file is, you can use the same kernel image for several boards with different i2c-circuits (also different flash, ram, ...). The device tree blob, the result of the compiled dts-file, a tree structure that describes the hardware, is also loadable onto target. I've got the patches for an old kernel version (2.6.28.) - should I post them anyway? Unfortunately, I can update the patches to an actual kernel version earliest mid of September. Christian -----Original Message----- From: giometti@xxxxxxxxxxxx [mailto:giometti@xxxxxxxxxxxx] Sent: Monday, August 24, 2009 10:02 AM To: Herzig, Christian Cc: linux-i2c@xxxxxxxxxxxxxxx; chris@xxxxxxxxxxx Subject: Re: [PATCH] i2c pca954x: support channel selection in sysfs. On Mon, Aug 17, 2009 at 10:10:08AM +0200, Herzig, Christian wrote: > The need of setting and getting the channel out of the shell is for > debugging use only. Ok, if everything works properly, this is an > unessential attribute. I thought, maybe someone else is also interested, > so I _tried_ to publish this patch to Linux-i2c. Another reason, why > I've published this patch is, getting feedback from Linux community - > what is good, what is amiss, how implementation is better... I see but I have to think about it. This code can lead to misfunctioning and during debugging you can use custom code which can be removed after bug fixes. > My plan is, loading adapters and devices on the basis of a flattened > device tree (Documentation/powerpc/booting-without-of.txt). At the time, > I don't know where to tackle this problem. Any hints for me? I'm not sure to understand what you mean... can you please explain it, maybe with some examples? Thanks, Rodolfo -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
