Pascal Baerten <pascal.baerten <at> gmail.com> writes: > Hi Greg, > > I just verified on my setup and you right. You pointed out a problem that you have should have appeared only recently. > only bus.0 listing is showed other are empty! (only /bus.n/interface is shown) > However, my scripts that address slaves on different buses are still working with no problems. but they are addressed explicitely. > I verified the issue with owdir, owhttpd and owfs (fuse mounted fs) > > > > I'm pretty sure this worked before 2.8p0. > > If needed, I could provide debug output later this week... > > Pascal > > > > 2010/9/5 Greg Cusick <gregcusick <at> hotmail.com> > Hi everyone, > It'd be appreciated if anyone could offer any suggestions regarding my problem > below. > I have built up a DS2482-800 bus master, and everything is running fine with > owfs, but only on bus 0. I have i2c-parport loaded, and owserver. I can see > the > device or devices I place on the chip IO0 line (with meaningful data being > returned), but no devices is detected on any of the others. I've swapped end > devices around, so I know it's not them. > My logic probe tells me there is no attempt to drive the other bus lines low > at > all, so it would appear the filesystem is not scanning the other bus lines. > Are there magic gems I'm missing here ? > Many thanks - Greg
(snip) Hi Pascal, Many thanks for your update. Yes, I can also address the devices explicitly, so now I can make things work ok. I had a look on SF for a means to log a bug report, but can't find anything. I too can provide debug info if required. Cheers - Greg. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
