I did some investigation into this matter and came up with the following results:
- The w1 kernel module and OWFS are not compatible at this moment,
- Like you probably know, OWFS works with many hardware devices (1wire bridges from USB/I2C/Serial/TCP, etc) which outperform any bit banging solution,
- In the source code of OWFS (specially the owlib part) there is a whole rewrite of this w1 kernel module (based on the code from Evgeniy Polyakov, the w1 kernel module author), there is also an information page about this. But it looks like under construction/in development: OWFS w1 info. They also state that this module is accessed through a netlink connection (Busmaster table), and reports itself to OWFS using avahi. (check the source files in the owlib/src/c directory starting with ow_w1_*)
- The --w1 commandline parameter is used for many of the tools to tell the process to use the w1 kernel module, how you actually map GPIO pins to be used for the 1wire communication, I have no idea at this moment.
- Last but not least, on the OWFS Todo list there are entries for adding GPIO and the 'normal' w1 kernel module as you can see here: OWFS Todo
I do not have any 1wire stuff laying around to actually test if this 'rewrite' as mentioned in point 3 works. And specially how it should work, but on the info
page they talk about disabling the w1 kernel module or run OWFS as root so it can unload the w1 kernel module, but if this is already implemented and working I have no idea.
I hope this information gets you a little further, and please let us know some results.