Re: [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast)

[Martin Langer <martin-langer@gmx.de>]

On Fri, Nov 17, 2006 at 12:04:42PM +0100, Johannes Berg wrote:
> On Fri, 2006-11-17 at 11:35 +0100, Andreas Schwab wrote:
> 
> > Still the same.  One of them does not exist, the other one requires
> > Javascript!
> 
> Yeah, looks like Martin forgot to put the URLs in the the readme while
> he put them into commit messages...

The last update for README was quite some time ago. I think that file 
is a bad way to transport that kind of information. So I'm afraid a lot 
of links are really out of date now. A better way is probably an open 
wiki (berlios?). Volunteers and other ideas are always welcome.

The comments in the commit messages are more a kind of protocol and not 
the best link on earth. And if you wait some days the number of mirrors 
for the latest driver will explode. It would be bad to write the first 
available link into the README. A download link should be a direct 
link, a small package, easy to extract and so on. But I'm really not 
interested in doing that job of a hunter for the perfect download link 
and try to keep that link up to date. I think it's more important to 
write support for more driver files instead of doing that surrounding 
stuff for a few files in a perfect way. Google isn't that complicated 
these days and it's more up to date than our README.
 
> Support for bcmwl5.sys v4.80.53.0 added.
> ftp://downloads.netgear.com/files/wn511b_sw_3_28_3_8_setup.zip
> (bcmwl5.sys is renamed to wn511b.sys)
> 
> Support for bcmwl5(64).sys v4.100.15.5 added.
> >from the latest Linksys WPC300N driver at
> http://www.linksys.com/download/
> It's ucode revision 0x0173, patchlevel 0x0425, 2006-10-04.
> 
> Martin, can you add these to the readme?

These are bad examples for adding to README. People aren't prepared 
well enough to look for renamed bcmwl5.sys files which are packaged 
twice and they expect direct links, too. ...

Martin