Can you explain a little bit what you need?
Are you trying to add a non-1-wire device into owfs? To really fit in, it
should have a unique ID that is roughly compatible with 1-wire. Probably the
easiest would be to make a controller that looks like a small owserver, so
any owfs program can talk to it. That could be written in perl if you like.
It's an easy job, especially since the allowable queires are limited.
Paul Alfille
On Wed, Nov 19, 2008 at 5:42 AM, Stuart Poulton <[EMAIL PROTECTED]> wrote:
> I'm pretty sure this has been covered in the past. But here goes.
>
> I'd like to be able to include data from a non owfs source in owfs, can
> this be done ? Perhaps by the creation of a new device family ?
>
> I'm currently reading data from the device using perl, it's two simple
> parameters of current and temperature.
>
> Any thoughts and solutions great-fully received.
>
> Thanks
>
> Stuart
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
