Jan,

> I just hope he does not design for space or airplanes or something like
> that 'unlikely to happen' (bus conflict), for me rules Murphy's law:
> If it can happen it will.

Really ?  Is that so ?

So, how do you protect both the Pi as well as th I2C modules you connect to
it against mishaps like I already described (miswiring, voltage
differences - and I'm sure there are more) ?

Or do you think that that is way more unlikely than a glitch ?    For the
record, I don't.   Especially not as both the Pi and the attached modules
are there to experimenting with.  Murphy's law indeed.

> Same for 2 programs using the same i2c hardware nd semaphore
> communication, if one fails (could be user exit, crash, whatever)
> while it has the 'i2c in use flag' set, then the other will also fail,
> wait
> forever, do nothing.

Ah, the old "I'm are not going to answer the person who asked it, but use it
to impress someone who already agrees with me instead".   Great going kid.
A bit obvious though.

But I wonder how different OSes deal with .... I dunno, multiple programs
trying to access the internet, and not geting in a deadlock.

I mean, if deadlocks are as easy to get into as you try to make it sound
than I should have had one even just in the last month, if not week.  But
for some reason I can't seem to remember one, not even for the last year
(or ever actually) ...  How is that possible ? Can you explain ?

And if you can, why isn't the same approach not usable for an I2C device ?

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05