summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2007-10-13 14:43:54 +0100
committerDavid Woodhouse <dwmw2@infradead.org>2007-10-13 14:43:54 +0100
commitb160292cc216a50fd0cd386b0bda2cd48352c73b (patch)
treeef07cf98f91353ee4c9ec1e1ca7a2a5d9d4b538a /Documentation
parentb37bde147890c8fea8369a5a4e230dabdea4ebfb (diff)
parentbbf25010f1a6b761914430f5fca081ec8c7accd1 (diff)
downloadop-kernel-dev-b160292cc216a50fd0cd386b0bda2cd48352c73b.zip
op-kernel-dev-b160292cc216a50fd0cd386b0bda2cd48352c73b.tar.gz
Merge Linux 2.6.23
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/00-INDEX2
-rw-r--r--Documentation/DocBook/deviceiobook.tmpl3
-rw-r--r--Documentation/HOWTO4
-rw-r--r--Documentation/ManagementStyle2
-rw-r--r--Documentation/SubmittingPatches4
-rw-r--r--Documentation/crypto/async-tx-api.txt219
-rw-r--r--Documentation/devices.txt2
-rw-r--r--Documentation/feature-removal-schedule.txt16
-rw-r--r--Documentation/filesystems/00-INDEX2
-rw-r--r--Documentation/filesystems/9p.txt24
-rw-r--r--Documentation/filesystems/ocfs2.txt13
-rw-r--r--Documentation/i2c/busses/i2c-piix42
-rw-r--r--Documentation/input/iforce-protocol.txt508
-rw-r--r--Documentation/kernel-parameters.txt22
-rw-r--r--Documentation/ko_KR/HOWTO623
-rw-r--r--Documentation/lguest/lguest.c2
-rw-r--r--Documentation/lockstat.txt120
-rw-r--r--Documentation/networking/00-INDEX3
-rw-r--r--Documentation/networking/multiqueue.txt10
-rw-r--r--Documentation/networking/sk98lin.txt568
-rw-r--r--Documentation/sysrq.txt2
-rw-r--r--Documentation/thinkpad-acpi.txt96
-rw-r--r--Documentation/video4linux/cx2341x/fw-encoder-api.txt4
23 files changed, 1942 insertions, 309 deletions
diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX
index 8b05636..43e89b1 100644
--- a/Documentation/00-INDEX
+++ b/Documentation/00-INDEX
@@ -134,8 +134,6 @@ dvb/
- info on Linux Digital Video Broadcast (DVB) subsystem.
early-userspace/
- info about initramfs, klibc, and userspace early during boot.
-ecryptfs.txt
- - docs on eCryptfs: stacked cryptographic filesystem for Linux.
eisa.txt
- info on EISA bus support.
exception.txt
diff --git a/Documentation/DocBook/deviceiobook.tmpl b/Documentation/DocBook/deviceiobook.tmpl
index 90ed23d..c917de6 100644
--- a/Documentation/DocBook/deviceiobook.tmpl
+++ b/Documentation/DocBook/deviceiobook.tmpl
@@ -316,7 +316,8 @@ CPU B: spin_unlock_irqrestore(&amp;dev_lock, flags)
<chapter id="pubfunctions">
<title>Public Functions Provided</title>
-!Einclude/asm-i386/io.h
+!Iinclude/asm-i386/io.h
+!Elib/iomap.c
</chapter>
</book>
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index f8cc3f8..c64e969 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -208,7 +208,7 @@ tools. One such tool that is particularly recommended is the Linux
Cross-Reference project, which is able to present source code in a
self-referential, indexed webpage format. An excellent up-to-date
repository of the kernel code may be found at:
- http://sosdg.org/~coywolf/lxr/
+ http://users.sosdg.org/~qiyong/lxr/
The development process
@@ -384,7 +384,7 @@ One of the best ways to put into practice your hacking skills is by fixing
bugs reported by other people. Not only you will help to make the kernel
more stable, you'll learn to fix real world problems and you will improve
your skills, and other developers will be aware of your presence. Fixing
-bugs is one of the best ways to earn merit amongst the developers, because
+bugs is one of the best ways to get merits among other developers, because
not many people like wasting time fixing other people's bugs.
To work in the already reported bug reports, go to http://bugzilla.kernel.org.
diff --git a/Documentation/ManagementStyle b/Documentation/ManagementStyle
index cbbebfb..49a8efa 100644
--- a/Documentation/ManagementStyle
+++ b/Documentation/ManagementStyle
@@ -166,7 +166,7 @@ To solve this problem, you really only have two options:
The option of being unfailingly polite really doesn't exist. Nobody will
trust somebody who is so clearly hiding his true character.
-(*) Paul Simon sang "Fifty Ways to Lose Your Lover", because quite
+(*) Paul Simon sang "Fifty Ways to Leave Your Lover", because quite
frankly, "A Million Ways to Tell a Developer He Is a D*ckhead" doesn't
scan nearly as well. But I'm sure he thought about it.
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index d6b45a9..a30dd44 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -126,7 +126,7 @@ the reviewers time and will get your patch rejected, probably
without even being read.
At a minimum you should check your patches with the patch style
-checker prior to submission (scripts/patchcheck.pl). You should
+checker prior to submission (scripts/checkpatch.pl). You should
be able to justify all violations that remain in your patch.
@@ -560,7 +560,7 @@ NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
<http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>
Kernel Documentation/CodingStyle:
- <http://sosdg.org/~coywolf/lxr/source/Documentation/CodingStyle>
+ <http://users.sosdg.org/~qiyong/lxr/source/Documentation/CodingStyle>
Linus Torvalds's mail on the canonical patch format:
<http://lkml.org/lkml/2005/4/7/183>
diff --git a/Documentation/crypto/async-tx-api.txt b/Documentation/crypto/async-tx-api.txt
new file mode 100644
index 0000000..c1e9545
--- /dev/null
+++ b/Documentation/crypto/async-tx-api.txt
@@ -0,0 +1,219 @@
+ Asynchronous Transfers/Transforms API
+
+1 INTRODUCTION
+
+2 GENEALOGY
+
+3 USAGE
+3.1 General format of the API
+3.2 Supported operations
+3.3 Descriptor management
+3.4 When does the operation execute?
+3.5 When does the operation complete?
+3.6 Constraints
+3.7 Example
+
+4 DRIVER DEVELOPER NOTES
+4.1 Conformance points
+4.2 "My application needs finer control of hardware channels"
+
+5 SOURCE
+
+---
+
+1 INTRODUCTION
+
+The async_tx API provides methods for describing a chain of asynchronous
+bulk memory transfers/transforms with support for inter-transactional
+dependencies. It is implemented as a dmaengine client that smooths over
+the details of different hardware offload engine implementations. Code
+that is written to the API can optimize for asynchronous operation and
+the API will fit the chain of operations to the available offload
+resources.
+
+2 GENEALOGY
+
+The API was initially designed to offload the memory copy and
+xor-parity-calculations of the md-raid5 driver using the offload engines
+present in the Intel(R) Xscale series of I/O processors. It also built
+on the 'dmaengine' layer developed for offloading memory copies in the
+network stack using Intel(R) I/OAT engines. The following design
+features surfaced as a result:
+1/ implicit synchronous path: users of the API do not need to know if
+ the platform they are running on has offload capabilities. The
+ operation will be offloaded when an engine is available and carried out
+ in software otherwise.
+2/ cross channel dependency chains: the API allows a chain of dependent
+ operations to be submitted, like xor->copy->xor in the raid5 case. The
+ API automatically handles cases where the transition from one operation
+ to another implies a hardware channel switch.
+3/ dmaengine extensions to support multiple clients and operation types
+ beyond 'memcpy'
+
+3 USAGE
+
+3.1 General format of the API:
+struct dma_async_tx_descriptor *
+async_<operation>(<op specific parameters>,
+ enum async_tx_flags flags,
+ struct dma_async_tx_descriptor *dependency,
+ dma_async_tx_callback callback_routine,
+ void *callback_parameter);
+
+3.2 Supported operations:
+memcpy - memory copy between a source and a destination buffer
+memset - fill a destination buffer with a byte value
+xor - xor a series of source buffers and write the result to a
+ destination buffer
+xor_zero_sum - xor a series of source buffers and set a flag if the
+ result is zero. The implementation attempts to prevent
+ writes to memory
+
+3.3 Descriptor management:
+The return value is non-NULL and points to a 'descriptor' when the operation
+has been queued to execute asynchronously. Descriptors are recycled
+resources, under control of the offload engine driver, to be reused as
+operations complete. When an application needs to submit a chain of
+operations it must guarantee that the descriptor is not automatically recycled
+before the dependency is submitted. This requires that all descriptors be
+acknowledged by the application before the offload engine driver is allowed to
+recycle (or free) the descriptor. A descriptor can be acked by one of the
+following methods:
+1/ setting the ASYNC_TX_ACK flag if no child operations are to be submitted
+2/ setting the ASYNC_TX_DEP_ACK flag to acknowledge the parent
+ descriptor of a new operation.
+3/ calling async_tx_ack() on the descriptor.
+
+3.4 When does the operation execute?
+Operations do not immediately issue after return from the
+async_<operation> call. Offload engine drivers batch operations to
+improve performance by reducing the number of mmio cycles needed to
+manage the channel. Once a driver-specific threshold is met the driver
+automatically issues pending operations. An application can force this
+event by calling async_tx_issue_pending_all(). This operates on all
+channels since the application has no knowledge of channel to operation
+mapping.
+
+3.5 When does the operation complete?
+There are two methods for an application to learn about the completion
+of an operation.
+1/ Call dma_wait_for_async_tx(). This call causes the CPU to spin while
+ it polls for the completion of the operation. It handles dependency
+ chains and issuing pending operations.
+2/ Specify a completion callback. The callback routine runs in tasklet
+ context if the offload engine driver supports interrupts, or it is
+ called in application context if the operation is carried out
+ synchronously in software. The callback can be set in the call to
+ async_<operation>, or when the application needs to submit a chain of
+ unknown length it can use the async_trigger_callback() routine to set a
+ completion interrupt/callback at the end of the chain.
+
+3.6 Constraints:
+1/ Calls to async_<operation> are not permitted in IRQ context. Other
+ contexts are permitted provided constraint #2 is not violated.
+2/ Completion callback routines cannot submit new operations. This
+ results in recursion in the synchronous case and spin_locks being
+ acquired twice in the asynchronous case.
+
+3.7 Example:
+Perform a xor->copy->xor operation where each operation depends on the
+result from the previous operation:
+
+void complete_xor_copy_xor(void *param)
+{
+ printk("complete\n");
+}
+
+int run_xor_copy_xor(struct page **xor_srcs,
+ int xor_src_cnt,
+ struct page *xor_dest,
+ size_t xor_len,
+ struct page *copy_src,
+ struct page *copy_dest,
+ size_t copy_len)
+{
+ struct dma_async_tx_descriptor *tx;
+
+ tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len,
+ ASYNC_TX_XOR_DROP_DST, NULL, NULL, NULL);
+ tx = async_memcpy(copy_dest, copy_src, 0, 0, copy_len,
+ ASYNC_TX_DEP_ACK, tx, NULL, NULL);
+ tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len,
+ ASYNC_TX_XOR_DROP_DST | ASYNC_TX_DEP_ACK | ASYNC_TX_ACK,
+ tx, complete_xor_copy_xor, NULL);
+
+ async_tx_issue_pending_all();
+}
+
+See include/linux/async_tx.h for more information on the flags. See the
+ops_run_* and ops_complete_* routines in drivers/md/raid5.c for more
+implementation examples.
+
+4 DRIVER DEVELOPMENT NOTES
+4.1 Conformance points:
+There are a few conformance points required in dmaengine drivers to
+accommodate assumptions made by applications using the async_tx API:
+1/ Completion callbacks are expected to happen in tasklet context
+2/ dma_async_tx_descriptor fields are never manipulated in IRQ context
+3/ Use async_tx_run_dependencies() in the descriptor clean up path to
+ handle submission of dependent operations
+
+4.2 "My application needs finer control of hardware channels"
+This requirement seems to arise from cases where a DMA engine driver is
+trying to support device-to-memory DMA. The dmaengine and async_tx
+implementations were designed for offloading memory-to-memory
+operations; however, there are some capabilities of the dmaengine layer
+that can be used for platform-specific channel management.
+Platform-specific constraints can be handled by registering the
+application as a 'dma_client' and implementing a 'dma_event_callback' to
+apply a filter to the available channels in the system. Before showing
+how to implement a custom dma_event callback some background of
+dmaengine's client support is required.
+
+The following routines in dmaengine support multiple clients requesting
+use of a channel:
+- dma_async_client_register(struct dma_client *client)
+- dma_async_client_chan_request(struct dma_client *client)
+
+dma_async_client_register takes a pointer to an initialized dma_client
+structure. It expects that the 'event_callback' and 'cap_mask' fields
+are already initialized.
+
+dma_async_client_chan_request triggers dmaengine to notify the client of
+all channels that satisfy the capability mask. It is up to the client's
+event_callback routine to track how many channels the client needs and
+how many it is currently using. The dma_event_callback routine returns a
+dma_state_client code to let dmaengine know the status of the
+allocation.
+
+Below is the example of how to extend this functionality for
+platform-specific filtering of the available channels beyond the
+standard capability mask:
+
+static enum dma_state_client
+my_dma_client_callback(struct dma_client *client,
+ struct dma_chan *chan, enum dma_state state)
+{
+ struct dma_device *dma_dev;
+ struct my_platform_specific_dma *plat_dma_dev;
+
+ dma_dev = chan->device;
+ plat_dma_dev = container_of(dma_dev,
+ struct my_platform_specific_dma,
+ dma_dev);
+
+ if (!plat_dma_dev->platform_specific_capability)
+ return DMA_DUP;
+
+ . . .
+}
+
+5 SOURCE
+include/linux/dmaengine.h: core header file for DMA drivers and clients
+drivers/dma/dmaengine.c: offload engine channel management routines
+drivers/dma/: location for offload engine drivers
+include/linux/async_tx.h: core header file for the async_tx api
+crypto/async_tx/async_tx.c: async_tx interface to dmaengine and common code
+crypto/async_tx/async_memcpy.c: copy offload
+crypto/async_tx/async_memset.c: memory fill offload
+crypto/async_tx/async_xor.c: xor and xor zero sum offload
diff --git a/Documentation/devices.txt b/Documentation/devices.txt
index 8de132a..6c46730 100644
--- a/Documentation/devices.txt
+++ b/Documentation/devices.txt
@@ -94,6 +94,8 @@ Your cooperation is appreciated.
9 = /dev/urandom Faster, less secure random number gen.
10 = /dev/aio Asynchronous I/O notification interface
11 = /dev/kmsg Writes to this come out as printk's
+ 12 = /dev/oldmem Used by crashdump kernels to access
+ the memory of the kernel that crashed.
1 block RAM disk
0 = /dev/ram0 First RAM disk
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index a43d287..00928d2 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -197,6 +197,14 @@ Who: Len Brown <len.brown@intel.com>
---------------------------
+What: /proc/acpi/event
+When: February 2008
+Why: /proc/acpi/event has been replaced by events via the input layer
+ and netlink since 2.6.23.
+Who: Len Brown <len.brown@intel.com>
+
+---------------------------
+
What: Compaq touchscreen device emulation
When: Oct 2007
Files: drivers/input/tsdev.c
@@ -290,3 +298,11 @@ Why: All mthca hardware also supports MSI-X, which provides
Who: Roland Dreier <rolandd@cisco.com>
---------------------------
+
+What: sk98lin network driver
+When: Feburary 2008
+Why: In kernel tree version of driver is unmaintained. Sk98lin driver
+ replaced by the skge driver.
+Who: Stephen Hemminger <shemminger@linux-foundation.org>
+
+---------------------------
diff --git a/Documentation/filesystems/00-INDEX b/Documentation/filesystems/00-INDEX
index 57178588..59db1bc 100644
--- a/Documentation/filesystems/00-INDEX
+++ b/Documentation/filesystems/00-INDEX
@@ -32,6 +32,8 @@ directory-locking
- info about the locking scheme used for directory operations.
dlmfs.txt
- info on the userspace interface to the OCFS2 DLM.
+ecryptfs.txt
+ - docs on eCryptfs: stacked cryptographic filesystem for Linux.
ext2.txt
- info, mount options and specifications for the Ext2 filesystem.
ext3.txt
diff --git a/Documentation/filesystems/9p.txt b/Documentation/filesystems/9p.txt
index bbd8b28..cda6905c 100644
--- a/Documentation/filesystems/9p.txt
+++ b/Documentation/filesystems/9p.txt
@@ -6,12 +6,26 @@ ABOUT
v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol.
-This software was originally developed by Ron Minnich <rminnich@lanl.gov>
-and Maya Gokhale <maya@lanl.gov>. Additional development by Greg Watson
+This software was originally developed by Ron Minnich <rminnich@sandia.gov>
+and Maya Gokhale. Additional development by Greg Watson
<gwatson@lanl.gov> and most recently Eric Van Hensbergen
<ericvh@gmail.com>, Latchesar Ionkov <lucho@ionkov.net> and Russ Cox
<rsc@swtch.com>.
+The best detailed explanation of the Linux implementation and applications of
+the 9p client is available in the form of a USENIX paper:
+ http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html
+
+Other applications are described in the following papers:
+ * XCPU & Clustering
+ http://www.xcpu.org/xcpu-talk.pdf
+ * KVMFS: control file system for KVM
+ http://www.xcpu.org/kvmfs.pdf
+ * CellFS: A New ProgrammingModel for the Cell BE
+ http://www.xcpu.org/cellfs-talk.pdf
+ * PROSE I/O: Using 9p to enable Application Partitions
+ http://plan9.escet.urjc.es/iwp9/cready/PROSE_iwp9_2006.pdf
+
USAGE
=====
@@ -90,9 +104,9 @@ subset of the namespace by extending the path: '#U*'/tmp would just export
and export.
A Linux version of the 9p server is now maintained under the npfs project
-on sourceforge (http://sourceforge.net/projects/npfs). There is also a
-more stable single-threaded version of the server (named spfs) available from
-the same CVS repository.
+on sourceforge (http://sourceforge.net/projects/npfs). The currently
+maintained version is the single-threaded version of the server (named spfs)
+available from the same CVS repository.
There are user and developer mailing lists available through the v9fs project
on sourceforge (http://sourceforge.net/projects/v9fs).
diff --git a/Documentation/filesystems/ocfs2.txt b/Documentation/filesystems/ocfs2.txt
index 8ccf0c1..ed55238 100644
--- a/Documentation/filesystems/ocfs2.txt
+++ b/Documentation/filesystems/ocfs2.txt
@@ -28,11 +28,7 @@ Manish Singh <manish.singh@oracle.com>
Caveats
=======
Features which OCFS2 does not support yet:
- - sparse files
- extended attributes
- - shared writable mmap
- - loopback is supported, but data written will not
- be cluster coherent.
- quotas
- cluster aware flock
- cluster aware lockf
@@ -57,3 +53,12 @@ nointr Do not allow signals to interrupt cluster
atime_quantum=60(*) OCFS2 will not update atime unless this number
of seconds has passed since the last update.
Set to zero to always update atime.
+data=ordered (*) All data are forced directly out to the main file
+ system prior to its metadata being committed to the
+ journal.
+data=writeback Data ordering is not preserved, data may be written
+ into the main file system after its metadata has been
+ committed to the journal.
+preferred_slot=0(*) During mount, try to use this filesystem slot first. If
+ it is in use by another node, the first empty one found
+ will be chosen. Invalid values will be ignored.
diff --git a/Documentation/i2c/busses/i2c-piix4 b/Documentation/i2c/busses/i2c-piix4
index fa0c786..cf6b6cb 100644
--- a/Documentation/i2c/busses/i2c-piix4
+++ b/Documentation/i2c/busses/i2c-piix4
@@ -6,7 +6,7 @@ Supported adapters:
Datasheet: Publicly available at the Intel website
* ServerWorks OSB4, CSB5, CSB6 and HT-1000 southbridges
Datasheet: Only available via NDA from ServerWorks
- * ATI IXP200, IXP300, IXP400, SB600 and SB700 southbridges
+ * ATI IXP200, IXP300, IXP400, SB600, SB700 and SB800 southbridges
Datasheet: Not publicly available
* Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge
Datasheet: Publicly available at the SMSC website http://www.smsc.com
diff --git a/Documentation/input/iforce-protocol.txt b/Documentation/input/iforce-protocol.txt
index 95df4ca..8777d2d 100644
--- a/Documentation/input/iforce-protocol.txt
+++ b/Documentation/input/iforce-protocol.txt
@@ -1,254 +1,254 @@
-** Introduction
-This document describes what I managed to discover about the protocol used to
-specify force effects to I-Force 2.0 devices. None of this information comes
-from Immerse. That's why you should not trust what is written in this
-document. This document is intended to help understanding the protocol.
-This is not a reference. Comments and corrections are welcome. To contact me,
-send an email to: deneux@ifrance.com
-
-** WARNING **
-I may not be held responsible for any dammage or harm caused if you try to
-send data to your I-Force device based on what you read in this document.
-
-** Preliminary Notes:
-All values are hexadecimal with big-endian encoding (msb on the left). Beware,
-values inside packets are encoded using little-endian. Bytes whose roles are
-unknown are marked ??? Information that needs deeper inspection is marked (?)
-
-** General form of a packet **
-This is how packets look when the device uses the rs232 to communicate.
-2B OP LEN DATA CS
-CS is the checksum. It is equal to the exclusive or of all bytes.
-
-When using USB:
-OP DATA
-The 2B, LEN and CS fields have disappeared, probably because USB handles frames and
-data corruption is handled or unsignificant.
-
-First, I describe effects that are sent by the device to the computer
-
-** Device input state
-This packet is used to indicate the state of each button and the value of each
-axis
-OP= 01 for a joystick, 03 for a wheel
-LEN= Varies from device to device
-00 X-Axis lsb
-01 X-Axis msb
-02 Y-Axis lsb, or gas pedal for a wheel
-03 Y-Axis msb, or brake pedal for a wheel
-04 Throttle
-05 Buttons
-06 Lower 4 bits: Buttons
- Upper 4 bits: Hat
-07 Rudder
-
-** Device effects states
-OP= 02
-LEN= Varies
-00 ? Bit 1 (Value 2) is the value of the deadman switch
-01 Bit 8 is set if the effect is playing. Bits 0 to 7 are the effect id.
-02 ??
-03 Address of parameter block changed (lsb)
-04 Address of parameter block changed (msb)
-05 Address of second parameter block changed (lsb)
-... depending on the number of parameter blocks updated
-
-** Force effect **
-OP= 01
-LEN= 0e
-00 Channel (when playing several effects at the same time, each must be assigned a channel)
-01 Wave form
- Val 00 Constant
- Val 20 Square
- Val 21 Triangle
- Val 22 Sine
- Val 23 Sawtooth up
- Val 24 Sawtooth down
- Val 40 Spring (Force = f(pos))
- Val 41 Friction (Force = f(velocity)) and Inertia (Force = f(acceleration))
-
-
-02 Axes affected and trigger
- Bits 4-7: Val 2 = effect along one axis. Byte 05 indicates direction
- Val 4 = X axis only. Byte 05 must contain 5a
- Val 8 = Y axis only. Byte 05 must contain b4
- Val c = X and Y axes. Bytes 05 must contain 60
- Bits 0-3: Val 0 = No trigger
- Val x+1 = Button x triggers the effect
- When the whole byte is 0, cancel the previously set trigger
-
-03-04 Duration of effect (little endian encoding, in ms)
-
-05 Direction of effect, if applicable. Else, see 02 for value to assign.
-
-06-07 Minimum time between triggering.
-
-08-09 Address of periodicity or magnitude parameters
-0a-0b Address of attack and fade parameters, or ffff if none.
-*or*
-08-09 Address of interactive parameters for X-axis, or ffff if not applicable
-0a-0b Address of interactive parameters for Y-axis, or ffff if not applicable
-
-0c-0d Delay before execution of effect (little endian encoding, in ms)
-
-
-** Time based parameters **
-
-*** Attack and fade ***
-OP= 02
-LEN= 08
-00-01 Address where to store the parameteres
-02-03 Duration of attack (little endian encoding, in ms)
-04 Level at end of attack. Signed byte.
-05-06 Duration of fade.
-07 Level at end of fade.
-
-*** Magnitude ***
-OP= 03
-LEN= 03
-00-01 Address
-02 Level. Signed byte.
-
-*** Periodicity ***
-OP= 04
-LEN= 07
-00-01 Address
-02 Magnitude. Signed byte.
-03 Offset. Signed byte.
-04 Phase. Val 00 = 0 deg, Val 40 = 90 degs.
-05-06 Period (little endian encoding, in ms)
-
-** Interactive parameters **
-OP= 05
-LEN= 0a
-00-01 Address
-02 Positive Coeff
-03 Negative Coeff
-04+05 Offset (center)
-06+07 Dead band (Val 01F4 = 5000 (decimal))
-08 Positive saturation (Val 0a = 1000 (decimal) Val 64 = 10000 (decimal))
-09 Negative saturation
-
-The encoding is a bit funny here: For coeffs, these are signed values. The
-maximum value is 64 (100 decimal), the min is 9c.
-For the offset, the minimum value is FE0C, the maximum value is 01F4.
-For the deadband, the minimum value is 0, the max is 03E8.
-
-** Controls **
-OP= 41
-LEN= 03
-00 Channel
-01 Start/Stop
- Val 00: Stop
- Val 01: Start and play once.
- Val 41: Start and play n times (See byte 02 below)
-02 Number of iterations n.
-
-** Init **
-
-*** Querying features ***
-OP= ff
-Query command. Length varies according to the query type.
-The general format of this packet is:
-ff 01 QUERY [INDEX] CHECKSUM
-reponses are of the same form:
-FF LEN QUERY VALUE_QUERIED CHECKSUM2
-where LEN = 1 + length(VALUE_QUERIED)
-
-**** Query ram size ****
-QUERY = 42 ('B'uffer size)
-The device should reply with the same packet plus two additionnal bytes
-containing the size of the memory:
-ff 03 42 03 e8 CS would mean that the device has 1000 bytes of ram available.
-
-**** Query number of effects ****
-QUERY = 4e ('N'umber of effects)
-The device should respond by sending the number of effects that can be played
-at the same time (one byte)
-ff 02 4e 14 CS would stand for 20 effects.
-
-**** Vendor's id ****
-QUERY = 4d ('M'anufacturer)
-Query the vendors'id (2 bytes)
-
-**** Product id *****
-QUERY = 50 ('P'roduct)
-Query the product id (2 bytes)
-
-**** Open device ****
-QUERY = 4f ('O'pen)
-No data returned.
-
-**** Close device *****
-QUERY = 43 ('C')lose
-No data returned.
-
-**** Query effect ****
-QUERY = 45 ('E')
-Send effect type.
-Returns nonzero if supported (2 bytes)
-
-**** Firmware Version ****
-QUERY = 56 ('V'ersion)
-Sends back 3 bytes - major, minor, subminor
-
-*** Initialisation of the device ***
-
-**** Set Control ****
-!!! Device dependent, can be different on different models !!!
-OP= 40 <idx> <val> [<val>]
-LEN= 2 or 3
-00 Idx
- Idx 00 Set dead zone (0..2048)
- Idx 01 Ignore Deadman sensor (0..1)
- Idx 02 Enable comm watchdog (0..1)
- Idx 03 Set the strength of the spring (0..100)
- Idx 04 Enable or disable the spring (0/1)
- Idx 05 Set axis saturation threshold (0..2048)
-
-**** Set Effect State ****
-OP= 42 <val>
-LEN= 1
-00 State
- Bit 3 Pause force feedback
- Bit 2 Enable force feedback
- Bit 0 Stop all effects
-
-**** Set overall gain ****
-OP= 43 <val>
-LEN= 1
-00 Gain
- Val 00 = 0%
- Val 40 = 50%
- Val 80 = 100%
-
-** Parameter memory **
-
-Each device has a certain amount of memory to store parameters of effects.
-The amount of RAM may vary, I encountered values from 200 to 1000 bytes. Below
-is the amount of memory apparently needed for every set of parameters:
- - period : 0c
- - magnitude : 02
- - attack and fade : 0e
- - interactive : 08
-
-** Appendix: How to study the protocol ? **
-
-1. Generate effects using the force editor provided with the DirectX SDK, or use Immersion Studio (freely available at their web site in the developer section: www.immersion.com)
-2. Start a soft spying RS232 or USB (depending on where you connected your joystick/wheel). I used ComPortSpy from fCoder (alpha version!)
-3. Play the effect, and watch what happens on the spy screen.
-
-A few words about ComPortSpy:
-At first glance, this soft seems, hum, well... buggy. In fact, data appear with a few seconds latency. Personnaly, I restart it every time I play an effect.
-Remember it's free (as in free beer) and alpha!
-
-** URLS **
-Check www.immerse.com for Immersion Studio, and www.fcoder.com for ComPortSpy.
-
-** Author of this document **
-Johann Deneux <deneux@ifrance.com>
-Home page at http://www.esil.univ-mrs.fr/~jdeneux/projects/ff/
-
-Additions by Vojtech Pavlik.
-
-I-Force is trademark of Immersion Corp.
+** Introduction
+This document describes what I managed to discover about the protocol used to
+specify force effects to I-Force 2.0 devices. None of this information comes
+from Immerse. That's why you should not trust what is written in this
+document. This document is intended to help understanding the protocol.
+This is not a reference. Comments and corrections are welcome. To contact me,
+send an email to: deneux@ifrance.com
+
+** WARNING **
+I may not be held responsible for any dammage or harm caused if you try to
+send data to your I-Force device based on what you read in this document.
+
+** Preliminary Notes:
+All values are hexadecimal with big-endian encoding (msb on the left). Beware,
+values inside packets are encoded using little-endian. Bytes whose roles are
+unknown are marked ??? Information that needs deeper inspection is marked (?)
+
+** General form of a packet **
+This is how packets look when the device uses the rs232 to communicate.
+2B OP LEN DATA CS
+CS is the checksum. It is equal to the exclusive or of all bytes.
+
+When using USB:
+OP DATA
+The 2B, LEN and CS fields have disappeared, probably because USB handles frames and
+data corruption is handled or unsignificant.
+
+First, I describe effects that are sent by the device to the computer
+
+** Device input state
+This packet is used to indicate the state of each button and the value of each
+axis
+OP= 01 for a joystick, 03 for a wheel
+LEN= Varies from device to device
+00 X-Axis lsb
+01 X-Axis msb
+02 Y-Axis lsb, or gas pedal for a wheel
+03 Y-Axis msb, or brake pedal for a wheel
+04 Throttle
+05 Buttons
+06 Lower 4 bits: Buttons
+ Upper 4 bits: Hat
+07 Rudder
+
+** Device effects states
+OP= 02
+LEN= Varies
+00 ? Bit 1 (Value 2) is the value of the deadman switch
+01 Bit 8 is set if the effect is playing. Bits 0 to 7 are the effect id.
+02 ??
+03 Address of parameter block changed (lsb)
+04 Address of parameter block changed (msb)
+05 Address of second parameter block changed (lsb)
+... depending on the number of parameter blocks updated
+
+** Force effect **
+OP= 01
+LEN= 0e
+00 Channel (when playing several effects at the same time, each must be assigned a channel)
+01 Wave form
+ Val 00 Constant
+ Val 20 Square
+ Val 21 Triangle
+ Val 22 Sine
+ Val 23 Sawtooth up
+ Val 24 Sawtooth down
+ Val 40 Spring (Force = f(pos))
+ Val 41 Friction (Force = f(velocity)) and Inertia (Force = f(acceleration))
+
+
+02 Axes affected and trigger
+ Bits 4-7: Val 2 = effect along one axis. Byte 05 indicates direction
+ Val 4 = X axis only. Byte 05 must contain 5a
+ Val 8 = Y axis only. Byte 05 must contain b4
+ Val c = X and Y axes. Bytes 05 must contain 60
+ Bits 0-3: Val 0 = No trigger
+ Val x+1 = Button x triggers the effect
+ When the whole byte is 0, cancel the previously set trigger
+
+03-04 Duration of effect (little endian encoding, in ms)
+
+05 Direction of effect, if applicable. Else, see 02 for value to assign.
+
+06-07 Minimum time between triggering.
+
+08-09 Address of periodicity or magnitude parameters
+0a-0b Address of attack and fade parameters, or ffff if none.
+*or*
+08-09 Address of interactive parameters for X-axis, or ffff if not applicable
+0a-0b Address of interactive parameters for Y-axis, or ffff if not applicable
+
+0c-0d Delay before execution of effect (little endian encoding, in ms)
+
+
+** Time based parameters **
+
+*** Attack and fade ***
+OP= 02
+LEN= 08
+00-01 Address where to store the parameteres
+02-03 Duration of attack (little endian encoding, in ms)
+04 Level at end of attack. Signed byte.
+05-06 Duration of fade.
+07 Level at end of fade.
+
+*** Magnitude ***
+OP= 03
+LEN= 03
+00-01 Address
+02 Level. Signed byte.
+
+*** Periodicity ***
+OP= 04
+LEN= 07
+00-01 Address
+02 Magnitude. Signed byte.
+03 Offset. Signed byte.
+04 Phase. Val 00 = 0 deg, Val 40 = 90 degs.
+05-06 Period (little endian encoding, in ms)
+
+** Interactive parameters **
+OP= 05
+LEN= 0a
+00-01 Address
+02 Positive Coeff
+03 Negative Coeff
+04+05 Offset (center)
+06+07 Dead band (Val 01F4 = 5000 (decimal))
+08 Positive saturation (Val 0a = 1000 (decimal) Val 64 = 10000 (decimal))
+09 Negative saturation
+
+The encoding is a bit funny here: For coeffs, these are signed values. The
+maximum value is 64 (100 decimal), the min is 9c.
+For the offset, the minimum value is FE0C, the maximum value is 01F4.
+For the deadband, the minimum value is 0, the max is 03E8.
+
+** Controls **
+OP= 41
+LEN= 03
+00 Channel
+01 Start/Stop
+ Val 00: Stop
+ Val 01: Start and play once.
+ Val 41: Start and play n times (See byte 02 below)
+02 Number of iterations n.
+
+** Init **
+
+*** Querying features ***
+OP= ff
+Query command. Length varies according to the query type.
+The general format of this packet is:
+ff 01 QUERY [INDEX] CHECKSUM
+reponses are of the same form:
+FF LEN QUERY VALUE_QUERIED CHECKSUM2
+where LEN = 1 + length(VALUE_QUERIED)
+
+**** Query ram size ****
+QUERY = 42 ('B'uffer size)
+The device should reply with the same packet plus two additionnal bytes
+containing the size of the memory:
+ff 03 42 03 e8 CS would mean that the device has 1000 bytes of ram available.
+
+**** Query number of effects ****
+QUERY = 4e ('N'umber of effects)
+The device should respond by sending the number of effects that can be played
+at the same time (one byte)
+ff 02 4e 14 CS would stand for 20 effects.
+
+**** Vendor's id ****
+QUERY = 4d ('M'anufacturer)
+Query the vendors'id (2 bytes)
+
+**** Product id *****
+QUERY = 50 ('P'roduct)
+Query the product id (2 bytes)
+
+**** Open device ****
+QUERY = 4f ('O'pen)
+No data returned.
+
+**** Close device *****
+QUERY = 43 ('C')lose
+No data returned.
+
+**** Query effect ****
+QUERY = 45 ('E')
+Send effect type.
+Returns nonzero if supported (2 bytes)
+
+**** Firmware Version ****
+QUERY = 56 ('V'ersion)
+Sends back 3 bytes - major, minor, subminor
+
+*** Initialisation of the device ***
+
+**** Set Control ****
+!!! Device dependent, can be different on different models !!!
+OP= 40 <idx> <val> [<val>]
+LEN= 2 or 3
+00 Idx
+ Idx 00 Set dead zone (0..2048)
+ Idx 01 Ignore Deadman sensor (0..1)
+ Idx 02 Enable comm watchdog (0..1)
+ Idx 03 Set the strength of the spring (0..100)
+ Idx 04 Enable or disable the spring (0/1)
+ Idx 05 Set axis saturation threshold (0..2048)
+
+**** Set Effect State ****
+OP= 42 <val>
+LEN= 1
+00 State
+ Bit 3 Pause force feedback
+ Bit 2 Enable force feedback
+ Bit 0 Stop all effects
+
+**** Set overall gain ****
+OP= 43 <val>
+LEN= 1
+00 Gain
+ Val 00 = 0%
+ Val 40 = 50%
+ Val 80 = 100%
+
+** Parameter memory **
+
+Each device has a certain amount of memory to store parameters of effects.
+The amount of RAM may vary, I encountered values from 200 to 1000 bytes. Below
+is the amount of memory apparently needed for every set of parameters:
+ - period : 0c
+ - magnitude : 02
+ - attack and fade : 0e
+ - interactive : 08
+
+** Appendix: How to study the protocol ? **
+
+1. Generate effects using the force editor provided with the DirectX SDK, or use Immersion Studio (freely available at their web site in the developer section: www.immersion.com)
+2. Start a soft spying RS232 or USB (depending on where you connected your joystick/wheel). I used ComPortSpy from fCoder (alpha version!)
+3. Play the effect, and watch what happens on the spy screen.
+
+A few words about ComPortSpy:
+At first glance, this soft seems, hum, well... buggy. In fact, data appear with a few seconds latency. Personnaly, I restart it every time I play an effect.
+Remember it's free (as in free beer) and alpha!
+
+** URLS **
+Check www.immerse.com for Immersion Studio, and www.fcoder.com for ComPortSpy.
+
+** Author of this document **
+Johann Deneux <deneux@ifrance.com>
+Home page at http://www.esil.univ-mrs.fr/~jdeneux/projects/ff/
+
+Additions by Vojtech Pavlik.
+
+I-Force is trademark of Immersion Corp.
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 975f029..4d175c7 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -468,9 +468,6 @@ and is between 256 and 4096 characters. It is defined in the file
Format:
<first_slot>,<last_slot>,<port>,<enum_bit>[,<debug>]
- cpia_pp= [HW,PPT]
- Format: { parport<nr> | auto | none }
-
crashkernel=nn[KMG]@ss[KMG]
[KNL] Reserve a chunk of physical memory to
hold a kernel to switch to with kexec on panic.
@@ -952,14 +949,10 @@ and is between 256 and 4096 characters. It is defined in the file
Format: <1-256>
maxcpus= [SMP] Maximum number of processors that an SMP kernel
- should make use of.
- Using "nosmp" or "maxcpus=0" will disable SMP
- entirely (the MPS table probe still happens, though).
- A command-line option of "maxcpus=<NUM>", where <NUM>
- is an integer greater than 0, limits the maximum number
- of CPUs activated in SMP mode to <NUM>.
- Using "maxcpus=1" on an SMP kernel is the trivial
- case of an SMP kernel with only one CPU.
+ should make use of. maxcpus=n : n >= 0 limits the
+ kernel to using 'n' processors. n=0 is a special case,
+ it is equivalent to "nosmp", which also disables
+ the IO APIC.
max_addr=[KMG] [KNL,BOOT,ia64] All physical memory greater than or
equal to this physical address is ignored.
@@ -1184,7 +1177,8 @@ and is between 256 and 4096 characters. It is defined in the file
nosep [BUGS=X86-32] Disables x86 SYSENTER/SYSEXIT support.
- nosmp [SMP] Tells an SMP kernel to act as a UP kernel.
+ nosmp [SMP] Tells an SMP kernel to act as a UP kernel,
+ and disable the IO APIC. legacy for "maxcpus=0".
nosoftlockup [KNL] Disable the soft-lockup detector.
@@ -1826,6 +1820,10 @@ and is between 256 and 4096 characters. It is defined in the file
-1: disable all active trip points in all thermal zones
<degrees C>: override all lowest active trip points
+ thermal.crt= [HW,ACPI]
+ -1: disable all critical trip points in all thermal zones
+ <degrees C>: lower all critical trip points
+
thermal.nocrt= [HW,ACPI]
Set to disable actions on ACPI thermal zone
critical and hot trip points.
diff --git a/Documentation/ko_KR/HOWTO b/Documentation/ko_KR/HOWTO
new file mode 100644
index 0000000..b51d7ca
--- /dev/null
+++ b/Documentation/ko_KR/HOWTO
@@ -0,0 +1,623 @@
+NOTE:
+This is a version of Documentation/HOWTO translated into korean
+This document is maintained by minchan Kim < minchan.kim@gmail.com>
+If you find any difference between this document and the original file or
+a problem with the translation, please contact the maintainer of this file.
+
+Please also note that the purpose of this file is to be easier to
+read for non English (read: korean) speakers and is not intended as
+a fork. So if you have any comments or updates for this file please
+try to update the original English file first.
+
+==================================
+์ด ๋ฌธ์„œ๋Š”
+Documentation/HOWTO
+์˜ ํ•œ๊ธ€ ๋ฒˆ์—ญ์ž…๋‹ˆ๋‹ค.
+
+์—ญ์ž๏ผš ๊น€๋ฏผ์ฐฌ <minchan.kim@gmail.com >
+๊ฐ์ˆ˜๏ผš ์ด์ œ์ด๋ฏธ <jamee.lee@samsung.com>
+==================================
+
+์–ด๋–ป๊ฒŒ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ์„ ํ•˜๋Š”๊ฐ€
+---------------------------------
+
+์ด ๋ฌธ์„œ๋Š” ์ปค๋„ ๊ฐœ๋ฐœ์— ์žˆ์–ด ๊ฐ€์žฅ ์ค‘์š”ํ•œ ๋ฌธ์„œ์ด๋‹ค. ์ด ๋ฌธ์„œ๋Š”
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ์ž๊ฐ€ ๋˜๋Š” ๋ฒ•๊ณผ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ ์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ์ผํ•˜๋Š”
+๋ฒ•์„ ๋‹ด๊ณ ์žˆ๋‹ค. ์ปค๋„ ํ”„๋กœ๊ทธ๋ž˜๋ฐ์˜๊ธฐ์ˆ ์ ์ธ ์ธก๋ฉด๊ณผ ๊ด€๋ จ๋œ ๋‚ด์šฉ๋“ค์€
+ํฌํ•จํ•˜์ง€ ์•Š์œผ๋ ค๊ณ  ํ•˜์˜€์ง€๋งŒ ์˜ฌ๋ฐ”์œผ๋กœ ์—ฌ๋Ÿฌ๋ถ„์„ ์•ˆ๋‚ดํ•˜๋Š” ๋ฐ ๋„์›€์ด
+๋  ๊ฒƒ์ด๋‹ค.
+
+์ด ๋ฌธ์„œ์—์„œ ์˜ค๋ž˜๋œ ๊ฒƒ์„ ๋ฐœ๊ฒฌํ•˜๋ฉด ๋ฌธ์„œ์˜ ์•„๋ž˜์ชฝ์— ๋‚˜์—ด๋œ ๋ฉ”์ธํŠธ๋„ˆ์—๊ฒŒ
+ํŒจ์น˜๋ฅผ ๋ณด๋‚ด๋‹ฌ๋ผ.
+
+
+์†Œ๊ฐœ
+----
+
+์ž, ์—ฌ๋Ÿฌ๋ถ„์€ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ์ž๊ฐ€ ๋˜๋Š” ๋ฒ•์„ ๋ฐฐ์šฐ๊ณ  ์‹ถ์€๊ฐ€? ์•„๋‹ˆ๋ฉด
+์ƒ์‚ฌ๋กœ๋ถ€ํ„ฐ"์ด ์žฅ์น˜๋ฅผ ์œ„ํ•œ ๋ฆฌ๋ˆ…์Šค ๋“œ๋ผ์ด๋ฒ„๋ฅผ ์ž‘์„ฑํ•˜์‹œ์˜ค"๋ผ๋Š” ๋ง์„
+๋“ค์—ˆ๋Š”๊ฐ€? ์ด ๋ฌธ์„œ๋Š” ์—ฌ๋Ÿฌ๋ถ„์ด ๊ฒช๊ฒŒ ๋  ๊ณผ์ •๊ณผ ์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ์ผํ•˜๋Š” ๋ฒ•์„
+์กฐ์–ธํ•˜์—ฌ ์—ฌ๋Ÿฌ๋ถ„์˜ ๋ชฉ์ ์„ ๋‹ฌ์„ฑํ•˜๊ธฐ ์œ„ํ•ด ํ•„์š”ํ•œ ๊ฒƒ ๋ชจ๋‘๋ฅผ ์•Œ๋ ค์ฃผ๋Š”
+๊ฒƒ์ด๋‹ค.
+
+์ปค๋„์€ ๋Œ€๋ถ€๋ถ„์€ C๋กœ ์ž‘์„ฑ๋˜์—ˆ์–ด๊ณ  ๋ช‡๋ช‡ ์•„ํ‚คํ…์ณ์˜ ์˜์กด์ ์ธ ๋ถ€๋ถ„์€
+์–ด์…ˆ๋ธ”๋ฆฌ๋กœ ์ž‘์„ฑ๋˜์—ˆ๋‹ค. ์ปค๋„ ๊ฐœ๋ฐœ์„ ์œ„ํ•ด C๋ฅผ ์ž˜ ์ดํ•ดํ•˜๊ณ  ์žˆ์–ด์•ผ ํ•œ๋‹ค.
+์—ฌ๋Ÿฌ๋ถ„์ด ํŠน์ • ์•„ํ‚คํ…์ณ์˜ low-level ๊ฐœ๋ฐœ์„ ํ•  ๊ฒƒ์ด ์•„๋‹ˆ๋ผ๋ฉด
+์–ด์…ˆ๋ธ”๋ฆฌ(ํŠน์ • ์•„ํ‚คํ…์ณ)๋Š” ์ž˜ ์•Œ์•„์•ผ ํ•  ํ•„์š”๋Š” ์—†๋‹ค.
+๋‹ค์Œ์˜ ์ฐธ๊ณ ์„œ์ ๋“ค์€ ๊ธฐ๋ณธ์— ์ถฉ์‹คํ•œ C ๊ต์œก์ด๋‚˜ ์ˆ˜๋…„๊ฐ„์˜ ๊ฒฝํ—˜์— ๊ฒฌ์ฃผ์ง€๋Š”
+๋ชปํ•˜์ง€๋งŒ ์ ์–ด๋„ ์ฐธ๊ณ  ์šฉ๋„๋กœ๋Š” ์ข‹์„ ๊ฒƒ์ด๋‹ค
+ - "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
+ - "Practical C Programming" by Steve Oualline [O'Reilly]
+ - "C: A Reference Manual" by Harbison and Steele [Prentice Hall]
+
+์ปค๋„์€ GNU C์™€ GNU ํˆด์ฒด์ธ์„ ์‚ฌ์šฉํ•˜์—ฌ ์ž‘์„ฑ๋˜์—ˆ๋‹ค. ์ด ํˆด๋“ค์€ ISO C89 ํ‘œ์ค€์„
+๋”ฐ๋ฅด๋Š” ๋ฐ˜๋ฉด ํ‘œ์ค€์— ์žˆ์ง€ ์•Š์€ ๋งŽ์€ ํ™•์žฅ๊ธฐ๋Šฅ๋„ ๊ฐ€์ง€๊ณ  ์žˆ๋‹ค. ์ปค๋„์€ ํ‘œ์ค€ C
+๋ผ์ด๋ธŒ๋Ÿฌ๋ฆฌ์™€๋Š” ๊ด€๊ณ„์—†์ด freestanding C ํ™˜๊ฒฝ์ด์–ด์„œ C ํ‘œ์ค€์˜ ์ผ๋ถ€๋Š”
+์ง€์›๋˜์ง€ ์•Š๋Š”๋‹ค. ์ž„์˜์˜ long long ๋‚˜๋ˆ„๊ธฐ๋‚˜ floating point๋Š” ์ง€์›๋˜์ง€ ์•Š๋Š”๋‹ค.
+๋•Œ๋ก  ์ด๋Ÿฐ ์ด์œ ๋กœ ์ปค๋„์ด ๊ทธ๋Ÿฐ ํ™•์žฅ ๊ธฐ๋Šฅ์„ ๊ฐ€์ง„ ํˆด์ฒด์ธ์„ ๊ฐ€์ง€๊ณ  ๋งŒ๋“ค์–ด์กŒ๋‹ค๋Š”
+๊ฒƒ์ด ์ดํ•ดํ•˜๊ธฐ ์–ด๋ ค์šธ ์ˆ˜๋„ ์žˆ๊ณ  ๊ฒŒ๋‹ค๊ฐ€ ๋ถˆํ–‰ํ•˜๊ฒŒ๋„ ๊ทธ๋Ÿฐ ๊ฒƒ์„ ์ •ํ™•ํ•˜๊ฒŒ ์„ค๋ช…ํ•˜๋Š”
+์–ด๋–ค ์ฐธ๊ณ ๋ฌธ์„œ๋„ ์žˆ์ง€ ์•Š๋‹ค. ์ •๋ณด๋ฅผ ์–ป๊ธฐ ์œ„ํ•ด์„œ๋Š” gcc info (`info gcc`)ํŽ˜์ด์ง€๋ฅผ
+์‚ดํŽด๋ณด๋ผ.
+
+์—ฌ๋Ÿฌ๋ถ„์€ ๊ธฐ์กด์˜ ๊ฐœ๋ฐœ ์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ์ผํ•˜๋Š” ๋ฒ•์„ ๋ฐฐ์šฐ๋ ค๊ณ  ํ•˜๊ณ  ์žˆ๋‹ค๋Š” ๊ฒƒ์„
+๊ธฐ์–ตํ•˜๋ผ. ์ฝ”๋”ฉ, ์Šคํƒ€์ผ, ์ ˆ์ฐจ์— ๊ด€ํ•œ ํ›Œ๋ฅญํ•œ ํ‘œ์ค€์„ ๊ฐ€์ง„ ์‚ฌ๋žŒ๋“ค์ด ๋ชจ์ธ
+๋‹ค์–‘ํ•œ ๊ทธ๋ฃน์ด ์žˆ๋‹ค. ์ด ํ‘œ์ค€๋“ค์€ ์˜ค๋žœ๋™์•ˆ ํฌ๊ณ  ์ง€์—ญ์ ์œผ๋กœ ๋ถ„์‚ฐ๋œ ํŒ€๋“ค์—
+์˜ํ•ด ๊ฐ€์žฅ ์ข‹์€ ๋ฐฉ๋ฒ•์œผ๋กœ ์ผํ•˜๊ธฐ์œ„ํ•˜์—ฌ ์ฐพ์€ ๊ฒƒ์„ ๊ธฐ์ดˆ๋กœ ๋งŒ๋“ค์–ด์ ธ์™”๋‹ค.
+๊ทธ ํ‘œ์ค€๋“ค์€ ๋ฌธ์„œํ™”๊ฐ€ ์ž˜ ๋˜์–ด ์žˆ๊ธฐ ๋•Œ๋ฌธ์— ๊ฐ€๋Šฅํ•œํ•œ ๋ฏธ๋ฆฌ ๋งŽ์€ ํ‘œ์ค€๋“ค์—
+๊ด€ํ•˜์—ฌ ๋ฐฐ์šฐ๋ ค๊ณ  ์‹œ๋„ํ•˜๋ผ. ๋‹ค๋ฅธ ์‚ฌ๋žŒ๋“ค์€ ์—ฌ๋Ÿฌ๋ถ„์ด๋‚˜ ์—ฌ๋Ÿฌ๋ถ„์˜ ํšŒ์‚ฌ๊ฐ€
+์ผํ•˜๋Š” ๋ฐฉ์‹์— ์ ์‘ํ•˜๋Š” ๊ฒƒ์„ ์›ํ•˜์ง€๋Š” ์•Š๋Š”๋‹ค.
+
+
+๋ฒ•์  ๋ฌธ์ œ
+---------
+
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ์†Œ์Šค ์ฝ”๋“œ๋Š” GPL๋กœ ๋ฐฐํฌ(release)๋˜์—ˆ๋‹ค. ์†Œ์ŠคํŠธ๋ฆฌ์˜ ๋ฉ”์ธ
+๋””๋ ‰ํ† ๋ฆฌ์— ์žˆ๋Š” ๋ผ์ด์„ผ์Šค์— ๊ด€ํ•˜์—ฌ ์ƒ์„ธํ•˜๊ฒŒ ์“ฐ์—ฌ ์žˆ๋Š” COPYING์ด๋ผ๋Š”
+ํŒŒ์ผ์„ ๋ด๋ผ.์—ฌ๋Ÿฌ๋ถ„์ด ๋ผ์ด์„ผ์Šค์— ๊ด€ํ•œ ๋” ๊นŠ์€ ๋ฌธ์ œ๋ฅผ ๊ฐ€์ง€๊ณ  ์žˆ๋‹ค๋ฉด
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์— ๋ฌป์ง€๋ง๊ณ  ๋ณ€ํ˜ธ์‚ฌ์™€ ์—ฐ๋ฝํ•˜๋ผ. ๋ฉ”์ผ๋ง
+๋ฆฌ์ŠคํŠธ๋“ค์— ์žˆ๋Š” ์‚ฌ๋žŒ๋“ค์€ ๋ณ€ํ˜ธ์‚ฌ๊ฐ€ ์•„๋‹ˆ๊ธฐ ๋•Œ๋ฌธ์— ๋ฒ•์  ๋ฌธ์ œ์— ๊ด€ํ•˜์—ฌ
+๊ทธ๋“ค์˜ ๋ง์— ์˜์ง€ํ•ด์„œ๋Š” ์•ˆ๋œ๋‹ค.
+
+GPL์— ๊ด€ํ•œ ์žฆ์€ ์งˆ๋ฌธ๋“ค๊ณผ ๋‹ต๋ณ€๋“ค์€ ๋‹ค์Œ์„ ์ฐธ์กฐํ•˜๋ผ.
+ http://www.gnu.org/licenses/gpl-faq.html
+
+
+๋ฌธ์„œ
+----
+
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ์†Œ์Šค ํŠธ๋ฆฌ๋Š” ์ปค๋„ ์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ์ผํ•˜๋Š” ๋ฒ•์„ ๋ฐฐ์šฐ๊ธฐ ์œ„ํ•œ ๋งŽ์€
+๊ท€์ค‘ํ•œ ๋ฌธ์„œ๋“ค์„ ๊ฐ€์ง€๊ณ  ์žˆ๋‹ค. ์ƒˆ๋กœ์šด ๊ธฐ๋Šฅ๋“ค์ด ์ปค๋„์— ๋“ค์–ด๊ฐ€๊ฒŒ ๋  ๋•Œ,
+๊ทธ ๊ธฐ๋Šฅ์„ ์–ด๋–ป๊ฒŒ ์‚ฌ์šฉํ•˜๋Š”์ง€์— ๊ด€ํ•œ ์„ค๋ช…์„ ์œ„ํ•˜์—ฌ ์ƒˆ๋กœ์šด ๋ฌธ์„œ ํŒŒ์ผ์„
+์ถ”๊ฐ€ํ•˜๋Š” ๊ฒƒ์„ ๊ถŒ์žฅํ•œ๋‹ค. ์ปค๋„์ด ์œ ์ €์ŠคํŽ˜์ด์Šค๋กœ ๋…ธ์ถœํ•˜๋Š” ์ธํ„ฐํŽ˜์ด์Šค๋ฅผ
+๋ณ€๊ฒฝํ•˜๊ฒŒ ๋˜๋ฉด ๋ณ€๊ฒฝ์„ ์„ค๋ช…ํ•˜๋Š” ๋ฉ”๋‰ด์–ผ ํŽ˜์ด์ง€๋“ค์— ๋Œ€ํ•œ ํŒจ์น˜๋‚˜ ์ •๋ณด๋ฅผ
+mtk-manpages@gmx.net์˜ ๋ฉ”์ธํŠธ๋„ˆ์—๊ฒŒ ๋ณด๋‚ผ ๊ฒƒ์„ ๊ถŒ์žฅํ•œ๋‹ค.
+
+๋‹ค์Œ์€ ์ปค๋„ ์†Œ์Šค ํŠธ๋ฆฌ์— ์žˆ๋Š” ์ฝ์–ด์•ผ ํ•  ํŒŒ์ผ๋“ค์˜ ๋ฆฌ์ŠคํŠธ์ด๋‹ค.
+ README
+ ์ด ํŒŒ์ผ์€ ๋ฆฌ๋ˆ…์Šค ์ปค๋„์— ๊ด€ํ•˜์—ฌ ๊ฐ„๋‹จํ•œ ๋ฐฐ๊ฒฝ ์„ค๋ช…๊ณผ ์ปค๋„์„ ์„ค์ •ํ•˜๊ณ 
+ ๋นŒ๋“œํ•˜๊ธฐ ์œ„ํ•ด ํ•„์š”ํ•œ ๊ฒƒ์„ ์„ค๋ช…ํ•œ๋‹ค. ์ปค๋„์— ์ž…๋ฌธํ•˜๋Š” ์‚ฌ๋žŒ๋“ค์€ ์—ฌ๊ธฐ์„œ
+ ์‹œ์ž‘ํ•ด์•ผ ํ•œ๋‹ค.
+
+ Documentation/Changes
+ ์ด ํŒŒ์ผ์€ ์ปค๋„์„ ์„ฑ๊ณต์ ์œผ๋กœ ๋นŒ๋“œํ•˜๊ณ  ์‹คํ–‰์‹œํ‚ค๊ธฐ ์œ„ํ•ด ํ•„์š”ํ•œ ๋‹ค์–‘ํ•œ
+ ์†Œํ”„ํŠธ์›จ์–ด ํŒจํ‚ค์ง€๋“ค์˜ ์ตœ์†Œ ๋ฒ„์ ผ์„ ๋‚˜์—ดํ•œ๋‹ค.
+
+ Documentation/CodingStyle
+ ์ด ๋ฌธ์„œ๋Š” ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ์ฝ”๋”ฉ ์Šคํƒ€์ผ๊ณผ ๊ทธ๋ ‡๊ฒŒ ํ•œ ๋ช‡๋ช‡ ์ด์œ ๋ฅผ ์„ค๋ช…ํ•œ๋‹ค.
+ ๋ชจ๋“  ์ƒˆ๋กœ์šด ์ฝ”๋“œ๋Š” ์ด ๋ฌธ์„œ์— ๊ฐ€์ด๋“œ๋ผ์ธ๋“ค์„ ๋”ฐ๋ผ์•ผ ํ•œ๋‹ค. ๋Œ€๋ถ€๋ถ„์˜
+ ๋ฉ”์ธํŠธ๋„ˆ๋“ค์€ ์ด ๊ทœ์น™์„ ๋”ฐ๋ฅด๋Š” ํŒจ์น˜๋“ค๋งŒ์„ ๋ฐ›์•„๋“ค์ผ ๊ฒƒ์ด๊ณ  ๋งŽ์€ ์‚ฌ๋žŒ๋“ค์ด
+ ๊ทธ ํŒจ์น˜๊ฐ€ ์˜ฌ๋ฐ”๋ฅธ ์Šคํƒ€์ผ์ผ ๊ฒฝ์šฐ๋งŒ ์ฝ”๋“œ๋ฅผ ๊ฒ€ํ† ํ•  ๊ฒƒ์ด๋‹ค.
+
+ Documentation/SubmittingPatches
+ Documentation/SubmittingDrivers
+ ์ด ํŒŒ์ผ๋“ค์€ ์„ฑ๊ณต์ ์œผ๋กœ ํŒจ์น˜๋ฅผ ๋งŒ๋“ค๊ณ  ๋ณด๋‚ด๋Š” ๋ฒ•์„ ๋‹ค์Œ์˜ ๋‚ด์šฉ๋“ค๋กœ
+ ๊ต‰์žฅํžˆ ์ƒ์„ธํžˆ ์„ค๋ช…ํ•˜๊ณ  ์žˆ๋‹ค(๊ทธ๋Ÿฌ๋‚˜ ๋‹ค์Œ์œผ๋กœ ํ•œ์ •๋˜์ง„ ์•Š๋Š”๋‹ค).
+ - Email ๋‚ด์šฉ๋“ค
+ - Email ์–‘์‹
+ - ๊ทธ๊ฒƒ์„ ๋ˆ„๊ตฌ์—๊ฒŒ ๋ณด๋‚ผ์ง€
+ ์ด๋Ÿฌํ•œ ๊ทœ์น™๋“ค์„ ๋”ฐ๋ฅด๋Š” ๊ฒƒ์ด ์„ฑ๊ณต์„ ๋ณด์žฅํ•˜์ง„ ์•Š๋Š”๋‹ค(์™œ๋ƒํ•˜๋ฉด ๋ชจ๋“ 
+ ํŒจ์น˜๋“ค์€ ๋‚ด์šฉ๊ณผ ์Šคํƒ€์ผ์— ๊ด€ํ•˜์—ฌ ๋ฉด๋ฐ€ํžˆ ๊ฒ€ํ† ๋˜๊ธฐ ๋•Œ๋ฌธ์ด๋‹ค).
+ ๊ทธ๋Ÿฌ๋‚˜ ๊ทœ์น™์„ ๋”ฐ๋ฅด์ง€ ์•Š๋Š”๋‹ค๋ฉด ๊ฑฐ์˜ ์„ฑ๊ณตํ•˜์ง€๋„ ๋ชปํ•  ๊ฒƒ์ด๋‹ค.
+
+ ์˜ฌ๋ฐ”๋ฅธ ํŒจ์น˜๋“ค์„ ๋งŒ๋“œ๋Š” ๋ฒ•์— ๊ด€ํ•œ ํ›Œ๋ฅญํ•œ ๋‹ค๋ฅธ ๋ฌธ์„œ๋“ค์ด ์žˆ๋‹ค.
+ "The Perfect Patch"
+ http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
+ "Linux kernel patch submission format"
+ http://linux.yyz.us/patch-format.html
+
+ Documentation/stable_api_nonsense.txt
+ ์ด ๋ฌธ์„œ๋Š” ์˜๋„์ ์œผ๋กœ ์ปค๋„์ด ๋ณ€ํ•˜์ง€ ์•Š๋Š” API๋ฅผ ๊ฐ–์ง€ ์•Š๋„๋ก ๊ฒฐ์ •ํ•œ
+ ์ด์œ ๋ฅผ ์„ค๋ช…ํ•˜๋ฉฐ ๋‹ค์Œ๊ณผ ๊ฐ™์€ ๊ฒƒ๋“ค์„ ํฌํ•จํ•œ๋‹ค.
+ - ์„œ๋ธŒ์‹œ์Šคํ…œ shim-layer(ํ˜ธํ™˜์„ฑ์„ ์œ„ํ•ด?)
+ - ์šด์˜ ์ฒด์ œ๋“ค ๊ฐ„์˜ ๋“œ๋ผ์ด๋ฒ„ ์ด์‹์„ฑ
+ - ์ปค๋„ ์†Œ์Šค ํŠธ๋ฆฌ๋‚ด์— ๋น ๋ฅธ ๋ณ€ํ™”๋ฅผ ๋Šฆ์ถ”๋Š” ๊ฒƒ(๋˜๋Š” ๋น ๋ฅธ ๋ณ€ํ™”๋ฅผ ๋ง‰๋Š” ๊ฒƒ)
+ ์ด ๋ฌธ์„œ๋Š” ๋ฆฌ๋ˆ…์Šค ๊ฐœ๋ฐœ ์ฒ ํ•™์„ ์ดํ•ดํ•˜๋Š”๋ฐ ํ•„์ˆ˜์ ์ด๋ฉฐ ๋‹ค๋ฅธ ์šด์˜์ฒด์ œ์—์„œ
+ ๋ฆฌ๋ˆ…์Šค๋กœ ์˜ฎ๊ฒจ์˜ค๋Š” ์‚ฌ๋žŒ๋“ค์—๊ฒŒ๋Š” ๋งค์šฐ ์ค‘์š”ํ•˜๋‹ค.
+
+
+ Documentation/SecurityBugs
+ ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ๋ฆฌ๋ˆ…์Šค ์ปค๋„์˜ ๋ณด์•ˆ ๋ฌธ์ œ๋ฅผ ๋ฐœ๊ฒฌํ–ˆ๋‹ค๊ณ  ์ƒ๊ฐํ•œ๋‹ค๋ฉด ์ด ๋ฌธ์„œ์—
+ ๋‚˜์˜จ ๋‹จ๊ณ„์— ๋”ฐ๋ผ์„œ ์ปค๋„ ๊ฐœ๋ฐœ์ž๋“ค์—๊ฒŒ ์•Œ๋ฆฌ๊ณ  ๊ทธ ๋ฌธ์ œ๋ฅผ ํ•ด๊ฒฐํ•  ์ˆ˜ ์žˆ๋„๋ก
+ ๋„์™€ ๋‹ฌ๋ผ.
+
+ Documentation/ManagementStyle
+ ์ด ๋ฌธ์„œ๋Š” ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๋ฉ”์ธํŠธ๋„ˆ๋“ค์ด ์–ด๋–ป๊ฒŒ ๊ทธ๋“ค์˜ ๋ฐฉ๋ฒ•๋ก ์˜ ์ •์‹ ์„
+ ์–ด๋–ป๊ฒŒ ๊ณต์œ ํ•˜๊ณ  ์šด์˜ํ•˜๋Š”์ง€๋ฅผ ์„ค๋ช…ํ•œ๋‹ค. ์ด๊ฒƒ์€ ์ปค๋„ ๊ฐœ๋ฐœ์— ์ž…๋ฌธํ•˜๋Š”
+ ๋ชจ๋“  ์‚ฌ๋žŒ๋“ค(๋˜๋Š” ์ปค๋„ ๊ฐœ๋ฐœ์— ์ž‘์€ ํ˜ธ๊ธฐ์‹ฌ์ด๋ผ๋„ ์žˆ๋Š” ์‚ฌ๋žŒ๋“ค)์ด
+ ์ฝ์–ด์•ผ ํ•  ์ค‘์š”ํ•œ ๋ฌธ์„œ์ด๋‹ค. ์™œ๋ƒํ•˜๋ฉด ์ด ๋ฌธ์„œ๋Š” ์ปค๋„ ๋ฉ”์ธํŠธ๋„ˆ๋“ค์˜
+ ๋…ํŠนํ•œ ํ–‰๋™์— ๊ด€ํ•˜์—ฌ ํ”ํžˆ ์žˆ๋Š” ์˜คํ•ด๋“ค๊ณผ ํ˜ผ๋ž€๋“ค์„ ํ•ด์†Œํ•˜๊ณ  ์žˆ๊ธฐ
+ ๋•Œ๋ฌธ์ด๋‹ค.
+
+ Documentation/stable_kernel_rules.txt
+ ์ด ๋ฌธ์„œ๋Š” ์•ˆ์ •์ ์ธ ์ปค๋„ ๋ฐฐํฌ๊ฐ€ ์ด๋ฃจ์–ด์ง€๋Š” ๊ทœ์น™์„ ์„ค๋ช…ํ•˜๊ณ  ์žˆ์œผ๋ฉฐ
+ ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ์ด๋Ÿฌํ•œ ๋ฐฐํฌ๋“ค ์ค‘ ํ•˜๋‚˜์— ๋ณ€๊ฒฝ์„ ํ•˜๊ธธ ์›ํ•œ๋‹ค๋ฉด
+ ๋ฌด์—‡์„ ํ•ด์•ผ ํ•˜๋Š”์ง€๋ฅผ ์„ค๋ช…ํ•œ๋‹ค.
+
+ Documentation/kernel-docs.txt
+ ์ปค๋„ ๊ฐœ๋ฐœ์— ๊ด€๊ณ„๋œ ์™ธ๋ถ€ ๋ฌธ์„œ์˜ ๋ฆฌ์ŠคํŠธ์ด๋‹ค. ์ปค๋„ ๋‚ด์˜ ํฌํ•จ๋œ ๋ฌธ์„œ๋“ค
+ ์ค‘์— ์—ฌ๋Ÿฌ๋ถ„์ด ์ฐพ๊ณ  ์‹ถ์€ ๋ฌธ์„œ๋ฅผ ๋ฐœ๊ฒฌํ•˜์ง€ ๋ชปํ•  ๊ฒฝ์šฐ ์ด ๋ฆฌ์ŠคํŠธ๋ฅผ
+ ์‚ดํŽด๋ณด๋ผ.
+
+ Documentation/applying-patches.txt
+ ํŒจ์น˜๊ฐ€ ๋ฌด์—‡์ด๋ฉฐ ๊ทธ๊ฒƒ์„ ์ปค๋„์˜ ๋‹ค๋ฅธ ๊ฐœ๋ฐœ ๋ธŒ๋žœ์น˜๋“ค์— ์–ด๋–ป๊ฒŒ
+ ์ ์šฉํ•˜๋Š”์ง€์— ๊ด€ํ•˜์—ฌ ์ž์„ธํžˆ ์„ค๋ช… ํ•˜๊ณ  ์žˆ๋Š” ์ข‹์€ ์ž…๋ฌธ์„œ์ด๋‹ค.
+
+์ปค๋„์€ ์†Œ์Šค ์ฝ”๋“œ ๊ทธ ์ž์ฒด์—์„œ ์ž๋™์ ์œผ๋กœ ๋งŒ๋“ค์–ด์งˆ ์ˆ˜ ์žˆ๋Š” ๋งŽ์€ ๋ฌธ์„œ๋“ค์„
+๊ฐ€์ง€๊ณ  ์žˆ๋‹ค. ์ด๊ฒƒ์€ ์ปค๋„ ๋‚ด์˜ API์— ๋Œ€ํ•œ ๋ชจ๋“  ์„ค๋ช…, ๊ทธ๋ฆฌ๊ณ  ๋ฝํ‚น์„
+์˜ฌ๋ฐ”๋ฅด๊ฒŒ ์ฒ˜๋ฆฌํ•˜๋Š” ๋ฒ•์— ๊ด€ํ•œ ๊ทœ์น™์„ ํฌํ•จํ•˜๊ณ  ์žˆ๋‹ค. ์ด ๋ฌธ์„œ๋Š”
+Documentation/DocBook/ ๋””๋ ‰ํ† ๋ฆฌ ๋‚ด์—์„œ ๋งŒ๋“ค์–ด์ง€๋ฉฐ PDF, Postscript, HTML,
+๊ทธ๋ฆฌ๊ณ  man ํŽ˜์ด์ง€๋“ค๋กœ ๋‹ค์Œ๊ณผ ๊ฐ™์ด ์‹คํ–‰ํ•˜์—ฌ ๋งŒ๋“ค์–ด ์ง„๋‹ค.
+ make pdfdocs
+ make psdocs
+ make htmldocs
+ make mandocs
+๊ฐ๊ฐ์˜ ๋ช…๋ น์„ ๋ฉ”์ธ ์ปค๋„ ์†Œ์Šค ๋””๋ ‰ํ† ๋ฆฌ๋กœ๋ถ€ํ„ฐ ์‹คํ–‰ํ•œ๋‹ค.
+
+
+์ปค๋„ ๊ฐœ๋ฐœ์ž๊ฐ€ ๋˜๋Š” ๊ฒƒ
+---------------------
+
+์—ฌ๋Ÿฌ๋ถ„์ด ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ์— ๊ด€ํ•˜์—ฌ ์•„๋ฌด๊ฒƒ๋„ ๋ชจ๋ฅธ๋‹ค๋ฉด Linux KernelNewbies
+ํ”„๋กœ์ ํŠธ๋ฅผ ๋ด์•ผ ํ•œ๋‹ค.
+ http://kernelnewbies.org
+๊ทธ๊ณณ์€ ๊ฑฐ์˜ ๋ชจ๋“  ์ข…๋ฅ˜์˜ ๊ธฐ๋ณธ์ ์ธ ์ปค๋„ ๊ฐœ๋ฐœ ์งˆ๋ฌธ๋“ค(์งˆ๋ฌธํ•˜๊ธฐ ์ „์— ๋จผ์ €
+์•„์นด์ด๋ธŒ๋ฅผ ์ฐพ์•„๋ด๋ผ. ๊ณผ๊ฑฐ์— ์ด๋ฏธ ๋‹ต๋ณ€๋˜์—ˆ์„ ์ˆ˜๋„ ์žˆ๋‹ค)์„ ํ• ์ˆ˜์žˆ๋Š” ๋„์›€์ด
+๋ ๋งŒํ•œ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๊ฐ€ ์žˆ๋‹ค. ๋˜ํ•œ ์‹ค์‹œ๊ฐ„์œผ๋กœ ์งˆ๋ฌธ ํ• ์ˆ˜ ์žˆ๋Š” IRC ์ฑ„๋„๋„
+๊ฐ€์ง€๊ณ  ์žˆ์œผ๋ฉฐ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ์„ ๋ฐฐ์šฐ๋Š” ๋ฐ ์œ ์šฉํ•œ ๋ฌธ์„œ๋“ค์„ ๋ณด์œ ํ•˜๊ณ  ์žˆ๋‹ค.
+
+์›น์‚ฌ์ดํŠธ๋Š” ์ฝ”๋“œ๊ตฌ์„ฑ, ์„œ๋ธŒ์‹œ์Šคํ…œ๋“ค, ๊ทธ๋ฆฌ๊ณ  ํ˜„์žฌ ํ”„๋กœ์ ํŠธ๋“ค
+(ํŠธ๋ฆฌ ๋‚ด, ์™ธ๋ถ€์— ์กด์žฌํ•˜๋Š”)์— ๊ด€ํ•œ ๊ธฐ๋ณธ์ ์ธ ์ •๋ณด๋“ค์„ ๊ฐ€์ง€๊ณ  ์žˆ๋‹ค. ๋˜ํ•œ
+๊ทธ๊ณณ์€ ์ปค๋„ ์ปดํŒŒ์ผ์ด๋‚˜ ํŒจ์น˜๋ฅผ ํ•˜๋Š” ๋ฒ•๊ณผ ๊ฐ™์€ ๊ธฐ๋ณธ์ ์ธ ๊ฒƒ๋“ค์„ ์„ค๋ช…ํ•œ๋‹ค.
+
+์—ฌ๋Ÿฌ๋ถ„์ด ์–ด๋””์„œ ์‹œ์ž‘ํ•ด์•ผ ํ• ์ง„ ๋ชจ๋ฅด์ง€๋งŒ ์ปค๋„ ๊ฐœ๋ฐœ ์ปค๋ฎค๋‹ˆํ‹ฐ์— ์ฐธ์—ฌํ•  ์ˆ˜
+์žˆ๋Š” ์ผ๋“ค์„ ์ฐพ๊ธธ ์›ํ•œ๋‹ค๋ฉด ๋ฆฌ๋ˆ…์Šค ์ปค๋„ Janitor ํ”„๋กœ์ ํŠธ๋ฅผ ์‚ดํŽด๋ด๋ผ.
+ http://janitor.kernelnewbies.org/
+๊ทธ๊ณณ์€ ์‹œ์ž‘ํ•˜๊ธฐ์— ์•„์ฃผ ๋”ฑ ์ข‹์€ ๊ณณ์ด๋‹ค. ๊ทธ๊ณณ์€ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ์†Œ์Šค ํŠธ๋ฆฌ๋‚ด์—
+๊ฐ„๋‹จํžˆ ์ •๋ฆฌ๋˜๊ณ  ์ˆ˜์ •๋  ์ˆ˜ ์žˆ๋Š” ๋ฌธ์ œ๋“ค์— ๊ด€ํ•˜์—ฌ ์„ค๋ช…ํ•œ๋‹ค. ์—ฌ๋Ÿฌ๋ถ„์€ ์ด
+ํ”„๋กœ์ ํŠธ๋ฅผ ๋Œ€ํ‘œํ•˜๋Š” ๊ฐœ๋ฐœ์ž๋“ค๊ณผ ์ผํ•˜๋ฉด์„œ ์ž์‹ ์˜ ํŒจ์น˜๋ฅผ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ํŠธ๋ฆฌ์—
+๋ฐ˜์˜ํ•˜๊ธฐ ์œ„ํ•œ ๊ธฐ๋ณธ์ ์ธ ๊ฒƒ๋“ค์„ ๋ฐฐ์šฐ๊ฒŒ ๋ ๊ฒƒ์ด๋ฉฐ ์—ฌ๋Ÿฌ๋ถ„์ด ์•„์ง ์•„์ด๋””์–ด๋ฅผ
+๊ฐ€์ง€๊ณ  ์žˆ์ง€ ์•Š๋‹ค๋ฉด ๋‹ค์Œ์— ๋ฌด์—‡์„ ํ•ด์•ผํ• ์ง€์— ๊ด€ํ•œ ๋ฐฉํ–ฅ์„ ๋ฐฐ์šธ ์ˆ˜ ์žˆ์„
+๊ฒƒ์ด๋‹ค.
+
+์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ์ด๋ฏธ ์ปค๋„ ํŠธ๋ฆฌ์— ๋ฐ˜์˜ํ•˜๊ธธ ์›ํ•˜๋Š” ์ฝ”๋“œ ๋ฌถ์Œ์„ ๊ฐ€์ง€๊ณ  ์žˆ์ง€๋งŒ
+์˜ฌ๋ฐ”๋ฅธ ํฌ๋งท์œผ๋กœ ํฌ์žฅํ•˜๋Š”๋ฐ ๋„์›€์ด ํ•„์š”ํ•˜๋‹ค๋ฉด ๊ทธ๋Ÿฌํ•œ ๋ฌธ์ œ๋ฅผ ๋•๊ธฐ ์œ„ํ•ด
+๋งŒ๋“ค์–ด์ง„ kernel-mentors ํ”„๋กœ์ ํŠธ๊ฐ€ ์žˆ๋‹ค. ๊ทธ๊ณณ์€ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์ด๋ฉฐ
+๋‹ค์Œ์—์„œ ์ฐธ์กฐํ•  ์ˆ˜ ์žˆ๋‹ค.
+ http://selenic.com/mailman/listinfo/kernel-mentors
+
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ์ฝ”๋“œ์— ์‹ค์ œ ๋ณ€๊ฒฝ์„ ํ•˜๊ธฐ ์ „์— ๋ฐ˜๋“œ์‹œ ๊ทธ ์ฝ”๋“œ๊ฐ€ ์–ด๋–ป๊ฒŒ
+๋™์ž‘ํ•˜๋Š”์ง€ ์ดํ•ดํ•˜๊ณ  ์žˆ์–ด์•ผ ํ•œ๋‹ค. ์ฝ”๋“œ๋ฅผ ๋ถ„์„ํ•˜๊ธฐ ์œ„ํ•˜์—ฌ ํŠน์ •ํ•œ ํˆด์˜
+๋„์›€์„ ๋นŒ๋ ค์„œ๋ผ๋„ ์ฝ”๋“œ๋ฅผ ์ง์ ‘ ์ฝ๋Š” ๊ฒƒ๋ณด๋‹ค ์ข‹์€ ๊ฒƒ์€ ์—†๋‹ค(๋Œ€๋ถ€๋ถ„์˜
+์ž์ž˜ํ•œ ๋ถ€๋ถ„๋“ค์€ ์ž˜ ์ฝ”๋ฉ˜ํŠธ๋˜์–ด ์žˆ๋‹ค). ๊ทธ๋Ÿฐ ํˆด๋“ค ์ค‘์— ํŠนํžˆ ์ถ”์ฒœํ• ๋งŒํ•œ
+๊ฒƒ์€ Linux Cross-Reference project์ด๋ฉฐ ๊ทธ๊ฒƒ์€ ์ž๊ธฐ ์ฐธ์กฐ ๋ฐฉ์‹์ด๋ฉฐ
+์†Œ์Šค์ฝ”๋“œ๋ฅผ ์ธ๋ฑ์Šค๋œ ์›น ํŽ˜์ด์ง€๋“ค์˜ ํ˜•ํƒœ๋กœ ๋ณด์—ฌ์ค€๋‹ค. ์ตœ์‹ ์˜ ๋ฉ‹์ง„ ์ปค๋„
+์ฝ”๋“œ ์ €์žฅ์†Œ๋Š” ๋‹ค์Œ์„ ํ†ตํ•˜์—ฌ ์ฐธ์กฐํ•  ์ˆ˜ ์žˆ๋‹ค.
+ http://sosdg.org/~coywolf/lxr/
+
+
+๊ฐœ๋ฐœ ํ”„๋กœ์„ธ์Šค
+-------------
+
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ ํ”„๋กœ์„ธ์Šค๋Š” ํ˜„์žฌ ๋ช‡๋ช‡ ๋‹ค๋ฅธ ๋ฉ”์ธ ์ปค๋„ "๋ธŒ๋žœ์น˜๋“ค"๊ณผ
+์„œ๋ธŒ์‹œ์Šคํ…œ์— ํŠนํ™”๋œ ์ปค๋„ ๋ธŒ๋žœ์น˜๋“ค๋กœ ๊ตฌ์„ฑ๋œ๋‹ค. ๋ช‡๋ช‡ ๋‹ค๋ฅธ ๋ฉ”์ธ
+๋ธŒ๋žœ์น˜๋“ค์€ ๋‹ค์Œ๊ณผ ๊ฐ™๋‹ค.
+ - main 2.6.x ์ปค๋„ ํŠธ๋ฆฌ
+ - 2.6.x.y - ์•ˆ์ •๋œ ์ปค๋„ ํŠธ๋ฆฌ
+ - 2.6.x -git ์ปค๋„ ํŒจ์น˜๋“ค
+ - 2.6.x -mm ์ปค๋„ ํŒจ์น˜๋“ค
+ - ์„œ๋ธŒ์‹œ์Šคํ…œ์„ ์œ„ํ•œ ์ปค๋„ ํŠธ๋ฆฌ๋“ค๊ณผ ํŒจ์น˜๋“ค
+
+2.6.x ์ปค๋„ ํŠธ๋ฆฌ
+---------------
+
+2.6.x ์ปค๋„๋“ค์€ Linux Torvalds๊ฐ€ ๊ด€๋ฆฌํ•˜๋ฉฐ kernel.org์˜ pub/linux/kernel/v2.6/
+๋””๋ ‰ํ† ๋ฆฌ์—์„œ ์ฐธ์กฐ๋  ์ˆ˜ ์žˆ๋‹ค.๊ฐœ๋ฐœ ํ”„๋กœ์„ธ์Šค๋Š” ๋‹ค์Œ๊ณผ ๊ฐ™๋‹ค.
+ - ์ƒˆ๋กœ์šด ์ปค๋„์ด ๋ฐฐํฌ๋˜์ž๋งˆ์ž 2์ฃผ์˜ ์‹œ๊ฐ„์ด ์ฃผ์–ด์ง„๋‹ค. ์ด ๊ธฐ๊ฐ„๋™์€
+ ๋ฉ”์ธํŠธ๋„ˆ๋“ค์€ ํฐ diff๋“ค์„ Linus์—๊ฒŒ ์ œ์ถœํ•  ์ˆ˜ ์žˆ๋‹ค. ๋Œ€๊ฐœ ์ด ํŒจ์น˜๋“ค์€
+ ๋ช‡ ์ฃผ ๋™์•ˆ -mm ์ปค๋„๋‚ด์— ์ด๋ฏธ ์žˆ์—ˆ๋˜ ๊ฒƒ๋“ค์ด๋‹ค. ํฐ ๋ณ€๊ฒฝ๋“ค์„ ์ œ์ถœํ•˜๋Š” ๋ฐ
+ ์„ ํ˜ธ๋˜๋Š” ๋ฐฉ๋ฒ•์€ git(์ปค๋„์˜ ์†Œ์Šค ๊ด€๋ฆฌ ํˆด, ๋” ๋งŽ์€ ์ •๋ณด๋“ค์€ http://git.or.cz/
+ ์—์„œ ์ฐธ์กฐํ•  ์ˆ˜ ์žˆ๋‹ค)๋ฅผ ์‚ฌ์šฉํ•˜๋Š” ๊ฒƒ์ด์ง€๋งŒ ์ˆœ์ˆ˜ํ•œ ํŒจ์น˜ํŒŒ์ผ์˜ ํ˜•์‹์œผ๋กœ ๋ณด๋‚ด๋„
+ ๊ฒƒ๋„ ๋ฌด๊ด€ํ•˜๋‹ค.
+ - 2์ฃผ ํ›„์— -rc1 ์ปค๋„์ด ๋ฐฐํฌ๋˜๋ฉฐ ์ง€๊ธˆ๋ถ€ํ„ฐ๋Š” ์ „์ฒด ์ปค๋„์˜ ์•ˆ์ •์„ฑ์— ์˜ํ–ฅ์„
+ ๋ฏธ์น ์ˆ˜ ์žˆ๋Š” ์ƒˆ๋กœ์šด ๊ธฐ๋Šฅ๋“ค์„ ํฌํ•จํ•˜์ง€ ์•Š๋Š” ํŒจ์น˜๋“ค๋งŒ์„ ์ถ”๊ฐ€๋  ์ˆ˜ ์žˆ๋‹ค.
+ ์™„์ „ํžˆ ์ƒˆ๋กœ์šด ๋“œ๋ผ์ด๋ฒ„(ํ˜น์€ ํŒŒ์ผ์‹œ์Šคํ…œ)๋Š” -rc1 ์ดํ›„์—๋งŒ ๋ฐ›์•„๋“ค์—ฌ์ง„๋‹ค๋Š”
+ ๊ฒƒ์„ ๊ธฐ์–ตํ•ด๋ผ. ์™œ๋ƒํ•˜๋ฉด ๋ณ€๊ฒฝ์ด ์ž์ฒด๋‚ด์—์„œ๋งŒ ๋ฐœ์ƒํ•˜๊ณ  ์ถ”๊ฐ€๋œ ์ฝ”๋“œ๊ฐ€
+ ๋“œ๋ผ์ด๋ฒ„ ์™ธ๋ถ€์˜ ๋‹ค๋ฅธ ๋ถ€๋ถ„์—๋Š” ์˜ํ–ฅ์„ ์ฃผ์ง€ ์•Š์œผ๋ฏ€๋กœ ๊ทธ๋Ÿฐ ๋ณ€๊ฒฝ์€
+ ํ‡ด๋ณด(regression)๋ฅผ ์ผ์œผํ‚ฌ ๋งŒํ•œ ์œ„ํ—˜์„ ๊ฐ€์ง€๊ณ  ์žˆ์ง€ ์•Š๊ธฐ ๋•Œ๋ฌธ์ด๋‹ค. -rc1์ด
+ ๋ฐฐํฌ๋œ ์ดํ›„์— git๋ฅผ ์‚ฌ์šฉํ•˜์—ฌ ํŒจ์น˜๋“ค์„ Linus์—๊ฒŒ ๋ณด๋‚ผ์ˆ˜ ์žˆ์ง€๋งŒ ํŒจ์น˜๋“ค์€
+ ๊ณต์‹์ ์ธ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๋กœ ๋ณด๋‚ด์„œ ๊ฒ€ํ† ๋ฅผ ๋ฐ›์„ ํ•„์š”๊ฐ€ ์žˆ๋‹ค.
+ - ์ƒˆ๋กœ์šด -rc๋Š” Linus๋Š” ํ˜„์žฌ git tree๊ฐ€ ํ…Œ์ŠคํŠธ ํ•˜๊ธฐ์— ์ถฉ๋ถ„ํžˆ ์•ˆ์ •๋œ ์ƒํƒœ์—
+ ์žˆ๋‹ค๊ณ  ํŒ๋‹จ๋  ๋•Œ๋งˆ๋‹ค ๋ฐฐํฌ๋œ๋‹ค. ๋ชฉํ‘œ๋Š” ์ƒˆ๋กœ์šด -rc ์ปค๋„์„ ๋งค์ฃผ ๋ฐฐํฌํ•˜๋Š”
+ ๊ฒƒ์ด๋‹ค.
+ - ์ด๋Ÿฌํ•œ ํ”„๋กœ์„ธ์Šค๋Š” ์ปค๋„์ด "์ค€๋น„"๋˜์—ˆ๋‹ค๊ณ  ์—ฌ๊ฒจ์งˆ๋•Œ๊นŒ์ง€ ๊ณ„์†๋œ๋‹ค.
+ ํ”„๋กœ์„ธ์Šค๋Š” ๋Œ€์ฒด๋กœ 6์ฃผ๊ฐ„ ์ง€์†๋œ๋‹ค.
+ - ๊ฐ -rc ๋ฐฐํฌ์— ์žˆ๋Š” ์•Œ๋ ค์ง„ ํ‡ด๋ณด์˜ ๋ชฉ๋ก๋“ค์€ ๋‹ค์Œ URI์— ๋‚จ๊ฒจ์ง„๋‹ค.
+ http://kernelnewbies.org/known_regressions
+
+์ปค๋„ ๋ฐฐํฌ์— ์žˆ์–ด์„œ ์–ธ๊ธ‰ํ• ๋งŒํ•œ ๊ฐ€์น˜๊ฐ€ ์žˆ๋Š” ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์˜
+Andrew Morton์˜ ๊ธ€์ด ์žˆ๋‹ค.
+ "์ปค๋„์ด ์–ธ์ œ ๋ฐฐํฌ๋ ์ง€๋Š” ์•„๋ฌด๋กœ ๋ชจ๋ฅธ๋‹ค. ์™œ๋ƒํ•˜๋ฉด ๋ฐฐํฌ๋Š” ์•Œ๋ ค์ง„
+ ๋ฒ„๊ทธ์˜ ์ƒํ™ฉ์— ๋”ฐ๋ผ ๋ฐฐํฌ๋˜๋Š” ๊ฒƒ์ด์ง€ ๋ฏธ๋ฆฌ์ •ํ•ด ๋†“์€ ์‹œ๊ฐ„์— ๋”ฐ๋ผ
+ ๋ฐฐํฌ๋˜๋Š” ๊ฒƒ์€ ์•„๋‹ˆ๊ธฐ ๋•Œ๋ฌธ์ด๋‹ค."
+
+2.6.x.y - ์•ˆ์ • ์ปค๋„ ํŠธ๋ฆฌ
+------------------------
+
+4 ์ž๋ฆฌ ์ˆซ์ž๋กœ ์ด๋ฃจ์–ด์ง„ ๋ฒ„์ ผ์˜ ์ปค๋„๋“ค์€ -stable ์ปค๋„๋“ค์ด๋‹ค. ๊ทธ๊ฒƒ๋“ค์€ 2.6.x
+์ปค๋„์—์„œ ๋ฐœ๊ฒฌ๋œ ํฐ ํ‡ด๋ณด๋“ค์ด๋‚˜ ๋ณด์•ˆ ๋ฌธ์ œ๋“ค ์ค‘ ๋น„๊ต์  ์ž‘๊ณ  ์ค‘์š”ํ•œ ์ˆ˜์ •๋“ค์„
+ํฌํ•จํ•œ๋‹ค.
+
+์ด๊ฒƒ์€ ๊ฐ€์žฅ ์ตœ๊ทผ์˜ ์•ˆ์ •์ ์ธ ์ปค๋„์„ ์›ํ•˜๋Š” ์‚ฌ์šฉ์ž์—๊ฒŒ ์ถ”์ฒœ๋˜๋Š” ๋ธŒ๋žœ์น˜์ด๋ฉฐ,
+๊ฐœ๋ฐœ/์‹คํ—˜์  ๋ฒ„์ ผ์„ ํ…Œ์ŠคํŠธํ•˜๋Š” ๊ฒƒ์„ ๋•๋Š”๋ฐ๋Š” ๋ณ„๋กœ ๊ด€์‹ฌ์ด ์—†๋‹ค.
+
+์–ด๋–ค 2.6.x.y ์ปค๋„๋„ ์‚ฌ์šฉ๊ฐ€๋Šฅํ•˜์ง€ ์•Š๋‹ค๋ฉด ๊ทธ๋•Œ๋Š” ๊ฐ€์žฅ ๋†’์€ ์ˆซ์ž์˜ 2.6.x
+์ปค๋„์ด ํ˜„์žฌ์˜ ์•ˆ์ • ์ปค๋„์ด๋‹ค.
+
+2.6.x.y๋Š” "stable" ํŒ€<stable@kernel.org>์— ์˜ํ•ด ๊ด€๋ฆฌ๋˜๋ฉฐ ๊ฑฐ์˜ ๋งค๋ฒˆ ๊ฒฉ์ฃผ๋กœ
+๋ฐฐํฌ๋œ๋‹ค.
+
+์ปค๋„ ํŠธ๋ฆฌ ๋ฌธ์„œ๋“ค ๋‚ด์— Documentation/stable_kernel_rules.txt ํŒŒ์ผ์€ ์–ด๋–ค
+์ข…๋ฅ˜์˜ ๋ณ€๊ฒฝ๋“ค์ด -stable ํŠธ๋ฆฌ๋กœ ๋“ค์–ด์™”๋Š”์ง€์™€ ๋ฐฐํฌ ํ”„๋กœ์„ธ์Šค๊ฐ€ ์–ด๋–ป๊ฒŒ
+์ง„ํ–‰๋˜๋Š”์ง€๋ฅผ ์„ค๋ช…ํ•œ๋‹ค.
+
+
+2.6.x -git ํŒจ์น˜๋“ค
+------------------
+git ์ €์žฅ์†Œ(๊ทธ๋Ÿฌ๋ฏ€๋กœ -git์ด๋ผ๋Š” ์ด๋ฆ„์ด ๋ถ™์Œ)์—๋Š” ๋‚ ๋งˆ๋‹ค ๊ด€๋ฆฌ๋˜๋Š” Linus์˜
+์ปค๋„ ํŠธ๋ฆฌ์˜ snapshot ๋“ค์ด ์žˆ๋‹ค. ์ด ํŒจ์น˜๋“ค์€ ์ผ๋ฐ˜์ ์œผ๋กœ ๋‚ ๋งˆ๋‹ค ๋ฐฐํฌ๋˜๋ฉฐ
+Linus์˜ ํŠธ๋ฆฌ์˜ ํ˜„์žฌ ์ƒํƒœ๋ฅผ ๋‚˜ํƒ€๋‚ธ๋‹ค. ์ด ํŒจ์น˜๋“ค์€ ์ •์ƒ์ ์ธ์ง€ ์กฐ๊ธˆ๋„
+์‚ดํŽด๋ณด์ง€ ์•Š๊ณ  ์ž๋™์ ์œผ๋กœ ์ƒ์„ฑ๋œ ๊ฒƒ์ด๋ฏ€๋กœ -rc ์ปค๋„๋“ค ๋ณด๋‹ค๋„ ๋” ์‹คํ—˜์ ์ด๋‹ค.
+
+2.6.x -mm ์ปค๋„ ํŒจ์น˜๋“ค
+---------------------
+Andrew Morton์— ์˜ํ•ด ๋ฐฐํฌ๋œ ์‹คํ—˜์ ์ธ ์ปค๋„ ํŒจ์น˜๋“ค์ด๋‹ค. Andrew๋Š” ๋ชจ๋“  ๋‹ค๋ฅธ
+์„œ๋ธŒ์‹œ์Šคํ…œ ์ปค๋„ ํŠธ๋ฆฌ์™€ ํŒจ์น˜๋“ค์„ ๊ฐ€์ ธ์™€์„œ ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๋กœ
+์˜จ ๋งŽ์€ ํŒจ์น˜๋“ค๊ณผ ํ•œ๋ฐ ๋ฌถ๋Š”๋‹ค. ์ด ํŠธ๋ฆฌ๋Š” ์ƒˆ๋กœ์šด ๊ธฐ๋Šฅ๋“ค๊ณผ ํŒจ์น˜๋“ค์„ ์œ„ํ•œ
+์žฅ์†Œ๋ฅผ ์ œ๊ณตํ•˜๋Š” ์—ญํ• ์„ ํ•œ๋‹ค. ํ•˜๋‚˜์˜ ํŒจ์น˜๊ฐ€ -mm์— ํ•œ๋™์•ˆ ์žˆ์œผ๋ฉด์„œ ๊ทธ ๊ฐ€์น˜๊ฐ€
+์ฆ๋ช…๋˜๊ฒŒ ๋˜๋ฉด Andrew๋‚˜ ์„œ๋ธŒ์‹œ์Šคํ…œ ๋ฉ”์ธํŠธ๋„ˆ๋Š” ๊ทธ๊ฒƒ์„ ๋ฉ”์ธ๋ผ์ธ์— ํฌํ•จ์‹œํ‚ค๊ธฐ
+์œ„ํ•˜์—ฌ Linus์—๊ฒŒ ๋ณด๋‚ธ๋‹ค.
+
+์ปค๋„ ํŠธ๋ฆฌ์— ํฌํ•จํ•˜๊ณ  ์‹ถ์€ ๋ชจ๋“  ์ƒˆ๋กœ์šด ํŒจ์น˜๋“ค์€ Linus์—๊ฒŒ ๋ณด๋‚ด์ง€๊ธฐ ์ „์—
+-mm ํŠธ๋ฆฌ์—์„œ ํ…Œ์ŠคํŠธ๋ฅผ ํ•˜๋Š” ๊ฒƒ์„ ์ ๊ทน ์ถ”์ฒœํ•œ๋‹ค.
+
+์ด ์ปค๋„๋“ค์€ ์•ˆ์ •๋˜๊ฒŒ ์‚ฌ์šฉํ•  ์‹œ์Šคํ…œ์—์„œ์— ์‹คํ–‰ํ•˜๋Š” ๊ฒƒ์€ ์ ํ•ฉํ•˜์ง€ ์•Š์œผ๋ฉฐ
+๋‹ค๋ฅธ ๋ธŒ๋žœ์น˜๋“ค์˜ ์–ด๋–ค ๊ฒƒ๋“ค๋ณด๋‹ค ์œ„ํ—˜ํ•˜๋‹ค.
+
+์—ฌ๋Ÿฌ๋ถ„์ด ์ปค๋„ ๊ฐœ๋ฐœ ํ”„๋กœ์„ธ์Šค๋ฅผ ๋•๊ธธ ์›ํ•œ๋‹ค๋ฉด ์ด ์ปค๋„ ๋ฐฐํฌ๋“ค์„ ์‚ฌ์šฉํ•˜๊ณ 
+ํ…Œ์ŠคํŠธํ•œ ํ›„ ์–ด๋–ค ๋ฌธ์ œ๋ฅผ ๋ฐœ๊ฒฌํ•˜๊ฑฐ๋‚˜ ๋˜๋Š” ๋ชจ๋“  ๊ฒƒ์ด ์ž˜ ๋™์ž‘ํ•œ๋‹ค๋ฉด ๋ฆฌ๋ˆ…์Šค
+์ปค๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๋กœ ํ”ผ๋“œ๋ฐฑ์„ ํ•ด๋‹ฌ๋ผ.
+
+์ด ์ปค๋„๋“ค์€ ์ผ๋ฐ˜์ ์œผ๋กœ ๋ชจ๋“  ๋‹ค๋ฅธ ์‹คํ—˜์ ์ธ ํŒจ์น˜๋“ค๊ณผ ๋ฐฐํฌ๋  ๋‹น์‹œ์˜
+์‚ฌ์šฉ๊ฐ€๋Šฅํ•œ ๋ฉ”์ธ๋ผ์ธ -git ์ปค๋„๋“ค์˜ ๋ช‡๋ช‡ ๋ณ€๊ฒฝ์„ ํฌํ•จํ•œ๋‹ค.
+
+-mm ์ปค๋„๋“ค์€ ์ •ํ•ด์ง„ ์ผ์ •๋Œ€๋กœ ๋ฐฐํฌ๋˜์ง€ ์•Š๋Š”๋‹ค. ํ•˜์ง€๋งŒ ๋Œ€๊ฐœ ๋ช‡๋ช‡ -mm ์ปค๋„๋“ค์€
+๊ฐ -rc ์ปค๋„(1๋ถ€ํ„ฐ 3์ด ํ”ํ•จ) ์‚ฌ์ด์—์„œ ๋ฐฐํฌ๋œ๋‹ค.
+
+์„œ๋ธŒ์‹œ์Šคํ…œ ์ปค๋„ ํŠธ๋ฆฌ๋“ค๊ณผ ํŒจ์น˜๋“ค
+-------------------------------
+๋งŽ์€ ๋‹ค๋ฅธ ์ปค๋„ ์„œ๋ธŒ์‹œ์Šคํ…œ ๊ฐœ๋ฐœ์ž๋“ค์€ ์ปค๋„์˜ ๋‹ค๋ฅธ ๋ถ€๋ถ„๋“ค์—์„œ ๋ฌด์Šจ ์ผ์ด
+์ผ์–ด๋‚˜๊ณ  ์žˆ๋Š”์ง€๋ฅผ ๋ณผ์ˆ˜ ์žˆ๋„๋ก ๊ทธ๋“ค์˜ ๊ฐœ๋ฐœ ํŠธ๋ฆฌ๋ฅผ ๊ณต๊ฐœํ•œ๋‹ค. ์ด ํŠธ๋ฆฌ๋“ค์€
+์œ„์—์„œ ์„ค๋ช…ํ•˜์˜€๋˜ ๊ฒƒ ์ฒ˜๋Ÿผ -mm ์ปค๋„ ๋ฐฐํฌ๋“ค๋กœ ํ•ฉ์ณ์ง„๋‹ค.
+
+๋‹ค์Œ์€ ํ™œ์šฉ๊ฐ€๋Šฅํ•œ ์ปค๋„ ํŠธ๋ฆฌ๋“ค์„ ๋‚˜์—ดํ•œ๋‹ค.
+ git trees:
+ - Kbuild development tree, Sam Ravnborg < sam@ravnborg.org>
+ git.kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git
+
+ - ACPI development tree, Len Brown <len.brown@intel.com >
+ git.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git
+
+ - Block development tree, Jens Axboe <axboe@suse.de>
+ git.kernel.org:/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git
+
+ - DRM development tree, Dave Airlie <airlied@linux.ie>
+ git.kernel.org:/pub/scm/linux/kernel/git/airlied/drm-2.6.git
+
+ - ia64 development tree, Tony Luck < tony.luck@intel.com>
+ git.kernel.org:/pub/scm/linux/kernel/git/aegl/linux-2.6.git
+
+ - infiniband, Roland Dreier <rolandd@cisco.com >
+ git.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git
+
+ - libata, Jeff Garzik <jgarzik@pobox.com>
+ git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
+
+ - network drivers, Jeff Garzik <jgarzik@pobox.com>
+ git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
+
+ - pcmcia, Dominik Brodowski < linux@dominikbrodowski.net>
+ git.kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git
+
+ - SCSI, James Bottomley < James.Bottomley@SteelEye.com>
+ git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
+
+ quilt trees:
+ - USB, PCI, Driver Core, and I2C, Greg Kroah-Hartman < gregkh@suse.de>
+ kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
+ - x86-64, partly i386, Andi Kleen < ak@suse.de>
+ ftp.firstfloor.org:/pub/ak/x86_64/quilt/
+
+ ๋‹ค๋ฅธ ์ปค๋„ ํŠธ๋ฆฌ๋“ค์€ http://kernel.org/git์™€ MAINTAINERS ํŒŒ์ผ์—์„œ ์ฐธ์กฐํ•  ์ˆ˜
+ ์žˆ๋‹ค.
+
+๋ฒ„๊ทธ ๋ณด๊ณ 
+---------
+bugzilla.kernel.org๋Š” ๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๊ฐœ๋ฐœ์ž๋“ค์ด ์ปค๋„์˜ ๋ฒ„๊ทธ๋ฅผ ์ถ”์ ํ•˜๋Š” ๊ณณ์ด๋‹ค.
+์‚ฌ์šฉ์ž๋“ค์€ ๋ฐœ๊ฒฌํ•œ ๋ชจ๋“  ๋ฒ„๊ทธ๋“ค์„ ๋ณด๊ณ ํ•˜๊ธฐ ์œ„ํ•˜์—ฌ ์ด ํˆด์„ ์‚ฌ์šฉํ•  ๊ฒƒ์„ ๊ถŒ์žฅํ•œ๋‹ค.
+kernel bugzilla๋ฅผ ์‚ฌ์šฉํ•˜๋Š” ์ž์„ธํ•œ ๋ฐฉ๋ฒ•์€ ๋‹ค์Œ์„ ์ฐธ์กฐํ•˜๋ผ.
+ http://test.kernel.org/bugzilla/faq.html
+
+๋ฉ”์ธ ์ปค๋„ ์†Œ์Šค ๋””๋ ‰ํ† ๋ฆฌ์— ์žˆ๋Š” REPORTING-BUGS ํŒŒ์ผ์€ ์ปค๋„ ๋ฒ„๊ทธ์ผ ๊ฒƒ ๊ฐ™์€
+๊ฒƒ์„ ๋ณด๊ณ ํ•˜๋Š”๋Š” ๋ฒ•์— ๊ด€ํ•œ ์ข‹์€ ํ…œํ”Œ๋ฆฟ์ด๊ณ  ๋ฌธ์ œ๋ฅผ ์ถ”์ ํ•˜๊ธฐ ์œ„ํ•ด์„œ ์ปค๋„
+๊ฐœ๋ฐœ์ž๋“ค์ด ํ•„์š”๋กœ ํ•˜๋Š” ์ •๋ณด๊ฐ€ ๋ฌด์—‡๋“ค์ธ์ง€๋ฅผ ์ƒ์„ธํžˆ ์„ค๋ช…ํ•˜๊ณ  ์žˆ๋‹ค.
+
+
+๋ฒ„๊ทธ ๋ฆฌํฌํŠธ๋“ค์˜ ๊ด€๋ฆฌ
+--------------------
+
+์—ฌ๋Ÿฌ๋ถ„์˜ ํ•ดํ‚น ๊ธฐ์ˆ ์„ ์—ฐ์Šตํ•˜๋Š” ๊ฐ€์žฅ ์ข‹์€ ๋ฐฉ๋ฒ• ์ค‘์˜ ํ•˜๋Š” ๋‹ค๋ฅธ ์‚ฌ๋žŒ๋“ค์ด
+๋ณด๊ณ ํ•œ ๋ฒ„๊ทธ๋“ค์„ ์ˆ˜์ •ํ•˜๋Š” ๊ฒƒ์ด๋‹ค. ์—ฌ๋Ÿฌ๋ถ„์€ ์ปค๋„์„ ๋”์šฑ ์•ˆ์ •ํ™”์‹œํ‚ค๋Š”๋ฐ
+๋„์›€์„ ์ค„ ๋ฟ๋งŒ์ด ์•„๋‹ˆ๋ผ ์‹ค์ œ์žˆ๋Š” ๋ฌธ์ œ๋“ค์„ ์ˆ˜์ •ํ•˜๋Š” ๋ฒ•์„ ๋ฐฐ์šฐ๊ฒŒ ๋˜๊ณ 
+๊ทธ์™€ ํ•จ๊ป˜ ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ๊ธฐ์ˆ ์€ ํ–ฅ์ƒ๋  ๊ฒƒ์ด๋ฉฐ ๋‹ค๋ฅธ ๊ฐœ๋ฐœ์ž๋“ค์ด ์—ฌ๋Ÿฌ๋ถ„์˜
+์กด์žฌ์— ๋Œ€ํ•ด ์•Œ๊ฒŒ ๋  ๊ฒƒ์ด๋‹ค. ๋ฒ„๊ทธ๋ฅผ ์ˆ˜์ •ํ•˜๋Š” ๊ฒƒ์€ ๊ฐœ๋ฐœ์ž๋“ค ์‚ฌ์ด์—์„œ
+์ ์ˆ˜๋ฅผ ์–ป์„ ์ˆ˜ ์žˆ๋Š” ๊ฐ€์žฅ ์ข‹์€ ๋ฐฉ๋ฒ•์ค‘์˜ ํ•˜๋‚˜์ด๋‹ค. ์™œ๋ƒํ•˜๋ฉด ๋งŽ์€ ์‚ฌ๋žŒ๋“ค์€
+๋‹ค๋ฅธ ์‚ฌ๋žŒ๋“ค์˜ ๋ฒ„๊ทธ๋“ค์„ ์ˆ˜์ •ํ•˜๊ธฐ ์œ„ํ•˜์—ฌ ์‹œ๊ฐ„์„ ๋‚ญ๋น„ํ•˜์ง€ ์•Š๊ธฐ ๋•Œ๋ฌธ์ด๋‹ค.
+
+์ด๋ฏธ ๋ณด๊ณ ๋œ ๋ฒ„๊ทธ ๋ฆฌํฌํŠธ๋“ค์„ ๊ฐ€์ง€๊ณ  ์ž‘์—…ํ•˜๊ธฐ ์œ„ํ•ด์„œ http://bugzilla.kernelorg๋ฅผ
+์ฐธ์กฐํ•˜๋ผ. ์—ฌ๋Ÿฌ๋ถ„์ด ์•ž์œผ๋กœ ์ƒ๊ฒจ๋‚  ๋ฒ„๊ทธ ๋ฆฌํฌํŠธ๋“ค์˜ ์กฐ์–ธ์ž๊ฐ€ ๋˜๊ธธ ์›ํ•œ๋‹ค๋ฉด
+bugme-new ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๋‚˜(์ƒˆ๋กœ์šด ๋ฒ„๊ทธ ๋ฆฌํฌํŠธ๋“ค๋งŒ์ด ์ด๊ณณ์—์„œ ๋ฉ”์ผ๋กœ ์ „ํ•ด์ง„๋‹ค)
+bugme-janitor ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ(bugzilla์— ๋ชจ๋“  ๋ณ€ํ™”๋“ค์ด ์—ฌ๊ธฐ์„œ ๋ฉ”์ผ๋กœ ์ „ํ•ด์ง„๋‹ค)
+์— ๋“ฑ๋กํ•˜๋ฉด ๋œ๋‹ค.
+
+ http://lists.osdl.org/mailman/listinfo/bugme-new
+ http://lists.osdl.org/mailman/listinfo/bugme-janitors
+
+
+
+๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๋“ค
+---------------
+
+์œ„์˜ ๋ช‡๋ช‡ ๋ฌธ์„œ๋“ค์ด ์„ค๋ช…ํ•˜์˜€์ง€๋งŒ ํ•ต์‹ฌ ์ปค๋„ ๊ฐœ๋ฐœ์ž๋“ค์˜ ๋Œ€๋‹ค์ˆ˜๋Š”
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์— ์ฐธ์—ฌํ•˜๊ณ  ์žˆ๋‹ค. ๋ฆฌ์ŠคํŠธ์— ๋“ฑ๋กํ•˜๊ณ  ํ•ด์ง€ํ•˜๋Š”
+๋ฐฉ๋ฒ•์— ๊ด€ํ•œ ์ž์„ธํ•œ ์‚ฌํ•ญ์€ ๋‹ค์Œ์—์„œ ์ฐธ์กฐํ•  ์ˆ˜ ์žˆ๋‹ค.
+ http://vger.kernel.org/vger-lists.html#linux-kernel
+์›น์ƒ์˜ ๋งŽ์€ ๋‹ค๋ฅธ ๊ณณ์—๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์˜ ์•„์นด์ด๋ธŒ๋“ค์ด ์žˆ๋‹ค.
+์ด๋Ÿฌํ•œ ์•„์นด์ด๋ธŒ๋“ค์„ ์ฐพ์œผ๋ ค๋ฉด ๊ฒ€์ƒ‰ ์—”์ง„์„ ์‚ฌ์šฉํ•˜๋ผ. ์˜ˆ๋ฅผ ๋“ค์–ด:
+ http://dir.gmane.org/gmane.linux.kernel
+์—ฌ๋Ÿฌ๋ถ„์ด ์ƒˆ๋กœ์šด ๋ฌธ์ œ์— ๊ด€ํ•ด ๋ฆฌ์ŠคํŠธ์— ์˜ฌ๋ฆฌ๊ธฐ ์ „์— ๋งํ•˜๊ณ  ์‹ถ์€ ์ฃผ์ œ์— ๋Œ€ํ•œ
+๊ฒƒ์„ ์•„์นด์ด๋ธŒ์—์„œ ๋จผ์ € ์ฐพ๊ธฐ๋ฅผ ๊ฐ•๋ ฅํžˆ ๊ถŒ์žฅํ•œ๋‹ค. ์ด๋ฏธ ์ƒ์„ธํ•˜๊ฒŒ ํ† ๋ก ๋œ ๋งŽ์€
+๊ฒƒ๋“ค์ด ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์˜ ์•„์นด์ด๋ธŒ์— ๊ธฐ๋ก๋˜์–ด ์žˆ๋‹ค.
+
+๊ฐ๊ฐ์˜ ์ปค๋„ ์„œ๋ธŒ์‹œ์Šคํ…œ๋“ค์˜ ๋Œ€๋ถ€๋ถ„์€ ์ž์‹ ๋“ค์˜ ๊ฐœ๋ฐœ์— ๊ด€ํ•œ ๋…ธ๋ ฅ๋“ค๋กœ ์ด๋ฃจ์–ด์ง„
+๋ถ„๋ฆฌ๋œ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ๋ฅผ ๋”ฐ๋กœ ๊ฐ€์ง€๊ณ  ์žˆ๋‹ค. ๋‹ค๋ฅธ ๊ทธ๋ฃน๋“ค์ด ๋ฌด์Šจ ๋ฆฌ์ŠคํŠธ๋ฅผ ๊ฐ€์ง€๊ณ 
+์žˆ๋Š”์ง€๋Š” MAINTAINERS ํŒŒ์ผ์„ ์ฐธ์กฐํ•˜๋ผ.
+
+๋งŽ์€ ๋ฆฌ์ŠคํŠธ๋“ค์€ kernel.org์—์„œ ํ˜ธ์ŠคํŠธ๋˜๊ณ  ์žˆ๋‹ค. ๊ทธ ์ •๋ณด๋“ค์€ ๋‹ค์Œ์—์„œ ์ฐธ์กฐ๋  ์ˆ˜ ์žˆ๋‹ค.
+ http://vger.kernel.org/vger-lists.html
+
+๋ฆฌ์ŠคํŠธ๋“ค์„ ์‚ฌ์šฉํ•  ๋•Œ๋Š” ์˜ฌ๋ฐ”๋ฅธ ์˜ˆ์ ˆ์„ ๋”ฐ๋ฅผ ๊ฒƒ์„ ์œ ๋…ํ•ด๋ผ.
+๋Œ€๋‹จํ•˜์ง„ ์•Š์ง€๋งŒ ๋‹ค์Œ URL์€ ๋ฆฌ์ŠคํŠธ(ํ˜น์€ ๋ชจ๋“  ๋ฆฌ์ŠคํŠธ)์™€ ๋Œ€ํ™”ํ•˜๋Š” ๋ช‡๋ช‡ ๊ฐ„๋‹จํ•œ
+๊ฐ€์ด๋“œ๋ผ์ธ์„ ๊ฐ€์ง€๊ณ  ์žˆ๋‹ค.
+ http://www.albion.com/netiquette/
+
+์—ฌ๋Ÿฌ ์‚ฌ๋žŒ๋“ค์ด ์—ฌ๋Ÿฌ๋ถ„์˜ ๋ฉ”์ผ์— ์‘๋‹ตํ•œ๋‹ค๋ฉด CC: ์ฆ‰ ์ˆ˜์‹  ๋ฆฌ์ŠคํŠธ๋Š” ๊ฝค ์ปค์ง€๊ฒŒ
+๋  ๊ฒƒ์ด๋‹ค. ์•„๋ฌด ์ด์œ ์—†์ด CC์—์„œ ์–ด๋–ค ์‚ฌ๋žŒ๋„ ์ œ๊ฑฐํ•˜๊ฑฐ๋‚˜ ๋ฆฌ์ŠคํŠธ ์ฃผ์†Œ๋กœ๋งŒ
+ํšŒ์‹ ํ•˜์ง€ ๋งˆ๋ผ. ๋ฉ”์ผ์„ ๋ณด๋‚ธ ์‚ฌ๋žŒ์œผ๋กœ์„œ ํ•˜๋‚˜๋ฅผ ๋ฐ›๊ณ  ๋ฆฌ์ŠคํŠธ๋กœ๋ถ€ํ„ฐ ๋˜
+ํ•˜๋‚˜๋ฅผ ๋ฐ›์•„ ๋‘๋ฒˆ ๋ฐ›๋Š” ๊ฒƒ์— ์ต์ˆ™ํ•˜์—ฌ ์žˆ์œผ๋‹ˆ mail-header๋ฅผ ์กฐ์ž‘ํ•˜๋ ค๊ณ  ํ•˜์ง€
+๋ง์•„๋ผ. ์‚ฌ๋žŒ๋“ค์€ ๊ทธ๋Ÿฐ ๊ฒƒ์„ ์ข‹์•„ํ•˜์ง€ ์•Š์„ ๊ฒƒ์ด๋‹ค.
+
+์—ฌ๋Ÿฌ๋ถ„์˜ ํšŒ์‹ ์˜ ๋ฌธ๋งฅ์„ ์›๋ž˜๋Œ€๋กœ ์œ ์ง€ํ•ด์•ผ ํ•œ๋‹ค. ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ํšŒ์‹ ์˜ ์œ—๋ถ€๋ถ„์—
+"John ์ปค๋„ํ•ด์ปค๋Š” ์ž‘์„ฑํ–ˆ๋‹ค...."๋ฅผ ์œ ์ง€ํ•˜๋ฉฐ ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ์˜๊ฒฌ์„ ๊ทธ ๋ฉ”์ผ์˜ ์œ—๋ถ€๋ถ„์—
+์ž‘์„ฑํ•˜์ง€ ๋ง๊ณ  ๊ฐ ์ธ์šฉํ•œ ๋‹จ๋ฝ๋“ค ์‚ฌ์ด์— ๋„ฃ์–ด๋ผ.
+
+์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ํŒจ์น˜๋“ค์„ ๋ฉ”์ผ์— ๋„ฃ๋Š”๋‹ค๋ฉด ๊ทธ๊ฒƒ๋“ค์€ Documentation/SubmittingPatches์—
+๋‚˜์™€์žˆ๋Š”๋ฐ๋กœ ๋ช…๋ฐฑํžˆ(plain) ์ฝ์„ ์ˆ˜ ์žˆ๋Š” ํ…์ŠคํŠธ์—ฌ์•ผ ํ•œ๋‹ค. ์ปค๋„ ๊ฐœ๋ฐœ์ž๋“ค์€
+์ฒจ๋ถ€ํŒŒ์ผ์ด๋‚˜ ์••์ถ•๋œ ํŒจ์น˜๋“ค์„ ์›ํ•˜์ง€ ์•Š๋Š”๋‹ค. ๊ทธ๋“ค์€ ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ํŒจ์น˜์˜
+๊ฐ ๋ผ์ธ ๋‹จ์œ„๋กœ ์ฝ”๋ฉ˜ํŠธ๋ฅผ ํ•˜๊ธธ ์›ํ•˜๋ฉฐ ์••์ถ•ํ•˜๊ฑฐ๋‚˜ ์ฒจ๋ถ€ํ•˜์ง€ ์•Š๊ณ  ๋ณด๋‚ด๋Š” ๊ฒƒ์ด
+๊ทธ๋ ‡๊ฒŒ ํ•  ์ˆ˜ ์žˆ๋Š” ์œ ์ผํ•œ ๋ฐฉ๋ฒ•์ด๋‹ค. ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ์‚ฌ์šฉํ•˜๋Š” ๋ฉ”์ผ ํ”„๋กœ๊ทธ๋žจ์ด
+์ŠคํŽ˜์ด์Šค๋‚˜ ํƒญ ๋ฌธ์ž๋“ค์„ ์กฐ์ž‘ํ•˜์ง€ ์•Š๋Š”์ง€ ํ™•์ธํ•˜๋ผ. ๊ฐ€์žฅ ์ข‹์€ ์ฒซ ํ…Œ์ŠคํŠธ๋Š”
+๋ฉ”์ผ์„ ์ž์‹ ์—๊ฒŒ ๋ณด๋‚ด๋ณด๊ณ  ์Šค์Šค๋กœ ๊ทธ ํŒจ์น˜๋ฅผ ์ ์šฉํ•ด๋ณด๋ผ. ๊ทธ๊ฒƒ์ด ๋™์ž‘ํ•˜์ง€
+์•Š๋Š”๋‹ค๋ฉด ์—ฌ๋Ÿฌ๋ถ„์˜ ๋ฉ”์ผ ํ”„๋กœ๊ทธ๋žจ์„ ๊ณ ์น˜๋˜๊ฐ€ ์ œ๋Œ€๋กœ ๋™์ž‘ํ•˜๋Š” ํ”„๋กœ๊ทธ๋žจ์œผ๋กœ
+๋ฐ”๊พธ์–ด๋ผ.
+
+๋ฌด์—‡๋ณด๋‹ค๋„ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์˜ ๋‹ค๋ฅธ ๊ตฌ๋…์ž๋“ค์—๊ฒŒ ๋ณด์—ฌ์ฃผ๋ ค ํ•œ๋‹ค๋Š” ๊ฒƒ์„ ๊ธฐ์–ตํ•˜๋ผ.
+
+
+์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ์ผํ•˜๋Š” ๋ฒ•
+--------------------
+
+์ปค๋„ ์ปค๋ฎค๋‹ˆํ‹ฐ์˜ ๋ชฉ์ ์€ ๊ฐ€๋Šฅํ•œํ•œ ๊ฐ€์žฅ ์ข‹์€ ์ปค๋„์„ ์ œ๊ณตํ•˜๋Š” ๊ฒƒ์ด๋‹ค. ์—ฌ๋Ÿฌ๋ถ„์ด
+๋ฐ›์•„๋“ค์—ฌ์งˆ ํŒจ์น˜๋ฅผ ์ œ์ถœํ•˜๊ฒŒ ๋˜๋ฉด ๊ทธ ํŒจ์น˜์˜ ๊ธฐ์ˆ ์ ์ธ ์ด์ ์œผ๋กœ ๊ฒ€ํ† ๋  ๊ฒƒ์ด๋‹ค.
+๊ทธ๋Ÿผ ์—ฌ๋Ÿฌ๋ถ„๋“ค์€ ๋ฌด์—‡์„ ๊ธฐ๋Œ€ํ•˜๊ณ  ์žˆ์–ด์•ผ ํ•˜๋Š”๊ฐ€?
+ - ๋น„ํŒ
+ - ์˜๊ฒฌ
+ - ๋ณ€๊ฒฝ์„ ์œ„ํ•œ ์š”๊ตฌ
+ - ๋‹น์œ„์„ฑ์„ ์œ„ํ•œ ์š”๊ตฌ
+ - ๊ณ ์š”
+
+๊ธฐ์–ตํ•˜๋ผ. ์ด๊ฒƒ๋“ค์€ ์—ฌ๋Ÿฌ๋ถ„์˜ ํŒจ์น˜๊ฐ€ ์ปค๋„๋กœ ๋“ค์–ด๊ฐ€๊ธฐ ์œ„ํ•œ ๊ณผ์ •์ด๋‹ค. ์—ฌ๋Ÿฌ๋ถ„์˜
+ํŒจ์น˜๋“ค์€ ๋น„ํŒ๊ณผ ๋‹ค๋ฅธ ์˜๊ฒฌ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ๊ณ  ๊ทธ๊ฒƒ๋“ค์„ ๊ธฐ์ˆ ์ ์ธ ๋ ˆ๋ฒจ๋กœ ํ‰๊ฐ€ํ•˜๊ณ 
+์žฌ์ž‘์—…ํ•˜๊ฑฐ๋‚˜ ๋˜๋Š” ์™œ ์ˆ˜์ •ํ•˜๋ฉด ์•ˆ๋˜๋Š”์ง€์— ๊ด€ํ•˜์—ฌ ๋ช…๋ฃŒํ•˜๊ณ  ๊ฐ„๊ฒฐํ•œ ์ด์œ ๋ฅผ
+๋งํ•  ์ˆ˜ ์žˆ์–ด์•ผ ํ•œ๋‹ค. ์—ฌ๋Ÿฌ๋ถ„์ด ์ œ์ถœํ•œ ๊ฒƒ์— ์–ด๋–ค ์‘๋‹ต๋„ ์žˆ์ง€ ์•Š๋‹ค๋ฉด ๋ช‡ ์ผ์„
+๊ธฐ๋‹ค๋ ค๋ณด๊ณ  ๋‹ค์‹œ ์‹œ๋„ํ•ด๋ผ. ๋•Œ๋ก  ๋„ˆ๋ฌด ๋งŽ์€ ๋ฉ”์ผ๋“ค ์†์— ๋ฌปํ˜€๋ฒ„๋ฆฌ๊ธฐ๋„ ํ•œ๋‹ค.
+
+์—ฌ๋Ÿฌ๋ถ„์€ ๋ฌด์—‡์„ ํ•ด์„œ๋Š” ์•ˆ๋˜๋Š”๊ฐ€?
+ - ์—ฌ๋Ÿฌ๋ถ„์˜ ํŒจ์น˜๊ฐ€ ์•„๋ฌด ์งˆ๋ฌธ ์—†์ด ๋ฐ›์•„๋“ค์—ฌ์ง€๊ธฐ๋ฅผ ๊ธฐ๋Œ€ํ•˜๋Š” ๊ฒƒ
+ - ๋ฐฉ์–ด์ ์ด ๋˜๋Š” ๊ฒƒ
+ - ์˜๊ฒฌ์„ ๋ฌด์‹œํ•˜๋Š” ๊ฒƒ
+ - ์š”์ฒญ๋œ ๋ณ€๊ฒฝ์„ ํ•˜์ง€ ์•Š๊ณ  ํŒจ์น˜๋ฅผ ๋‹ค์‹œ ์ œ์ถœํ•˜๋Š” ๊ฒƒ
+
+๊ฐ€๋Šฅํ•œํ•œ ๊ฐ€์žฅ ์ข‹์€ ๊ธฐ์ˆ ์ ์ธ ํ•ด๋‹ต์„ ์ฐพ๊ณ  ์žˆ๋Š” ์ปค๋ฎค๋‹ˆํ‹ฐ์—์„œ๋Š” ํ•ญ์ƒ
+์–ด๋–ค ํŒจ์น˜๊ฐ€ ์–ผ๋งˆ๋‚˜ ์ข‹์€์ง€์— ๊ด€ํ•˜์—ฌ ๋‹ค๋ฅธ ์˜๊ฒฌ๋“ค์ด ์žˆ์„ ์ˆ˜ ์žˆ๋‹ค. ์—ฌ๋Ÿฌ๋ถ„์€
+ํ˜‘์กฐ์ ์ด์–ด์•ผ ํ•˜๊ณ  ๊ธฐ๊บผ์ด ์—ฌ๋Ÿฌ๋ถ„์˜ ์ƒ๊ฐ์„ ์ปค๋„ ๋‚ด์— ๋งž์ถ”์–ด์•ผ ํ•œ๋‹ค. ์•„๋‹ˆ๋ฉด
+์ ์–ด๋„ ์—ฌ๋Ÿฌ๋ถ„์˜ ๊ฒƒ์ด ๊ฐ€์น˜์žˆ๋‹ค๋Š” ๊ฒƒ์„ ์ค‘๋ช…ํ•˜์—ฌ์•ผ ํ•œ๋‹ค. ์ž˜๋ชป๋œ ๊ฒƒ๋„ ์—ฌ๋Ÿฌ๋ถ„์ด
+์˜ฌ๋ฐ”๋ฅธ ๋ฐฉํ–ฅ์˜ ํ•ด๊ฒฐ์ฑ…์œผ๋กœ ์ด๋Œ์–ด๊ฐˆ ์˜์ง€๊ฐ€ ์žˆ๋‹ค๋ฉด ๋ฐ›์•„๋“ค์—ฌ์งˆ ๊ฒƒ์ด๋ผ๋Š” ์ ์„
+๊ธฐ์–ตํ•˜๋ผ.
+
+์—ฌ๋Ÿฌ๋ถ„์˜ ์ฒซ ํŒจ์น˜์— ์—ฌ๋Ÿฌ๋ถ„์ด ์ˆ˜์ •ํ•ด์•ผํ•˜๋Š” ์‹ญ์—ฌ๊ฐœ ์ •๋„์˜ ํšŒ์‹ ์ด ์˜ค๋Š”
+๊ฒฝ์šฐ๋„ ํ”ํ•˜๋‹ค. ์ด๊ฒƒ์€ ์—ฌ๋Ÿฌ๋ถ„์˜ ํŒจ์น˜๊ฐ€ ๋ฐ›์•„๋“ค์—ฌ์ง€์ง€ ์•Š์„ ๊ฒƒ์ด๋ผ๋Š” ๊ฒƒ์„
+์˜๋ฏธํ•˜๋Š” ๊ฒƒ์ด ์•„๋‹ˆ๊ณ  ๊ฐœ์ธ์ ์œผ๋กœ ์—ฌ๋Ÿฌ๋ถ„์—๊ฒŒ ๊ฐ์ •์ด ์žˆ์–ด์„œ ๊ทธ๋Ÿฌ๋Š” ๊ฒƒ๋„
+์•„๋‹ˆ๋‹ค. ๊ฐ„๋‹จํžˆ ์—ฌ๋Ÿฌ๋ถ„์˜ ํŒจ์น˜์— ์ œ๊ธฐ๋œ ๋ฌธ์ œ๋“ค์„ ์ˆ˜์ •ํ•˜๊ณ  ๊ทธ๊ฒƒ์„ ๋‹ค์‹œ
+๋ณด๋‚ด๋ผ.
+
+
+์ปค๋„ ์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ๊ธฐ์—… ์กฐ์ง๊ฐ„์˜ ์ฐจ์ด์ 
+-----------------------------------------------------------------
+์ปค๋„ ์ปค๋ฎค๋‹ˆํ‹ฐ๋Š” ๊ฐ€์žฅ ์ „ํ†ต์ ์ธ ํšŒ์‚ฌ์˜ ๊ฐœ๋ฐœ ํ™˜๊ฒฝ๊ณผ๋Š” ๋‹ค๋ฅด๋‹ค. ์—ฌ๊ธฐ์— ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜
+๋ฌธ์ œ๋ฅผ ํ”ผํ•˜๊ธฐ ์œ„ํ•œ ๋ชฉ๋ก์ด ์žˆ๋‹ค.
+ ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ์ œ์•ˆํ•œ ๋ณ€๊ฒฝ๋“ค์— ๊ด€ํ•˜์—ฌ ๋งํ•  ๋•Œ ์ข‹์€ ๊ฒƒ๋“ค :
+ - " ์ด๊ฒƒ์€ ์—ฌ๋Ÿฌ ๋ฌธ์ œ๋“ค์„ ํ•ด๊ฒนํ•ฉ๋‹ˆ๋‹ค."
+ - "์ด๊ฒƒ์€ 2000 ๋ผ์ธ์˜ ์ฝ”๋“œ๋ฅผ ์ œ๊ฑฐํ•ฉ๋‹ˆ๋‹ค."
+ - "์ด๊ฒƒ์€ ๋‚ด๊ฐ€ ๋งํ•˜๋ ค๋Š” ๊ฒƒ์— ๊ด€ํ•ด ์„ค๋ช…ํ•˜๋Š” ํŒจ์น˜์ž…๋‹ˆ๋‹ค."
+ - "๋‚˜๋Š” 5๊ฐœ์˜ ๋‹ค๋ฅธ ์•„ํ‚คํ…์ณ์—์„œ ๊ทธ๊ฒƒ์„ ํ…Œ์ŠคํŠธํ–ˆ์Šด์œผ๋กœ..."
+ - "์—ฌ๊ธฐ์— ์ผ๋ จ์˜ ์ž‘์€ ํŒจ์น˜๋“ค์ด ์žˆ์Šต์Œ๋กœ..."
+ - "์ด๊ฒƒ์€ ์ผ๋ฐ˜์ ์ธ ๋จธ์‹ ์—์„œ ์„ฑ๋Šฅ์„ ํ–ฅ์ƒ์‹œํ‚ค๋ฏ€๋กœ..."
+
+ ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ๋งํ•  ๋•Œ ํ”ผํ•ด์•ผ ํ•  ์ข‹์ง€ ์•Š์€ ๊ฒƒ๋“ค :
+ - "์šฐ๋ฆฌ๋ฅผ ๊ทธ๊ฒƒ์„ AIT/ptx/Solaris์—์„œ ์ด๋Ÿฌํ•œ ๋ฐฉ๋ฒ•์œผ๋กœ ํ–ˆ๋‹ค. ๊ทธ๋Ÿฌ๋ฏ€๋กœ ๊ทธ๊ฒƒ์€ ์ข‹์€ ๊ฒƒ์ž„์— ํ‹€๋ฆฝ์—†๋‹ค..."
+ - "๋‚˜๋Š” 20๋…„๋™์•ˆ ์ด๊ฒƒ์„ ํ•ด์™”๋‹ค. ๊ทธ๋Ÿฌ๋ฏ€๋กœ..."
+ - "์ด๊ฒƒ์€ ๋ˆ์„ ๋ฒŒ๊ธฐ์œ„ํ•ด ๋‚˜์˜ ํšŒ์‚ฌ๊ฐ€ ํ•„์š”๋กœ ํ•˜๋Š” ๊ฒƒ์ด๋‹ค."
+ - "์ด๊ฒƒ์€ ์šฐ๋ฆฌ์˜ ์—”ํ„ฐํ”„๋ผ์ด์ฆˆ ์ƒํ’ˆ ๋ผ์ธ์„ ์œ„ํ•œ ๊ฒƒ์ด๋‹ค."
+ - "์—ฌ๊ธฐ์— ๋‚˜์˜ ์ƒ๊ฐ์„ ๋งํ•˜๊ณ  ์žˆ๋Š” 1000 ํŽ˜์ด์ง€ ์„ค๊ณ„ ๋ฌธ์„œ๊ฐ€ ์žˆ๋‹ค."
+ - "๋‚˜๋Š” 6๋‹ฌ๋™์•ˆ ์ด๊ฒƒ์„ ํ–ˆ์œผ๋‹ˆ..."
+ - "์—ฌ๊ธฐ์„ธ 5000๋ผ์ธ ์งœ๋ฆฌ ํŒจ์น˜๊ฐ€ ์žˆ์œผ๋‹ˆ..."
+ - "๋‚˜๋Š” ํ˜„์žฌ ๋’ค์ฃฝ๋ฐ•์ฃฝ์ธ ๊ฒƒ์„ ์žฌ์ž‘์„ฑํ–ˆ๋‹ค. ๊ทธ๋ฆฌ๊ณ  ์—ฌ๊ธฐ์—..."
+ - "๋‚˜๋Š” ๋งˆ๊ฐ์‹œํ•œ์„ ๊ฐ€์ง€๊ณ  ์žˆ์œผ๋ฏ€๋กœ ์ด ํŒจ์น˜๋Š” ์ง€๊ธˆ ์ ์šฉ๋  ํ•„์š”๊ฐ€ ์žˆ๋‹ค."
+
+์ปค๋„ ์ปค๋ฎค๋‹ˆํ‹ฐ๊ฐ€ ์ „ํ†ต์ ์ธ ์†Œํ”„ํŠธ์›จ์–ด ์—”์ง€๋‹ˆ์–ด๋ง ๊ฐœ๋ฐœ ํ™˜๊ฒฝ๋“ค๊ณผ
+๋˜ ๋‹ค๋ฅธ ์ ์€ ์–ผ๊ตด์„ ๋ณด์ง€ ์•Š๊ณ  ์ผํ•œ๋‹ค๋Š” ์ ์ด๋‹ค. ์ด๋ฉ”์ผ๊ณผ irc๋ฅผ ๋Œ€ํ™”์˜
+์ฃผ์š”์ˆ˜๋‹จ์œผ๋กœ ์‚ฌ์šฉํ•˜๋Š” ๊ฒƒ์˜ ํ•œ๊ฐ€์ง€ ์žฅ์ ์€ ์„ฑ๋ณ„์ด๋‚˜ ์ธ์ข…์˜ ์ฐจ๋ณ„์ด
+์—†๋‹ค๋Š” ๊ฒƒ์ด๋‹ค. ๋ฆฌ๋ˆ…์Šค ์ปค๋„์˜ ์ž‘์—… ํ™˜๊ฒฝ์—์„œ๋Š” ๋‹จ์ง€ ์ด๋ฉ”์ผ ์ฃผ์†Œ๋งŒ
+์•Œ์ˆ˜ ์žˆ๊ธฐ ๋•Œ๋ฌธ์— ์—ฌ์„ฑ๊ณผ ์†Œ์ˆ˜ ๋ฏผ์กฑ๋“ค๋„ ๋ชจ๋‘ ๋ฐ›์•„๋“ค์—ฌ์ง„๋‹ค. ๊ตญ์ œ์ ์œผ๋กœ
+์ผํ•˜๊ฒŒ ๋˜๋Š” ์ธก๋ฉด์€ ์‚ฌ๋žŒ์˜ ์ด๋ฆ„์— ๊ทผ๊ฑฐํ•˜์—ฌ ์„ฑ๋ณ„์„ ์ถ”์ธกํ•  ์ˆ˜ ์—†๊ฒŒ
+ํ•˜๊ธฐ๋•Œ๋ฌธ์— ์ฐจ๋ณ„์„ ์—†์• ๋Š” ๋ฐ ๋„์›€์„ ์ค€๋‹ค. Andrea๋ผ๋Š” ์ด๋ฆ„์„ ๊ฐ€์ง„ ๋‚จ์ž์™€
+Pat์ด๋ผ๋Š” ์ด๋ฆ„์„ ๊ฐ€์ง„ ์—ฌ์ž๊ฐ€ ์žˆ์„ ์ˆ˜๋„ ์žˆ๋Š” ๊ฒƒ์ด๋‹ค. ๋ฆฌ๋ˆ…์Šค ์ปค๋„์—์„œ
+์ž‘์—…ํ•˜๋ฉฐ ์ƒ๊ฐ์„ ํ‘œํ˜„ํ•ด์™”๋˜ ๋Œ€๋ถ€๋ถ„์˜ ์—ฌ์„ฑ๋“ค์€ ๊ธ์ •์ ์ธ ๊ฒฝํ—˜์„ ๊ฐ€์ง€๊ณ 
+์žˆ๋‹ค.
+
+์–ธ์–ด ์žฅ๋ฒฝ์€ ์˜์–ด์— ์ต์ˆ™ํ•˜์ง€ ์•Š์€ ๋ช‡๋ช‡ ์‚ฌ๋žŒ๋“ค์—๊ฒŒ ๋ฌธ์ œ๊ฐ€ ๋  ์ˆ˜๋„ ์žˆ๋‹ค.
+ ์–ธ์–ด์˜ ํ›Œ๋ฅญํ•œ ๊ตฌ์‚ฌ๋Š” ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์—์„œ ์˜ฌ๋ฐ”๋ฅด๊ฒŒ ์ž์‹ ์˜ ์ƒ๊ฐ์„
+ํ‘œํ˜„ํ•˜๊ธฐ ์œ„ํ•˜์—ฌ ํ•„์š”ํ•˜๋‹ค. ๊ทธ๋ž˜์„œ ์—ฌ๋Ÿฌ๋ถ„์€ ์ด๋ฉ”์ผ์„ ๋ณด๋‚ด๊ธฐ ์ „์—
+์˜์–ด๋ฅผ ์˜ฌ๋ฐ”๋ฅด๊ฒŒ ์‚ฌ์šฉํ•˜๊ณ  ์žˆ๋Š”์ง€๋ฅผ ์ฒดํฌํ•˜๋Š” ๊ฒƒ์ด ๋ฐ”๋žŒ์งํ•˜๋‹ค.
+
+
+์—ฌ๋Ÿฌ๋ถ„์˜ ๋ณ€๊ฒฝ์„ ๋‚˜๋ˆ„์–ด๋ผ
+------------------------
+
+๋ฆฌ๋ˆ…์Šค ์ปค๋„ ์ปค๋ฎค๋‹ˆํ‹ฐ๋Š” ํ•œ๊บผ๋ฒˆ์— ๊ต‰์žฅํžˆ ํฐ ์ฝ”๋“œ์˜ ๋ฌถ์Œ์„ ์‰ฝ๊ฒŒ
+๋ฐ›์•„๋“ค์ด์ง€ ์•Š๋Š”๋‹ค. ๋ณ€๊ฒฝ์€ ์ ์ ˆํ•˜๊ฒŒ ์†Œ๊ฐœ๋˜๊ณ , ๊ฒ€ํ† ๋˜๊ณ , ๊ฐ๊ฐ์˜
+๋ถ€๋ถ„์œผ๋กœ ์ž‘๊ฒŒ ๋‚˜๋ˆ„์–ด์ ธ์•ผ ํ•œ๋‹ค. ์ด๊ฒƒ์€ ํšŒ์‚ฌ์—์„œ ํ•˜๋Š” ๊ฒƒ๊ณผ๋Š” ์ •ํ™•ํžˆ
+๋ฐ˜๋Œ€๋˜๋Š” ๊ฒƒ์ด๋‹ค. ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ์ œ์•ˆ์€ ๊ฐœ๋ฐœ ์ดˆ๊ธฐ์— ์ผ์ฐ์ด ์†Œ๊ฐœ๋˜์•ผ ํ•œ๋‹ค.
+๊ทธ๋ž˜์„œ ์—ฌ๋Ÿฌ๋ถ„๋“ค์€ ์ž์‹ ์ด ํ•˜๊ณ  ์žˆ๋Š” ๊ฒƒ์— ๊ด€ํ•˜์—ฌ ํ”ผ๋“œ๋ฐฑ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ๊ฒŒ
+๋œ๋‹ค. ์ปค๋ฎค๋‹ˆํ‹ฐ๊ฐ€ ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ํ•จ๊ป˜ ์ผํ•˜๊ณ  ์žˆ๋‹ค๋Š” ๊ฒƒ์„
+๋Š๋ผ๋„๋ก ๋งŒ๋“ค๊ณ  ์ปค๋ฎค๋‹ˆํ‹ฐ๊ฐ€ ์—ฌ๋Ÿฌ๋ถ„์˜ ๊ธฐ๋Šฅ์„ ์œ„ํ•œ ์“ฐ๋ ˆ๊ธฐ ์žฅ์œผ๋กœ์„œ
+์‚ฌ์šฉ๋˜์ง€ ์•Š๊ณ  ์žˆ๋‹ค๋Š” ๊ฒƒ์„ ๋Š๋ผ๊ฒŒ ํ•˜์ž. ๊ทธ๋Ÿฌ๋‚˜ ๋ฉ”์ผ๋ง ๋ฆฌ์ŠคํŠธ์— ํ•œ๋ฒˆ์—
+50๊ฐœ์˜ ์ด๋ฉ”์ผ์„ ๋ณด๋‚ด์ง€๋Š” ๋ง์•„๋ผ. ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ์ผ๋ จ์˜ ํŒจ์น˜๋“ค์€ ํ•ญ์ƒ
+๋” ์ž‘์•„์•ผ ํ•œ๋‹ค.
+
+ํŒจ์น˜๋ฅผ ๋‚˜๋ˆ„๋Š” ์ด์œ ๋Š” ๋‹ค์Œ๊ณผ ๊ฐ™๋‹ค.
+
+1) ์ž‘์€ ํŒจ์น˜๋“ค์€ ์—ฌ๋Ÿฌ๋ถ„์˜ ํŒจ์น˜๋“ค์ด ์ ์šฉ๋  ์ˆ˜ ์žˆ๋Š” ํ™•๋ฅ ์„ ๋†’์—ฌ์ค€๋‹ค.
+ ์™œ๋ƒํ•˜๋ฉด ๋‹ค๋ฅธ ์‚ฌ๋žŒ๋“ค์€ ์ •ํ™•์„ฑ์„ ๊ฒ€์ฆํ•˜๊ธฐ ์œ„ํ•˜์—ฌ ๋งŽ์€ ์‹œ๊ฐ„๊ณผ ๋…ธ๋ ฅ์„
+ ๋“ค์ด๊ธฐ๋ฅผ ์›ํ•˜์ง€ ์•Š๋Š”๋‹ค. 5์ค„์˜ ํŒจ์น˜๋Š” ๋ฉ”์ธํŠธ๋„ˆ๊ฐ€ ๊ฑฐ์˜ ๋ช‡ ์ดˆ๊ฐ„ ํž๋—
+ ๋ณด๋ฉด ์ ์šฉ๋  ์ˆ˜ ์žˆ๋‹ค. ๊ทธ๋Ÿฌ๋‚˜ 500 ์ค„์˜ ํŒจ์น˜๋Š” ์ •ํ™•์„ฑ์„ ๊ฒ€ํ† ํ•˜๊ธฐ ์œ„ํ•˜์—ฌ
+ ๋ช‡์‹œ๊ฐ„์ด ๊ฑธ๋ฆด ์ˆ˜๋„ ์žˆ๋‹ค(๊ฑธ๋ฆฌ๋Š” ์‹œ๊ฐ„์€ ํŒจ์น˜์˜ ํฌ๊ธฐ ํ˜น์€ ๋‹ค๋ฅธ ๊ฒƒ์—
+ ๋น„๋ก€ํ•˜์—ฌ ๊ธฐํ•˜๊ธ‰์ˆ˜์ ์œผ๋กœ ๋Š˜์–ด๋‚œ๋‹ค).
+
+ ํŒจ์น˜๋ฅผ ์ž‘๊ฒŒ ๋งŒ๋“œ๋Š” ๊ฒƒ์€ ๋ฌด์—‡์ธ๊ฐ€ ์ž˜๋ชป๋˜์—ˆ์„ ๋•Œ ๋””๋ฒ„๊ทธํ•˜๋Š” ๊ฒƒ์„
+ ์‰ฝ๊ฒŒ ๋งŒ๋“ ๋‹ค. ์ฆ‰, ๊ทธ๋ ‡๊ฒŒ ๋งŒ๋“œ๋Š” ๊ฒƒ์€ ๋งค์šฐ ํฐ ํŒจ์น˜๋ฅผ ์ ์šฉํ•œ ํ›„์—
+ ์กฐ์‚ฌํ•˜๋Š” ๊ฒƒ ๋ณด๋‹ค ์ž‘์€ ํŒจ์น˜๋ฅผ ์ ์šฉํ•œ ํ›„์— (๊ทธ๋ฆฌ๊ณ  ๋ช‡๋ช‡์˜ ๊ฒƒ์ด
+ ๊นจ์กŒ์„ ๋•Œ) ํ•˜๋‚˜์”ฉ ํŒจ์น˜๋“ค์„ ์ œ๊ฑฐํ•ด๊ฐ€๋ฉฐ ๋””๋ฒ„๊ทธ ํ•˜๊ธฐ ์‰ฝ๋„๋ก ๋งŒ๋“ค์–ด ์ค€๋‹ค.
+
+2) ์ž‘์€ ํŒจ์น˜๋“ค์„ ๋ณด๋‚ด๋Š” ๊ฒƒ๋ฟ๋งŒ ์•„๋‹ˆ๋ผ ํŒจ์น˜๋“ค์„ ์ œ์ถœํ•˜๊ธฐ์ „์— ์žฌ์ž‘์„ฑํ•˜๊ณ 
+ ๊ฐ„๋‹จํ•˜๊ฒŒ(ํ˜น์€ ๊ฐ„๋‹จํ•œ๊ฒŒ ์žฌ๋ฐฐ์น˜ํ•˜์—ฌ) ํ•˜๋Š” ๊ฒƒ๋„ ์ค‘์š”ํ•˜๋‹ค.
+
+์—ฌ๊ธฐ์— ์ปค๋„ ๊ฐœ๋ฐœ์ž Al Viro์˜ ์ด์•ผ๊ธฐ๊ฐ€ ์žˆ๋‹ค.
+ "ํ•™์ƒ์˜ ์ˆ˜ํ•™ ์ˆ™์ œ๋ฅผ ์ฑ„์ ํ•˜๋Š” ์„ ์ƒ๋‹˜์„ ์ƒ๊ฐํ•ด๋ณด๋ผ. ์„ ์ƒ๋‹˜์€ ํ•™์ƒ๋“ค์ด
+ ๋‹ต์„ ์–ป์„๋•Œ๊นŒ์ง€ ๊ฒช์€ ์‹œํ–‰์ฐฉ์˜ค๋ฅผ ๋ณด๊ธธ ์›ํ•˜์ง€ ์•Š๋Š”๋‹ค. ์„ ์ƒ๋‹˜๋“ค์€
+ ๊ฐ„๊ฒฐํ•˜๊ณ  ๊ฐ€์žฅ ๋›ฐ์–ด๋‚œ ๋‹ต์„ ๋ณด๊ธธ ์›ํ•œ๋‹ค. ํ›Œ๋ฅญํ•œ ํ•™์ƒ์€ ์ด๊ฒƒ์„ ์•Œ๊ณ 
+ ๋งˆ์ง€๋ง‰์œผ๋กœ ๋‹ต์„ ์–ป๊ธฐ ์ „ ์ค‘๊ฐ„ ๊ณผ์ •๋“ค์„ ์ œ์ถœํ•˜์ง„ ์•Š๋Š”๋‹ค.
+
+ ์ปค๋„ ๊ฐœ๋ฐœ๋„ ๋งˆ์ฐฌ๊ฐ€์ง€์ด๋‹ค. ๋ฉ”์ธํŠธ๋„ˆ๋“ค๊ณผ ๊ฒ€ํ† ํ•˜๋Š” ์‚ฌ๋žŒ๋“ค์€ ๋ฌธ์ œ๋ฅผ
+ ํ’€์–ด๋‚˜๊ฐ€๋Š” ๊ณผ์ •์†์— ์ˆจ๊ฒจ์ง„ ๊ณผ์ •์„ ๋ณด๊ธธ ์›ํ•˜์ง„ ์•Š๋Š”๋‹ค. ๊ทธ๋“ค์€
+ ๊ฐ„๊ฒฐํ•˜๊ณ  ๋ฉ‹์ง„ ๋‹ต์„ ๋ณด๊ธธ ์›ํ•œ๋‹ค."
+
+์ปค๋ฎค๋‹ˆํ‹ฐ์™€ ํ•จ๊ป˜ ์ผํ•˜๋ฉฐ ๋›ฐ์–ด๋‚œ ๋‹ต์„ ์ฐพ๊ณ  ์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ์™„์„ฑ๋˜์ง€ ์•Š์€ ์ผ๋“ค
+์‚ฌ์ด์— ๊ท ํ˜•์„ ์œ ์ง€ํ•ด์•ผ ํ•˜๋Š” ์–ด๋ ค์›€์ด ์žˆ์„ ์ˆ˜ ์žˆ๋‹ค. ๊ทธ๋Ÿฌ๋ฏ€๋กœ ํ”„๋กœ์„ธ์Šค์˜
+์ดˆ๋ฐ˜์— ์—ฌ๋Ÿฌ๋ถ„์˜ ์ผ์„ ํ–ฅ์ƒ์‹œํ‚ค๊ธฐ์œ„ํ•œ ํ”ผ๋“œ๋ฐฑ์„ ์–ป๋Š” ๊ฒƒ ๋ฟ๋งŒ ์•„๋‹ˆ๋ผ
+์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ๋ณ€๊ฒฝ๋“ค์„ ์ž‘์€ ๋ฌถ์Œ์œผ๋กœ ์œ ์ง€ํ•ด์„œ ์‹ฌ์ง€์–ด๋Š” ์—ฌ๋Ÿฌ๋ถ„์˜ ์ž‘์—…์˜
+๋ชจ๋“  ๋ถ€๋ถ„์ด ์ง€๊ธˆ์€ ํฌํ•จ๋  ์ค€๋น„๊ฐ€ ๋˜์–ด์žˆ์ง€ ์•Š์ง€๋งŒ ์ž‘์€ ๋ถ€๋ถ„์€ ์ด๋ฏธ
+๋ฐ›์•„๋“ค์—ฌ์งˆ ์ˆ˜ ์žˆ๋„๋ก ์œ ์ง€ํ•˜๋Š” ๊ฒƒ์ด ๋ฐ”๋žŒ์งํ•˜๋‹ค.
+
+๋˜ํ•œ ์™„์„ฑ๋˜์ง€ ์•Š์•˜๊ณ  "๋‚˜์ค‘์— ์ˆ˜์ •๋  ๊ฒƒ์ด๋‹ค." ์™€ ๊ฐ™์€ ๊ฒƒ๋“ค์€ ํฌํ•จํ•˜๋Š”
+ํŒจ์น˜๋“ค์€ ๋ฐ›์•„๋“ค์—ฌ์ง€์ง€ ์•Š์„ ๊ฒƒ์ด๋ผ๋Š” ์ ์„ ์œ ๋…ํ•˜๋ผ.
+
+๋ณ€๊ฒฝ์„ ์ •๋‹นํ™”ํ•ด๋ผ
+-----------------
+
+์—ฌ๋Ÿฌ๋ถ„๋“ค์˜ ๋‚˜๋ˆ„์–ด์ง„ ํŒจ์น˜๋“ค์„ ๋ฆฌ๋ˆ…์Šค ์ปค๋ฎค๋‹ˆํ‹ฐ๊ฐ€ ์™œ ๋ฐ˜์˜ํ•ด์•ผ ํ•˜๋Š”์ง€๋ฅผ
+์•Œ๋„๋ก ํ•˜๋Š” ๊ฒƒ์€ ๋งค์šฐ ์ค‘์š”ํ•˜๋‹ค. ์ƒˆ๋กœ์šด ๊ธฐ๋Šฅ๋“ค์ด ํ•„์š”ํ•˜๊ณ  ์œ ์šฉํ•˜๋‹ค๋Š”
+๊ฒƒ์€ ๋ฐ˜๋“œ์‹œ ๊ทธ์— ๋งž๋Š” ์ด์œ ๊ฐ€ ์žˆ์–ด์•ผ ํ•œ๋‹ค.
+
+
+๋ณ€๊ฒฝ์„ ๋ฌธ์„œํ™”ํ•ด๋ผ
+-----------------
+
+์—ฌ๋Ÿฌ๋ถ„์ด ํŒจ์น˜๋ฅผ ๋ณด๋‚ด๋ ค ํ• ๋•Œ๋Š” ์—ฌ๋Ÿฌ๋ถ„์ด ๋ฌด์—‡์„ ๋งํ•˜๋ ค๊ณ  ํ•˜๋Š”์ง€๋ฅผ ์ถฉ๋ถ„ํžˆ
+์ƒ๊ฐํ•˜์—ฌ ์ด๋ฉ”์ผ์„ ์ž‘์„ฑํ•ด์•ผ ํ•œ๋‹ค. ์ด ์ •๋ณด๋Š” ํŒจ์น˜๋ฅผ ์œ„ํ•œ ChangeLog๊ฐ€ ๋ 
+๊ฒƒ์ด๋‹ค. ๊ทธ๋ฆฌ๊ณ  ํ•ญ์ƒ ๊ทธ ๋‚ด์šฉ์„ ๋ณด๊ธธ ์›ํ•˜๋Š” ๋ชจ๋“  ์‚ฌ๋žŒ๋“ค์„ ์œ„ํ•ด ๋ณด์กด๋ 
+๊ฒƒ์ด๋‹ค. ํŒจ์น˜๋Š” ์™„๋ฒฝํ•˜๊ฒŒ ๋‹ค์Œ๊ณผ ๊ฐ™์€ ๋‚ด์šฉ๋“ค์„ ํฌํ•จํ•˜์—ฌ ์„ค๋ช…ํ•ด์•ผ ํ•œ๋‹ค.
+ - ๋ณ€๊ฒฝ์ด ์™œ ํ•„์š”ํ•œ์ง€
+ - ํŒจ์น˜์— ๊ด€ํ•œ ์ „์ฒด ์„ค๊ณ„ ์–ดํ”„๋กœ์น˜
+ - ๊ตฌํ˜„ ์ƒ์„ธ๋“ค
+ - ํ…Œ์ŠคํŠธ ๊ฒฐ๊ณผ๋“ค
+
+์ด๊ฒƒ์ด ๋ฌด์—‡์ธ์ง€ ๋” ์ž์„ธํ•œ ๊ฒƒ์„ ์•Œ๊ณ  ์‹ถ๋‹ค๋ฉด ๋‹ค์Œ ๋ฌธ์„œ์˜ ChageLog ํ•ญ์„ ๋ด๋ผ.
+ "The Perfect Patch"
+ http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
+
+
+
+
+์ด ๋ชจ๋“  ๊ฒƒ์„ ํ•˜๋Š” ๊ฒƒ์€ ๋งค์šฐ ์–ด๋ ค์šด ์ผ์ด๋‹ค. ์™„๋ฒฝํžˆ ์†Œํ™”ํ•˜๋Š” ๋ฐ๋Š” ์ ์–ด๋„ ๋ช‡๋…„์ด
+๊ฑธ๋ฆด ์ˆ˜๋„ ์žˆ๋‹ค. ๋งŽ์€ ์ธ๋‚ด์™€ ๊ฒฐ์˜๊ฐ€ ํ•„์š”ํ•œ ๊ณ„์†๋˜๋Š” ๊ฐœ์„ ์˜ ๊ณผ์ •์ด๋‹ค. ๊ทธ๋Ÿฌ๋‚˜
+๊ฐ€๋Šฅํ•œํ•œ ํฌ๊ธฐํ•˜์ง€ ๋ง๋ผ. ๋งŽ์€ ์‚ฌ๋žŒ๋“ค์€ ์ด์ „๋ถ€ํ„ฐ ํ•ด์™”๋˜ ๊ฒƒ์ด๊ณ  ๊ทธ ์‚ฌ๋žŒ๋“ค๋„
+์ •ํ™•ํ•˜๊ฒŒ ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ์ง€๊ธˆ ์„œ ์žˆ๋Š” ๊ทธ ๊ณณ๋ถ€ํ„ฐ ์‹œ์ž‘ํ–ˆ์—ˆ๋‹ค.
+
+
+
+
+----------
+"๊ฐœ๋ฐœ ํ”„๋กœ์„ธ์Šค"(http://linux.tar.gz/articles/2.6-development_process) ์„น์…˜์„
+์ž‘์„ฑํ•˜๋Š”๋ฐ ์žˆ์–ด ์ฐธ๊ณ ํ•  ๋ฌธ์„œ๋ฅผ ์‚ฌ์šฉํ•˜๋„๋ก ํ—ˆ๋ฝํ•ด์ค€ Paolo Ciarrocchi์—๊ฒŒ
+๊ฐ์‚ฌํ•œ๋‹ค. ์—ฌ๋Ÿฌ๋ถ„๋“ค์ด ๋งํ•ด์•ผ ํ•  ๊ฒƒ๊ณผ ๋งํ•ด์„œ๋Š” ์•ˆ๋˜๋Š” ๊ฒƒ์˜ ๋ชฉ๋ก ์ค‘ ์ผ๋ถ€๋ฅผ ์ œ๊ณตํ•ด์ค€
+Randy Dunlap๊ณผ Gerrit Huizenga์—๊ฒŒ ๊ฐ์‚ฌํ•œ๋‹ค. ๋˜ํ•œ ๊ฒ€ํ† ์™€ ์˜๊ฒฌ ๊ทธ๋ฆฌ๊ณ 
+๊ณตํ—Œ์„ ์•„๋ผ์ง€ ์•Š์€ Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers,
+Vojtech Pavlik, Jan Kara, Josh Boyer, Kees Cook, Andrew Morton, Andi Kleen,
+Vadim Lobanov, Jesper Juhl, Adrian Bunk, Keri Harris, Frans Pop,
+David A. Wheeler, Junio Hamano, Michael Kerrisk, and Alex Shepard์—๊ฒŒ๋„ ๊ฐ์‚ฌ๋ฅผ ์ „ํ•œ๋‹ค.
+๊ทธ๋“ค์˜ ๋„์›€์ด ์—†์—ˆ๋‹ค๋ฉด ์ด ๋ฌธ์„œ๋Š” ์กด์žฌํ•˜์ง€ ์•Š์•˜์„ ๊ฒƒ์ด๋‹ค.
+
+
+
+๋ฉ”์ธํŠธ๋„ˆ: Greg Kroah-Hartman <greg@kroah.com>
diff --git a/Documentation/lguest/lguest.c b/Documentation/lguest/lguest.c
index f791840..73c5f1f 100644
--- a/Documentation/lguest/lguest.c
+++ b/Documentation/lguest/lguest.c
@@ -882,7 +882,7 @@ static u32 handle_block_output(int fd, const struct iovec *iov,
* of the block file (possibly extending it). */
if (off + len > device_len) {
/* Trim it back to the correct length */
- ftruncate(dev->fd, device_len);
+ ftruncate64(dev->fd, device_len);
/* Die, bad Guest, die. */
errx(1, "Write past end %llu+%u", off, len);
}
diff --git a/Documentation/lockstat.txt b/Documentation/lockstat.txt
new file mode 100644
index 0000000..4ba4664
--- /dev/null
+++ b/Documentation/lockstat.txt
@@ -0,0 +1,120 @@
+
+LOCK STATISTICS
+
+- WHAT
+
+As the name suggests, it provides statistics on locks.
+
+- WHY
+
+Because things like lock contention can severely impact performance.
+
+- HOW
+
+Lockdep already has hooks in the lock functions and maps lock instances to
+lock classes. We build on that. The graph below shows the relation between
+the lock functions and the various hooks therein.
+
+ __acquire
+ |
+ lock _____
+ | \
+ | __contended
+ | |
+ | <wait>
+ | _______/
+ |/
+ |
+ __acquired
+ |
+ .
+ <hold>
+ .
+ |
+ __release
+ |
+ unlock
+
+lock, unlock - the regular lock functions
+__* - the hooks
+<> - states
+
+With these hooks we provide the following statistics:
+
+ con-bounces - number of lock contention that involved x-cpu data
+ contentions - number of lock acquisitions that had to wait
+ wait time min - shortest (non-0) time we ever had to wait for a lock
+ max - longest time we ever had to wait for a lock
+ total - total time we spend waiting on this lock
+ acq-bounces - number of lock acquisitions that involved x-cpu data
+ acquisitions - number of times we took the lock
+ hold time min - shortest (non-0) time we ever held the lock
+ max - longest time we ever held the lock
+ total - total time this lock was held
+
+From these number various other statistics can be derived, such as:
+
+ hold time average = hold time total / acquisitions
+
+These numbers are gathered per lock class, per read/write state (when
+applicable).
+
+It also tracks 4 contention points per class. A contention point is a call site
+that had to wait on lock acquisition.
+
+ - USAGE
+
+Look at the current lock statistics:
+
+( line numbers not part of actual output, done for clarity in the explanation
+ below )
+
+# less /proc/lock_stat
+
+01 lock_stat version 0.2
+02 -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+03 class name con-bounces contentions waittime-min waittime-max waittime-total acq-bounces acquisitions holdtime-min holdtime-max holdtime-total
+04 -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+05
+06 &inode->i_data.tree_lock-W: 15 21657 0.18 1093295.30 11547131054.85 58 10415 0.16 87.51 6387.60
+07 &inode->i_data.tree_lock-R: 0 0 0.00 0.00 0.00 23302 231198 0.25 8.45 98023.38
+08 --------------------------
+09 &inode->i_data.tree_lock 0 [<ffffffff8027c08f>] add_to_page_cache+0x5f/0x190
+10
+11 ...............................................................................................................................................................................................
+12
+13 dcache_lock: 1037 1161 0.38 45.32 774.51 6611 243371 0.15 306.48 77387.24
+14 -----------
+15 dcache_lock 180 [<ffffffff802c0d7e>] sys_getcwd+0x11e/0x230
+16 dcache_lock 165 [<ffffffff802c002a>] d_alloc+0x15a/0x210
+17 dcache_lock 33 [<ffffffff8035818d>] _atomic_dec_and_lock+0x4d/0x70
+18 dcache_lock 1 [<ffffffff802beef8>] shrink_dcache_parent+0x18/0x130
+
+This excerpt shows the first two lock class statistics. Line 01 shows the
+output version - each time the format changes this will be updated. Line 02-04
+show the header with column descriptions. Lines 05-10 and 13-18 show the actual
+statistics. These statistics come in two parts; the actual stats separated by a
+short separator (line 08, 14) from the contention points.
+
+The first lock (05-10) is a read/write lock, and shows two lines above the
+short separator. The contention points don't match the column descriptors,
+they have two: contentions and [<IP>] symbol.
+
+
+View the top contending locks:
+
+# grep : /proc/lock_stat | head
+ &inode->i_data.tree_lock-W: 15 21657 0.18 1093295.30 11547131054.85 58 10415 0.16 87.51 6387.60
+ &inode->i_data.tree_lock-R: 0 0 0.00 0.00 0.00 23302 231198 0.25 8.45 98023.38
+ dcache_lock: 1037 1161 0.38 45.32 774.51 6611 243371 0.15 306.48 77387.24
+ &inode->i_mutex: 161 286 18446744073709 62882.54 1244614.55 3653 20598 18446744073709 62318.60 1693822.74
+ &zone->lru_lock: 94 94 0.53 7.33 92.10 4366 32690 0.29 59.81 16350.06
+ &inode->i_data.i_mmap_lock: 79 79 0.40 3.77 53.03 11779 87755 0.28 116.93 29898.44
+ &q->__queue_lock: 48 50 0.52 31.62 86.31 774 13131 0.17 113.08 12277.52
+ &rq->rq_lock_key: 43 47 0.74 68.50 170.63 3706 33929 0.22 107.99 17460.62
+ &rq->rq_lock_key#2: 39 46 0.75 6.68 49.03 2979 32292 0.17 125.17 17137.63
+ tasklist_lock-W: 15 15 1.45 10.87 32.70 1201 7390 0.58 62.55 13648.47
+
+Clear the statistics:
+
+# echo 0 > /proc/lock_stat
diff --git a/Documentation/networking/00-INDEX b/Documentation/networking/00-INDEX
index d63f480..153d84d 100644
--- a/Documentation/networking/00-INDEX
+++ b/Documentation/networking/00-INDEX
@@ -96,6 +96,9 @@ routing.txt
- the new routing mechanism
shaper.txt
- info on the module that can shape/limit transmitted traffic.
+sk98lin.txt
+ - Marvell Yukon Chipset / SysKonnect SK-98xx compliant Gigabit
+ Ethernet Adapter family driver info
skfp.txt
- SysKonnect FDDI (SK-5xxx, Compaq Netelligent) driver info.
smc9.txt
diff --git a/Documentation/networking/multiqueue.txt b/Documentation/networking/multiqueue.txt
index 00b60cc..ea5a42e 100644
--- a/Documentation/networking/multiqueue.txt
+++ b/Documentation/networking/multiqueue.txt
@@ -58,9 +58,13 @@ software, so it's a straight round-robin qdisc. It uses the same syntax and
classification priomap that sch_prio uses, so it should be intuitive to
configure for people who've used sch_prio.
-The PRIO qdisc naturally plugs into a multiqueue device. If PRIO has been
-built with NET_SCH_PRIO_MQ, then upon load, it will make sure the number of
-bands requested is equal to the number of queues on the hardware. If they
+In order to utilitize the multiqueue features of the qdiscs, the network
+device layer needs to enable multiple queue support. This can be done by
+selecting NETDEVICES_MULTIQUEUE under Drivers.
+
+The PRIO qdisc naturally plugs into a multiqueue device. If
+NETDEVICES_MULTIQUEUE is selected, then on qdisc load, the number of
+bands requested is compared to the number of queues on the hardware. If they
are equal, it sets a one-to-one mapping up between the queues and bands. If
they're not equal, it will not load the qdisc. This is the same behavior
for RR. Once the association is made, any skb that is classified will have
diff --git a/Documentation/networking/sk98lin.txt b/Documentation/networking/sk98lin.txt
new file mode 100644
index 0000000..8590a95
--- /dev/null
+++ b/Documentation/networking/sk98lin.txt
@@ -0,0 +1,568 @@
+(C)Copyright 1999-2004 Marvell(R).
+All rights reserved
+===========================================================================
+
+sk98lin.txt created 13-Feb-2004
+
+Readme File for sk98lin v6.23
+Marvell Yukon/SysKonnect SK-98xx Gigabit Ethernet Adapter family driver for LINUX
+
+This file contains
+ 1 Overview
+ 2 Required Files
+ 3 Installation
+ 3.1 Driver Installation
+ 3.2 Inclusion of adapter at system start
+ 4 Driver Parameters
+ 4.1 Per-Port Parameters
+ 4.2 Adapter Parameters
+ 5 Large Frame Support
+ 6 VLAN and Link Aggregation Support (IEEE 802.1, 802.1q, 802.3ad)
+ 7 Troubleshooting
+
+===========================================================================
+
+
+1 Overview
+===========
+
+The sk98lin driver supports the Marvell Yukon and SysKonnect
+SK-98xx/SK-95xx compliant Gigabit Ethernet Adapter on Linux. It has
+been tested with Linux on Intel/x86 machines.
+***
+
+
+2 Required Files
+=================
+
+The linux kernel source.
+No additional files required.
+***
+
+
+3 Installation
+===============
+
+It is recommended to download the latest version of the driver from the
+SysKonnect web site www.syskonnect.com. If you have downloaded the latest
+driver, the Linux kernel has to be patched before the driver can be
+installed. For details on how to patch a Linux kernel, refer to the
+patch.txt file.
+
+3.1 Driver Installation
+------------------------
+
+The following steps describe the actions that are required to install
+the driver and to start it manually. These steps should be carried
+out for the initial driver setup. Once confirmed to be ok, they can
+be included in the system start.
+
+NOTE 1: To perform the following tasks you need 'root' access.
+
+NOTE 2: In case of problems, please read the section "Troubleshooting"
+ below.
+
+The driver can either be integrated into the kernel or it can be compiled
+as a module. Select the appropriate option during the kernel
+configuration.
+
+Compile/use the driver as a module
+----------------------------------
+To compile the driver, go to the directory /usr/src/linux and
+execute the command "make menuconfig" or "make xconfig" and proceed as
+follows:
+
+To integrate the driver permanently into the kernel, proceed as follows:
+
+1. Select the menu "Network device support" and then "Ethernet(1000Mbit)"
+2. Mark "Marvell Yukon Chipset / SysKonnect SK-98xx family support"
+ with (*)
+3. Build a new kernel when the configuration of the above options is
+ finished.
+4. Install the new kernel.
+5. Reboot your system.
+
+To use the driver as a module, proceed as follows:
+
+1. Enable 'loadable module support' in the kernel.
+2. For automatic driver start, enable the 'Kernel module loader'.
+3. Select the menu "Network device support" and then "Ethernet(1000Mbit)"
+4. Mark "Marvell Yukon Chipset / SysKonnect SK-98xx family support"
+ with (M)
+5. Execute the command "make modules".
+6. Execute the command "make modules_install".
+ The appropriate modules will be installed.
+7. Reboot your system.
+
+
+Load the module manually
+------------------------
+To load the module manually, proceed as follows:
+
+1. Enter "modprobe sk98lin".
+2. If a Marvell Yukon or SysKonnect SK-98xx adapter is installed in
+ your computer and you have a /proc file system, execute the command:
+ "ls /proc/net/sk98lin/"
+ This should produce an output containing a line with the following
+ format:
+ eth0 eth1 ...
+ which indicates that your adapter has been found and initialized.
+
+ NOTE 1: If you have more than one Marvell Yukon or SysKonnect SK-98xx
+ adapter installed, the adapters will be listed as 'eth0',
+ 'eth1', 'eth2', etc.
+ For each adapter, repeat steps 3 and 4 below.
+
+ NOTE 2: If you have other Ethernet adapters installed, your Marvell
+ Yukon or SysKonnect SK-98xx adapter will be mapped to the
+ next available number, e.g. 'eth1'. The mapping is executed
+ automatically.
+ The module installation message (displayed either in a system
+ log file or on the console) prints a line for each adapter
+ found containing the corresponding 'ethX'.
+
+3. Select an IP address and assign it to the respective adapter by
+ entering:
+ ifconfig eth0 <ip-address>
+ With this command, the adapter is connected to the Ethernet.
+
+ SK-98xx Gigabit Ethernet Server Adapters: The yellow LED on the adapter
+ is now active, the link status LED of the primary port is active and
+ the link status LED of the secondary port (on dual port adapters) is
+ blinking (if the ports are connected to a switch or hub).
+ SK-98xx V2.0 Gigabit Ethernet Adapters: The link status LED is active.
+ In addition, you will receive a status message on the console stating
+ "ethX: network connection up using port Y" and showing the selected
+ connection parameters (x stands for the ethernet device number
+ (0,1,2, etc), y stands for the port name (A or B)).
+
+ NOTE: If you are in doubt about IP addresses, ask your network
+ administrator for assistance.
+
+4. Your adapter should now be fully operational.
+ Use 'ping <otherstation>' to verify the connection to other computers
+ on your network.
+5. To check the adapter configuration view /proc/net/sk98lin/[devicename].
+ For example by executing:
+ "cat /proc/net/sk98lin/eth0"
+
+Unload the module
+-----------------
+To stop and unload the driver modules, proceed as follows:
+
+1. Execute the command "ifconfig eth0 down".
+2. Execute the command "rmmod sk98lin".
+
+3.2 Inclusion of adapter at system start
+-----------------------------------------
+
+Since a large number of different Linux distributions are
+available, we are unable to describe a general installation procedure
+for the driver module.
+Because the driver is now integrated in the kernel, installation should
+be easy, using the standard mechanism of your distribution.
+Refer to the distribution's manual for installation of ethernet adapters.
+
+***
+
+4 Driver Parameters
+====================
+
+Parameters can be set at the command line after the module has been
+loaded with the command 'modprobe'.
+In some distributions, the configuration tools are able to pass parameters
+to the driver module.
+
+If you use the kernel module loader, you can set driver parameters
+in the file /etc/modprobe.conf (or /etc/modules.conf in 2.4 or earlier).
+To set the driver parameters in this file, proceed as follows:
+
+1. Insert a line of the form :
+ options sk98lin ...
+ For "...", the same syntax is required as described for the command
+ line parameters of modprobe below.
+2. To activate the new parameters, either reboot your computer
+ or
+ unload and reload the driver.
+ The syntax of the driver parameters is:
+
+ modprobe sk98lin parameter=value1[,value2[,value3...]]
+
+ where value1 refers to the first adapter, value2 to the second etc.
+
+NOTE: All parameters are case sensitive. Write them exactly as shown
+ below.
+
+Example:
+Suppose you have two adapters. You want to set auto-negotiation
+on the first adapter to ON and on the second adapter to OFF.
+You also want to set DuplexCapabilities on the first adapter
+to FULL, and on the second adapter to HALF.
+Then, you must enter:
+
+ modprobe sk98lin AutoNeg_A=On,Off DupCap_A=Full,Half
+
+NOTE: The number of adapters that can be configured this way is
+ limited in the driver (file skge.c, constant SK_MAX_CARD_PARAM).
+ The current limit is 16. If you happen to install
+ more adapters, adjust this and recompile.
+
+
+4.1 Per-Port Parameters
+------------------------
+
+These settings are available for each port on the adapter.
+In the following description, '?' stands for the port for
+which you set the parameter (A or B).
+
+Speed
+-----
+Parameter: Speed_?
+Values: 10, 100, 1000, Auto
+Default: Auto
+
+This parameter is used to set the speed capabilities. It is only valid
+for the SK-98xx V2.0 copper adapters.
+Usually, the speed is negotiated between the two ports during link
+establishment. If this fails, a port can be forced to a specific setting
+with this parameter.
+
+Auto-Negotiation
+----------------
+Parameter: AutoNeg_?
+Values: On, Off, Sense
+Default: On
+
+The "Sense"-mode automatically detects whether the link partner supports
+auto-negotiation or not.
+
+Duplex Capabilities
+-------------------
+Parameter: DupCap_?
+Values: Half, Full, Both
+Default: Both
+
+This parameters is only relevant if auto-negotiation for this port is
+not set to "Sense". If auto-negotiation is set to "On", all three values
+are possible. If it is set to "Off", only "Full" and "Half" are allowed.
+This parameter is useful if your link partner does not support all
+possible combinations.
+
+Flow Control
+------------
+Parameter: FlowCtrl_?
+Values: Sym, SymOrRem, LocSend, None
+Default: SymOrRem
+
+This parameter can be used to set the flow control capabilities the
+port reports during auto-negotiation. It can be set for each port
+individually.
+Possible modes:
+ -- Sym = Symmetric: both link partners are allowed to send
+ PAUSE frames
+ -- SymOrRem = SymmetricOrRemote: both or only remote partner
+ are allowed to send PAUSE frames
+ -- LocSend = LocalSend: only local link partner is allowed
+ to send PAUSE frames
+ -- None = no link partner is allowed to send PAUSE frames
+
+NOTE: This parameter is ignored if auto-negotiation is set to "Off".
+
+Role in Master-Slave-Negotiation (1000Base-T only)
+--------------------------------------------------
+Parameter: Role_?
+Values: Auto, Master, Slave
+Default: Auto
+
+This parameter is only valid for the SK-9821 and SK-9822 adapters.
+For two 1000Base-T ports to communicate, one must take the role of the
+master (providing timing information), while the other must be the
+slave. Usually, this is negotiated between the two ports during link
+establishment. If this fails, a port can be forced to a specific setting
+with this parameter.
+
+
+4.2 Adapter Parameters
+-----------------------
+
+Connection Type (SK-98xx V2.0 copper adapters only)
+---------------
+Parameter: ConType
+Values: Auto, 100FD, 100HD, 10FD, 10HD
+Default: Auto
+
+The parameter 'ConType' is a combination of all five per-port parameters
+within one single parameter. This simplifies the configuration of both ports
+of an adapter card! The different values of this variable reflect the most
+meaningful combinations of port parameters.
+
+The following table shows the values of 'ConType' and the corresponding
+combinations of the per-port parameters:
+
+ ConType | DupCap AutoNeg FlowCtrl Role Speed
+ ----------+------------------------------------------------------
+ Auto | Both On SymOrRem Auto Auto
+ 100FD | Full Off None Auto (ignored) 100
+ 100HD | Half Off None Auto (ignored) 100
+ 10FD | Full Off None Auto (ignored) 10
+ 10HD | Half Off None Auto (ignored) 10
+
+Stating any other port parameter together with this 'ConType' variable
+will result in a merged configuration of those settings. This due to
+the fact, that the per-port parameters (e.g. Speed_? ) have a higher
+priority than the combined variable 'ConType'.
+
+NOTE: This parameter is always used on both ports of the adapter card.
+
+Interrupt Moderation
+--------------------
+Parameter: Moderation
+Values: None, Static, Dynamic
+Default: None
+
+Interrupt moderation is employed to limit the maximum number of interrupts
+the driver has to serve. That is, one or more interrupts (which indicate any
+transmit or receive packet to be processed) are queued until the driver
+processes them. When queued interrupts are to be served, is determined by the
+'IntsPerSec' parameter, which is explained later below.
+
+Possible modes:
+
+ -- None - No interrupt moderation is applied on the adapter card.
+ Therefore, each transmit or receive interrupt is served immediately
+ as soon as it appears on the interrupt line of the adapter card.
+
+ -- Static - Interrupt moderation is applied on the adapter card.
+ All transmit and receive interrupts are queued until a complete
+ moderation interval ends. If such a moderation interval ends, all
+ queued interrupts are processed in one big bunch without any delay.
+ The term 'static' reflects the fact, that interrupt moderation is
+ always enabled, regardless how much network load is currently
+ passing via a particular interface. In addition, the duration of
+ the moderation interval has a fixed length that never changes while
+ the driver is operational.
+
+ -- Dynamic - Interrupt moderation might be applied on the adapter card,
+ depending on the load of the system. If the driver detects that the
+ system load is too high, the driver tries to shield the system against
+ too much network load by enabling interrupt moderation. If - at a later
+ time - the CPU utilization decreases again (or if the network load is
+ negligible) the interrupt moderation will automatically be disabled.
+
+Interrupt moderation should be used when the driver has to handle one or more
+interfaces with a high network load, which - as a consequence - leads also to a
+high CPU utilization. When moderation is applied in such high network load
+situations, CPU load might be reduced by 20-30%.
+
+NOTE: The drawback of using interrupt moderation is an increase of the round-
+trip-time (RTT), due to the queueing and serving of interrupts at dedicated
+moderation times.
+
+Interrupts per second
+---------------------
+Parameter: IntsPerSec
+Values: 30...40000 (interrupts per second)
+Default: 2000
+
+This parameter is only used if either static or dynamic interrupt moderation
+is used on a network adapter card. Using this parameter if no moderation is
+applied will lead to no action performed.
+
+This parameter determines the length of any interrupt moderation interval.
+Assuming that static interrupt moderation is to be used, an 'IntsPerSec'
+parameter value of 2000 will lead to an interrupt moderation interval of
+500 microseconds.
+
+NOTE: The duration of the moderation interval is to be chosen with care.
+At first glance, selecting a very long duration (e.g. only 100 interrupts per
+second) seems to be meaningful, but the increase of packet-processing delay
+is tremendous. On the other hand, selecting a very short moderation time might
+compensate the use of any moderation being applied.
+
+
+Preferred Port
+--------------
+Parameter: PrefPort
+Values: A, B
+Default: A
+
+This is used to force the preferred port to A or B (on dual-port network
+adapters). The preferred port is the one that is used if both are detected
+as fully functional.
+
+RLMT Mode (Redundant Link Management Technology)
+------------------------------------------------
+Parameter: RlmtMode
+Values: CheckLinkState,CheckLocalPort, CheckSeg, DualNet
+Default: CheckLinkState
+
+RLMT monitors the status of the port. If the link of the active port
+fails, RLMT switches immediately to the standby link. The virtual link is
+maintained as long as at least one 'physical' link is up.
+
+Possible modes:
+
+ -- CheckLinkState - Check link state only: RLMT uses the link state
+ reported by the adapter hardware for each individual port to
+ determine whether a port can be used for all network traffic or
+ not.
+
+ -- CheckLocalPort - In this mode, RLMT monitors the network path
+ between the two ports of an adapter by regularly exchanging packets
+ between them. This mode requires a network configuration in which
+ the two ports are able to "see" each other (i.e. there must not be
+ any router between the ports).
+
+ -- CheckSeg - Check local port and segmentation: This mode supports the
+ same functions as the CheckLocalPort mode and additionally checks
+ network segmentation between the ports. Therefore, this mode is only
+ to be used if Gigabit Ethernet switches are installed on the network
+ that have been configured to use the Spanning Tree protocol.
+
+ -- DualNet - In this mode, ports A and B are used as separate devices.
+ If you have a dual port adapter, port A will be configured as eth0
+ and port B as eth1. Both ports can be used independently with
+ distinct IP addresses. The preferred port setting is not used.
+ RLMT is turned off.
+
+NOTE: RLMT modes CLP and CLPSS are designed to operate in configurations
+ where a network path between the ports on one adapter exists.
+ Moreover, they are not designed to work where adapters are connected
+ back-to-back.
+***
+
+
+5 Large Frame Support
+======================
+
+The driver supports large frames (also called jumbo frames). Using large
+frames can result in an improved throughput if transferring large amounts
+of data.
+To enable large frames, set the MTU (maximum transfer unit) of the
+interface to the desired value (up to 9000), execute the following
+command:
+ ifconfig eth0 mtu 9000
+This will only work if you have two adapters connected back-to-back
+or if you use a switch that supports large frames. When using a switch,
+it should be configured to allow large frames and auto-negotiation should
+be set to OFF. The setting must be configured on all adapters that can be
+reached by the large frames. If one adapter is not set to receive large
+frames, it will simply drop them.
+
+You can switch back to the standard ethernet frame size by executing the
+following command:
+ ifconfig eth0 mtu 1500
+
+To permanently configure this setting, add a script with the 'ifconfig'
+line to the system startup sequence (named something like "S99sk98lin"
+in /etc/rc.d/rc2.d).
+***
+
+
+6 VLAN and Link Aggregation Support (IEEE 802.1, 802.1q, 802.3ad)
+==================================================================
+
+The Marvell Yukon/SysKonnect Linux drivers are able to support VLAN and
+Link Aggregation according to IEEE standards 802.1, 802.1q, and 802.3ad.
+These features are only available after installation of open source
+modules available on the Internet:
+For VLAN go to: http://www.candelatech.com/~greear/vlan.html
+For Link Aggregation go to: http://www.st.rim.or.jp/~yumo
+
+NOTE: SysKonnect GmbH does not offer any support for these open source
+ modules and does not take the responsibility for any kind of
+ failures or problems arising in connection with these modules.
+
+NOTE: Configuring Link Aggregation on a SysKonnect dual link adapter may
+ cause problems when unloading the driver.
+
+
+7 Troubleshooting
+==================
+
+If any problems occur during the installation process, check the
+following list:
+
+
+Problem: The SK-98xx adapter cannot be found by the driver.
+Solution: In /proc/pci search for the following entry:
+ 'Ethernet controller: SysKonnect SK-98xx ...'
+ If this entry exists, the SK-98xx or SK-98xx V2.0 adapter has
+ been found by the system and should be operational.
+ If this entry does not exist or if the file '/proc/pci' is not
+ found, there may be a hardware problem or the PCI support may
+ not be enabled in your kernel.
+ The adapter can be checked using the diagnostics program which
+ is available on the SysKonnect web site:
+ www.syskonnect.com
+
+ Some COMPAQ machines have problems dealing with PCI under Linux.
+ This problem is described in the 'PCI howto' document
+ (included in some distributions or available from the
+ web, e.g. at 'www.linux.org').
+
+
+Problem: Programs such as 'ifconfig' or 'route' cannot be found or the
+ error message 'Operation not permitted' is displayed.
+Reason: You are not logged in as user 'root'.
+Solution: Logout and login as 'root' or change to 'root' via 'su'.
+
+
+Problem: Upon use of the command 'ping <address>' the message
+ "ping: sendto: Network is unreachable" is displayed.
+Reason: Your route is not set correctly.
+Solution: If you are using RedHat, you probably forgot to set up the
+ route in the 'network configuration'.
+ Check the existing routes with the 'route' command and check
+ if an entry for 'eth0' exists, and if so, if it is set correctly.
+
+
+Problem: The driver can be started, the adapter is connected to the
+ network, but you cannot receive or transmit any packets;
+ e.g. 'ping' does not work.
+Reason: There is an incorrect route in your routing table.
+Solution: Check the routing table with the command 'route' and read the
+ manual help pages dealing with routes (enter 'man route').
+
+NOTE: Although the 2.2.x kernel versions generate the routing entry
+ automatically, problems of this kind may occur here as well. We've
+ come across a situation in which the driver started correctly at
+ system start, but after the driver has been removed and reloaded,
+ the route of the adapter's network pointed to the 'dummy0'device
+ and had to be corrected manually.
+
+
+Problem: Your computer should act as a router between multiple
+ IP subnetworks (using multiple adapters), but computers in
+ other subnetworks cannot be reached.
+Reason: Either the router's kernel is not configured for IP forwarding
+ or the routing table and gateway configuration of at least one
+ computer is not working.
+
+Problem: Upon driver start, the following error message is displayed:
+ "eth0: -- ERROR --
+ Class: internal Software error
+ Nr: 0xcc
+ Msg: SkGeInitPort() cannot init running ports"
+Reason: You are using a driver compiled for single processor machines
+ on a multiprocessor machine with SMP (Symmetric MultiProcessor)
+ kernel.
+Solution: Configure your kernel appropriately and recompile the kernel or
+ the modules.
+
+
+
+If your problem is not listed here, please contact SysKonnect's technical
+support for help (linux@syskonnect.de).
+When contacting our technical support, please ensure that the following
+information is available:
+- System Manufacturer and HW Informations (CPU, Memory... )
+- PCI-Boards in your system
+- Distribution
+- Kernel version
+- Driver version
+***
+
+
+
+***End of Readme File***
diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt
index ef19142..10c8f69 100644
--- a/Documentation/sysrq.txt
+++ b/Documentation/sysrq.txt
@@ -43,7 +43,7 @@ On x86 - You press the key combo 'ALT-SysRq-<command key>'. Note - Some
keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is
also known as the 'Print Screen' key. Also some keyboards cannot
handle so many keys being pressed at the same time, so you might
- have better luck with "press Alt", "press SysRq", "release Alt",
+ have better luck with "press Alt", "press SysRq", "release SysRq",
"press <command key>", release everything.
On SPARC - You press 'ALT-STOP-<command key>', I believe.
diff --git a/Documentation/thinkpad-acpi.txt b/Documentation/thinkpad-acpi.txt
index eb2f598..60953d6 100644
--- a/Documentation/thinkpad-acpi.txt
+++ b/Documentation/thinkpad-acpi.txt
@@ -1,7 +1,7 @@
ThinkPad ACPI Extras Driver
- Version 0.15
- July 1st, 2007
+ Version 0.16
+ August 2nd, 2007
Borislav Deianov <borislav@users.sf.net>
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
@@ -161,20 +161,22 @@ system. Enabling the hotkey functionality of thinkpad-acpi signals the
firmware that such a driver is present, and modifies how the ThinkPad
firmware will behave in many situations.
+The driver enables the hot key feature automatically when loaded. The
+feature can later be disabled and enabled back at runtime. The driver
+will also restore the hot key feature to its previous state and mask
+when it is unloaded.
+
When the hotkey feature is enabled and the hot key mask is set (see
-below), the various hot keys either generate ACPI events in the
-following format:
+below), the driver will report HKEY events in the following format:
ibm/hotkey HKEY 00000080 0000xxxx
-or events over the input layer. The input layer support accepts the
-standard IOCTLs to remap the keycodes assigned to each hotkey.
+Some of these events refer to hot key presses, but not all.
-When the input device is open, the driver will suppress any ACPI hot key
-events that get translated into a meaningful input layer event, in order
-to avoid sending duplicate events to userspace. Hot keys that are
-mapped to KEY_RESERVED in the keymap are not translated, and will always
-generate an ACPI ibm/hotkey HKEY event, and no input layer events.
+The driver will generate events over the input layer for hot keys and
+radio switches, and over the ACPI netlink layer for other events. The
+input layer support accepts the standard IOCTLs to remap the keycodes
+assigned to each hot key.
The hot key bit mask allows some control over which hot keys generate
events. If a key is "masked" (bit set to 0 in the mask), the firmware
@@ -256,6 +258,20 @@ sysfs notes:
disabled" postition, and 1 if the switch is in the
"radios enabled" position.
+ hotkey_report_mode:
+ Returns the state of the procfs ACPI event report mode
+ filter for hot keys. If it is set to 1 (the default),
+ all hot key presses are reported both through the input
+ layer and also as ACPI events through procfs (but not
+ through netlink). If it is set to 2, hot key presses
+ are reported only through the input layer.
+
+ This attribute is read-only in kernels 2.6.23 or later,
+ and read-write on earlier kernels.
+
+ May return -EPERM (write access locked out by module
+ parameter) or -EACCES (read-only).
+
input layer notes:
A Hot key is mapped to a single input layer EV_KEY event, possibly
@@ -393,21 +409,63 @@ unknown by the driver if the ThinkPad firmware triggered these events on
hot key press or release, but the firmware will do it for either one, not
both.
-If a key is mapped to KEY_RESERVED, it generates no input events at all,
-and it may generate a legacy thinkpad-acpi ACPI hotkey event.
-
+If a key is mapped to KEY_RESERVED, it generates no input events at all.
If a key is mapped to KEY_UNKNOWN, it generates an input event that
-includes an scan code, and it may also generate a legacy thinkpad-acpi
-ACPI hotkey event.
-
-If a key is mapped to anything else, it will only generate legacy
-thinkpad-acpi ACPI hotkey events if nobody has opened the input device.
+includes an scan code. If a key is mapped to anything else, it will
+generate input device EV_KEY events.
Non hot-key ACPI HKEY event map:
0x5001 Lid closed
0x5002 Lid opened
0x7000 Radio Switch may have changed state
+The above events are not propagated by the driver, except for legacy
+compatibility purposes when hotkey_report_mode is set to 1.
+
+Compatibility notes:
+
+ibm-acpi and thinkpad-acpi 0.15 (mainline kernels before 2.6.23) never
+supported the input layer, and sent events over the procfs ACPI event
+interface.
+
+To avoid sending duplicate events over the input layer and the ACPI
+event interface, thinkpad-acpi 0.16 implements a module parameter
+(hotkey_report_mode), and also a sysfs device attribute with the same
+name.
+
+Make no mistake here: userspace is expected to switch to using the input
+layer interface of thinkpad-acpi, together with the ACPI netlink event
+interface in kernels 2.6.23 and later, or with the ACPI procfs event
+interface in kernels 2.6.22 and earlier.
+
+If no hotkey_report_mode module parameter is specified (or it is set to
+zero), the driver defaults to mode 1 (see below), and on kernels 2.6.22
+and earlier, also allows one to change the hotkey_report_mode through
+sysfs. In kernels 2.6.23 and later, where the netlink ACPI event
+interface is available, hotkey_report_mode cannot be changed through
+sysfs (it is read-only).
+
+If the hotkey_report_mode module parameter is set to 1 or 2, it cannot
+be changed later through sysfs (any writes will return -EPERM to signal
+that hotkey_report_mode was locked. On 2.6.23 and later, where
+hotkey_report_mode cannot be changed at all, writes will return -EACES).
+
+hotkey_report_mode set to 1 makes the driver export through the procfs
+ACPI event interface all hot key presses (which are *also* sent to the
+input layer). This is a legacy compatibility behaviour, and it is also
+the default mode of operation for the driver.
+
+hotkey_report_mode set to 2 makes the driver filter out the hot key
+presses from the procfs ACPI event interface, so these events will only
+be sent through the input layer. Userspace that has been updated to use
+the thinkpad-acpi input layer interface should set hotkey_report_mode to
+2.
+
+Hot key press events are never sent to the ACPI netlink event interface.
+Really up-to-date userspace under kernel 2.6.23 and later is to use the
+netlink interface and the input layer interface, and don't bother at all
+with hotkey_report_mode.
+
Bluetooth
---------
diff --git a/Documentation/video4linux/cx2341x/fw-encoder-api.txt b/Documentation/video4linux/cx2341x/fw-encoder-api.txt
index 5dd3109..5a27af2 100644
--- a/Documentation/video4linux/cx2341x/fw-encoder-api.txt
+++ b/Documentation/video4linux/cx2341x/fw-encoder-api.txt
@@ -407,8 +407,10 @@ Description
u32 length; // Length of this frame
u32 offset_low; // Offset in the file of the
u32 offset_high; // start of this frame
- u32 mask1; // Bits 0-1 are the type mask:
+ u32 mask1; // Bits 0-2 are the type mask:
// 1=I, 2=P, 4=B
+ // 0=End of Program Index, other fields
+ // are invalid.
u32 pts; // The PTS of the frame
u32 mask2; // Bit 0 is bit 32 of the pts.
};
OpenPOWER on IntegriCloud