Re: [Owfs-developers] OWCAPI OW_put buffer

2014-02-21 Thread Robin Gilks
> >> >> I'm off to try loading 2.7p21 onto the router, if I can get it to cross >> compile OK... > > OK - 2.7p21 still has a problem on the router so I guess its an endianess > issue. The router I'm using, a TPLink WR-1043ND, uses the AR71XX series > SOC which is MIPS based. Back on 2.8p13 and us

Re: [Owfs-developers] OWCAPI OW_put buffer

2014-02-21 Thread Robin Gilks
> > I'm off to try loading 2.7p21 onto the router, if I can get it to cross > compile OK... OK - 2.7p21 still has a problem on the router so I guess its an endianess issue. The router I'm using, a TPLink WR-1043ND, uses the AR71XX series SOC which is MIPS based. As I said before, all the reads a

Re: [Owfs-developers] OWCAPI OW_put buffer

2014-02-21 Thread Robin Gilks
> On 02/20/2014 10:59 PM, Robin Gilks wrote: >> Greetings all >> >> I've just started to migrate from the public domain Dallas tools (that >> go >> way back to the DOS days as well as Linux) to OWFS and I'm a bit >> confused >> about the C API interface. >> >> I take it that the buffer in OW_put fo

Re: [Owfs-developers] OWCAPI OW_put buffer

2014-02-21 Thread Paul W Panish
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It uses the same value that would be returned by strlen(), which excludes the null termination. On 02/20/2014 10:59 PM, Robin Gilks wrote: > Greetings all > > I've just started to migrate from the public domain Dallas tools (that go > way back to th