Re: New Linux Development Model

[Bill Davidsen <davidsen@tmr.com>]

Marcos Marado wrote:
> On Wed, 2005-11-09 at 02:47 +0100, Ian Kumlien wrote:
> 
> 
>>Anyways, I was also miffed that the kernel folks merged a 'ancient'
>>version of ipw2200 and ieee802.11, if they had merged something more
>>current everything would have worked out of the box and all the cleanups
>>would have been easier to cope with. Ie, the intel ppl could release
>>straight patches to the in kernel version. I dunno if they have changed
>>the way their driver works now.
>>
>>Atm, the 'ancient' ieee802.11 is what breaks the ipw2200 build. So,
>>basically all testing of cutting edge kernels gets very tedious due to
>>the ieee802.11 package removing the offending .h file and making
>>reversing -gitX and applying -gitY a real PITA.
> 
> 
> Those are no "ancient" versions, they are the "stable" versions of
> ieee80211, ipw2100 and ipw2200. ipw* folks think, and I have to agree,
> that for the stable kernel (Linux tree) it makes sense to add the stable
> versions of their projects.

To what end? The current drivers compile and load, but they don't 
function for wireless communication! What's the point of having code 
which is essentially a no-op, why have it if it doesn't provide any 
functionality?

With the current firmware and driver a "scan" shows 14 connectible 
points outside an apartment building (only one secured in any way ;-) 
whic is just what Windows shows. With the stock kernel zero are found. 
That's not stable that's moribund.

> 
> For more about their versioning, make sure you read
> http://ipw2100.sourceforge.net/#downloads .
> 

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me