On Tue, 2005-02-22 at 12:38 +0100, Miklos Szeredi wrote:
> > Nope... 2.4.20 is missing alloc_inode and destroy_inode in
> > super_operations struct.
> OK, it's 2.4.21 then.
> > 2.4.20 is used in WRT54G routers and that's why I can't use the
> > latest cvs version.
> Now that I have brought one, so I should be motivated :) What is it
> exactly that you do with FUSE on a WRT54G?
How nice! I actually got mine from Paul Alfille who is the founder
of owfs which reads 1-wire sensors from different 1-wire interfaces.
The WRT54G router could easily be modified to get a serial port,
and from that port you connect all your 1-wire sensors.
If you look at this page you find more information about
hardware modifications and then my pre-compiled binaries
which includes fuse+owfs+rrdtool . You can then use your router
to create graphs of all temperature sensors for example.
There is a tar-file owfs_wrt54g-*.tar.gz which you can try
to upload to your router. Follow the instructions and your
router will create graphs of all sensors... (but the graphs
will be empty until you connect a 1-wire adapter to your router)
> > Do you think it would be possible to add some workaround
> > for this in the cvs-version?
> It's possible, but as I said earlier I have doubts, as to whether it's
> worth the effort. Is there a reason why you need to use the latest
> FUSE version?
Since I have another embedded system with a Coldfire processor
(which use uClinux-2.4.27-uc0), I have tried to keep owfs compatible
to all fuse versions.
It would be much easier for me if latest version of fuse would
work on all platforms.... I can live with using fuse-1.4 on
the WRT54G router, but I'm much into using the latest versions
all the time. It seems that fuse-1.4 lock the kernel module
of owfs crash (which happens during development), and then I have
to reboot the router to get rid of the loaded module.
I hope that you could accept this as a reason, and I hope you
enjoy the idea of using owfs and fuse in your router too... :)