Slashdot Mirror
Atheros Hardware Abstraction Layer Source Is Released
chrb writes "With the recent discussion here on proprietary blobs in the Linux kernel, it's nice to see that today Sam Leffler has released the source for the Atheros Hardware Abstraction Layer under the ISC license, which is both GPL and BSD compatible. The Atheros chipset is used in many laptops, so this is another important step towards running a completely free distribution."
I have a Macbook from just over a year ago, and it uses a Atheros wireless card, and it's the biggest pain to get running in Linux. Hopefully, with the Source released, it will be easier in the future to get the wireless working on this model of computer.
The argument about BLOBs - binary loadable objects in the kernel - is not new, despite Bruce Byfield's recent report. I guess he just doesn't read the kernel list and other distro internal discussions, where this has been going on for a decade. And FSF did not "redefine" anything, they've always held that opinion.
It would be nice to draw a line at the hardware bus, with all above that Open Source and all below that whatever the hardware manufacturer likes because we don't deal with it. But BLOBs break that, because they are both above and below the bus. If we're going to handle the code, we can't really deny that there's a computer there running closed-source code. And given the degree to which wifi firmware sucks the world would be nicer if it was Free Software. Now, we just have to drive some sense into FCC, etc.
Bruce
Bruce Perens.
Does this mean the sleep function will finally work as it should without draining the batteries? I have yet to see a laptop running Linux go into hibernate mode and not bleed off the batteries.
I noticed this on the dd-wrt.com website a couple of months back (dated 8.28.08) We would like to announce the release of a new HAL for Atheros WLAN devices. The new HAL is the result of a collaboration between OpenWrt.org, DD-WRT and MakSat Technologies (P) Ltd. It is the first result of a common effort, and the present collaborators would like to share the product of this work. It is the intention to provide reliable and continued support for other projects using this new HAL for Atheros WLAN devices. The HAL provides a defined API to access and contol Atheros WLAN chipsets, and is an integral part for many drivers such as MadWifi. Comparing it with the HAL that's currently used by MadWifi, the most important changes are: * many known bugs have been fixed * improved noise immunity measures * added support for additional architectures, such as ARM11, MIPS64 and MIPS32r2 * enhanced support for Atheros WiSOC (Wireless System on Chip) * added support for Atheros AR7100 Home of the new HAL will be the website of the madwifi.org project, http://madwifi.org./ Future development will be coordinated here, and the bug tracking facility can be used to report bugs or file feature requests. For commercial requests please contact hal@maksat.deThis e-mail address is being protected from spambots, you need JavaScript enabled to view it . So with the new news maybe things will really get rolling
I wonder if this could be used to help port OpenWRT over to the atheros chipset. Currently the only routers that OpenWRT (and conversely by that DD-WRT) really work well on are the broadcom chipsets. Many routers that use the Atheros chipset have been written off as impossible to port to. Maybe they could be used if this proves any insight to how they operate.
Procrastinating life a way at a rapid rate of speed.
From the article apparaently he had "an agreement with Atheros" to "access to information about their devices". Does that mean he developed the HAL with little help from the company? (And apparaently he'll have no more access since the agreement is "concluded".)
It is nice to have an open source driver released, but it is NOT nice that an individual have to go jump through hoops and write it himself to make it happen.
I was under the impression that the atheros HAL is not a binary blob in the sense the summary refers to, but a program executed on the host CPU. That makes this even better news than if it were a blob. It is debatable whether or not a system that needs to load a bunch of blobs onto its peripherals at startup is free or not(personally, I'm inclined to say it is, as long as the mechanisms for loading the firmware and interacting with the peripheral are open and the firmware is freely redistributable); but a system with a big binary lump running in kernel space definitely isn't.
It is very encouraging to see progress towards removing one of the most common causes of tainted kernels(probably second only to video card drivers); but it isn't really related to the blob question.
In the UK this stuff is patent free because there are no software patents in England. It depends very much on where you live.
If Canonical made a UK distribution which included all the patented free software it would also create prior art in case of any changes in UK patent law.
And please don't let any money grubbing developer who only cares about money do any more "open source" work for you in the future! Sam stood up at Usenix and told the OpenBSD guys to stop their efforts to reverse-engineer HAL or else there would be no open source support at all. Now they've succeeded and not only is there open source support for Atheros, there's more support for it because now Sam's forced to open source HAL in order to keep the money stream coming in from a formerly proprietary monopoly situation. Sam shouldn't be allowed work on open source software, for any organization.
Since Mr. Reyk hasn't filed suit, it's totally academic what the 'madwifi fuckers' did or did not do.
For someone who make such strong claims on being intellectually correct, this is an interesting position to take. So, in your world, as long as no suit is filed, any action taken is just "totally academic"?
If you have an axe to grind, take it up with them.
I don't really have an axe to grind. It's just two people in the madwifi group that did that "totally academic" but unethical thing. And have not apologized for it.
If, alternately, you have a thoughtful and reasoned criticism (and preferably some strong evidence for your allegations), please share it.
Umm... you did not manage to follow the original link that I had originally responded to? Would you like a signed and sealed piece of paper? Go read the link again - note that Theo was talking about the OpenHAL code. http://kerneltrap.org/mailarchive/openbsd-misc/2007/9/13/259448/thread
If you want to look for evidence, you can find it yourself. OpenBSD's CVS is open. I'm sure madwifi's repository is available too. Look at code check in dates. Make up your own mind. *big hint* OpenBSD's OpenHAL is dated a year earlier, according to 3rd party reports. Please do not let this *big hint* color your perception or conclusion. KTHXHAND
I really hope the programmers behind KisMAC are reading this thread.
We MacBook users are really hoping that we can run injections and other advanced features using our built-in network cards now. Until now, all our packets were trash and we couldn't work out the SSID.
Sad days they have been, but now we have reason to be optimistic!