Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-23 Thread Martin Rapavy
I agree, it would make much more sense to fork your implementation of ds1wm. Could you estimate how long would it take you? I'm quite in a hurry with my project. Or could you perhaps answer the question how OWFS handles updates on that master structures. I suppose this will be essential to exten

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-23 Thread Paul Alfille
I'm working on the ds1wm support. Just got example code from Maxim. How about basing you modifications from that. Paul On Feb 23, 2015 10:46 AM, "Martin Rapavy" wrote: > Hello Paul, > > > > so far I came to following conclusions about the parts of owlib which need > to be extended in order to s

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-23 Thread Martin Rapavy
Hello Paul, so far I came to following conclusions about the parts of owlib which need to be extended in order to support new bus master type: ยท Write new module (.c file) which exports a detect function (K1WM_detect in my case) o I suppose this is the configuration/connection func

Re: [Owfs-developers] OWFS on Raspberry Pi

2015-02-23 Thread Jaroslav SOBOTA
I guess I should have been more specific, sorry for that. On Raspberry Pi everything works OK with I2C to 1-Wire chips (e.g. DS2482), the problem is only with the w1 kernel module when the DS18B20 thermometer is connected directly to the GPIO pins of Raspberry Pi. It is possible to read tempera

Re: [Owfs-developers] OWFS on Raspberry Pi

2015-02-23 Thread Colin Reese
I was unaware of the aliases you mentioned, but included with those I know already: i2c=i2c_arm=i2c1 i2c_vc=i2c0 Thus, including dtparam=i2c and dtparam=i2c_arm or dtparam=i2c1 is redundant, as are dtparam=i2c_vc and dtparam=i2c0. NB, be careful with i2c0. It's really only there to service the

Re: [Owfs-developers] OWFS on Raspberry Pi

2015-02-23 Thread Mick Sulley
Yes this is related to device tree, I hit it a few weeks back with a new install. After a lot of digging around I got an answer on the Pi forum, things have changed and you now need to add dtparam=i2c1=on dtparam=i2c0=on to the end of /boot/config.txt for details see http://www.raspberrypi.or

Re: [Owfs-developers] OWFS on Raspberry Pi

2015-02-23 Thread Colin Reese
I should have looked first. These are w1 driver/owfs issues which I have no knowledge of. I CAN confirm that owfs works great on RPi2 with an i2c master, as I mentioned. C On 2/23/2015 12:37 AM, Jaroslav SOBOTA wrote: > Hi everybody, > I have problems getting OWFS running on Raspberry Pi and ac

Re: [Owfs-developers] OWFS on Raspberry Pi

2015-02-23 Thread Colin Reese
I'm running 2.9p5 on with RPi2, DS2483, DS18B20s with no complications. The only trick is getting the i2c bus up and recognized, but that's just a matter of putting 'dtparam=i2c=on' in /boot/config.txt (and rebooting on change). They switched from blacklist alone to using device tree to selecti

[Owfs-developers] OWFS on Raspberry Pi

2015-02-23 Thread Jaroslav SOBOTA
Hi everybody, I have problems getting OWFS running on Raspberry Pi and according to the Raspberry Pi forums I'm not alone. It seems that the problems occurred after Raspbian switched to device tree but I'm no Linux expert. Can you please have a look at the following posts? Any help would be wel