TIP: Click on subject to list as thread! ANSI
echo: rberrypi
to: ALL
from: R.WIESER
date: 2019-11-30 19:20:00
subject: Re: One I2C bus, two prog

druck,

> Normally for a device which requires reading and writng you would create a
> driver providing an API to clients, which would serialise access
> to the device.

That would be the second-optimal solution (the first one being that its done
by the OS itself).

Alas, thats not always possible.    Take for example an RTC.  When its
installed the OS might access it whenever it pleases, and at the same time
another program might be trying to set one of its alarms.   I don't think
I've got much control over when/how the OS does its thing, nor can I easily
put a gatekeeper inbetween the OS and the RTC ...

Next to that, such a driver providing an API to clients needs the
cooperation of the involved programs.   Including those written by other
hobbyists like myself.  Do you see the problem ?

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.