I agree with most of this. After discussing this with a friend, we
came to the conclusion that most uC implementations will support only
what is actually implemented in their ROM image, and little else, so
exposing all the functions is probably not helpful, but is still
possible if desired.
I've been thinking about this issue off and on for a couple years now,
and I like a large part of what I see so far, but also want to throw
in some thoughts.
After reading some details on the BAE chip as well as talking to some
embedded designers and thinking about applications, I envisioned
somet
On Wed, Feb 24, 2010 at 12:45 PM, Jerry Scharf <
sch...@lagunawayconsulting.com> wrote:
> I think we need to look into loadable drivers for OWserver/OWFS. [I can
> imagine smoke coming out of Paul's ears.] Once drivers become complex,
> this is the next step of being able to load, unload and updat
On 24 February 2010 17:31, wrote:
>> Give me some time and I'll work on a draft spec.
> Just confirming, you saw my mini spec at the end of that last email, right?
Yup and liked it a lot! :)
Take care,
Ben
--
Download
Hi,
I come from a different world, that of communications protocols, so I
have a different bias. I understand and agree with your desire to expose
as much as possible from a device designer's point of view. I am more
from the system designer side and want to have things be the most
consistent
> Give me some time and I'll work on a draft spec.
Just confirming, you saw my mini spec at the end of that last email, right?
-tmk
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed c
On 24 February 2010 09:15, wrote:
> For the casual reader, here is the short version:
> I propose:
> * memory-map based interface
> * pre-defined 'drivers' for different functionality
> * keep driver interfaces as close to uC hardware implementation as possible
> * drivers can and should be cross
Ah, ok I was not aware of that
How do you feel about the mini driver (per functionality) concept?
Owfs is probably already built in a somewhat similar manner for other
devices (temp. sensors perhaps)
-tmk
On Feb 24, 2010, at 3:28 AM, Paul Alfille
wrote:
On Wed, Feb 24, 2010 at 4:15 AM
On Wed, Feb 24, 2010 at 4:15 AM, wrote:
> OWFS typically presents all of the possible functions of a device in the
> directory for that device, eg take my DS2780: It has a high-sensitivity ADC
> which can be used to measure tiny voltages. Those tiny voltages can also be
> interpreted functionally
This is a long response with lots of technical stuff.
For the casual reader, here is the short version:
I propose:
* memory-map based interface
* pre-defined 'drivers' for different functionality
* keep driver interfaces as close to uC hardware implementation as possible
* drivers can and should b
Pascal,
Received my unit last week, just got it connected into my hub and by all
accounts worked just fine. On the weekend I will get it installed into a
case with the output FET's installed so I can play with the device with real
devices connected. Can't wait to get my hands on all those varia
11 matches
Mail list logo
