Am 10.11.2016 um 09:09 schrieb Waldek:
> Hi,
>
> I have use w1-gpio-custom module to get access to DS18B20. I have load
> w1-gpio-custom with parameter
>
> w1-gpio-custom bus0=0,2,0
>
> the command of lsmod result
> w1_gpio 1424 0
> w1_gpio_custom 864 0
> w1_therm 2064 0
>
> and I can find my DS18B20 in /sys/bus/w1/ ...
>
This is independent of the netlink socket. But good to know it's not a
wiring problem or anything else on Onewire side.
> but OWFS 3.1p4 have still problem to see tree DS18B20
>
owfs can only see what the kernel's w1 driver delivers through the
netlink socket.
I can look into it and check with some kernels but this will take a
while as I'm pretty busy with my everyday work right now. It would help
very much if you could check the different kernels yourself. I know
linux-3.10.28 to work and others got it to work with the kernel
delivered with Raspbian Jessie and owfs-3.1p4.
You don't have to try all those kernels on the OpenWrt box but maybe you
could check what has changed in
[linux-kernel]/drivers/w1/w1_netlink.c
There was a known change at linux-3.16rc1 which broke owfs versions
before 3.1p1. But maybe there's another change which breaks it again
with the single kernel version you unfortunately have.
Kind regards
Jan
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
