diff options
Diffstat (limited to 'Documentation')
23 files changed, 1942 insertions, 309 deletions
diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX index 8b0563633442..43e89b1537d9 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 90ed23df1f68..c917de681ccd 100644 --- a/Documentation/DocBook/deviceiobook.tmpl +++ b/Documentation/DocBook/deviceiobook.tmpl @@ -316,7 +316,8 @@ CPU B: spin_unlock_irqrestore(&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 f8cc3f8ed152..c64e969dc33b 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 cbbebfb51ffe..49a8efa5afeb 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 d6b45a9b29b4..a30dd4480ad4 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 000000000000..c1e9545c59bd --- /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 8de132a02ba9..6c46730c631a 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 a43d2878a4ef..00928d2ecfb2 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 571785887a4f..59db1bca7027 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 bbd8b28c13de..cda6905cbe49 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 8ccf0c1b58ed..ed55238023a9 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 fa0c786a8bf5..cf6b6cb02aa1 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 95df4ca70e71..8777d2d321e3 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 975f029be25c..4d175c751246 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 000000000000..b51d7ca842ba --- /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 f7918401a007..73c5f1f3d5d2 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 000000000000..4ba4664ce5c3 --- /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 d63f480afb74..153d84d281e6 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 00b60cce2224..ea5a42e8f79f 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 000000000000..8590a954df1d --- /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 ef19142896ca..10c8f6922ef4 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 eb2f5986e1eb..60953d6c919d 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 5dd3109a8b3f..5a27af2ee1c6 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. }; |