Am Mittwoch, 1. August 2007 14:41 schrieb Matthias Urlichs:
> Hi,
>
> Jan Kandziora:
> > I specifically think of onewire chips built into laptop batteries. As
> > soon a user encounters such a device, wants to monitor it through the
> > usual kernel hardware monitoring interfaces *and* connects some devices
> > to the laptop through owfs (e.g. servicing my vending machine), he will
> > run into a "deadlock".
>
> A conflict would exist only if those are connected through the same
> interface.
>
> I think that's exceedingly unlikely. A laptop battery's monitor would be
> connected via I²C, I'd assume. There's no reason at all to sacrifice an
> internal USB port plus pay for an expensive USB->1wire adapter.
>
No, but the problem exists for the i2c<->1w bridge as well. And that chip is
cheap enough.
> I also assume that nobody who's remotely sane would add put an externally-
> accessible I²C or 1wire interface into their laptop … and even if so,
> using the same wire that's carrying the battery monitor data would be
> deadly. :-/
>
Ok, you have a point here. USB<->remote 1W is the most likely configuration.
Kind regards
Jan
--
DOS: n., A small annoying boot virus that causes random spontaneous
system crashes, usually just before saving a massive project.
Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
