Merge branch 'master' of...

Contact:	"Ike Panhc <ike.pan@canonical.com>"

Description:

		Control the power of camera module. 1 means on, 0 means off.

What:		/sys/devices/platform/ideapad/cfg

Date:		Jun 2011

KernelVersion:	3.1

Contact:	"Ike Panhc <ike.pan@canonical.com>"

Description:

		Ideapad capability bits.

		Bit 8-10: 1 - Intel graphic only

		          2 - ATI graphic only

		          3 - Nvidia graphic only

		          4 - Intel and ATI graphic

		          5 - Intel and Nvidia graphic

		Bit 16: Bluetooth exist (1 for exist)

		Bit 17: 3G exist (1 for exist)

		Bit 18: Wifi exist (1 for exist)

		Bit 19: Camera exist (1 for exist)

The limit on the length of lines is 80 columns and this is a strongly

preferred limit.

Statements longer than 80 columns will be broken into sensible chunks.

Descendants are always substantially shorter than the parent and are placed

substantially to the right. The same applies to function headers with a long

argument list. Long strings are as well broken into shorter strings. The

only exception to this is where exceeding 80 columns significantly increases

readability and does not hide information.

void fun(int a, int b, int c)

{

	if (condition)

		printk(KERN_WARNING "Warning this is a long printk with "

						"3 parameters a: %u b: %u "

						"c: %u \n", a, b, c);

	else

		next_statement;

}

Statements longer than 80 columns will be broken into sensible chunks, unless

exceeding 80 columns significantly increases readability and does not hide

information. Descendants are always substantially shorter than the parent and

are placed substantially to the right. The same applies to function headers

with a long argument list. However, never break user-visible strings such as

printk messages, because that breaks the ability to grep for them.

		Chapter 3: Placing Braces and Spaces

- param1

  This file is used to set the first error parameter value. Effect of

  parameter depends on error_type specified. For memory error, this is

  physical memory address.

  physical memory address.  Only available if param_extension module

  parameter is specified.

- param2

  This file is used to set the second error parameter value. Effect of

  parameter depends on error_type specified. For memory error, this is

  physical memory address mask.

  physical memory address mask.  Only available if param_extension

  module parameter is specified.

Injecting parameter support is a BIOS version specific extension, that

is, it only works on some BIOS version.  If you want to use it, please

make sure your BIOS version has the proper support and specify

"param_extension=y" in module parameter.

For more information about EINJ, please refer to ACPI specification

version 4.0, section 17.5.

Device-Mapper's "crypt" target provides transparent encryption of block devices

using the kernel crypto API.

Parameters: <cipher> <key> <iv_offset> <device path> <offset>

Parameters: <cipher> <key> <iv_offset> <device path> \

	      <offset> [<#opt_params> <opt_params>]

<cipher>

    Encryption cipher and an optional IV generation mode.

<offset>

    Starting sector within the device where the encrypted data begins.

<#opt_params>

    Number of optional parameters. If there are no optional parameters,

    the optional paramaters section can be skipped or #opt_params can be zero.

    Otherwise #opt_params is the number of following arguments.

    Example of optional parameters section:

        1 allow_discards

allow_discards

    Block discard requests (a.k.a. TRIM) are passed through the crypt device.

    The default is to ignore discard requests.

    WARNING: Assess the specific security risks carefully before enabling this

    option.  For example, allowing discards on encrypted devices may lead to

    the leak of information about the ciphertext device (filesystem type,

    used space etc.) if the discarded blocks can be located easily on the

    device later.

Example scripts

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

LUKS (Linux Unified Key Setup) is now the preferred way to set up disk

dm-flakey

=========

This target is the same as the linear target except that it returns I/O

errors periodically.  It's been found useful in simulating failing

devices for testing purposes.

This target is the same as the linear target except that it exhibits

unreliable behaviour periodically.  It's been found useful in simulating

failing devices for testing purposes.

Starting from the time the table is loaded, the device is available for

<up interval> seconds, then returns errors for <down interval> seconds,

and then this cycle repeats.

<up interval> seconds, then exhibits unreliable behaviour for <down

interval> seconds, and then this cycle repeats.

Parameters: <dev path> <offset> <up interval> <down interval>

Also, consider using this in combination with the dm-delay target too,

which can delay reads and writes and/or send them to different

underlying devices.

Table parameters

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

  <dev path> <offset> <up interval> <down interval> \

    [<num_features> [<feature arguments>]]

Mandatory parameters:

    <dev path>: Full pathname to the underlying block-device, or a

                "major:minor" device-number.

    <offset>: Starting sector within the device.

    <up interval>: Number of seconds device is available.

    <down interval>: Number of seconds device returns errors.

Optional feature parameters:

  If no feature parameters are present, during the periods of

  unreliability, all I/O returns errors.

  drop_writes:

	All write I/O is silently ignored.

	Read I/O is handled correctly.

  corrupt_bio_byte <Nth_byte> <direction> <value> <flags>:

	During <down interval>, replace <Nth_byte> of the data of

	each matching bio with <value>.

    <Nth_byte>: The offset of the byte to replace.

		Counting starts at 1, to replace the first byte.

    <direction>: Either 'r' to corrupt reads or 'w' to corrupt writes.

		 'w' is incompatible with drop_writes.

    <value>: The value (from 0-255) to write.

    <flags>: Perform the replacement only if bio->bi_rw has all the

	     selected flags set.

Examples:

  corrupt_bio_byte 32 r 1 0

	- replaces the 32nd byte of READ bios with the value 1

  corrupt_bio_byte 224 w 0 32

	- replaces the 224th byte of REQ_META (=32) bios with the value 0