Re: [RFC][2.6] Additional i2c adapter flags for i2c client isolation

From: Greg KH
Date: Wed Mar 17 2004 - 19:01:32 EST


On Wed, Mar 17, 2004 at 09:05:04PM +0100, Jean Delvare wrote:
> > > How would we export the value though? Numerical, with user-space
> > > headers to be included by user-space applications? Or converted to
> > > some explicit text strings so that no headers are needed?
> >
> > A text string would be simple enough to use.
>
> I'm not sure. What about a chip driver that would belong to more than
> one class? What about the eeprom driver which will belong to all
> classes? With a numeric value, a simple binary operation handles all
> the cases. With text strings we would end having to parse a possibly
> multi-valued string, and do string comparisons, with at least one
> exception to handle. This is likely to require much more resources,
> don't you think?

Ok, I wasn't really awake when writing that, you are correct. Other
devices export "values" that have to be looked up in tables in userspace
(think device ids). We can just export a hex number that matches the
ones in i2c.h

Anyone want to write a patch? :)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/