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.
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. :-/
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
A continuing flow of paper is sufficient to continue the flow of paper.
-- Dyer
-------------------------------------------------------------------------
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
