| Kernel Log: Linux 2.6.34 goes into testing | ||||||||||||||||||
| 摘自: www.h-online.com 被阅读次数: 1093 | ||||||||||||||||||
由 yangyi 于 2010-03-11 22:18:15 提供 | ||||||||||||||||||
by Thorsten Leemhuis
With the release of Linux 2.6.34-rc1[1] on Monday night, Linus Torvalds has closed the merge window of Linux 2.6.34 – only 12 days after releasing Linux 2.6.33[2]. While Torvalds usually allows at least two weeks at the beginning of each development cycle for integrating the most important new features, he had already indicated[3] that the current first phase would be shorter in an attempt to get subsystem maintainers out of the habit of submitting their changes at the last minute. The developers made numerous further changes to the graphics driver code. Among the new additions is a KMS graphics driver for Radeon 5000 graphics cards[4] and improved support of the power-saving mechanisms in modern Radeon graphics chips. Major restructuring measures[5] in the kernel's Nouveau driver have changed the API; this has made older Nouveau drivers for X.org incompatible with the new kernel. The Nouveau code can now generate[6] the firmware for recent graphics chips itself and no longer requires the external ctxprogs that caused discussions[7] when Nouveau was first integrated. In notebooks equipped with chip-set graphics as well as a separate graphics chip, the kernel can now switch between the two graphics systems. The developers extended the Intel graphics drivers to include first components[8] for an Intel processor so far only known by its code name, Sandybridge, which contains a GPU and is expected to become available early next year. Some drivers for the pertaining motherboard chip-sets, which are currently only known as Cougar Point, were also added to the kernel during this merge window. Another new addition is the LogFS[9] file system, which is mainly interesting for Flash media without wear levelling such as those used in embedded applications. Further additions include a driver for Apple's Magic Mouse, a Python scripting engine for the tracing subsystem, and the vhost_net Virtio server. Various power-saving techniques were also improved. As usual, the Kernel Log at The H Open will discuss these and many other new features in a "Coming in 2.6.34" mini series in the coming few weeks. Let's, however, wait another few days before we start: Torvalds might still add a few more changes submitted by subsystem maintainers who missed the merge window. According to his release email[10], Torvalds is also considering integrating the Ceph file system and a number of debug patches. Compared with the number of changes introduced in the first RCs of previous kernels, the current release candidate, 2.6.34-rc1, contains considerably fewer changes:
Google wants to integrate Android code into Linux kernel in the long runAfter several insufficiently maintained drivers for Android devices were stripped from the main development branch of Linux[11] a few weeks ago, Chris DiBona, Google's Open Source Program Manager, said on Zdnet[12] that Google plans to integrate Android's kernel extensions into the main development branch of the Linux kernel – "in the next couple of years". However, the kernel extensions in question go far beyond these drivers, which has caused controversy between Google and the kernel developers. This was apparent in a discussion between DiBona and kernel hacker Greg Kroah-Hartmann that was sparked by an article on LWN.net[13] concerning the lack of co-operation between Google and the kernel community. Responding to Kroah-Hartmanns ("gregkh") complaints that Google wasn't interested in getting the Android changes integrated into the standard kernel, DiBona ("cdibona") said at the time that Android's Linux kernel requirements were very different from those of desktop or server systems. Forking the Linux kernel for Android is OK, although ultimately not Google's goal, he said. DiBona compared the Android kernel to the kernels of Red Hat Enterprise Linux and other distributions which, according to the executive, are just as much forks from the main development branch as the Android kernel. DiBona also said that the Linux code Google use internally for their non-mobile systems is quite close to the main development branch, but that Android is a different story. At the Kernel Summit 2009 only a few months ago[14], however, a Google employee presented a report about Google's use of Linux; a summary of this presentation can be found in the article "How Google uses Linux[15]" on LWN.net. According to this presentation, Google has also made comprehensive changes internally without putting major effort into getting these changes integrated into the main development branch or comparing notes with the kernel hackers. However, the presenter did say that Google wants to improve its cooperation. In briefKernel
Graphics
Kernel environment ("plumbing layer"), userland drivers, Git, ...
Older Kernel Logs can be found in the archives[25] or by using the search function[26] at The H Open Source[27]. New editions of Kernel Logs are also mentioned on Identi.ca[28] and Twitter[29] via "@kernellog2". The Kernel Log author also posts updates about various topics on Identi.ca[30] and Twitter[31] via "@kernellogauthor". (thl[32])
URL of this article:
Links in this Article: Original link: http://www.h-online.com/open/fea... |
