Merge branch 'defconfigs-for-arnd' of git://git.linaro.org/people/triad/linux-stericsson into fixes

		when a discarded area is read the discard_zeroes_data

		parameter will be set to one. Otherwise it will be 0 and

		the result of reading a discarded area is undefined.

What:		/sys/block/<disk>/alias

Date:		Aug 2011

Contact:	Nao Nishijima <nao.nishijima.xt@hitachi.com>

Description:

		A raw device name of a disk does not always point a same disk

		each boot-up time. Therefore, users have to use persistent

		device names, which udev creates when the kernel finds a disk,

		instead of raw device name. However, kernel doesn't show those

		persistent names on its messages (e.g. dmesg).

		This file can store an alias of the disk and it would be

		appeared in kernel messages if it is set. A disk can have an

		alias which length is up to 255bytes. Users can use alphabets,

		numbers, "-" and "_" in alias name. This file is writeonce.

</para>

<itemizedlist>

<listitem><para>

<varname>const char *name</varname>: Optional. Set this to help identify

the memory region, it will show up in the corresponding sysfs node.

</para></listitem>

<listitem><para>

<varname>int memtype</varname>: Required if the mapping is used. Set this to

<varname>UIO_MEM_PHYS</varname> if you you have physical memory on your

</itemizedlist>

<para>

Please do not touch the <varname>kobj</varname> element of

Please do not touch the <varname>map</varname> element of

<varname>struct uio_mem</varname>! It is used by the UIO framework

to set up sysfs files for this mapping. Simply leave it alone.

</para>

"SCSI support" in your kernel configuration to be able to use SCSI

tape drives with your Smart Array 5xxx controller.

Additionally, note that the driver will not engage the SCSI core at init 

time.  The driver must be directed to dynamically engage the SCSI core via 

the /proc filesystem entry which the "block" side of the driver creates as 

/proc/driver/cciss/cciss* at runtime.  This is because at driver init time, 

the SCSI core may not yet be initialized (because the driver is a block 

driver) and attempting to register it with the SCSI core in such a case 

would cause a hang.  This is best done via an initialization script 

(typically in /etc/init.d, but could vary depending on distribution). 

Additionally, note that the driver will engage the SCSI core at init

time if any tape drives or medium changers are detected.  The driver may

also be directed to dynamically engage the SCSI core via the /proc filesystem

entry which the "block" side of the driver creates as

/proc/driver/cciss/cciss* at runtime.  This is best done via a script.

For example:

	for x in /proc/driver/cciss/cciss[0-9]*

The I2C protocol knows about two kinds of device addresses: normal 7 bit

addresses, and an extended set of 10 bit addresses. The sets of addresses

do not intersect: the 7 bit address 0x10 is not the same as the 10 bit

address 0x10 (though a single device could respond to both of them). You

select a 10 bit address by adding an extra byte after the address

byte:

  S Addr7 Rd/Wr ....

becomes

  S 11110 Addr10 Rd/Wr

S is the start bit, Rd/Wr the read/write bit, and if you count the number

of bits, you will see the there are 8 after the S bit for 7 bit addresses,

and 16 after the S bit for 10 bit addresses.

address 0x10 (though a single device could respond to both of them).

WARNING! The current 10 bit address support is EXPERIMENTAL. There are

several places in the code that will cause SEVERE PROBLEMS with 10 bit

addresses, even though there is some basic handling and hooks. Also,

almost no supported adapter handles the 10 bit addresses correctly.

I2C messages to and from 10-bit address devices have a different format.

See the I2C specification for the details.

As soon as a real 10 bit address device is spotted 'in the wild', we

can and will add proper support. Right now, 10 bit address devices

are defined by the I2C protocol, but we have never seen a single device

which supports them.

The current 10 bit address support is minimal. It should work, however

you can expect some problems along the way:

* Not all bus drivers support 10-bit addresses. Some don't because the

  hardware doesn't support them (SMBus doesn't require 10-bit address

  support for example), some don't because nobody bothered adding the

  code (or it's there but not working properly.) Software implementation

  (i2c-algo-bit) is known to work.

* Some optional features do not support 10-bit addresses. This is the

  case of automatic detection and instantiation of devices by their,

  drivers, for example.

* Many user-space packages (for example i2c-tools) lack support for

  10-bit addresses.

Note that 10-bit address devices are still pretty rare, so the limitations

listed above could stay for a long time, maybe even forever if nobody

needs them to be fixed.

	default FALSE

min_pmtu - INTEGER

	default 562 - minimum discovered Path MTU

	default 552 - minimum discovered Path MTU

route/max_size - INTEGER

	Maximum number of routes allowed in the kernel.  Increase