http://www.h-online.com/news/Kernel-Log-main-development-phase-for-2-6-29-ends-new-X-org-drivers--/112399

Kernel Log: main development phase for 2.6.29 ends, new X.org drivers

With the release of 2.6.29-rc1 on Saturday night, Linus Torvalds has closed the 2.6.29 merge window and brought to a close the development phase, during which the major new features for the next version of Linux are adopted. All significant changes in 2.6.29 should now be in the Linux source code management system, including new features previously discussed on heise open such as WiMAX, access point support and the Btrfs and Squashfs file systems.

These changes are just some of the more conspicuous changes adopted by the kernel hackers for 2.6.29. Support has been added for kernel-based mode setting on Intel graphics hardware and improvements have been made to the Graphics Execution Manager (GEM), which was integrated with 2.6.28. The SCSI subsystem now supports Fibre Channel over Ethernet (FCoE) and there are fixes to, and new functions in, the eCryptfs, Ext4, OCFS2 and XFS file systems. There are also numerous new and revised drivers, including new or revised audio drivers from the Alsa project and over 600 changes to the V4L/DVB drivers. These are now joined by various, in some cases very large, staging drivers, such as the Comedi framework, or support for Google's Android. heise open's Kernel Log will carry detailed reports on these and other changes over the next few weeks as part of our "What's coming in 2.6.29" series.

The realtime defragmenter (online ext4 defragmentation) has not made it into 2.6.29 – Theodore Tso explains why on LKML. Also left out, for the time being, are support for operation as a primary Xen domain (Dom0) and compression of the kernel image with bzip2/lzma. It looks like it could also be a while before support for kernel-based mode setting with AMD hardware meets the kernel development team's quality standards.

All about X.org

AMD developer Alex Deucher has released version 6.10 of the xf86-video-ati driver package, usually known simply as ati or radeon. It includes support for the RV710 (Radeon HD 4300/HD 4500) and RV730 (Radeon HD 4600) Radeon chips. The new version also reduces tearing during video playback and supports Bicubic Xv scaling on r3xx/r4xx/r5xx/rs690 Radeon chips. The developer discusses further changes on his blog. Matthias Hopf has now released the AtomBIOS disassembler previously used for programming the alternative Radeon graphics driver radeonhd. He describes some of the background to the tool on his blog.

The X.org developers have also released version 1.4.0 of the xf86-input-mouse mouse driver. This driver deals with many of the tasks previously dealt with by X server, and the code responsible for this has been removed from X server – with the result that in X server 1.6, currently under development, users will, unless their systems use Evdev, need at least version 1.4.0 of xf86-input-mouse.

In Brief:

  • Following LWN.net's occasional publication of analysis of which kernel developers have, for instance, introduced the most or the largest changes into a kernel version (e.g. 1, 2, 3), Wang Chen has been trying his hand at a similar set of online statistics.
  • SELinux hacker James Morris has announced the creation of the Kernel Security Wiki on his blog, where he has also recently summarised all the most significant security-related changes in Linux 2.6.28.
  • Daniel Phillips is continuing to work on Tux3 and is keeping the developer community updated on new features or internal matters in his "Tux3 Report" – a recent e-mail to LKML, for example, elucidates the current structure of the file system.
  • A group of developers are working on open source firmware for some of the Broadcom WLAN chips supported under Linux by the b43 driver; this firmware does not, however, appear to work for all testers. Marvell has made WLAN firmware for the GSPI-88W8686 available to download, but has not released the source code.

Further background and information about developments in the Linux kernel and its environment can also be found in previous issues of the kernel log at heise open:

Older Kernel logs can be found in the archives or by using the search function at heise open. (thl/c't)


Reply via email to