From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Lawnick Subject: Re: [lm-sensors] Use the Linux I2C subsystem for a two wire interface protocol Date: Wed, 15 Jul 2009 07:41:30 +0200 Message-ID: <4A5D6C0A.7030903@gmx.de> References: <528f13590907140925h7aa36452o60da32d3bf941241@mail.gmail.com> <4A5CB908.4060404@cam.ac.uk> <528f13590907141358w17869b6fq450bf223e4f54687@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <528f13590907141358w17869b6fq450bf223e4f54687-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: alfred steele Cc: Jonathan Cameron , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, LM Sensors List-Id: linux-i2c@vger.kernel.org alfred steele said the following: > To sum it up, the intention is code > reusablity in the sense that if we move to a different part which sits > on the I2c bus, we need not have to modify the kernel driver, just > keep the complexity in the userspace. I'd say this is just the wrong way round: Design goal should be to keep application as is and just load another driver on H/W change + changing access path in some config file. Just my 2 cents Michael From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Lawnick Date: Wed, 15 Jul 2009 05:41:30 +0000 Subject: Re: [lm-sensors] Use the Linux I2C subsystem for a two Message-Id: <4A5D6C0A.7030903@gmx.de> List-Id: References: <528f13590907140925h7aa36452o60da32d3bf941241@mail.gmail.com> <4A5CB908.4060404@cam.ac.uk> <528f13590907141358w17869b6fq450bf223e4f54687@mail.gmail.com> In-Reply-To: <528f13590907141358w17869b6fq450bf223e4f54687-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: alfred steele Cc: Jonathan Cameron , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, LM Sensors alfred steele said the following: > To sum it up, the intention is code > reusablity in the sense that if we move to a different part which sits > on the I2c bus, we need not have to modify the kernel driver, just > keep the complexity in the userspace. I'd say this is just the wrong way round: Design goal should be to keep application as is and just load another driver on H/W change + changing access path in some config file. Just my 2 cents Michael _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors