Sense of self awareness? :)

[Tuc at T-B-O-H.NET]

Hi,

	I'm not "able" per se. I'll put it in as a ticket and see if the
powers to be accept it. I've actually turned my attention to something
else I'd RATHER have instead though... The "Accounting-On/Off" patches.
I think thats a better solution to the problem they are running into.

	As for the ENDIAN/ARM/XSCALE issue.... Thats beyond my knowledge,
I'm just cutting/pasting the reason I was given by the DD-WRT author. If
its untrue, I have no problem going back and saying "Its fixed, take another
look, and PLEASE get it in there for the next release". Unfortuantely,
thats also where my capabilities end. I'm not a committer, so I don't have
the authority to do it, just beg/plead. If someone wants to help campaign
it to the author, I'll be happy to offlist give an email contact address.

	For the umpteenth time, I'm not on old school Chilli because I 
want to. My hands are tied. Short of buying the WISP thats doing this, I
don't own it yet so don't have any authority to do anything except give
my opinion and suggestions. I would like almost nothing more (I'd like
only 1 thing more than this, but I can't mention it on list) than to be
using Coova on DD-WRT!!!!!!!!

		Tuc
> 
> If you are more able to patch chillispot in dd-wrt, then just  
> consider coova-chilli a really big chillispot patch (which it is). I  
> personally haven't compiled it on xscale, but I don't know what you  
> mean by it not being arm/xscale ready. I assume you mean that there  
> is a byte order issue somewhere -- which there was, actually, in the  
> original chillispot, fixed by OpenWrt for the FONera. This patch is  
> not in CoovaChilli only because I did the same fix differently. If  
> there are other endian issues that I am unaware of, well, it would be  
> nice if someone made them known instead of spreading mis-information.
> 
> Perhaps you will find better hotspot centric community support here  
> -- using CoovaChilli/AP :)
> 
> On May 16, 2008, at 6:29 AM, Tuc at T-B-O-H.NET wrote:
> 
> >>
> >>> 	Kewl, exactly what I need. Maybe I can see what it took to  
> >>> accomplish
> >>> this can get it patched into the old server for use. Or, I'll find
> >>> its just
> >>> way too much and have to find other means of accomplishing my
> >>> goals. But now
> >>> I have direction.
> >>
> >> I don't think taking patches back to chillispot is that great of an
> >> idea. CoovaChilli has _many_ fixes and new features that make it
> >> worth the switch. I wonder that the point is in keeping chillispot
> >> limping along with band-aids.
> >>
> > 	I agree its not a great idea. Its worse than chicken wire and
> > bubble gum in my opinion. But bringing Coova over to DD-WRT isn't  
> > happening
> > because as the author has stated "right now coova is not big endian  
> > and
> > arm/xscale safe". I'm limited in what I can do with presenting  
> > something
> > to the person running the network. If it can't be supported by the  
> > DD-WRT
> > community through a general distribution release, then its  
> > unacceptable.
> > That means, instead of allowing me to add a small script that would  
> > backup
> > the config of the appliance, as well as restore it during a "I've  
> > been reset
> > to default" reboot, he rolls a truck when a unit loses all the  
> > configuration.
> > Is there someone who rolled a version with this in it? Yes. Is it  
> > default in
> > the DD-WRT images? No. So, it doesn't happen. I have my hands tied.  
> > This is
> > the same people rather suffer a 6 hour outage due to equipment  
> > failure, than
> > get emails saying the equipment is down the seconds it happens  
> > since "Too many
> > emails makes Vista work poorly".
> >
> > 	So until the big endian and arm/xscale issue is resolved in BS's  
> > view,
> > and Coova makes it into DD-WRT, I'm stuck with what can be done in  
> > the mean time.
> > And that, unfortunately, may mean some ugly patching potentially.  
> > Or, just
> > letting yet another thing be "ignored".
> >
> > 			Tuc