Merge branches 'cns3xxx/devel', 'davinci/devel', 'imx/devel', 'lpc32xx/devel',...

=====

This document is designed to provide a list of the minimum levels of

software necessary to run the 2.6 kernels, as well as provide brief

instructions regarding any other "Gotchas" users may encounter when

trying life on the Bleeding Edge.  If upgrading from a pre-2.4.x

kernel, please consult the Changes file included with 2.4.x kernels for

additional information; most of that information will not be repeated

here.  Basically, this document assumes that your system is already

functional and running at least 2.4.x kernels.

software necessary to run the 3.0 kernels.

This document is originally based on my "Changes" file for 2.0.x kernels

and therefore owes credit to the same people as that file (Jared Mauch,

encountered a bug!  If you're unsure what version you're currently

running, the suggested command should tell you.

Again, keep in mind that this list assumes you are already

functionally running a Linux 2.4 kernel.  Also, not all tools are

necessary on all systems; obviously, if you don't have any ISDN

hardware, for example, you probably needn't concern yourself with

isdn4k-utils.

Again, keep in mind that this list assumes you are already functionally

running a Linux kernel.  Also, not all tools are necessary on all

systems; obviously, if you don't have any ISDN hardware, for example,

you probably needn't concern yourself with isdn4k-utils.

o  Gnu C                  3.2                     # gcc --version

o  Gnu make               3.80                    # make --version

If the unthinkable happens and your kernel oopses, you may need the

ksymoops tool to decode it, but in most cases you don't.

In the 2.6 kernel it is generally preferred to build the kernel with

CONFIG_KALLSYMS so that it produces readable dumps that can be used as-is

(this also produces better output than ksymoops).

If for some reason your kernel is not build with CONFIG_KALLSYMS and

you have no way to rebuild and reproduce the Oops with that option, then

you can still decode that Oops with ksymoops.

It is generally preferred to build the kernel with CONFIG_KALLSYMS so

that it produces readable dumps that can be used as-is (this also

produces better output than ksymoops).  If for some reason your kernel

is not build with CONFIG_KALLSYMS and you have no way to rebuild and

reproduce the Oops with that option, then you can still decode that Oops

with ksymoops.

Module-Init-Tools

-----------------

NFS-utils

---------

In 2.4 and earlier kernels, the nfs server needed to know about any

client that expected to be able to access files via NFS.  This

In ancient (2.4 and earlier) kernels, the nfs server needed to know

about any client that expected to be able to access files via NFS.  This

information would be given to the kernel by "mountd" when the client

mounted the filesystem, or by "exportfs" at system startup.  exportfs

would take information about active clients from /var/lib/nfs/rmtab.

fail-over.  Even when the system is working well, rmtab suffers from

getting lots of old entries that never get removed.

With 2.6 we have the option of having the kernel tell mountd when it

gets a request from an unknown host, and mountd can give appropriate

export information to the kernel.  This removes the dependency on

rmtab and means that the kernel only needs to know about currently

active clients.

With modern kernels we have the option of having the kernel tell mountd

when it gets a request from an unknown host, and mountd can give

appropriate export information to the kernel.  This removes the

dependency on rmtab and means that the kernel only needs to know about

currently active clients.

To enable this new functionality, you need to:

		Chapter 14: Allocating memory

The kernel provides the following general purpose memory allocators:

kmalloc(), kzalloc(), kcalloc(), and vmalloc().  Please refer to the API

documentation for further information about them.

kmalloc(), kzalloc(), kcalloc(), vmalloc(), and vzalloc().  Please refer to

the API documentation for further information about them.

The preferred form for passing a size of a struct is the following:

- Specify a bandwidth rate on particular device for root group. The format

  for policy is "<major>:<minor>  <byes_per_second>".

        echo "8:16  1048576" > /sys/fs/cgroup/blkio/blkio.read_bps_device

        echo "8:16  1048576" > /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device

  Above will put a limit of 1MB/second on reads happening for root group

  on device having major/minor number 8:16.

        1024+0 records out

        4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s

 Limits for writes can be put using blkio.write_bps_device file.

 Limits for writes can be put using blkio.throttle.write_bps_device file.

Hierarchical Cgroups

====================

	  specified in bytes per second. Rules are per deivce. Following is

	  the format.

  echo "<major>:<minor>  <rate_bytes_per_second>" > /cgrp/blkio.read_bps_device

  echo "<major>:<minor>  <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device

- blkio.throttle.write_bps_device

	- Specifies upper limit on WRITE rate to the device. IO rate is

	  specified in bytes per second. Rules are per deivce. Following is

	  the format.

  echo "<major>:<minor>  <rate_bytes_per_second>" > /cgrp/blkio.write_bps_device

  echo "<major>:<minor>  <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device

- blkio.throttle.read_iops_device

	- Specifies upper limit on READ rate from the device. IO rate is

	  specified in IO per second. Rules are per deivce. Following is

	  the format.

  echo "<major>:<minor>  <rate_io_per_second>" > /cgrp/blkio.read_iops_device

  echo "<major>:<minor>  <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device

- blkio.throttle.write_iops_device

	- Specifies upper limit on WRITE rate to the device. IO rate is

	  specified in io per second. Rules are per deivce. Following is

	  the format.

  echo "<major>:<minor>  <rate_io_per_second>" > /cgrp/blkio.write_iops_device

  echo "<major>:<minor>  <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device

Note: If both BW and IOPS rules are specified for a device, then IO is

      subjectd to both the constraints.

Who:	Laurent Pinchart <laurent.pinchart@ideasonboard.com>

----------------------------

What:	For VIDIOC_S_FREQUENCY the type field must match the device node's type.

	If not, return -EINVAL.

When:	3.2

Why:	It makes no sense to switch the tuner to radio mode by calling

	VIDIOC_S_FREQUENCY on a video node, or to switch the tuner to tv mode by

	calling VIDIOC_S_FREQUENCY on a radio node. This is the first step of a

	move to more consistent handling of tv and radio tuners.

Who:	Hans Verkuil <hans.verkuil@cisco.com>

----------------------------

What:	Opening a radio device node will no longer automatically switch the

	tuner mode from tv to radio.

When:	3.3

Why:	Just opening a V4L device should not change the state of the hardware

	like that. It's very unexpected and against the V4L spec. Instead, you

	switch to radio mode by calling VIDIOC_S_FREQUENCY. This is the second

	and last step of the move to consistent handling of tv and radio tuners.

Who:	Hans Verkuil <hans.verkuil@cisco.com>

----------------------------

in which case the page will not be stored in the cache this time.

BULK INODE PAGE UNCACHE

-----------------------

A convenience routine is provided to perform an uncache on all the pages

attached to an inode.  This assumes that the pages on the inode correspond on a

1:1 basis with the pages in the cache.

	void fscache_uncache_all_inode_pages(struct fscache_cookie *cookie,

					     struct inode *inode);

This takes the netfs cookie that the pages were cached with and the inode that

the pages are attached to.  This function will wait for pages to finish being

written to the cache and for the cache to finish with the page generally.  No

error is returned.

==========================

INDEX AND DATA FILE UPDATE

==========================