Advanced

Report: Moving Closer to 802.11n

Posted by Scott_Ruecker on · 3 comments
LinuxPlanet; By Carla Schroder
Mail this story
Print this story

Since our previous peek at the state of wireless networking in Linux, which is moving forward in an excellent fashion, the new unified Linux wireless stack (mac80211) has been accepted into the mainline 2.6.22 kernel. This is the new common base for all Linux wireless drivers. There are no drivers yet that use mac80211, but inclusion in the kernel is a huge step forward. Linux developers are hard at work porting old drivers and writing new ones, and this should attract participation from additional developers who now have a nice unified wireless networking stack to build on, instead of the previous mish-mash.

Full Story

  Nav
» Read more about: Story Type: News Story; Groups: Kernel, Linux

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (3)

Thanks TC, you did a great job on that one, the update is much appreciated.

However I would like to discuss, with the community one of the statements and supplied and read link about the legality of closed source kernel modules.

For argument I will use one that is essentially optional for non gamers.The nVidia driver, which with luck will be a moot point in the future. While I can see and agree with the argument that including this kernel linked driver is illegal, after market modification i.e. after I install my system, can not by definition be illegal.

My reasoning for this is fairly simple, once I set my system up I am free to use and abuse it in any way I see fit. By the GPL, there is no restriction that would kick in as long as I didn't try and redistribute it. This makes the closed source kernel module a non participant as far as the GPL is concerned. Shipping the driver enabled by default though ... very illegal unless one does some scripting chicanery such as Sabayon did, using a boot time linker where the module can be enabled/disabled via a boot parameter passed from Grub.

Any thoughts, rebuttals, fried green tomato's?
Thanks for the kind words, Azerthoth. IANAL, which doesn't seem all that meaningful anyway- I've seen opinions generated from random Scrabble tiles that made as much sense as some legal opinions. But I digress. I think you're right, at least that's how I've always understood how it works.
Debian makes it work by 1) putting the modules in a separate repository plainly marked "non-free", 2) making it so I have to compile and install it.

Sure they make a script to do the hard work, but it's still _me_ that is doing it, not them.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post