Why not put the information that pertains to the individual adapters
under the system along with the adapters that it pertains to. This
would allow a person to keep the settings with the adapter that needs it
as well as add any other adapter specific settings as well.
Steve
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Alfille
Sent: Tuesday, October 16, 2007 7:30 AM
To: [email protected]
Subject: Re: [Owfs-developers] Overdrive and other per-bus
settings
Sorry, incomplete message.
-------------------------------------
I'm writing for design help.
Briefly there are some settings, like "overdrive" and some of
the "flex-time" parameters that pertain to individual adapters.
There are 2 alternatives:
1. List them only in the specific bus.n directory
2. List them in the main directory as "overdrive.0, overdrive.1,
...
We currently do the second way, sort of.
The current setup for root directories is:
devices (e.g. 10.67C6697351FF)
uncached
simultaneous
alarm
structure
settings
statistics
bus.0
bus.1
...
system
Now "uncached" is more of a flag.
"Simultaneous" and "alarm" are special directories generated by
device conditions.
"Structure" shows the framework of supported devices and their
properties and properties' properties. It is global.
"Settings" shows/sets time limits and temperature scale. Global
(we could have different timeouts for each adapter, but we don't
currently).
"Statistics" shows things such as read and write counts, bytes
transfered, error counts. Some is bus-specific (statistics/bus) and the
rest is global.
"System" has
adapter information (system/adapter)
process information (system/process)
compilation information (system/configuration)
connection information (system/connections)
All but "system/adapter" are global.
The wrinkle is that if one of the connections is to an owserver,
all this same structure (but different values) exists under bus.x for
that owserver. So there are two types of bus.x directories:
Local: regular adapters like USB, serial, i2c HA7Net
Remote: owserver
So we have 2 design choices, I think:
1. /system/adapter/name.0 name.1 ... overdrive.0 overdrive.1,
... (arrays for each bus)
bus.x/system exists only if bus.x is remote bus (Also
bus.x/statistics, structure, settings exists only for remote bus)
2. /system/adapter doesn't exists in the root directory. Only
/bus.x/system/adapter (or some better name)
i.e. adapter-specific information and settings has to be
specifically addressed via bus.x
for remote adapters, this might mean several levels
bus.x/bus.y/system/adapter
Currently we sort of do case 1, but repeat global information
under local bus, which is simply wrong.
Any thoughts?
Paul Alfille
-------------------------------------------------------------------------
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
