Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 c4366889 编写于 作者: D Dave Jones
浏览文件
操作

Merge ../linus 

Conflicts:

	drivers/cpufreq/cpufreq.c
上级 db2fb9db e1036502
展开全部 隐藏空白更改
内联 并排
Showing with 38050 addition and 14304 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.gitignore
浏览文件 @ c4366889
......@@ -20,6 +20,7 @@
# Top-level generic files
#
tags
TAGS
vmlinux*
System.map
Module.symvers
......
CREDITS
浏览文件 @ c4366889
......@@ -45,7 +45,7 @@ S: Longford, Ireland
S: Sydney, Australia
N: Tigran A. Aivazian
E: tigran@veritas.com
E: tigran@aivazian.fsnet.co.uk
W: http://www.moses.uklinux.net/patches
D: BFS filesystem
D: Intel IA32 CPU microcode update support
......@@ -1808,6 +1808,14 @@ S: Kruislaan 419
S: 1098 VA Amsterdam
S: The Netherlands
N: Jiri Kosina
E: jikos@jikos.cz
E: jkosina@suse.cz
D: Generic HID layer - original code split, fixes
D: Various ACPI fixes, keeping correct battery state through suspend
D: various lockdep annotations, autofs and other random bugfixes
S: Prague, Czech Republic
N: Gene Kozin
E: 74604.152@compuserve.com
W: http://www.sangoma.com
......@@ -2598,6 +2606,9 @@ S: Ucitelska 1576
S: Prague 8
S: 182 00 Czech Republic
N: Rick Payne
D: RFC2385 Support for TCP
N: Barak A. Pearlmutter
E: bap@cs.unm.edu
W: http://www.cs.unm.edu/~bap/
......@@ -3511,14 +3522,12 @@ D: The Linux Support Team Erlangen
N: David Weinehall
E: tao@acc.umu.se
P: 1024D/DC47CA16 7ACE 0FB0 7A74 F994 9B36 E1D1 D14E 8526 DC47 CA16
W: http://www.acc.umu.se/~tao/
W: http://www.acc.umu.se/~mcalinux/
D: v2.0 kernel maintainer
D: Fixes for the NE/2-driver
D: Miscellaneous MCA-support
D: Cleanup of the Config-files
S: Axtorpsvagen 40:20
S: S-903 37 UMEA
S: Sweden
N: Matt Welsh
E: mdw@metalab.unc.edu
......
Documentation/00-INDEX
浏览文件 @ c4366889
......@@ -104,8 +104,6 @@ firmware_class/
- request_firmware() hotplug interface info.
floppy.txt
- notes and driver options for the floppy disk driver.
ftape.txt
- notes about the floppy tape device driver.
hayes-esp.txt
- info on using the Hayes ESP serial driver.
highuid.txt
......
Documentation/ABI/testing/debugfs-pktcdvd 0 → 100644
浏览文件 @ c4366889
What: /debug/pktcdvd/pktcdvd[0-7]
Date: Oct. 2006
KernelVersion: 2.6.19
Contact: Thomas Maier <balagi@justmail.de>
Description:
debugfs interface
-----------------
The pktcdvd module (packet writing driver) creates
these files in debugfs:
/debug/pktcdvd/pktcdvd[0-7]/
info (0444) Lots of human readable driver
statistics and infos. Multiple lines!
Example:
-------
cat /debug/pktcdvd/pktcdvd0/info
Documentation/ABI/testing/sysfs-class-pktcdvd 0 → 100644
浏览文件 @ c4366889
What: /sys/class/pktcdvd/
Date: Oct. 2006
KernelVersion: 2.6.19
Contact: Thomas Maier <balagi@justmail.de>
Description:
sysfs interface
---------------
The pktcdvd module (packet writing driver) creates
these files in the sysfs:
(<devid> is in format major:minor )
/sys/class/pktcdvd/
add (0200) Write a block device id (major:minor)
to create a new pktcdvd device and map
it to the block device.
remove (0200) Write the pktcdvd device id (major:minor)
to it to remove the pktcdvd device.
device_map (0444) Shows the device mapping in format:
pktcdvd[0-7] <pktdevid> <blkdevid>
/sys/class/pktcdvd/pktcdvd[0-7]/
dev (0444) Device id
uevent (0200) To send an uevent.
/sys/class/pktcdvd/pktcdvd[0-7]/stat/
packets_started (0444) Number of started packets.
packets_finished (0444) Number of finished packets.
kb_written (0444) kBytes written.
kb_read (0444) kBytes read.
kb_read_gather (0444) kBytes read to fill write packets.
reset (0200) Write any value to it to reset
pktcdvd device statistic values, like
bytes read/written.
/sys/class/pktcdvd/pktcdvd[0-7]/write_queue/
size (0444) Contains the size of the bio write
queue.
congestion_off (0644) If bio write queue size is below
this mark, accept new bio requests
from the block layer.
congestion_on (0644) If bio write queue size is higher
as this mark, do no longer accept
bio write requests from the block
layer and wait till the pktcdvd
device has processed enough bio's
so that bio write queue size is
below congestion off mark.
A value of <= 0 disables congestion
control.
Example:
--------
To use the pktcdvd sysfs interface directly, you can do:
# create a new pktcdvd device mapped to /dev/hdc
echo "22:0" >/sys/class/pktcdvd/add
cat /sys/class/pktcdvd/device_map
# assuming device pktcdvd0 was created, look at stat's
cat /sys/class/pktcdvd/pktcdvd0/stat/kb_written
# print the device id of the mapped block device
fgrep pktcdvd0 /sys/class/pktcdvd/device_map
# remove device, using pktcdvd0 device id 253:0
echo "253:0" >/sys/class/pktcdvd/remove
Documentation/ABI/testing/sysfs-power
浏览文件 @ c4366889
......@@ -21,7 +21,7 @@ Description:
these states.
What: /sys/power/disk
Date: August 2006
Date: September 2006
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/power/disk file controls the operating mode of the
......@@ -39,6 +39,19 @@ Description:
'reboot' - the memory image will be saved by the kernel and
the system will be rebooted.
Additionally, /sys/power/disk can be used to turn on one of the
two testing modes of the suspend-to-disk mechanism: 'testproc'
or 'test'. If the suspend-to-disk mechanism is in the
'testproc' mode, writing 'disk' to /sys/power/state will cause
the kernel to disable nonboot CPUs and freeze tasks, wait for 5
seconds, unfreeze tasks and enable nonboot CPUs. If it is in
the 'test' mode, writing 'disk' to /sys/power/state will cause
the kernel to disable nonboot CPUs and freeze tasks, shrink
memory, suspend devices, wait for 5 seconds, resume devices,
unfreeze tasks and enable nonboot CPUs. Then, we are able to
look in the log messages and work out, for example, which code
is being slow and which device drivers are misbehaving.
The suspend-to-disk method may be chosen by writing to this
file one of the accepted strings:
......@@ -46,6 +59,8 @@ Description:
'platform'
'shutdown'
'reboot'
'testproc'
'test'
It will only change to 'firmware' or 'platform' if the system
supports that.
......
Documentation/Changes
浏览文件 @ c4366889
......@@ -201,7 +201,7 @@ udev
----
udev is a userspace application for populating /dev dynamically with
only entries for devices actually present. udev replaces the basic
functionality of devfs, while allowing persistant device naming for
functionality of devfs, while allowing persistent device naming for
devices.
FUSE
......
Documentation/CodingStyle
浏览文件 @ c4366889
......@@ -35,12 +35,37 @@ In short, 8-char indents make things easier to read, and have the added
benefit of warning you when you're nesting your functions too deep.
Heed that warning.
The preferred way to ease multiple indentation levels in a switch statement is
to align the "switch" and its subordinate "case" labels in the same column
instead of "double-indenting" the "case" labels. E.g.:
switch (suffix) {
case 'G':
case 'g':
mem <<= 30;
break;
case 'M':
case 'm':
mem <<= 20;
break;
case 'K':
case 'k':
mem <<= 10;
/* fall through */
default:
break;
}
Don't put multiple statements on a single line unless you have
something to hide:
if (condition) do_this;
do_something_everytime;
Don't put multiple assignments on a single line either. Kernel coding style
is super simple. Avoid tricky expressions.
Outside of comments, documentation and except in Kconfig, spaces are never
used for indentation, and the above example is deliberately broken.
......@@ -69,7 +94,7 @@ void fun(int a, int b, int c)
next_statement;
}
Chapter 3: Placing Braces
Chapter 3: Placing Braces and Spaces
The other issue that always comes up in C styling is the placement of
braces. Unlike the indent size, there are few technical reasons to
......@@ -81,6 +106,20 @@ brace last on the line, and put the closing brace first, thusly:
we do y
}
This applies to all non-function statement blocks (if, switch, for,
while, do). E.g.:
switch (action) {
case KOBJ_ADD:
return "add";
case KOBJ_REMOVE:
return "remove";
case KOBJ_CHANGE:
return "change";
default:
return NULL;
}
However, there is one special case, namely functions: they have the
opening brace at the beginning of the next line, thus:
......@@ -121,6 +160,49 @@ supply of new-lines on your screen is not a renewable resource (think
25-line terminal screens here), you have more empty lines to put
comments on.
3.1: Spaces
Linux kernel style for use of spaces depends (mostly) on
function-versus-keyword usage. Use a space after (most) keywords. The
notable exceptions are sizeof, typeof, alignof, and __attribute__, which look
somewhat like functions (and are usually used with parentheses in Linux,
although they are not required in the language, as in: "sizeof info" after
"struct fileinfo info;" is declared).
So use a space after these keywords:
if, switch, case, for, do, while
but not with sizeof, typeof, alignof, or __attribute__. E.g.,
s = sizeof(struct file);
Do not add spaces around (inside) parenthesized expressions. This example is
*bad*:
s = sizeof( struct file );
When declaring pointer data or a function that returns a pointer type, the
preferred use of '*' is adjacent to the data name or function name and not
adjacent to the type name. Examples:
char *linux_banner;
unsigned long long memparse(char *ptr, char **retptr);
char *match_strdup(substring_t *s);
Use one space around (on each side of) most binary and ternary operators,
such as any of these:
= + - < > * / % | & ^ <= >= == != ? :
but no space after unary operators:
& * + - ~ ! sizeof typeof alignof __attribute__ defined
no space before the postfix increment & decrement unary operators:
++ --
no space after the prefix increment & decrement unary operators:
++ --
and no space around the '.' and "->" structure member operators.
Chapter 4: Naming
......@@ -152,7 +234,7 @@ variable that is used to hold a temporary value.
If you are afraid to mix up your local variable names, you have another
problem, which is called the function-growth-hormone-imbalance syndrome.
See next chapter.
See chapter 6 (Functions).
Chapter 5: Typedefs
......@@ -258,6 +340,20 @@ generally easily keep track of about 7 different things, anything more
and it gets confused. You know you're brilliant, but maybe you'd like
to understand what you did 2 weeks from now.
In source files, separate functions with one blank line. If the function is
exported, the EXPORT* macro for it should follow immediately after the closing
function brace line. E.g.:
int system_is_up(void)
{
return system_state == SYSTEM_RUNNING;
}
EXPORT_SYMBOL(system_is_up);
In function prototypes, include parameter names with their data types.
Although this is not required by the C language, it is preferred in Linux
because it is a simple way to add valuable information for the reader.
Chapter 7: Centralized exiting of functions
......@@ -306,16 +402,36 @@ time to explain badly written code.
Generally, you want your comments to tell WHAT your code does, not HOW.
Also, try to avoid putting comments inside a function body: if the
function is so complex that you need to separately comment parts of it,
you should probably go back to chapter 5 for a while. You can make
you should probably go back to chapter 6 for a while. You can make
small comments to note or warn about something particularly clever (or
ugly), but try to avoid excess. Instead, put the comments at the head
of the function, telling people what it does, and possibly WHY it does
it.
When commenting the kernel API functions, please use the kerneldoc format.
When commenting the kernel API functions, please use the kernel-doc format.
See the files Documentation/kernel-doc-nano-HOWTO.txt and scripts/kernel-doc
for details.
Linux style for comments is the C89 "/* ... */" style.
Don't use C99-style "// ..." comments.
The preferred style for long (multi-line) comments is:
/*
* This is the preferred style for multi-line
* comments in the Linux kernel source code.
* Please use it consistently.
*
* Description: A column of asterisks on the left side,
* with beginning and ending almost-blank lines.
*/
It's also important to comment data, whether they are basic types or derived
types. To this end, use just one data declaration per line (no commas for
multiple data declarations). This leaves you room for a small comment on each
item, explaining its use.
Chapter 9: You've made a mess of it
That's OK, we all do. You've probably been told by your long-time Unix
......@@ -591,4 +707,4 @@ Kernel CodingStyle, by greg@kroah.com at OLS 2002:
http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/
--
Last updated on 30 April 2006.
Last updated on 2006-December-06.
Documentation/DMA-API.txt
浏览文件 @ c4366889
......@@ -77,7 +77,7 @@ To get this part of the dma_ API, you must #include <linux/dmapool.h>
Many drivers need lots of small dma-coherent memory regions for DMA
descriptors or I/O buffers. Rather than allocating in units of a page
or more using dma_alloc_coherent(), you can use DMA pools. These work
much like a kmem_cache_t, except that they use the dma-coherent allocator
much like a struct kmem_cache, except that they use the dma-coherent allocator
not __get_free_pages(). Also, they understand common hardware constraints
for alignment, like queue heads needing to be aligned on N byte boundaries.
......@@ -94,7 +94,7 @@ The pool create() routines initialize a pool of dma-coherent buffers
for use with a given device. It must be called in a context which
can sleep.
The "name" is for diagnostics (like a kmem_cache_t name); dev and size
The "name" is for diagnostics (like a struct kmem_cache name); dev and size
are like what you'd pass to dma_alloc_coherent(). The device's hardware
alignment requirement for this type of data is "align" (which is expressed
in bytes, and must be a power of two). If your device has no boundary
......@@ -431,10 +431,10 @@ be identical to those passed in (and returned by
dma_alloc_noncoherent()).
int
dma_is_consistent(dma_addr_t dma_handle)
dma_is_consistent(struct device *dev, dma_addr_t dma_handle)
returns true if the memory pointed to by the dma_handle is actually
consistent.
returns true if the device dev is performing consistent DMA on the memory
area pointed to by the dma_handle.
int
dma_get_cache_alignment(void)
......@@ -459,7 +459,7 @@ anything like this. You must also be extra careful about accessing
memory you intend to sync partially.
void
dma_cache_sync(void *vaddr, size_t size,
dma_cache_sync(struct device *dev, void *vaddr, size_t size,
enum dma_data_direction direction)
Do a partial sync of memory that was allocated by
......@@ -489,7 +489,7 @@ size is the size of the area (must be multiples of PAGE_SIZE).
flags can be or'd together and are
DMA_MEMORY_MAP - request that the memory returned from
dma_alloc_coherent() be directly writeable.
dma_alloc_coherent() be directly writable.
DMA_MEMORY_IO - request that the memory returned from
dma_alloc_coherent() be addressable using read/write/memcpy_toio etc.
......
Documentation/DMA-ISA-LPC.txt
浏览文件 @ c4366889
......@@ -110,7 +110,7 @@ lock.
Once the DMA transfer is finished (or timed out) you should disable
the channel again. You should also check get_dma_residue() to make
sure that all data has been transfered.
sure that all data has been transferred.
Example:
......
Documentation/DocBook/Makefile
浏览文件 @ c4366889
......@@ -9,7 +9,7 @@
DOCBOOKS := wanbook.xml z8530book.xml mcabook.xml videobook.xml \
kernel-hacking.xml kernel-locking.xml deviceiobook.xml \
procfs-guide.xml writing_usb_driver.xml \
kernel-api.xml journal-api.xml lsm.xml usb.xml \
kernel-api.xml filesystems.xml lsm.xml usb.xml \
gadget.xml libata.xml mtdnand.xml librs.xml rapidio.xml \
genericirq.xml
......@@ -190,9 +190,13 @@ quiet_cmd_fig2png = FIG2PNG $@
###
# Help targets as used by the top-level makefile
dochelp:
@echo ' Linux kernel internal documentation in different formats:'
@echo ' xmldocs (XML DocBook), psdocs (Postscript), pdfdocs (PDF)'
@echo ' htmldocs (HTML), mandocs (man pages, use installmandocs to install)'
@echo ' Linux kernel internal documentation in different formats:'
@echo ' htmldocs - HTML'
@echo ' installmandocs - install man pages generated by mandocs'
@echo ' mandocs - man pages'
@echo ' pdfdocs - PDF'
@echo ' psdocs - Postscript'
@echo ' xmldocs - XML DocBook'
###
# Temporary files left by various tools
......
Documentation/DocBook/journal-api.tmpl → Documentation/DocBook/filesystems.tmpl
浏览文件 @ c4366889
......@@ -2,39 +2,11 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
<book id="LinuxJBDAPI">
<book id="Linux-filesystems-API">
<bookinfo>
<title>The Linux Journalling API</title>
<authorgroup>
<author>
<firstname>Roger</firstname>
<surname>Gammans</surname>
<affiliation>
<address>
<email>rgammans@computer-surgery.co.uk</email>
</address>
</affiliation>
</author>
</authorgroup>
<authorgroup>
<author>
<firstname>Stephen</firstname>
<surname>Tweedie</surname>
<affiliation>
<address>
<email>sct@redhat.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<title>Linux Filesystems API</title>
<copyright>
<year>2002</year>
<holder>Roger Gammans</holder>
</copyright>
<legalnotice>
<legalnotice>
<para>
This documentation is free software; you can redistribute
it and/or modify it under the terms of the GNU General Public
......@@ -42,21 +14,21 @@
version 2 of the License, or (at your option) any later
version.
</para>
<para>
This program is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
</para>
<para>
You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free
Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
MA 02111-1307 USA
</para>
<para>
For more details see the file COPYING in the source
distribution of Linux.
......@@ -66,17 +38,113 @@
<toc></toc>
<chapter id="Overview">
<chapter id="vfs">
<title>The Linux VFS</title>
<sect1><title>The Filesystem types</title>
!Iinclude/linux/fs.h
</sect1>
<sect1><title>The Directory Cache</title>
!Efs/dcache.c
!Iinclude/linux/dcache.h
</sect1>
<sect1><title>Inode Handling</title>
!Efs/inode.c
!Efs/bad_inode.c
</sect1>
<sect1><title>Registration and Superblocks</title>
!Efs/super.c
</sect1>
<sect1><title>File Locks</title>
!Efs/locks.c
!Ifs/locks.c
</sect1>
<sect1><title>Other Functions</title>
!Efs/mpage.c
!Efs/namei.c
!Efs/buffer.c
!Efs/bio.c
!Efs/seq_file.c
!Efs/filesystems.c
!Efs/fs-writeback.c
!Efs/block_dev.c
</sect1>
</chapter>
<chapter id="proc">
<title>The proc filesystem</title>
<sect1><title>sysctl interface</title>
!Ekernel/sysctl.c
</sect1>
<sect1><title>proc filesystem interface</title>
!Ifs/proc/base.c
</sect1>
</chapter>
<chapter id="sysfs">
<title>The Filesystem for Exporting Kernel Objects</title>
!Efs/sysfs/file.c
!Efs/sysfs/symlink.c
!Efs/sysfs/bin.c
</chapter>
<chapter id="debugfs">
<title>The debugfs filesystem</title>
<sect1><title>debugfs interface</title>
!Efs/debugfs/inode.c
!Efs/debugfs/file.c
</sect1>
</chapter>
<chapter id="LinuxJDBAPI">
<chapterinfo>
<title>The Linux Journalling API</title>
<authorgroup>
<author>
<firstname>Roger</firstname>
<surname>Gammans</surname>
<affiliation>
<address>
<email>rgammans@computer-surgery.co.uk</email>
</address>
</affiliation>
</author>
</authorgroup>
<authorgroup>
<author>
<firstname>Stephen</firstname>
<surname>Tweedie</surname>
<affiliation>
<address>
<email>sct@redhat.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<copyright>
<year>2002</year>
<holder>Roger Gammans</holder>
</copyright>
</chapterinfo>
<title>The Linux Journalling API</title>
<sect1>
<title>Overview</title>
<sect1>
<sect2>
<title>Details</title>
<para>
The journalling layer is easy to use. You need to
The journalling layer is easy to use. You need to
first of all create a journal_t data structure. There are
two calls to do this dependent on how you decide to allocate the physical
media on which the journal resides. The journal_init_inode() call
media on which the journal resides. The journal_init_inode() call
is for journals stored in filesystem inodes, or the journal_init_dev()
call can be use for journal stored on a raw device (in a continuous range
call can be use for journal stored on a raw device (in a continuous range
of blocks). A journal_t is a typedef for a struct pointer, so when
you are finally finished make sure you call journal_destroy() on it
to free up any used kernel memory.
......@@ -91,27 +159,26 @@ need to call journal_create().
<para>
Most of the time however your journal file will already have been created, but
before you load it you must call journal_wipe() to empty the journal file.
Hang on, you say , what if the filesystem wasn't cleanly umount()'d . Well, it is the
Hang on, you say , what if the filesystem wasn't cleanly umount()'d . Well, it is the
job of the client file system to detect this and skip the call to journal_wipe().
</para>
<para>
In either case the next call should be to journal_load() which prepares the
journal file for use. Note that journal_wipe(..,0) calls journal_skip_recovery()
journal file for use. Note that journal_wipe(..,0) calls journal_skip_recovery()
for you if it detects any outstanding transactions in the journal and similarly
journal_load() will call journal_recover() if necessary.
I would advise reading fs/ext3/super.c for examples on this stage.
[RGG: Why is the journal_wipe() call necessary - doesn't this needlessly
complicate the API. Or isn't a good idea for the journal layer to hide
[RGG: Why is the journal_wipe() call necessary - doesn't this needlessly
complicate the API. Or isn't a good idea for the journal layer to hide
dirty mounts from the client fs]
</para>
<para>
Now you can go ahead and start modifying the underlying
Now you can go ahead and start modifying the underlying
filesystem. Almost.
</para>
<para>
You still need to actually journal your filesystem changes, this
......@@ -138,10 +205,10 @@ individual buffers (blocks). Before you start to modify a buffer you
need to call journal_get_{create,write,undo}_access() as appropriate,
this allows the journalling layer to copy the unmodified data if it
needs to. After all the buffer may be part of a previously uncommitted
transaction.
transaction.
At this point you are at last ready to modify a buffer, and once
you are have done so you need to call journal_dirty_{meta,}data().
Or if you've asked for access to a buffer you now know is now longer
Or if you've asked for access to a buffer you now know is now longer
required to be pushed back on the device you can call journal_forget()
in much the same way as you might have used bforget() in the past.
</para>
......@@ -156,7 +223,6 @@ Then at umount time , in your put_super() (2.4) or write_super() (2.5)
you can then call journal_destroy() to clean up your in-core journal object.
</para>
<para>
Unfortunately there a couple of ways the journal layer can cause a deadlock.
The first thing to note is that each task can only have
......@@ -164,19 +230,19 @@ a single outstanding transaction at any one time, remember nothing
commits until the outermost journal_stop(). This means
you must complete the transaction at the end of each file/inode/address
etc. operation you perform, so that the journalling system isn't re-entered
on another journal. Since transactions can't be nested/batched
on another journal. Since transactions can't be nested/batched
across differing journals, and another filesystem other than
yours (say ext3) may be modified in a later syscall.
</para>
<para>
The second case to bear in mind is that journal_start() can
block if there isn't enough space in the journal for your transaction
The second case to bear in mind is that journal_start() can
block if there isn't enough space in the journal for your transaction
(based on the passed nblocks param) - when it blocks it merely(!) needs to
wait for transactions to complete and be committed from other tasks,
so essentially we are waiting for journal_stop(). So to avoid
wait for transactions to complete and be committed from other tasks,
so essentially we are waiting for journal_stop(). So to avoid
deadlocks you must treat journal_start/stop() as if they
were semaphores and include them in your semaphore ordering rules to prevent
were semaphores and include them in your semaphore ordering rules to prevent
deadlocks. Note that journal_extend() has similar blocking behaviour to
journal_start() so you can deadlock here just as easily as on journal_start().
</para>
......@@ -184,7 +250,7 @@ journal_start() so you can deadlock here just as easily as on journal_start().
<para>
Try to reserve the right number of blocks the first time. ;-). This will
be the maximum number of blocks you are going to touch in this transaction.
I advise having a look at at least ext3_jbd.h to see the basis on which
I advise having a look at at least ext3_jbd.h to see the basis on which
ext3 uses to make these decisions.
</para>
......@@ -193,13 +259,13 @@ Another wriggle to watch out for is your on-disk block allocation strategy.
why? Because, if you undo a delete, you need to ensure you haven't reused any
of the freed blocks in a later transaction. One simple way of doing this
is make sure any blocks you allocate only have checkpointed transactions
listed against them. Ext3 does this in ext3_test_allocatable().
listed against them. Ext3 does this in ext3_test_allocatable().
</para>
<para>
Lock is also providing through journal_{un,}lock_updates(),
ext3 uses this when it wants a window with a clean and stable fs for a moment.
eg.
eg.
</para>
<programlisting>
......@@ -230,19 +296,19 @@ extend it like this:-
struct journal_callback for_jbd;
// Stuff for myfs allocated together.
myfs_inode* i_commited;
}
</programlisting>
<para>
this would be useful if you needed to know when data was committed to a
this would be useful if you needed to know when data was committed to a
particular inode.
</para>
</sect1>
</sect2>
<sect1>
<title>Summary</title>
<sect2>
<title>Summary</title>
<para>
Using the journal is a matter of wrapping the different context changes,
being each mount, each modification (transaction) and each changed buffer
......@@ -260,15 +326,15 @@ an example.
if (clean) journal_wipe();
journal_load();
foreach(transaction) { /*transactions must be
foreach(transaction) { /*transactions must be
completed before
a syscall returns to
a syscall returns to
userspace*/
handle_t * xct=journal_start(my_jnrl);
foreach(bh) {
journal_get_{create,write,undo}_access(xact,bh);
if ( myfs_modify(bh) ) { /* returns true
if ( myfs_modify(bh) ) { /* returns true
if makes changes */
journal_dirty_{meta,}data(xact,bh);
} else {
......@@ -279,55 +345,57 @@ an example.
}
journal_destroy(my_jrnl);
</programlisting>
</sect1>
</sect2>
</chapter>
</sect1>
<chapter id="adt">
<sect1>
<title>Data Types</title>
<para>
<para>
The journalling layer uses typedefs to 'hide' the concrete definitions
of the structures used. As a client of the JBD layer you can
just rely on the using the pointer as a magic cookie of some sort.
Obviously the hiding is not enforced as this is 'C'.
</para>
<sect1><title>Structures</title>
</para>
<sect2><title>Structures</title>
!Iinclude/linux/jbd.h
</sect1>
</chapter>
</sect2>
</sect1>
<chapter id="calls">
<sect1>
<title>Functions</title>
<para>
<para>
The functions here are split into two groups those that
affect a journal as a whole, and those which are used to
manage transactions
</para>
<sect1><title>Journal Level</title>
</para>
<sect2><title>Journal Level</title>
!Efs/jbd/journal.c
!Ifs/jbd/recovery.c
</sect1>
<sect1><title>Transasction Level</title>
!Efs/jbd/transaction.c
</sect1>
</chapter>
<chapter>
</sect2>
<sect2><title>Transasction Level</title>
!Efs/jbd/transaction.c
</sect2>
</sect1>
<sect1>
<title>See also</title>
<para>
<citation>
<citation>
<ulink url="ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/journal-design.ps.gz">
Journaling the Linux ext2fs Filesystem,LinuxExpo 98, Stephen Tweedie
Journaling the Linux ext2fs Filesystem, LinuxExpo 98, Stephen Tweedie
</ulink>
</citation>
</para>
<para>
</citation>
</para>
<para>
<citation>
<ulink url="http://olstrans.sourceforge.net/release/OLS2000-ext3/OLS2000-ext3.html">
Ext3 Journalling FileSystem , OLS 2000, Dr. Stephen Tweedie
Ext3 Journalling FileSystem, OLS 2000, Dr. Stephen Tweedie
</ulink>
</citation>
</para>
</chapter>
</para>
</sect1>
</chapter>
</book>
Documentation/DocBook/kernel-api.tmpl
浏览文件 @ c4366889
......@@ -182,66 +182,6 @@ X!Ilib/string.c
</sect1>
</chapter>
<chapter id="vfs">
<title>The Linux VFS</title>
<sect1><title>The Filesystem types</title>
!Iinclude/linux/fs.h
</sect1>
<sect1><title>The Directory Cache</title>
!Efs/dcache.c
!Iinclude/linux/dcache.h
</sect1>
<sect1><title>Inode Handling</title>
!Efs/inode.c
!Efs/bad_inode.c
</sect1>
<sect1><title>Registration and Superblocks</title>
!Efs/super.c
</sect1>
<sect1><title>File Locks</title>
!Efs/locks.c
!Ifs/locks.c
</sect1>
<sect1><title>Other Functions</title>
!Efs/mpage.c
!Efs/namei.c
!Efs/buffer.c
!Efs/bio.c
!Efs/seq_file.c
!Efs/filesystems.c
!Efs/fs-writeback.c
!Efs/block_dev.c
</sect1>
</chapter>
<chapter id="proc">
<title>The proc filesystem</title>
<sect1><title>sysctl interface</title>
!Ekernel/sysctl.c
</sect1>
<sect1><title>proc filesystem interface</title>
!Ifs/proc/base.c
</sect1>
</chapter>
<chapter id="sysfs">
<title>The Filesystem for Exporting Kernel Objects</title>
!Efs/sysfs/file.c
!Efs/sysfs/symlink.c
!Efs/sysfs/bin.c
</chapter>
<chapter id="debugfs">
<title>The debugfs filesystem</title>
<sect1><title>debugfs interface</title>
!Efs/debugfs/inode.c
!Efs/debugfs/file.c
</sect1>
</chapter>
<chapter id="relayfs">
<title>relay interface support</title>
......@@ -478,9 +418,35 @@ X!Edrivers/pnp/system.c
!Idrivers/parport/daisy.c
</chapter>
<chapter id="viddev">
<title>Video4Linux</title>
!Edrivers/media/video/videodev.c
<chapter id="message_devices">
<title>Message-based devices</title>
<sect1><title>Fusion message devices</title>
!Edrivers/message/fusion/mptbase.c
!Idrivers/message/fusion/mptbase.c
!Edrivers/message/fusion/mptscsih.c
!Idrivers/message/fusion/mptscsih.c
!Idrivers/message/fusion/mptctl.c
!Idrivers/message/fusion/mptspi.c
!Idrivers/message/fusion/mptfc.c
!Idrivers/message/fusion/mptlan.c
</sect1>
<sect1><title>I2O message devices</title>
!Iinclude/linux/i2o.h
!Idrivers/message/i2o/core.h
!Edrivers/message/i2o/iop.c
!Idrivers/message/i2o/iop.c
!Idrivers/message/i2o/config-osm.c
!Edrivers/message/i2o/exec-osm.c
!Idrivers/message/i2o/exec-osm.c
!Idrivers/message/i2o/bus-osm.c
!Edrivers/message/i2o/device.c
!Idrivers/message/i2o/device.c
!Idrivers/message/i2o/driver.c
!Idrivers/message/i2o/pci.c
!Idrivers/message/i2o/i2o_block.c
!Idrivers/message/i2o/i2o_scsi.c
!Idrivers/message/i2o/i2o_proc.c
</sect1>
</chapter>
<chapter id="snddev">
......@@ -593,4 +559,12 @@ X!Idrivers/video/console/fonts.c
-->
</sect1>
</chapter>
<chapter id="input_subsystem">
<title>Input Subsystem</title>
!Iinclude/linux/input.h
!Edrivers/input/input.c
!Edrivers/input/ff-core.c
!Edrivers/input/ff-memless.c
</chapter>
</book>
Documentation/DocBook/writing_usb_driver.tmpl
浏览文件 @ c4366889
......@@ -345,8 +345,7 @@ static inline void skel_delete (struct usb_skel *dev)
usb_buffer_free (dev->udev, dev->bulk_out_size,
dev->bulk_out_buffer,
dev->write_urb->transfer_dma);
if (dev->write_urb != NULL)
usb_free_urb (dev->write_urb);
usb_free_urb (dev->write_urb);
kfree (dev);
}
</programlisting>
......
Documentation/HOWTO
浏览文件 @ c4366889
......@@ -395,6 +395,26 @@ bugme-janitor mailing list (every change in the bugzilla is mailed here)
Managing bug reports
--------------------
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 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.
If you want to be advised of the future bug reports, you can subscribe to the
bugme-new mailing list (only new bug reports are mailed here) or to the
bugme-janitor mailing list (every change in the bugzilla is mailed here)
http://lists.osdl.org/mailman/listinfo/bugme-new
http://lists.osdl.org/mailman/listinfo/bugme-janitors
Mailing lists
-------------
......
Documentation/IPMI.txt
浏览文件 @ c4366889
......@@ -365,6 +365,7 @@ You can change this at module load time (for a module) with:
regshifts=<shift1>,<shift2>,...
slave_addrs=<addr1>,<addr2>,...
force_kipmid=<enable1>,<enable2>,...
unload_when_empty=[0|1]
Each of these except si_trydefaults is a list, the first item for the
first interface, second item for the second interface, etc.
......@@ -416,6 +417,11 @@ by the driver, but systems with broken interrupts might need an enable,
or users that don't want the daemon (don't need the performance, don't
want the CPU hit) can disable it.
If unload_when_empty is set to 1, the driver will be unloaded if it
doesn't find any interfaces or all the interfaces fail to work. The
default is one. Setting to 0 is useful with the hotmod, but is
obviously only useful for modules.
When compiled into the kernel, the parameters can be specified on the
kernel command line as:
......@@ -441,6 +447,25 @@ have high-res timers enabled in the kernel and you don't have
interrupts enabled, the driver will run VERY slowly. Don't blame me,
these interfaces suck.
The driver supports a hot add and remove of interfaces. This way,
interfaces can be added or removed after the kernel is up and running.
This is done using /sys/modules/ipmi_si/hotmod, which is a write-only
parameter. You write a string to this interface. The string has the
format:
<op1>[:op2[:op3...]]
The "op"s are:
add|remove,kcs|bt|smic,mem|i/o,<address>[,<opt1>[,<opt2>[,...]]]
You can specify more than one interface on the line. The "opt"s are:
rsp=<regspacing>
rsi=<regsize>
rsh=<regshift>
irq=<irq>
ipmb=<ipmb slave addr>
and these have the same meanings as discussed above. Note that you
can also use this on the kernel command line for a more compact format
for specifying an interface. Note that when removing an interface,
only the first three parameters (si type, address type, and address)
are used for the comparison. Any options are ignored for removing.
The SMBus Driver
----------------
......@@ -502,7 +527,10 @@ used to control it:
modprobe ipmi_watchdog timeout=<t> pretimeout=<t> action=<action type>
preaction=<preaction type> preop=<preop type> start_now=x
nowayout=x
nowayout=x ifnum_to_use=n
ifnum_to_use specifies which interface the watchdog timer should use.
The default is -1, which means to pick the first one registered.
The timeout is the number of seconds to the action, and the pretimeout
is the amount of seconds before the reset that the pre-timeout panic will
......@@ -624,5 +652,9 @@ command line. The parameter is also available via the proc filesystem
in /proc/sys/dev/ipmi/poweroff_powercycle. Note that if the system
does not support power cycling, it will always do the power off.
The "ifnum_to_use" parameter specifies which interface the poweroff
code should use. The default is -1, which means to pick the first one
registered.
Note that if you have ACPI enabled, the system will prefer using ACPI to
power off.
Documentation/MSI-HOWTO.txt
浏览文件 @ c4366889
......@@ -219,7 +219,7 @@ into the field vector of each element contained in a second argument.
Note that the pre-assigned IOAPIC dev->irq is valid only if the device
operates in PIN-IRQ assertion mode. In MSI-X mode, any attempt at
using dev->irq by the device driver to request for interrupt service
may result unpredictabe behavior.
may result in unpredictable behavior.
For each MSI-X vector granted, a device driver is responsible for calling
other functions like request_irq(), enable_irq(), etc. to enable
......@@ -470,7 +470,68 @@ LOC: 324553 325068
ERR: 0
MIS: 0
6. FAQ
6. MSI quirks
Several PCI chipsets or devices are known to not support MSI.
The PCI stack provides 3 possible levels of MSI disabling:
* on a single device
* on all devices behind a specific bridge
* globally
6.1. Disabling MSI on a single device
Under some circumstances, it might be required to disable MSI on a
single device, It may be achived by either not calling pci_enable_msi()
or all, or setting the pci_dev->no_msi flag before (most of the time
in a quirk).
6.2. Disabling MSI below a bridge
The vast majority of MSI quirks are required by PCI bridges not
being able to route MSI between busses. In this case, MSI have to be
disabled on all devices behind this bridge. It is achieves by setting
the PCI_BUS_FLAGS_NO_MSI flag in the pci_bus->bus_flags of the bridge
subordinate bus. There is no need to set the same flag on bridges that
are below the broken brigde. When pci_enable_msi() is called to enable
MSI on a device, pci_msi_supported() takes care of checking the NO_MSI
flag in all parent busses of the device.
Some bridges actually support dynamic MSI support enabling/disabling
by changing some bits in their PCI configuration space (especially
the Hypertransport chipsets such as the nVidia nForce and Serverworks
HT2000). It may then be required to update the NO_MSI flag on the
corresponding devices in the sysfs hierarchy. To enable MSI support
on device "0000:00:0e", do:
echo 1 > /sys/bus/pci/devices/0000:00:0e/msi_bus
To disable MSI support, echo 0 instead of 1. Note that it should be
used with caution since changing this value might break interrupts.
6.3. Disabling MSI globally
Some extreme cases may require to disable MSI globally on the system.
For now, the only known case is a Serverworks PCI-X chipsets (MSI are
not supported on several busses that are not all connected to the
chipset in the Linux PCI hierarchy). In the vast majority of other
cases, disabling only behind a specific bridge is enough.
For debugging purpose, the user may also pass pci=nomsi on the kernel
command-line to explicitly disable MSI globally. But, once the appro-
priate quirks are added to the kernel, this option should not be
required anymore.
6.4. Finding why MSI cannot be enabled on a device
Assuming that MSI are not enabled on a device, you should look at
dmesg to find messages that quirks may output when disabling MSI
on some devices, some bridges or even globally.
Then, lspci -t gives the list of bridges above a device. Reading
/sys/bus/pci/devices/0000:00:0e/msi_bus will tell you whether MSI
are enabled (1) or disabled (0). In 0 is found in a single bridge
msi_bus file above the device, MSI cannot be enabled.
7. FAQ
Q1. Are there any limitations on using the MSI?
......
Documentation/SubmitChecklist
浏览文件 @ c4366889
......@@ -66,3 +66,9 @@ kernel patches.
See Documentation/ABI/README for more information.
20: Check that it all passes `make headers_check'.
21: Has been checked with injection of at least slab and page-allocation
fauilures. See Documentation/fault-injection/.
If the new code is substantial, addition of subsystem-specific fault
injection might be appropriate.
Documentation/accounting/getdelays.c
浏览文件 @ c4366889
......@@ -7,6 +7,8 @@
* Copyright (C) Balbir Singh, IBM Corp. 2006
* Copyright (c) Jay Lan, SGI. 2006
*
* Compile with
* gcc -I/usr/src/linux/include getdelays.c -o getdelays
*/
#include <stdio.h>
......@@ -35,13 +37,20 @@
#define NLA_DATA(na) ((void *)((char*)(na) + NLA_HDRLEN))
#define NLA_PAYLOAD(len) (len - NLA_HDRLEN)
#define err(code, fmt, arg...) do { printf(fmt, ##arg); exit(code); } while (0)
int done = 0;
int rcvbufsz=0;
char name[100];
int dbg=0, print_delays=0;
#define err(code, fmt, arg...) \
do { \
fprintf(stderr, fmt, ##arg); \
exit(code); \
} while (0)
int done;
int rcvbufsz;
char name[100];
int dbg;
int print_delays;
int print_io_accounting;
__u64 stime, utime;
#define PRINTF(fmt, arg...) { \
if (dbg) { \
printf(fmt, ##arg); \
......@@ -49,7 +58,7 @@ __u64 stime, utime;
}
/* Maximum size of response requested or message sent */
#define MAX_MSG_SIZE 256
#define MAX_MSG_SIZE 1024
/* Maximum number of cpus expected to be specified in a cpumask */
#define MAX_CPUS 32
/* Maximum length of pathname to log file */
......@@ -78,8 +87,9 @@ static int create_nl_socket(int protocol)
if (rcvbufsz)
if (setsockopt(fd, SOL_SOCKET, SO_RCVBUF,
&rcvbufsz, sizeof(rcvbufsz)) < 0) {
printf("Unable to set socket rcv buf size to %d\n",
rcvbufsz);
fprintf(stderr, "Unable to set socket rcv buf size "
"to %d\n",
rcvbufsz);
return -1;
}
......@@ -186,6 +196,15 @@ void print_delayacct(struct taskstats *t)
"count", "delay total", t->swapin_count, t->swapin_delay_total);
}
void print_ioacct(struct taskstats *t)
{
printf("%s: read=%llu, write=%llu, cancelled_write=%llu\n",
t->ac_comm,
(unsigned long long)t->read_bytes,
(unsigned long long)t->write_bytes,
(unsigned long long)t->cancelled_write_bytes);
}
int main(int argc, char *argv[])
{
int c, rc, rep_len, aggr_len, len2, cmd_type;
......@@ -208,7 +227,7 @@ int main(int argc, char *argv[])
struct msgtemplate msg;
while (1) {
c = getopt(argc, argv, "dw:r:m:t:p:v:l");
c = getopt(argc, argv, "diw:r:m:t:p:v:l");
if (c < 0)
break;
......@@ -217,6 +236,10 @@ int main(int argc, char *argv[])
printf("print delayacct stats ON\n");
print_delays = 1;
break;
case 'i':
printf("printing IO accounting\n");
print_io_accounting = 1;
break;
case 'w':
strncpy(logfile, optarg, MAX_FILENAME);
printf("write to file %s\n", logfile);
......@@ -238,14 +261,12 @@ int main(int argc, char *argv[])
if (!tid)
err(1, "Invalid tgid\n");
cmd_type = TASKSTATS_CMD_ATTR_TGID;
print_delays = 1;
break;
case 'p':
tid = atoi(optarg);
if (!tid)
err(1, "Invalid pid\n");
cmd_type = TASKSTATS_CMD_ATTR_PID;
print_delays = 1;
break;
case 'v':
printf("debug on\n");
......@@ -277,7 +298,7 @@ int main(int argc, char *argv[])
mypid = getpid();
id = get_family_id(nl_sd);
if (!id) {
printf("Error getting family id, errno %d", errno);
fprintf(stderr, "Error getting family id, errno %d\n", errno);
goto err;
}
PRINTF("family id %d\n", id);
......@@ -288,7 +309,7 @@ int main(int argc, char *argv[])
&cpumask, strlen(cpumask) + 1);
PRINTF("Sent register cpumask, retval %d\n", rc);
if (rc < 0) {
printf("error sending register cpumask\n");
fprintf(stderr, "error sending register cpumask\n");
goto err;
}
}
......@@ -298,7 +319,7 @@ int main(int argc, char *argv[])
cmd_type, &tid, sizeof(__u32));
PRINTF("Sent pid/tgid, retval %d\n", rc);
if (rc < 0) {
printf("error sending tid/tgid cmd\n");
fprintf(stderr, "error sending tid/tgid cmd\n");
goto done;
}
}
......@@ -310,13 +331,15 @@ int main(int argc, char *argv[])
PRINTF("received %d bytes\n", rep_len);
if (rep_len < 0) {
printf("nonfatal reply error: errno %d\n", errno);
fprintf(stderr, "nonfatal reply error: errno %d\n",
errno);
continue;
}
if (msg.n.nlmsg_type == NLMSG_ERROR ||
!NLMSG_OK((&msg.n), rep_len)) {
struct nlmsgerr *err = NLMSG_DATA(&msg);
printf("fatal reply error, errno %d\n", err->error);
fprintf(stderr, "fatal reply error, errno %d\n",
err->error);
goto done;
}
......@@ -356,6 +379,8 @@ int main(int argc, char *argv[])
count++;
if (print_delays)
print_delayacct((struct taskstats *) NLA_DATA(na));
if (print_io_accounting)
print_ioacct((struct taskstats *) NLA_DATA(na));
if (fd) {
if (write(fd, NLA_DATA(na), na->nla_len) < 0) {
err(1,"write error\n");
......@@ -365,7 +390,9 @@ int main(int argc, char *argv[])
goto done;
break;
default:
printf("Unknown nested nla_type %d\n", na->nla_type);
fprintf(stderr, "Unknown nested"
" nla_type %d\n",
na->nla_type);
break;
}
len2 += NLA_ALIGN(na->nla_len);
......@@ -374,7 +401,8 @@ int main(int argc, char *argv[])
break;
default:
printf("Unknown nla_type %d\n", na->nla_type);
fprintf(stderr, "Unknown nla_type %d\n",
na->nla_type);
break;
}
na = (struct nlattr *) (GENLMSG_DATA(&msg) + len);
......
Documentation/accounting/taskstats.txt
浏览文件 @ c4366889
......@@ -96,9 +96,9 @@ a) TASKSTATS_TYPE_AGGR_PID/TGID : attribute containing no payload but indicates
a pid/tgid will be followed by some stats.
b) TASKSTATS_TYPE_PID/TGID: attribute whose payload is the pid/tgid whose stats
is being returned.
are being returned.
c) TASKSTATS_TYPE_STATS: attribute with a struct taskstsats as payload. The
c) TASKSTATS_TYPE_STATS: attribute with a struct taskstats as payload. The
same structure is used for both per-pid and per-tgid stats.
3. New message sent by kernel whenever a task exits. The payload consists of a
......@@ -122,12 +122,12 @@ of atomicity).
However, maintaining per-process, in addition to per-task stats, within the
kernel has space and time overheads. To address this, the taskstats code
accumalates each exiting task's statistics into a process-wide data structure.
When the last task of a process exits, the process level data accumalated also
accumulates each exiting task's statistics into a process-wide data structure.
When the last task of a process exits, the process level data accumulated also
gets sent to userspace (along with the per-task data).
When a user queries to get per-tgid data, the sum of all other live threads in
the group is added up and added to the accumalated total for previously exited
the group is added up and added to the accumulated total for previously exited
threads of the same thread group.
Extending taskstats
......
Documentation/block/as-iosched.txt
浏览文件 @ c4366889
......@@ -24,8 +24,10 @@ very similar behavior to the deadline IO scheduler.
Selecting IO schedulers
-----------------------
To choose IO schedulers at boot time, use the argument 'elevator=deadline'.
'noop' and 'as' (the default) are also available. IO schedulers are assigned
globally at boot time only presently.
'noop', 'as' and 'cfq' (the default) are also available. IO schedulers are
assigned globally at boot time only presently. It's also possible to change
the IO scheduler for a determined device on the fly, as described in
Documentation/block/switching-sched.txt.
Anticipatory IO scheduler Policies
......
Documentation/block/biodoc.txt
浏览文件 @ c4366889
......@@ -183,7 +183,7 @@ it, the pci dma mapping routines and associated data structures have now been
modified to accomplish a direct page -> bus translation, without requiring
a virtual address mapping (unlike the earlier scheme of virtual address
-> bus translation). So this works uniformly for high-memory pages (which
do not have a correponding kernel virtual address space mapping) and
do not have a corresponding kernel virtual address space mapping) and
low-memory pages.
Note: Please refer to DMA-mapping.txt for a discussion on PCI high mem DMA
......@@ -391,7 +391,7 @@ forced such requests to be broken up into small chunks before being passed
on to the generic block layer, only to be merged by the i/o scheduler
when the underlying device was capable of handling the i/o in one shot.
Also, using the buffer head as an i/o structure for i/os that didn't originate
from the buffer cache unecessarily added to the weight of the descriptors
from the buffer cache unnecessarily added to the weight of the descriptors
which were generated for each such chunk.
The following were some of the goals and expectations considered in the
......@@ -403,14 +403,14 @@ i. Should be appropriate as a descriptor for both raw and buffered i/o -
for raw i/o.
ii. Ability to represent high-memory buffers (which do not have a virtual
address mapping in kernel address space).
iii.Ability to represent large i/os w/o unecessarily breaking them up (i.e
iii.Ability to represent large i/os w/o unnecessarily breaking them up (i.e
greater than PAGE_SIZE chunks in one shot)
iv. At the same time, ability to retain independent identity of i/os from
different sources or i/o units requiring individual completion (e.g. for
latency reasons)
v. Ability to represent an i/o involving multiple physical memory segments
(including non-page aligned page fragments, as specified via readv/writev)
without unecessarily breaking it up, if the underlying device is capable of
without unnecessarily breaking it up, if the underlying device is capable of
handling it.
vi. Preferably should be based on a memory descriptor structure that can be
passed around different types of subsystems or layers, maybe even
......@@ -1013,7 +1013,7 @@ Characteristics:
i. Binary tree
AS and deadline i/o schedulers use red black binary trees for disk position
sorting and searching, and a fifo linked list for time-based searching. This
gives good scalability and good availablility of information. Requests are
gives good scalability and good availability of information. Requests are
almost always dispatched in disk sort order, so a cache is kept of the next
request in sort order to prevent binary tree lookups.
......
Documentation/cdrom/packet-writing.txt
浏览文件 @ c4366889
......@@ -90,6 +90,41 @@ Notes
to create an ext2 filesystem on the disc.
Using the pktcdvd sysfs interface
---------------------------------
Since Linux 2.6.19, the pktcdvd module has a sysfs interface
and can be controlled by it. For example the "pktcdvd" tool uses
this interface. (see http://people.freenet.de/BalaGi#pktcdvd )
"pktcdvd" works similar to "pktsetup", e.g.:
# pktcdvd -a dev_name /dev/hdc
# mkudffs /dev/pktcdvd/dev_name
# mount -t udf -o rw,noatime /dev/pktcdvd/dev_name /dvdram
# cp files /dvdram
# umount /dvdram
# pktcdvd -r dev_name
For a description of the sysfs interface look into the file:
Documentation/ABI/testing/sysfs-block-pktcdvd
Using the pktcdvd debugfs interface
-----------------------------------
To read pktcdvd device infos in human readable form, do:
# cat /debug/pktcdvd/pktcdvd[0-7]/info
For a description of the debugfs interface look into the file:
Documentation/ABI/testing/debugfs-pktcdvd
Links
-----
......
Documentation/cpu-freq/cpufreq-nforce2.txt
浏览文件 @ c4366889
The cpufreq-nforce2 driver changes the FSB on nVidia nForce2 plattforms.
The cpufreq-nforce2 driver changes the FSB on nVidia nForce2 platforms.
This works better than on other plattforms, because the FSB of the CPU
This works better than on other platforms, because the FSB of the CPU
can be controlled independently from the PCI/AGP clock.
The module has two options:
......
Documentation/cpu-hotplug.txt
浏览文件 @ c4366889
......@@ -46,7 +46,7 @@ maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using
maxcpus=2 will only boot 2. You can choose to bring the
other cpus later online, read FAQ's for more info.
additional_cpus*=n Use this to limit hotpluggable cpus. This option sets
additional_cpus=n (*) Use this to limit hotpluggable cpus. This option sets
cpu_possible_map = cpu_present_map + additional_cpus
(*) Option valid only for following architectures
......@@ -54,8 +54,8 @@ additional_cpus*=n Use this to limit hotpluggable cpus. This option sets
ia64 and x86_64 use the number of disabled local apics in ACPI tables MADT
to determine the number of potentially hot-pluggable cpus. The implementation
should only rely on this to count the #of cpus, but *MUST* not rely on the
apicid values in those tables for disabled apics. In the event BIOS doesnt
should only rely on this to count the # of cpus, but *MUST* not rely on the
apicid values in those tables for disabled apics. In the event BIOS doesn't
mark such hot-pluggable cpus as disabled entries, one could use this
parameter "additional_cpus=x" to represent those cpus in the cpu_possible_map.
......@@ -101,15 +101,15 @@ cpu_possible_map/for_each_possible_cpu() to iterate.
Never use anything other than cpumask_t to represent bitmap of CPUs.
#include <linux/cpumask.h>
#include <linux/cpumask.h>
for_each_possible_cpu - Iterate over cpu_possible_map
for_each_online_cpu - Iterate over cpu_online_map
for_each_present_cpu - Iterate over cpu_present_map
for_each_cpu_mask(x,mask) - Iterate over some random collection of cpu mask.
for_each_possible_cpu - Iterate over cpu_possible_map
for_each_online_cpu - Iterate over cpu_online_map
for_each_present_cpu - Iterate over cpu_present_map
for_each_cpu_mask(x,mask) - Iterate over some random collection of cpu mask.
#include <linux/cpu.h>
lock_cpu_hotplug() and unlock_cpu_hotplug():
#include <linux/cpu.h>
lock_cpu_hotplug() and unlock_cpu_hotplug():
The above calls are used to inhibit cpu hotplug operations. While holding the
cpucontrol mutex, cpu_online_map will not change. If you merely need to avoid
......@@ -120,7 +120,7 @@ will work as long as stop_machine_run() is used to take a cpu down.
CPU Hotplug - Frequently Asked Questions.
Q: How to i enable my kernel to support CPU hotplug?
Q: How to enable my kernel to support CPU hotplug?
A: When doing make defconfig, Enable CPU hotplug support
"Processor type and Features" -> Support for Hotpluggable CPUs
......@@ -141,39 +141,39 @@ A: You should now notice an entry in sysfs.
Check if sysfs is mounted, using the "mount" command. You should notice
an entry as shown below in the output.
....
none on /sys type sysfs (rw)
....
....
none on /sys type sysfs (rw)
....
if this is not mounted, do the following.
If this is not mounted, do the following.
#mkdir /sysfs
#mount -t sysfs sys /sys
#mkdir /sysfs
#mount -t sysfs sys /sys
now you should see entries for all present cpu, the following is an example
Now you should see entries for all present cpu, the following is an example
in a 8-way system.
#pwd
#/sys/devices/system/cpu
#ls -l
total 0
drwxr-xr-x 10 root root 0 Sep 19 07:44 .
drwxr-xr-x 13 root root 0 Sep 19 07:45 ..
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu0
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu1
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu2
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu3
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu4
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu5
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu6
drwxr-xr-x 3 root root 0 Sep 19 07:48 cpu7
#pwd
#/sys/devices/system/cpu
#ls -l
total 0
drwxr-xr-x 10 root root 0 Sep 19 07:44 .
drwxr-xr-x 13 root root 0 Sep 19 07:45 ..
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu0
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu1
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu2
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu3
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu4
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu5
drwxr-xr-x 3 root root 0 Sep 19 07:44 cpu6
drwxr-xr-x 3 root root 0 Sep 19 07:48 cpu7
Under each directory you would find an "online" file which is the control
file to logically online/offline a processor.
Q: Does hot-add/hot-remove refer to physical add/remove of cpus?
A: The usage of hot-add/remove may not be very consistently used in the code.
CONFIG_CPU_HOTPLUG enables logical online/offline capability in the kernel.
CONFIG_HOTPLUG_CPU enables logical online/offline capability in the kernel.
To support physical addition/removal, one would need some BIOS hooks and
the platform should have something like an attention button in PCI hotplug.
CONFIG_ACPI_HOTPLUG_CPU enables ACPI support for physical add/remove of CPUs.
......@@ -181,17 +181,17 @@ CONFIG_ACPI_HOTPLUG_CPU enables ACPI support for physical add/remove of CPUs.
Q: How do i logically offline a CPU?
A: Do the following.
#echo 0 > /sys/devices/system/cpu/cpuX/online
#echo 0 > /sys/devices/system/cpu/cpuX/online
once the logical offline is successful, check
Once the logical offline is successful, check
#cat /proc/interrupts
#cat /proc/interrupts
you should now not see the CPU that you removed. Also online file will report
You should now not see the CPU that you removed. Also online file will report
the state as 0 when a cpu if offline and 1 when its online.
#To display the current cpu state.
#cat /sys/devices/system/cpu/cpuX/online
#To display the current cpu state.
#cat /sys/devices/system/cpu/cpuX/online
Q: Why cant i remove CPU0 on some systems?
A: Some architectures may have some special dependency on a certain CPU.
......@@ -234,8 +234,8 @@ Q: If i have some kernel code that needs to be aware of CPU arrival and
departure, how to i arrange for proper notification?
A: This is what you would need in your kernel code to receive notifications.
#include <linux/cpu.h>
static int __cpuinit foobar_cpu_callback(struct notifier_block *nfb,
#include <linux/cpu.h>
static int __cpuinit foobar_cpu_callback(struct notifier_block *nfb,
unsigned long action, void *hcpu)
{
unsigned int cpu = (unsigned long)hcpu;
......@@ -279,10 +279,10 @@ Q: I don't see my action being called for all CPUs already up and running?
A: Yes, CPU notifiers are called only when new CPUs are on-lined or offlined.
If you need to perform some action for each cpu already in the system, then
for_each_online_cpu(i) {
for_each_online_cpu(i) {
foobar_cpu_callback(&foobar_cpu_notifier, CPU_UP_PREPARE, i);
foobar_cpu_callback(&foobar-cpu_notifier, CPU_ONLINE, i);
}
foobar_cpu_callback(&foobar_cpu_notifier, CPU_ONLINE, i);
}
Q: If i would like to develop cpu hotplug support for a new architecture,
what do i need at a minimum?
......@@ -307,38 +307,38 @@ Q: I need to ensure that a particular cpu is not removed when there is some
work specific to this cpu is in progress.
A: First switch the current thread context to preferred cpu
int my_func_on_cpu(int cpu)
{
cpumask_t saved_mask, new_mask = CPU_MASK_NONE;
int curr_cpu, err = 0;
saved_mask = current->cpus_allowed;
cpu_set(cpu, new_mask);
err = set_cpus_allowed(current, new_mask);
if (err)
return err;
/*
* If we got scheduled out just after the return from
* set_cpus_allowed() before running the work, this ensures
* we stay locked.
*/
curr_cpu = get_cpu();
if (curr_cpu != cpu) {
err = -EAGAIN;
goto ret;
} else {
/*
* Do work : But cant sleep, since get_cpu() disables preempt
*/
}
ret:
put_cpu();
set_cpus_allowed(current, saved_mask);
return err;
}
int my_func_on_cpu(int cpu)
{
cpumask_t saved_mask, new_mask = CPU_MASK_NONE;
int curr_cpu, err = 0;
saved_mask = current->cpus_allowed;
cpu_set(cpu, new_mask);
err = set_cpus_allowed(current, new_mask);
if (err)
return err;
/*
* If we got scheduled out just after the return from
* set_cpus_allowed() before running the work, this ensures
* we stay locked.
*/
curr_cpu = get_cpu();
if (curr_cpu != cpu) {
err = -EAGAIN;
goto ret;
} else {
/*
* Do work : But cant sleep, since get_cpu() disables preempt
*/
}
ret:
put_cpu();
set_cpus_allowed(current, saved_mask);
return err;
}
Q: How do we determine how many CPUs are available for hotplug.
......
Documentation/devices.txt
浏览文件 @ c4366889
......@@ -3,7 +3,7 @@
Maintained by Torben Mathiasen <device@lanana.org>
Last revised: 15 May 2006
Last revised: 29 November 2006
This list is the Linux Device List, the official registry of allocated
device numbers and /dev directory nodes for the Linux operating
......@@ -92,8 +92,9 @@ Your cooperation is appreciated.
7 = /dev/full Returns ENOSPC on write
8 = /dev/random Nondeterministic random number gen.
9 = /dev/urandom Faster, less secure random number gen.
10 = /dev/aio Asyncronous I/O notification interface
10 = /dev/aio Asynchronous I/O notification interface
11 = /dev/kmsg Writes to this come out as printk's
1 block RAM disk
0 = /dev/ram0 First RAM disk
1 = /dev/ram1 Second RAM disk
......@@ -122,7 +123,7 @@ Your cooperation is appreciated.
devices are on major 128 and above and use the PTY
master multiplex (/dev/ptmx) to acquire a PTY on
demand.
2 block Floppy disks
0 = /dev/fd0 Controller 0, drive 0, autodetect
1 = /dev/fd1 Controller 0, drive 1, autodetect
......@@ -257,7 +258,7 @@ Your cooperation is appreciated.
129 = /dev/vcsa1 tty1 text/attribute contents
...
191 = /dev/vcsa63 tty63 text/attribute contents
NOTE: These devices permit both read and write access.
7 block Loopback devices
......@@ -411,7 +412,7 @@ Your cooperation is appreciated.
207 = /dev/video/em8300_sp EM8300 DVD decoder subpicture
208 = /dev/compaq/cpqphpc Compaq PCI Hot Plug Controller
209 = /dev/compaq/cpqrid Compaq Remote Insight Driver
210 = /dev/impi/bt IMPI coprocessor block transfer
210 = /dev/impi/bt IMPI coprocessor block transfer
211 = /dev/impi/smic IMPI coprocessor stream interface
212 = /dev/watchdogs/0 First watchdog device
213 = /dev/watchdogs/1 Second watchdog device
......@@ -506,6 +507,7 @@ Your cooperation is appreciated.
33 = /dev/patmgr1 Sequencer patch manager
34 = /dev/midi02 Third MIDI port
50 = /dev/midi03 Fourth MIDI port
14 block BIOS harddrive callback support {2.6}
0 = /dev/dos_hda First BIOS harddrive whole disk
64 = /dev/dos_hdb Second BIOS harddrive whole disk
......@@ -527,6 +529,7 @@ Your cooperation is appreciated.
16 char Non-SCSI scanners
0 = /dev/gs4500 Genius 4500 handheld scanner
16 block GoldStar CD-ROM
0 = /dev/gscd GoldStar CD-ROM
......@@ -548,6 +551,7 @@ Your cooperation is appreciated.
0 = /dev/ttyC0 First Cyclades port
...
31 = /dev/ttyC31 32nd Cyclades port
19 block "Double" compressed disk
0 = /dev/double0 First compressed disk
...
......@@ -563,6 +567,7 @@ Your cooperation is appreciated.
0 = /dev/cub0 Callout device for ttyC0
...
31 = /dev/cub31 Callout device for ttyC31
20 block Hitachi CD-ROM (under development)
0 = /dev/hitcd Hitachi CD-ROM
......@@ -582,7 +587,7 @@ Your cooperation is appreciated.
This device is used on the ARM-based Acorn RiscPC.
Partitions are handled the same way as for IDE disks
(see major number 3).
(see major number 3).
22 char Digiboard serial card
0 = /dev/ttyD0 First Digiboard port
......@@ -591,7 +596,7 @@ Your cooperation is appreciated.
22 block Second IDE hard disk/CD-ROM interface
0 = /dev/hdc Master: whole disk (or CD-ROM)
64 = /dev/hdd Slave: whole disk (or CD-ROM)
Partitions are handled the same way as for the first
interface (see major number 3).
......@@ -639,6 +644,7 @@ Your cooperation is appreciated.
26 char Quanta WinVision frame grabber {2.6}
0 = /dev/wvisfgrab Quanta WinVision frame grabber
26 block Second Matsushita (Panasonic/SoundBlaster) CD-ROM
0 = /dev/sbpcd4 Panasonic CD-ROM controller 1 unit 0
1 = /dev/sbpcd5 Panasonic CD-ROM controller 1 unit 1
......@@ -670,6 +676,7 @@ Your cooperation is appreciated.
37 = /dev/nrawqft1 Unit 1, no rewind-on-close, no file marks
38 = /dev/nrawqft2 Unit 2, no rewind-on-close, no file marks
39 = /dev/nrawqft3 Unit 3, no rewind-on-close, no file marks
27 block Third Matsushita (Panasonic/SoundBlaster) CD-ROM
0 = /dev/sbpcd8 Panasonic CD-ROM controller 2 unit 0
1 = /dev/sbpcd9 Panasonic CD-ROM controller 2 unit 1
......@@ -681,6 +688,7 @@ Your cooperation is appreciated.
1 = /dev/staliomem1 Second Stallion card I/O memory
2 = /dev/staliomem2 Third Stallion card I/O memory
3 = /dev/staliomem3 Fourth Stallion card I/O memory
28 char Atari SLM ACSI laser printer (68k/Atari)
0 = /dev/slm0 First SLM laser printer
1 = /dev/slm1 Second SLM laser printer
......@@ -690,6 +698,7 @@ Your cooperation is appreciated.
1 = /dev/sbpcd13 Panasonic CD-ROM controller 3 unit 1
2 = /dev/sbpcd14 Panasonic CD-ROM controller 3 unit 2
3 = /dev/sbpcd15 Panasonic CD-ROM controller 3 unit 3
28 block ACSI disk (68k/Atari)
0 = /dev/ada First ACSI disk whole disk
16 = /dev/adb Second ACSI disk whole disk
......@@ -750,6 +759,7 @@ Your cooperation is appreciated.
31 char MPU-401 MIDI
0 = /dev/mpu401data MPU-401 data port
1 = /dev/mpu401stat MPU-401 status port
31 block ROM/flash memory card
0 = /dev/rom0 First ROM card (rw)
...
......@@ -801,7 +811,7 @@ Your cooperation is appreciated.
34 block Fourth IDE hard disk/CD-ROM interface
0 = /dev/hdg Master: whole disk (or CD-ROM)
64 = /dev/hdh Slave: whole disk (or CD-ROM)
Partitions are handled the same way as for the first
interface (see major number 3).
......@@ -818,6 +828,7 @@ Your cooperation is appreciated.
129 = /dev/smpte1 Second MIDI port, SMPTE timed
130 = /dev/smpte2 Third MIDI port, SMPTE timed
131 = /dev/smpte3 Fourth MIDI port, SMPTE timed
35 block Slow memory ramdisk
0 = /dev/slram Slow memory ramdisk
......@@ -828,6 +839,7 @@ Your cooperation is appreciated.
16 = /dev/tap0 First Ethertap device
...
31 = /dev/tap15 16th Ethertap device
36 block MCA ESDI hard disk
0 = /dev/eda First ESDI disk whole disk
64 = /dev/edb Second ESDI disk whole disk
......@@ -882,6 +894,7 @@ Your cooperation is appreciated.
40 char Matrox Meteor frame grabber {2.6}
0 = /dev/mmetfgrab Matrox Meteor frame grabber
40 block Syquest EZ135 parallel port removable drive
0 = /dev/eza Parallel EZ135 drive, whole disk
......@@ -893,6 +906,7 @@ Your cooperation is appreciated.
41 char Yet Another Micro Monitor
0 = /dev/yamm Yet Another Micro Monitor
41 block MicroSolutions BackPack parallel port CD-ROM
0 = /dev/bpcd BackPack CD-ROM
......@@ -901,6 +915,7 @@ Your cooperation is appreciated.
the parallel port ATAPI CD-ROM driver at major number 46.
42 char Demo/sample use
42 block Demo/sample use
This number is intended for use in sample code, as
......@@ -918,6 +933,7 @@ Your cooperation is appreciated.
0 = /dev/ttyI0 First virtual modem
...
63 = /dev/ttyI63 64th virtual modem
43 block Network block devices
0 = /dev/nb0 First network block device
1 = /dev/nb1 Second network block device
......@@ -934,12 +950,13 @@ Your cooperation is appreciated.
0 = /dev/cui0 Callout device for ttyI0
...
63 = /dev/cui63 Callout device for ttyI63
44 block Flash Translation Layer (FTL) filesystems
0 = /dev/ftla FTL on first Memory Technology Device
16 = /dev/ftlb FTL on second Memory Technology Device
32 = /dev/ftlc FTL on third Memory Technology Device
...
240 = /dev/ftlp FTL on 16th Memory Technology Device
240 = /dev/ftlp FTL on 16th Memory Technology Device
Partitions are handled in the same way as for IDE
disks (see major number 3) except that the partition
......@@ -958,6 +975,7 @@ Your cooperation is appreciated.
191 = /dev/ippp63 64th SyncPPP device
255 = /dev/isdninfo ISDN monitor interface
45 block Parallel port IDE disk devices
0 = /dev/pda First parallel port IDE disk
16 = /dev/pdb Second parallel port IDE disk
......@@ -1044,6 +1062,7 @@ Your cooperation is appreciated.
1 = /dev/dcbri1 Second DataComm card
2 = /dev/dcbri2 Third DataComm card
3 = /dev/dcbri3 Fourth DataComm card
52 block Mylex DAC960 PCI RAID controller; fifth controller
0 = /dev/rd/c4d0 First disk, whole disk
8 = /dev/rd/c4d1 Second disk, whole disk
......@@ -1093,7 +1112,8 @@ Your cooperation is appreciated.
55 char DSP56001 digital signal processor
0 = /dev/dsp56k First DSP56001
55 block Mylex DAC960 PCI RAID controller; eigth controller
55 block Mylex DAC960 PCI RAID controller; eighth controller
0 = /dev/rd/c7d0 First disk, whole disk
8 = /dev/rd/c7d1 Second disk, whole disk
...
......@@ -1130,6 +1150,7 @@ Your cooperation is appreciated.
0 = /dev/cup0 Callout device for ttyP0
1 = /dev/cup1 Callout device for ttyP1
...
58 block Reserved for logical volume manager
59 char sf firewall package
......@@ -1149,6 +1170,7 @@ Your cooperation is appreciated.
NAMING CONFLICT -- PROPOSED REVISED NAME /dev/rpda0 etc
60-63 char LOCAL/EXPERIMENTAL USE
60-63 block LOCAL/EXPERIMENTAL USE
Allocated for local/experimental use. For devices not
assigned official numbers, these ranges should be
......@@ -1434,7 +1456,6 @@ Your cooperation is appreciated.
DAC960 (see major number 48) except that the limit on
partitions is 15.
78 char PAM Software's multimodem boards
0 = /dev/ttyM0 First PAM modem
1 = /dev/ttyM1 Second PAM modem
......@@ -1450,13 +1471,12 @@ Your cooperation is appreciated.
DAC960 (see major number 48) except that the limit on
partitions is 15.
79 char PAM Software's multimodem boards - alternate devices
0 = /dev/cum0 Callout device for ttyM0
1 = /dev/cum1 Callout device for ttyM1
...
79 block Compaq Intelligent Drive Array, eigth controller
79 block Compaq Intelligent Drive Array, eighth controller
0 = /dev/ida/c7d0 First logical drive whole disk
16 = /dev/ida/c7d1 Second logical drive whole disk
...
......@@ -1466,7 +1486,6 @@ Your cooperation is appreciated.
DAC960 (see major number 48) except that the limit on
partitions is 15.
80 char Photometrics AT200 CCD camera
0 = /dev/at200 Photometrics AT200 CCD camera
......@@ -1679,7 +1698,7 @@ Your cooperation is appreciated.
1 = /dev/dcxx1 Second capture card
...
94 block IBM S/390 DASD block storage
94 block IBM S/390 DASD block storage
0 = /dev/dasda First DASD device, major
1 = /dev/dasda1 First DASD device, block 1
2 = /dev/dasda2 First DASD device, block 2
......@@ -1695,7 +1714,7 @@ Your cooperation is appreciated.
1 = /dev/ipnat NAT control device/log file
2 = /dev/ipstate State information log file
3 = /dev/ipauth Authentication control device/log file
...
...
96 char Parallel port ATAPI tape devices
0 = /dev/pt0 First parallel port ATAPI tape
......@@ -1705,7 +1724,7 @@ Your cooperation is appreciated.
129 = /dev/npt1 Second p.p. ATAPI tape, no rewind
...
96 block Inverse NAND Flash Translation Layer
96 block Inverse NAND Flash Translation Layer
0 = /dev/inftla First INFTL layer
16 = /dev/inftlb Second INFTL layer
...
......@@ -1900,7 +1919,7 @@ Your cooperation is appreciated.
1 = /dev/av1 Second A/V card
...
111 block Compaq Next Generation Drive Array, eigth controller
111 block Compaq Next Generation Drive Array, eighth controller
0 = /dev/cciss/c7d0 First logical drive, whole disk
16 = /dev/cciss/c7d1 Second logical drive, whole disk
...
......@@ -1937,7 +1956,6 @@ Your cooperation is appreciated.
...
113 block IBM iSeries virtual CD-ROM
0 = /dev/iseries/vcda First virtual CD-ROM
1 = /dev/iseries/vcdb Second virtual CD-ROM
...
......@@ -2059,11 +2077,12 @@ Your cooperation is appreciated.
...
119 char VMware virtual network control
0 = /dev/vnet0 1st virtual network
1 = /dev/vnet1 2nd virtual network
0 = /dev/vmnet0 1st virtual network
1 = /dev/vmnet1 2nd virtual network
...
120-127 char LOCAL/EXPERIMENTAL USE
120-127 block LOCAL/EXPERIMENTAL USE
Allocated for local/experimental use. For devices not
assigned official numbers, these ranges should be
......@@ -2075,7 +2094,6 @@ Your cooperation is appreciated.
nodes; instead they should be accessed through the
/dev/ptmx cloning interface.
128 block SCSI disk devices (128-143)
0 = /dev/sddy 129th SCSI disk whole disk
16 = /dev/sddz 130th SCSI disk whole disk
......@@ -2087,7 +2105,6 @@ Your cooperation is appreciated.
disks (see major number 3) except that the limit on
partitions is 15.
129 block SCSI disk devices (144-159)
0 = /dev/sdeo 145th SCSI disk whole disk
16 = /dev/sdep 146th SCSI disk whole disk
......@@ -2123,7 +2140,6 @@ Your cooperation is appreciated.
disks (see major number 3) except that the limit on
partitions is 15.
132 block SCSI disk devices (192-207)
0 = /dev/sdgk 193rd SCSI disk whole disk
16 = /dev/sdgl 194th SCSI disk whole disk
......@@ -2135,7 +2151,6 @@ Your cooperation is appreciated.
disks (see major number 3) except that the limit on
partitions is 15.
133 block SCSI disk devices (208-223)
0 = /dev/sdha 209th SCSI disk whole disk
16 = /dev/sdhb 210th SCSI disk whole disk
......@@ -2147,7 +2162,6 @@ Your cooperation is appreciated.
disks (see major number 3) except that the limit on
partitions is 15.
134 block SCSI disk devices (224-239)
0 = /dev/sdhq 225th SCSI disk whole disk
16 = /dev/sdhr 226th SCSI disk whole disk
......@@ -2159,7 +2173,6 @@ Your cooperation is appreciated.
disks (see major number 3) except that the limit on
partitions is 15.
135 block SCSI disk devices (240-255)
0 = /dev/sdig 241st SCSI disk whole disk
16 = /dev/sdih 242nd SCSI disk whole disk
......@@ -2171,7 +2184,6 @@ Your cooperation is appreciated.
disks (see major number 3) except that the limit on
partitions is 15.
136-143 char Unix98 PTY slaves
0 = /dev/pts/0 First Unix98 pseudo-TTY
1 = /dev/pts/1 Second Unix98 pesudo-TTY
......@@ -2384,6 +2396,7 @@ Your cooperation is appreciated.
...
159 char RESERVED
159 block RESERVED
160 char General Purpose Instrument Bus (GPIB)
......@@ -2427,7 +2440,7 @@ Your cooperation is appreciated.
Partitions are handled in the same way as for IDE
disks (see major number 3) except that the limit on
partitions is 31.
partitions is 31.
162 char Raw block device interface
0 = /dev/rawctl Raw I/O control device
......@@ -2483,7 +2496,6 @@ Your cooperation is appreciated.
171 char Reserved for IEEE 1394 (Firewire)
172 char Moxa Intellio serial card
0 = /dev/ttyMX0 First Moxa port
1 = /dev/ttyMX1 Second Moxa port
......@@ -2543,9 +2555,6 @@ Your cooperation is appreciated.
64 = /dev/usb/rio500 Diamond Rio 500
65 = /dev/usb/usblcd USBLCD Interface (info@usblcd.de)
66 = /dev/usb/cpad0 Synaptics cPad (mouse/LCD)
67 = /dev/usb/adutux0 1st Ontrak ADU device
...
76 = /dev/usb/adutux10 10th Ontrak ADU device
96 = /dev/usb/hiddev0 1st USB HID device
...
111 = /dev/usb/hiddev15 16th USB HID device
......@@ -2558,7 +2567,7 @@ Your cooperation is appreciated.
132 = /dev/usb/idmouse ID Mouse (fingerprint scanner) device
133 = /dev/usb/sisusbvga1 First SiSUSB VGA device
...
140 = /dev/usb/sisusbvga8 Eigth SISUSB VGA device
140 = /dev/usb/sisusbvga8 Eighth SISUSB VGA device
144 = /dev/usb/lcd USB LCD device
160 = /dev/usb/legousbtower0 1st USB Legotower device
...
......@@ -2571,7 +2580,7 @@ Your cooperation is appreciated.
0 = /dev/uba First USB block device
8 = /dev/ubb Second USB block device
16 = /dev/ubc Third USB block device
...
...
181 char Conrad Electronic parallel port radio clocks
0 = /dev/pcfclock0 First Conrad radio clock
......@@ -2657,7 +2666,7 @@ Your cooperation is appreciated.
32 = /dev/mvideo/status2 Third device
...
...
240 = /dev/mvideo/status15 16th device
240 = /dev/mvideo/status15 16th device
...
195 char Nvidia graphics devices
......@@ -2795,6 +2804,10 @@ Your cooperation is appreciated.
...
185 = /dev/ttyNX15 Hilscher netX serial port 15
186 = /dev/ttyJ0 JTAG1 DCC protocol based serial port emulation
187 = /dev/ttyUL0 Xilinx uartlite - port 0
...
190 = /dev/ttyUL3 Xilinx uartlite - port 3
191 = /dev/xvc0 Xen virtual console - port 0
205 char Low-density serial ports (alternate device)
0 = /dev/culu0 Callout device for ttyLU0
......@@ -2832,7 +2845,6 @@ Your cooperation is appreciated.
82 = /dev/cuvr0 Callout device for ttyVR0
83 = /dev/cuvr1 Callout device for ttyVR1
206 char OnStream SC-x0 tape devices
0 = /dev/osst0 First OnStream SCSI tape, mode 0
1 = /dev/osst1 Second OnStream SCSI tape, mode 0
......@@ -2922,7 +2934,6 @@ Your cooperation is appreciated.
...
212 char LinuxTV.org DVB driver subsystem
0 = /dev/dvb/adapter0/video0 first video decoder of first card
1 = /dev/dvb/adapter0/audio0 first audio decoder of first card
2 = /dev/dvb/adapter0/sec0 (obsolete/unused)
......@@ -3008,9 +3019,9 @@ Your cooperation is appreciated.
2 = /dev/3270/tub2 Second 3270 terminal
...
229 char IBM iSeries virtual console
0 = /dev/iseries/vtty0 First console port
1 = /dev/iseries/vtty1 Second console port
229 char IBM iSeries/pSeries virtual console
0 = /dev/hvc0 First console port
1 = /dev/hvc1 Second console port
...
230 char IBM iSeries virtual tape
......@@ -3083,12 +3094,14 @@ Your cooperation is appreciated.
234-239 UNASSIGNED
240-254 char LOCAL/EXPERIMENTAL USE
240-254 block LOCAL/EXPERIMENTAL USE
Allocated for local/experimental use. For devices not
assigned official numbers, these ranges should be
used in order to avoid conflicting with future assignments.
255 char RESERVED
255 block RESERVED
This major is reserved to assist the expansion to a
......@@ -3115,7 +3128,20 @@ Your cooperation is appreciated.
257 char Phoenix Technologies Cryptographic Services Driver
0 = /dev/ptlsec Crypto Services Driver
257 block SSFDC Flash Translation Layer filesystem
0 = /dev/ssfdca First SSFDC layer
8 = /dev/ssfdcb Second SSFDC layer
16 = /dev/ssfdcc Third SSFDC layer
24 = /dev/ssfdcd 4th SSFDC layer
32 = /dev/ssfdce 5th SSFDC layer
40 = /dev/ssfdcf 6th SSFDC layer
48 = /dev/ssfdcg 7th SSFDC layer
56 = /dev/ssfdch 8th SSFDC layer
258 block ROM/Flash read-only translation layer
0 = /dev/blockrom0 First ROM card's translation layer interface
1 = /dev/blockrom1 Second ROM card's translation layer interface
...
**** ADDITIONAL /dev DIRECTORY ENTRIES
......
Documentation/driver-model/platform.txt
浏览文件 @ c4366889
Platform Devices and Drivers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
See <linux/platform_device.h> for the driver model interface to the
platform bus: platform_device, and platform_driver. This pseudo-bus
is used to connect devices on busses with minimal infrastructure,
like those used to integrate peripherals on many system-on-chip
processors, or some "legacy" PC interconnects; as opposed to large
formally specified ones like PCI or USB.
Platform devices
~~~~~~~~~~~~~~~~
Platform devices are devices that typically appear as autonomous
entities in the system. This includes legacy port-based devices and
host bridges to peripheral buses.
Platform drivers
~~~~~~~~~~~~~~~~
Drivers for platform devices are typically very simple and
unstructured. Either the device was present at a particular I/O port
and the driver was loaded, or it was not. There was no possibility
of hotplugging or alternative discovery besides probing at a specific
I/O address and expecting a specific response.
host bridges to peripheral buses, and most controllers integrated
into system-on-chip platforms. What they usually have in common
is direct addressing from a CPU bus. Rarely, a platform_device will
be connected through a segment of some other kind of bus; but its
registers will still be directly addressible.
Platform devices are given a name, used in driver binding, and a
list of resources such as addresses and IRQs.
Other Architectures, Modern Firmware, and new Platforms
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
These devices are not always at the legacy I/O ports. This is true on
other architectures and on some modern architectures. In most cases,
the drivers are modified to discover the devices at other well-known
ports for the given platform. However, the firmware in these systems
does usually know where exactly these devices reside, and in some
cases, it's the only way of discovering them.
struct platform_device {
const char *name;
u32 id;
struct device dev;
u32 num_resources;
struct resource *resource;
};
The Platform Bus
~~~~~~~~~~~~~~~~
A platform bus has been created to deal with these issues. First and
foremost, it groups all the legacy devices under a common bus, and
gives them a common parent if they don't already have one.
But, besides the organizational benefits, the platform bus can also
accommodate firmware-based enumeration.
Device Discovery
Platform drivers
~~~~~~~~~~~~~~~~
The platform bus has no concept of probing for devices. Devices
discovery is left up to either the legacy drivers or the
firmware. These entities are expected to notify the platform of
devices that it discovers via the bus's add() callback:
platform_bus.add(parent,bus_id).
Bus IDs
~~~~~~~
Bus IDs are the canonical names for the devices. There is no globally
standard addressing mechanism for legacy devices. In the IA-32 world,
we have Pnp IDs to use, as well as the legacy I/O ports. However,
neither tell what the device really is or have any meaning on other
platforms.
Since both PnP IDs and the legacy I/O ports (and other standard I/O
ports for specific devices) have a 1:1 mapping, we map the
platform-specific name or identifier to a generic name (at least
within the scope of the kernel).
For example, a serial driver might find a device at I/O 0x3f8. The
ACPI firmware might also discover a device with PnP ID (_HID)
PNP0501. Both correspond to the same device and should be mapped to the
canonical name 'serial'.
The bus_id field should be a concatenation of the canonical name and
the instance of that type of device. For example, the device at I/O
port 0x3f8 should have a bus_id of "serial0". This places the
responsibility of enumerating devices of a particular type up to the
discovery mechanism. But, they are the entity that should know best
(as opposed to the platform bus driver).
Drivers
~~~~~~~
Drivers for platform devices should have a name that is the same as
the canonical name of the devices they support. This allows the
platform bus driver to do simple matching with the basic data
structures to determine if a driver supports a certain device.
For example, a legacy serial driver should have a name of 'serial' and
register itself with the platform bus.
Driver Binding
~~~~~~~~~~~~~~
Legacy drivers assume they are bound to the device once they start up
and probe an I/O port. Divorcing them from this will be a difficult
process. However, that shouldn't prevent us from implementing
firmware-based enumeration.
The firmware should notify the platform bus about devices before the
legacy drivers have had a chance to load. Once the drivers are loaded,
they driver model core will attempt to bind the driver to any
previously-discovered devices. Once that has happened, it will be free
to discover any other devices it pleases.
Platform drivers follow the standard driver model convention, where
discovery/enumeration is handled outside the drivers, and drivers
provide probe() and remove() methods. They support power management
and shutdown notifications using the standard conventions.
struct platform_driver {
int (*probe)(struct platform_device *);
int (*remove)(struct platform_device *);
void (*shutdown)(struct platform_device *);
int (*suspend)(struct platform_device *, pm_message_t state);
int (*suspend_late)(struct platform_device *, pm_message_t state);
int (*resume_early)(struct platform_device *);
int (*resume)(struct platform_device *);
struct device_driver driver;
};
Note that probe() should general verify that the specified device hardware
actually exists; sometimes platform setup code can't be sure. The probing
can use device resources, including clocks, and device platform_data.
Platform drivers register themselves the normal way:
int platform_driver_register(struct platform_driver *drv);
Or, in common situations where the device is known not to be hot-pluggable,
the probe() routine can live in an init section to reduce the driver's
runtime memory footprint:
int platform_driver_probe(struct platform_driver *drv,
int (*probe)(struct platform_device *))
Device Enumeration
~~~~~~~~~~~~~~~~~~
As a rule, platform specific (and often board-specific) setup code wil
register platform devices:
int platform_device_register(struct platform_device *pdev);
int platform_add_devices(struct platform_device **pdevs, int ndev);
The general rule is to register only those devices that actually exist,
but in some cases extra devices might be registered. For example, a kernel
might be configured to work with an external network adapter that might not
be populated on all boards, or likewise to work with an integrated controller
that some boards might not hook up to any peripherals.
In some cases, boot firmware will export tables describing the devices
that are populated on a given board. Without such tables, often the
only way for system setup code to set up the correct devices is to build
a kernel for a specific target board. Such board-specific kernels are
common with embedded and custom systems development.
In many cases, the memory and IRQ resources associated with the platform
device are not enough to let the device's driver work. Board setup code
will often provide additional information using the device's platform_data
field to hold additional information.
Embedded systems frequently need one or more clocks for platform devices,
which are normally kept off until they're actively needed (to save power).
System setup also associates those clocks with the device, so that that
calls to clk_get(&pdev->dev, clock_name) return them as needed.
Device Naming and Driver Binding
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The platform_device.dev.bus_id is the canonical name for the devices.
It's built from two components:
* platform_device.name ... which is also used to for driver matching.
* platform_device.id ... the device instance number, or else "-1"
to indicate there's only one.
These are catenated, so name/id "serial"/0 indicates bus_id "serial.0", and
"serial/3" indicates bus_id "serial.3"; both would use the platform_driver
named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id)
and use the platform_driver called "my_rtc".
Driver binding is performed automatically by the driver core, invoking
driver probe() after finding a match between device and driver. If the
probe() succeeds, the driver and device are bound as usual. There are
three different ways to find such a match:
- Whenever a device is registered, the drivers for that bus are
checked for matches. Platform devices should be registered very
early during system boot.
- When a driver is registered using platform_driver_register(), all
unbound devices on that bus are checked for matches. Drivers
usually register later during booting, or by module loading.
- Registering a driver using platform_driver_probe() works just like
using platform_driver_register(), except that the the driver won't
be probed later if another device registers. (Which is OK, since
this interface is only for use with non-hotpluggable devices.)
Documentation/driver-model/porting.txt
浏览文件 @ c4366889
......@@ -92,7 +92,7 @@ struct device represents a single device. It mainly contains metadata
describing the relationship the device has to other entities.
- Embedd a struct device in the bus-specific device type.
- Embed a struct device in the bus-specific device type.
struct pci_dev {
......
Documentation/dvb/cards.txt
浏览文件 @ c4366889
......@@ -22,10 +22,10 @@ o Frontends drivers:
- ves1x93 : Alps BSRV2 (ves1893 demodulator) and dbox2 (ves1993)
- cx24110 : Conexant HM1221/HM1811 (cx24110 or cx24106 demod, cx24108 PLL)
- grundig_29504-491 : Grundig 29504-491 (Philips TDA8083 demodulator), tsa5522 PLL
- mt312 : Zarlink mt312 or Mitel vp310 demodulator, sl1935 or tsa5059 PLL
- mt312 : Zarlink mt312 or Mitel vp310 demodulator, sl1935 or tsa5059 PLLi, Technisat Sky2Pc with bios Rev. 2.3
- stv0299 : Alps BSRU6 (tsa5059 PLL), LG TDQB-S00x (tsa5059 PLL),
LG TDQF-S001F (sl1935 PLL), Philips SU1278 (tua6100 PLL),
Philips SU1278SH (tsa5059 PLL), Samsung TBMU24112IMB
Philips SU1278SH (tsa5059 PLL), Samsung TBMU24112IMB, Technisat Sky2Pc with bios Rev. 2.6
DVB-C:
- ves1820 : various (ves1820 demodulator, sp5659c or spXXXX PLL)
- at76c651 : Atmel AT76c651(B) with DAT7021 PLL
......
Documentation/dvb/ci.txt
浏览文件 @ c4366889
......@@ -71,7 +71,7 @@ eliminating the need for any additional ioctls.
The disadvantage is that the driver/hardware has to manage the rest. For
the application programmer it would be as simple as sending/receiving an
array to/from the CI ioctls as defined in the Linux DVB API. No changes
have been made in the API to accomodate this feature.
have been made in the API to accommodate this feature.
* Why the need for another CI interface ?
......@@ -102,7 +102,7 @@ This CI interface follows the CI high level interface, which is not
implemented by most applications. Hence this area is revisited.
This CI interface is quite different in the case that it tries to
accomodate all other CI based devices, that fall into the other categories
accommodate all other CI based devices, that fall into the other categories.
This means that this CI interface handles the EN50221 style tags in the
Application layer only and no session management is taken care of by the
......
Documentation/eisa.txt
浏览文件 @ c4366889
......@@ -62,7 +62,7 @@ res : root device I/O resource
bus_base_addr : slot 0 address on this bus
slots : max slot number to probe
force_probe : Probe even when slot 0 is empty (no EISA mainboard)
dma_mask : Default DMA mask. Usualy the bridge device dma_mask.
dma_mask : Default DMA mask. Usually the bridge device dma_mask.
bus_nr : unique bus id, set by eisa_root_register
** Driver :
......
Documentation/fault-injection/failcmd.sh 0 → 100644
浏览文件 @ c4366889
#!/bin/bash
echo 1 > /proc/self/make-it-fail
exec $*
Documentation/fault-injection/failmodule.sh 0 → 100644
浏览文件 @ c4366889
#!/bin/bash
#
# Usage: failmodule <failname> <modulename> [stacktrace-depth]
#
# <failname>: "failslab", "fail_alloc_page", or "fail_make_request"
#
# <modulename>: module name that you want to inject faults.
#
# [stacktrace-depth]: the maximum number of stacktrace walking allowed
#
STACKTRACE_DEPTH=5
if [ $# -gt 2 ]; then
STACKTRACE_DEPTH=$3
fi
if [ ! -d /debug/$1 ]; then
echo "Fault-injection $1 does not exist" >&2
exit 1
fi
if [ ! -d /sys/module/$2 ]; then
echo "Module $2 does not exist" >&2
exit 1
fi
# Disable any fault injection
echo 0 > /debug/$1/stacktrace-depth
echo `cat /sys/module/$2/sections/.text` > /debug/$1/require-start
echo `cat /sys/module/$2/sections/.exit.text` > /debug/$1/require-end
echo $STACKTRACE_DEPTH > /debug/$1/stacktrace-depth
Documentation/fault-injection/fault-injection.txt 0 → 100644
浏览文件 @ c4366889
Fault injection capabilities infrastructure
===========================================
See also drivers/md/faulty.c and "every_nth" module option for scsi_debug.
Available fault injection capabilities
--------------------------------------
o failslab
injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
o fail_page_alloc
injects page allocation failures. (alloc_pages(), get_free_pages(), ...)
o fail_make_request
injects disk IO errors on devices permitted by setting
/sys/block/<device>/make-it-fail or
/sys/block/<device>/<partition>/make-it-fail. (generic_make_request())
Configure fault-injection capabilities behavior
-----------------------------------------------
o debugfs entries
fault-inject-debugfs kernel module provides some debugfs entries for runtime
configuration of fault-injection capabilities.
- /debug/fail*/probability:
likelihood of failure injection, in percent.
Format: <percent>
Note that one-failure-per-hundred is a very high error rate
for some testcases. Consider setting probability=100 and configure
/debug/fail*/interval for such testcases.
- /debug/fail*/interval:
specifies the interval between failures, for calls to
should_fail() that pass all the other tests.
Note that if you enable this, by setting interval>1, you will
probably want to set probability=100.
- /debug/fail*/times:
specifies how many times failures may happen at most.
A value of -1 means "no limit".
- /debug/fail*/space:
specifies an initial resource "budget", decremented by "size"
on each call to should_fail(,size). Failure injection is
suppressed until "space" reaches zero.
- /debug/fail*/verbose
Format: { 0 | 1 | 2 }
specifies the verbosity of the messages when failure is
injected. '0' means no messages; '1' will print only a single
log line per failure; '2' will print a call trace too -- useful
to debug the problems revealed by fault injection.
- /debug/fail*/task-filter:
Format: { 'Y' | 'N' }
A value of 'N' disables filtering by process (default).
Any positive value limits failures to only processes indicated by
/proc/<pid>/make-it-fail==1.
- /debug/fail*/require-start:
- /debug/fail*/require-end:
- /debug/fail*/reject-start:
- /debug/fail*/reject-end:
specifies the range of virtual addresses tested during
stacktrace walking. Failure is injected only if some caller
in the walked stacktrace lies within the required range, and
none lies within the rejected range.
Default required range is [0,ULONG_MAX) (whole of virtual address space).
Default rejected range is [0,0).
- /debug/fail*/stacktrace-depth:
specifies the maximum stacktrace depth walked during search
for a caller within [require-start,require-end) OR
[reject-start,reject-end).
- /debug/fail_page_alloc/ignore-gfp-highmem:
Format: { 'Y' | 'N' }
default is 'N', setting it to 'Y' won't inject failures into
highmem/user allocations.
- /debug/failslab/ignore-gfp-wait:
- /debug/fail_page_alloc/ignore-gfp-wait:
Format: { 'Y' | 'N' }
default is 'N', setting it to 'Y' will inject failures
only into non-sleep allocations (GFP_ATOMIC allocations).
o Boot option
In order to inject faults while debugfs is not available (early boot time),
use the boot option:
failslab=
fail_page_alloc=
fail_make_request=<interval>,<probability>,<space>,<times>
How to add new fault injection capability
-----------------------------------------
o #include <linux/fault-inject.h>
o define the fault attributes
DECLARE_FAULT_INJECTION(name);
Please see the definition of struct fault_attr in fault-inject.h
for details.
o provide a way to configure fault attributes
- boot option
If you need to enable the fault injection capability from boot time, you can
provide boot option to configure it. There is a helper function for it:
setup_fault_attr(attr, str);
- debugfs entries
failslab, fail_page_alloc, and fail_make_request use this way.
Helper functions:
init_fault_attr_entries(entries, attr, name);
void cleanup_fault_attr_entries(entries);
- module parameters
If the scope of the fault injection capability is limited to a
single kernel module, it is better to provide module parameters to
configure the fault attributes.
o add a hook to insert failures
Upon should_fail() returning true, client code should inject a failure.
should_fail(attr, size);
Application Examples
--------------------
o inject slab allocation failures into module init/cleanup code
------------------------------------------------------------------------------
#!/bin/bash
FAILCMD=Documentation/fault-injection/failcmd.sh
BLACKLIST="root_plug evbug"
FAILNAME=failslab
echo Y > /debug/$FAILNAME/task-filter
echo 10 > /debug/$FAILNAME/probability
echo 100 > /debug/$FAILNAME/interval
echo -1 > /debug/$FAILNAME/times
echo 2 > /debug/$FAILNAME/verbose
echo 1 > /debug/$FAILNAME/ignore-gfp-wait
blacklist()
{
echo $BLACKLIST | grep $1 > /dev/null 2>&1
}
oops()
{
dmesg | grep BUG > /dev/null 2>&1
}
find /lib/modules/`uname -r` -name '*.ko' -exec basename {} .ko \; |
while read i
do
oops && exit 1
if ! blacklist $i
then
echo inserting $i...
bash $FAILCMD modprobe $i
fi
done
lsmod | awk '{ if ($3 == 0) { print $1 } }' |
while read i
do
oops && exit 1
if ! blacklist $i
then
echo removing $i...
bash $FAILCMD modprobe -r $i
fi
done
------------------------------------------------------------------------------
o inject slab allocation failures only for a specific module
------------------------------------------------------------------------------
#!/bin/bash
FAILMOD=Documentation/fault-injection/failmodule.sh
echo injecting errors into the module $1...
modprobe $1
bash $FAILMOD failslab $1 10
echo 25 > /debug/failslab/probability
------------------------------------------------------------------------------
Documentation/feature-removal-schedule.txt
浏览文件 @ c4366889
......@@ -30,11 +30,39 @@ Who: Adrian Bunk <bunk@stusta.de>
---------------------------
What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN
When: November 2006
Why: Deprecated in favour of the new ioctl-based rawiso interface, which is
more efficient. You should really be using libraw1394 for raw1394
access anyway.
Who: Jody McIntyre <scjody@modernduck.com>
When: June 2007
Why: Deprecated in favour of the more efficient and robust rawiso interface.
Affected are applications which use the deprecated part of libraw1394
(raw1394_iso_write, raw1394_start_iso_write, raw1394_start_iso_rcv,
raw1394_stop_iso_rcv) or bypass libraw1394.
Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: dv1394 driver (CONFIG_IEEE1394_DV1394)
When: June 2007
Why: Replaced by raw1394 + userspace libraries, notably libiec61883. This
shift of application support has been indicated on www.linux1394.org
and developers' mailinglists for quite some time. Major applications
have been converted, with the exception of ffmpeg and hence xine.
Piped output of dvgrab2 is a partial equivalent to dv1394.
Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: ieee1394 core's unused exports (CONFIG_IEEE1394_EXPORT_FULL_API)
When: January 2007
Why: There are no projects known to use these exported symbols, except
dfg1394 (uses one symbol whose functionality is core-internal now).
Who: Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: ieee1394's *_oui sysfs attributes (CONFIG_IEEE1394_OUI_DB)
When: January 2007
Files: drivers/ieee1394/: oui.db, oui2c.sh
Why: big size, little value
Who: Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
......@@ -53,18 +81,6 @@ Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
---------------------------
What: sys_sysctl
When: January 2007
Why: The same information is available through /proc/sys and that is the
interface user space prefers to use. And there do not appear to be
any existing user in user space of sys_sysctl. The additional
maintenance overhead of keeping a set of binary names gets
in the way of doing a good job of maintaining this interface.
Who: Eric Biederman <ebiederm@xmission.com>
---------------------------
What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
When: November 2005
Files: drivers/pcmcia/: pcmcia_ioctl.c
......@@ -82,18 +98,6 @@ Who: Dominik Brodowski <linux@brodo.de>
---------------------------
What: ip_queue and ip6_queue (old ipv4-only and ipv6-only netfilter queue)
When: December 2005
Why: This interface has been obsoleted by the new layer3-independent
"nfnetlink_queue". The Kernel interface is compatible, so the old
ip[6]tables "QUEUE" targets still work and will transparently handle
all packets into nfnetlink queue number 0. Userspace users will have
to link against API-compatible library on top of libnfnetlink_queue
instead of the current 'libipq'.
Who: Harald Welte <laforge@netfilter.org>
---------------------------
What: remove EXPORT_SYMBOL(kernel_thread)
When: August 2006
Files: arch/*/kernel/*_ksyms.c
......@@ -212,17 +216,6 @@ Who: Thomas Gleixner <tglx@linutronix.de>
---------------------------
What: i2c-ite and i2c-algo-ite drivers
When: September 2006
Why: These drivers never compiled since they were added to the kernel
tree 5 years ago. This feature removal can be reevaluated if
someone shows interest in the drivers, fixes them and takes over
maintenance.
http://marc.theaimsgroup.com/?l=linux-mips&m=115040510817448
Who: Jean Delvare <khali@linux-fr.org>
---------------------------
What: Bridge netfilter deferred IPv4/IPv6 output hook calling
When: January 2007
Why: The deferred output hooks are a layering violation causing unusual
......@@ -239,23 +232,8 @@ Who: Patrick McHardy <kaber@trash.net>
---------------------------
What: frame diverter
When: November 2006
Why: The frame diverter is included in most distribution kernels, but is
broken. It does not correctly handle many things:
- IPV6
- non-linear skb's
- network device RCU on removal
- input frames not correctly checked for protocol errors
It also adds allocation overhead even if not enabled.
It is not clear if anyone is still using it.
Who: Stephen Hemminger <shemminger@osdl.org>
---------------------------
What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
When: Oktober 2008
When: October 2008
Why: The stacking of class devices makes these values misleading and
inconsistent.
Class devices should not carry any of these properties, and bus
......@@ -273,11 +251,12 @@ Who: Jean Delvare <khali@linux-fr.org>
---------------------------
What: ftape
When: 2.6.20
Why: Orphaned for ages. SMP bugs long unfixed. Few users left
in the world.
Who: Jeff Garzik <jeff@garzik.org>
What: IPv4 only connection tracking/NAT/helpers
When: 2.6.22
Why: The new layer 3 independant connection tracking replaces the old
IPv4 only version. After some stabilization of the new code the
old one will be removed.
Who: Patrick McHardy <kaber@trash.net>
---------------------------
......
Documentation/filesystems/Locking
浏览文件 @ c4366889
......@@ -124,7 +124,7 @@ sync_fs: no no read
write_super_lockfs: ?
unlockfs: ?
statfs: no no no
remount_fs: no yes maybe (see below)
remount_fs: yes yes maybe (see below)
clear_inode: no
umount_begin: yes no no
show_options: no (vfsmount->sem)
......
Documentation/filesystems/adfs.txt
浏览文件 @ c4366889
......@@ -3,7 +3,7 @@ Mount options for ADFS
uid=nnn All files in the partition will be owned by
user id nnn. Default 0 (root).
gid=nnn All files in the partition willbe in group
gid=nnn All files in the partition will be in group
nnn. Default 0 (root).
ownmask=nnn The permission mask for ADFS 'owner' permissions
will be nnn. Default 0700.
......
Documentation/filesystems/configfs/configfs.txt
浏览文件 @ c4366889
......@@ -209,7 +209,7 @@ will happen for write(2).
[struct config_group]
A config_item cannot live in a vaccum. The only way one can be created
A config_item cannot live in a vacuum. The only way one can be created
is via mkdir(2) on a config_group. This will trigger creation of a
child item.
......@@ -275,7 +275,7 @@ directory is not empty.
[struct configfs_subsystem]
A subsystem must register itself, ususally at module_init time. This
A subsystem must register itself, usually at module_init time. This
tells configfs to make the subsystem appear in the file tree.
struct configfs_subsystem {
......
Documentation/filesystems/fuse.txt
浏览文件 @ c4366889
......@@ -51,6 +51,22 @@ homepage:
http://fuse.sourceforge.net/
Filesystem type
~~~~~~~~~~~~~~~
The filesystem type given to mount(2) can be one of the following:
'fuse'
This is the usual way to mount a FUSE filesystem. The first
argument of the mount system call may contain an arbitrary string,
which is not interpreted by the kernel.
'fuseblk'
The filesystem is block device based. The first argument of the
mount system call is interpreted as the name of the device.
Mount options
~~~~~~~~~~~~~
......@@ -94,6 +110,11 @@ Mount options
The default is infinite. Note that the size of read requests is
limited anyway to 32 pages (which is 128kbyte on i386).
'blksize=N'
Set the block size for the filesystem. The default is 512. This
option is only valid for 'fuseblk' type mounts.
Control filesystem
~~~~~~~~~~~~~~~~~~
......@@ -111,7 +132,7 @@ For each connection the following files exist within this directory:
'waiting'
The number of requests which are waiting to be transfered to
The number of requests which are waiting to be transferred to
userspace or being processed by the filesystem daemon. If there is
no filesystem activity and 'waiting' is non-zero, then the
filesystem is hung or deadlocked.
......@@ -136,7 +157,7 @@ following will happen:
2) If the request is not yet sent to userspace AND the signal is not
fatal, then an 'interrupted' flag is set for the request. When
the request has been successfully transfered to userspace and
the request has been successfully transferred to userspace and
this flag is set, an INTERRUPT request is queued.
3) If the request is already sent to userspace, then an INTERRUPT
......
Documentation/filesystems/hpfs.txt
浏览文件 @ c4366889
......@@ -274,7 +274,7 @@ History
Fixed race-condition in buffer code - it is in all filesystems in Linux;
when reading device (cat /dev/hda) while creating files on it, files
could be damaged
2.02 Woraround for bug in breada in Linux. breada could cause accesses beyond
2.02 Workaround for bug in breada in Linux. breada could cause accesses beyond
end of partition
2.03 Char, block devices and pipes are correctly created
Fixed non-crashing race in unlink (Alexander Viro)
......
Documentation/filesystems/ntfs.txt
浏览文件 @ c4366889
......@@ -337,7 +337,7 @@ Finally, for a mirrored volume, i.e. raid level 1, the table would look like
this (note all values are in 512-byte sectors):
--- cut here ---
# Ofs Size Raid Log Number Region Should Number Source Start Taget Start
# Ofs Size Raid Log Number Region Should Number Source Start Target Start
# in of the type type of log size sync? of Device in Device in
# vol volume params mirrors Device Device
0 2056320 mirror core 2 16 nosync 2 /dev/hda1 0 /dev/hdb1 0
......@@ -599,7 +599,7 @@ Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog.
- Major bug fixes for reading files and volumes in corner cases which
were being hit by Windows 2k/XP users.
2.1.2:
- Major bug fixes aleviating the hangs in statfs experienced by some
- Major bug fixes alleviating the hangs in statfs experienced by some
users.
2.1.1:
- Update handling of compressed files so people no longer get the
......
Documentation/filesystems/ocfs2.txt
浏览文件 @ c4366889
......@@ -30,7 +30,7 @@ Caveats
Features which OCFS2 does not support yet:
- sparse files
- extended attributes
- shared writeable mmap
- shared writable mmap
- loopback is supported, but data written will not
be cluster coherent.
- quotas
......@@ -54,3 +54,6 @@ errors=panic Panic and halt the machine if an error occurs.
intr (*) Allow signals to interrupt cluster operations.
nointr Do not allow signals to interrupt cluster
operations.
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.
Documentation/filesystems/proc.txt
浏览文件 @ c4366889
......@@ -1220,9 +1220,9 @@ applications are using mlock(), or if you are running with no swap then
you probably should increase the lower_zone_protection setting.
The units of this tunable are fairly vague. It is approximately equal
to "megabytes". So setting lower_zone_protection=100 will protect around 100
to "megabytes," so setting lower_zone_protection=100 will protect around 100
megabytes of the lowmem zone from user allocations. It will also make
those 100 megabytes unavaliable for use by applications and by
those 100 megabytes unavailable for use by applications and by
pagecache, so there is a cost.
The effects of this tunable may be observed by monitoring
......@@ -1538,10 +1538,10 @@ TCP settings
tcp_ecn
-------
This file controls the use of the ECN bit in the IPv4 headers, this is a new
This file controls the use of the ECN bit in the IPv4 headers. This is a new
feature about Explicit Congestion Notification, but some routers and firewalls
block trafic that has this bit set, so it could be necessary to echo 0 to
/proc/sys/net/ipv4/tcp_ecn, if you want to talk to this sites. For more info
block traffic that has this bit set, so it could be necessary to echo 0 to
/proc/sys/net/ipv4/tcp_ecn if you want to talk to these sites. For more info
you could read RFC2481.
tcp_retrans_collapse
......
Documentation/filesystems/spufs.txt
浏览文件 @ c4366889
......@@ -210,7 +210,7 @@ FILES
/signal2
The two signal notification channels of an SPU. These are read-write
files that operate on a 32 bit word. Writing to one of these files
triggers an interrupt on the SPU. The value writting to the signal
triggers an interrupt on the SPU. The value written to the signal
files can be read from the SPU through a channel read or from host user
space through the file. After the value has been read by the SPU, it
is reset to zero. The possible operations on an open signal1 or sig-
......
Documentation/filesystems/sysv-fs.txt
浏览文件 @ c4366889
This is the implementation of the SystemV/Coherent filesystem for Linux.
It implements all of
- Xenix FS,
- SystemV/386 FS,
- Coherent FS.
This is version beta 4.
To install:
* Answer the 'System V and Coherent filesystem support' question with 'y'
when configuring the kernel.
......@@ -28,11 +25,173 @@ Bugs in the present implementation:
for this FS on hard disk yet.
Please report any bugs and suggestions to
Bruno Haible <haible@ma2s2.mathematik.uni-karlsruhe.de>
Pascal Haible <haible@izfm.uni-stuttgart.de>
Krzysztof G. Baranowski <kgb@manjak.knm.org.pl>
These filesystems are rather similar. Here is a comparison with Minix FS:
* Linux fdisk reports on partitions
- Minix FS 0x81 Linux/Minix
- Xenix FS ??
- SystemV FS ??
- Coherent FS 0x08 AIX bootable
* Size of a block or zone (data allocation unit on disk)
- Minix FS 1024
- Xenix FS 1024 (also 512 ??)
- SystemV FS 1024 (also 512 and 2048)
- Coherent FS 512
* General layout: all have one boot block, one super block and
separate areas for inodes and for directories/data.
On SystemV Release 2 FS (e.g. Microport) the first track is reserved and
all the block numbers (including the super block) are offset by one track.
* Byte ordering of "short" (16 bit entities) on disk:
- Minix FS little endian 0 1
- Xenix FS little endian 0 1
- SystemV FS little endian 0 1
- Coherent FS little endian 0 1
Of course, this affects only the file system, not the data of files on it!
* Byte ordering of "long" (32 bit entities) on disk:
- Minix FS little endian 0 1 2 3
- Xenix FS little endian 0 1 2 3
- SystemV FS little endian 0 1 2 3
- Coherent FS PDP-11 2 3 0 1
Of course, this affects only the file system, not the data of files on it!
* Inode on disk: "short", 0 means non-existent, the root dir ino is:
- Minix FS 1
- Xenix FS, SystemV FS, Coherent FS 2
* Maximum number of hard links to a file:
- Minix FS 250
- Xenix FS ??
- SystemV FS ??
- Coherent FS >=10000
* Free inode management:
- Minix FS a bitmap
- Xenix FS, SystemV FS, Coherent FS
There is a cache of a certain number of free inodes in the super-block.
When it is exhausted, new free inodes are found using a linear search.
* Free block management:
- Minix FS a bitmap
- Xenix FS, SystemV FS, Coherent FS
Free blocks are organized in a "free list". Maybe a misleading term,
since it is not true that every free block contains a pointer to
the next free block. Rather, the free blocks are organized in chunks
of limited size, and every now and then a free block contains pointers
to the free blocks pertaining to the next chunk; the first of these
contains pointers and so on. The list terminates with a "block number"
0 on Xenix FS and SystemV FS, with a block zeroed out on Coherent FS.
* Super-block location:
- Minix FS block 1 = bytes 1024..2047
- Xenix FS block 1 = bytes 1024..2047
- SystemV FS bytes 512..1023
- Coherent FS block 1 = bytes 512..1023
* Super-block layout:
- Minix FS
unsigned short s_ninodes;
unsigned short s_nzones;
unsigned short s_imap_blocks;
unsigned short s_zmap_blocks;
unsigned short s_firstdatazone;
unsigned short s_log_zone_size;
unsigned long s_max_size;
unsigned short s_magic;
- Xenix FS, SystemV FS, Coherent FS
unsigned short s_firstdatazone;
unsigned long s_nzones;
unsigned short s_fzone_count;
unsigned long s_fzones[NICFREE];
unsigned short s_finode_count;
unsigned short s_finodes[NICINOD];
char s_flock;
char s_ilock;
char s_modified;
char s_rdonly;
unsigned long s_time;
short s_dinfo[4]; -- SystemV FS only
unsigned long s_free_zones;
unsigned short s_free_inodes;
short s_dinfo[4]; -- Xenix FS only
unsigned short s_interleave_m,s_interleave_n; -- Coherent FS only
char s_fname[6];
char s_fpack[6];
then they differ considerably:
Xenix FS
char s_clean;
char s_fill[371];
long s_magic;
long s_type;
SystemV FS
long s_fill[12 or 14];
long s_state;
long s_magic;
long s_type;
Coherent FS
unsigned long s_unique;
Note that Coherent FS has no magic.
* Inode layout:
- Minix FS
unsigned short i_mode;
unsigned short i_uid;
unsigned long i_size;
unsigned long i_time;
unsigned char i_gid;
unsigned char i_nlinks;
unsigned short i_zone[7+1+1];
- Xenix FS, SystemV FS, Coherent FS
unsigned short i_mode;
unsigned short i_nlink;
unsigned short i_uid;
unsigned short i_gid;
unsigned long i_size;
unsigned char i_zone[3*(10+1+1+1)];
unsigned long i_atime;
unsigned long i_mtime;
unsigned long i_ctime;
* Regular file data blocks are organized as
- Minix FS
7 direct blocks
1 indirect block (pointers to blocks)
1 double-indirect block (pointer to pointers to blocks)
- Xenix FS, SystemV FS, Coherent FS
10 direct blocks
1 indirect block (pointers to blocks)
1 double-indirect block (pointer to pointers to blocks)
1 triple-indirect block (pointer to pointers to pointers to blocks)
* Inode size, inodes per block
- Minix FS 32 32
- Xenix FS 64 16
- SystemV FS 64 16
- Coherent FS 64 8
* Directory entry on disk
- Minix FS
unsigned short inode;
char name[14/30];
- Xenix FS, SystemV FS, Coherent FS
unsigned short inode;
char name[14];
* Dir entry size, dir entries per block
- Minix FS 16/32 64/32
- Xenix FS 16 64
- SystemV FS 16 64
- Coherent FS 16 32
* How to implement symbolic links such that the host fsck doesn't scream:
- Minix FS normal
- Xenix FS kludge: as regular files with chmod 1000
- SystemV FS ??
- Coherent FS kludge: as regular files with chmod 1000
Bruno Haible
<haible@ma2s2.mathematik.uni-karlsruhe.de>
Notation: We often speak of a "block" but mean a zone (the allocation unit)
and not the disk driver's notion of "block".
Documentation/filesystems/udf.txt
浏览文件 @ c4366889
......@@ -7,8 +7,17 @@ If you encounter problems with reading UDF discs using this driver,
please report them to linux_udf@hpesjro.fc.hp.com, which is the
developer's list.
Write support requires a block driver which supports writing. The current
scsi and ide cdrom drivers do not support writing.
Write support requires a block driver which supports writing. Currently
dvd+rw drives and media support true random sector writes, and so a udf
filesystem on such devices can be directly mounted read/write. CD-RW
media however, does not support this. Instead the media can be formatted
for packet mode using the utility cdrwtool, then the pktcdvd driver can
be bound to the underlying cd device to provide the required buffering
and read-modify-write cycles to allow the filesystem random sector writes
while providing the hardware with only full packet writes. While not
required for dvd+rw media, use of the pktcdvd driver often enhances
performance due to very poor read-modify-write support supplied internally
by drive firmware.
-------------------------------------------------------------------------------
The following mount options are supported:
......
Documentation/ftape.txt 已删除 100644 → 0
浏览文件 @ db2fb9db
Intro
=====
This file describes some issues involved when using the "ftape"
floppy tape device driver that comes with the Linux kernel.
ftape has a home page at
http://ftape.dot-heine.de/
which contains further information about ftape. Please cross check
this WWW address against the address given (if any) in the MAINTAINERS
file located in the top level directory of the Linux kernel source
tree.
NOTE: This is an unmaintained set of drivers, and it is not guaranteed to work.
If you are interested in taking over maintenance, contact Claus-Justus Heine
<ch@dot-heine.de>, the former maintainer.
Contents
========
A minus 1: Ftape documentation
A. Changes
1. Goal
2. I/O Block Size
3. Write Access when not at EOD (End Of Data) or BOT (Begin Of Tape)
4. Formatting
5. Interchanging cartridges with other operating systems
B. Debugging Output
1. Introduction
2. Tuning the debugging output
C. Boot and load time configuration
1. Setting boot time parameters
2. Module load time parameters
3. Ftape boot- and load time options
4. Example kernel parameter setting
5. Example module parameter setting
D. Support and contacts
*******************************************************************************
A minus 1. Ftape documentation
==============================
Unluckily, the ftape-HOWTO is out of date. This really needs to be
changed. Up to date documentation as well as recent development
versions of ftape and useful links to related topics can be found at
the ftape home page at
http://ftape.dot-heine.de/
*******************************************************************************
A. Changes
==========
1. Goal
~~~~
The goal of all that incompatibilities was to give ftape an interface
that resembles the interface provided by SCSI tape drives as close
as possible. Thus any Unix backup program that is known to work
with SCSI tape drives should also work.
The concept of a fixed block size for read/write transfers is
rather unrelated to this SCSI tape compatibility at the file system
interface level. It developed out of a feature of zftape, a
block wise user transparent on-the-fly compression. That compression
support will not be dropped in future releases for compatibility
reasons with previous releases of zftape.
2. I/O Block Size
~~~~~~~~~~~~~~
The block size defaults to 10k which is the default block size of
GNU tar.
The block size can be tuned either during kernel configuration or
at runtime with the MTIOCTOP ioctl using the MTSETBLK operation
(i.e. do "mt -f /dev/qft0" setblk #BLKSZ). A block size of 0
switches to variable block size mode i.e. "mt setblk 0" switches
off the block size restriction. However, this disables zftape's
built in on-the-fly compression which doesn't work with variable
block size mode.
The BLKSZ parameter must be given as a byte count and must be a
multiple of 32k or 0, i.e. use "mt setblk 32768" to switch to a
block size of 32k.
The typical symptom of a block size mismatch is an "invalid
argument" error message.
3. Write Access when not at EOD (End Of Data) or BOT (Begin Of Tape)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
zftape (the file system interface of ftape-3.x) denies write access
to the tape cartridge when it isn't positioned either at BOT or
EOD.
4. Formatting
~~~~~~~~~~
ftape DOES support formatting of floppy tape cartridges. You need the
`ftformat' program that is shipped with the modules version of ftape.
Please get the latest version of ftape from
ftp://sunsite.unc.edu/pub/Linux/kernel/tapes
or from the ftape home page at
http://ftape.dot-heine.de/
`ftformat' is contained in the `./contrib/' subdirectory of that
separate ftape package.
5. Interchanging cartridges with other operating systems
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The internal emulation of Unix tape device file marks has changed
completely. ftape now uses the volume table segment as specified
by the QIC-40/80/3010/3020/113 standards to emulate file marks. As
a consequence there is limited support to interchange cartridges
with other operating systems.
To be more precise: ftape will detect volumes written by other OS's
programs and other OS's programs will detect volumes written by
ftape.
However, it isn't possible to extract the data dumped to the tape
by some MSDOS program with ftape. This exceeds the scope of a
kernel device driver. If you need such functionality, then go ahead
and write a user space utility that is able to do that. ftape already
provides all kernel level support necessary to do that.
*******************************************************************************
B. Debugging Output
================
1. Introduction
~~~~~~~~~~~~
The ftape driver can be very noisy in that is can print lots of
debugging messages to the kernel log files and the system console.
While this is useful for debugging it might be annoying during
normal use and enlarges the size of the driver by several kilobytes.
To reduce the size of the driver you can trim the maximal amount of
debugging information available during kernel configuration. Please
refer to the kernel configuration script and its on-line help
functionality.
The amount of debugging output maps to the "tracing" boot time
option and the "ft_tracing" modules option as follows:
0 bugs
1 + errors (with call-stack dump)
2 + warnings
3 + information
4 + more information
5 + program flow
6 + fdc/dma info
7 + data flow
8 + everything else
2. Tuning the debugging output
~~~~~~~~~~~~~~~~~~~~~~~~~~~
To reduce the amount of debugging output printed to the system
console you can
i) trim the debugging output at run-time with
mt -f /dev/nqft0 setdensity #DBGLVL
where "#DBGLVL" is a number between 0 and 9
ii) trim the debugging output at module load time with
modprobe ftape ft_tracing=#DBGLVL
Of course, this applies only if you have configured ftape to be
compiled as a module.
iii) trim the debugging output during system boot time. Add the
following to the kernel command line:
ftape=#DBGLVL,tracing
Please refer also to the next section if you don't know how to
set boot time parameters.
*******************************************************************************
C. Boot and load time configuration
================================
1. Setting boot time parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Assuming that you use lilo, the LI)nux LO)ader, boot time kernel
parameters can be set by adding a line
append some_kernel_boot_time_parameter
to `/etc/lilo.conf' or at real boot time by typing in the options
at the prompt provided by LILO. I can't give you advice on how to
specify those parameters with other loaders as I don't use them.
For ftape, each "some_kernel_boot_time_parameter" looks like
"ftape=value,option". As an example, the debugging output can be
increased with
ftape=4,tracing
NOTE: the value precedes the option name.
2. Module load time parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Module parameters can be specified either directly when invoking
the program 'modprobe' at the shell prompt:
modprobe ftape ft_tracing=4
or by editing the file `/etc/modprobe.conf' in which case they take
effect each time when the module is loaded with `modprobe' (please
refer to the respective manual pages). Thus, you should add a line
options ftape ft_tracing=4
to `/etc/modprobe.conf` if you intend to increase the debugging
output of the driver.
3. Ftape boot- and load time options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
i. Controlling the amount of debugging output
DBGLVL has to be replaced by a number between 0 and 8.
module | kernel command line
-----------------------|----------------------
ft_tracing=DBGLVL | ftape=DBGLVL,tracing
ii. Hardware setup
BASE is the base address of your floppy disk controller,
IRQ and DMA give its interrupt and DMA channel, respectively.
BOOL is an integer, "0" means "no"; any other value means
"yes". You don't need to specify anything if connecting your tape
drive to the standard floppy disk controller. All of these
values have reasonable defaults. The defaults can be modified
during kernel configuration, i.e. while running "make config",
"make menuconfig" or "make xconfig" in the top level directory
of the Linux kernel source tree. Please refer also to the on
line documentation provided during that kernel configuration
process.
ft_probe_fc10 is set to a non-zero value if you wish for ftape to
probe for a Colorado FC-10 or FC-20 controller.
ft_mach2 is set to a non-zero value if you wish for ftape to probe
for a Mountain MACH-2 controller.
module | kernel command line
-----------------------|----------------------
ft_fdc_base=BASE | ftape=BASE,ioport
ft_fdc_irq=IRQ | ftape=IRQ,irq
ft_fdc_dma=DMA | ftape=DMA,dma
ft_probe_fc10=BOOL | ftape=BOOL,fc10
ft_mach2=BOOL | ftape=BOOL,mach2
ft_fdc_threshold=THR | ftape=THR,threshold
ft_fdc_rate_limit=RATE | ftape=RATE,datarate
4. Example kernel parameter setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To configure ftape to probe for a Colorado FC-10/FC-20 controller
and to increase the amount of debugging output a little bit, add
the following line to `/etc/lilo.conf':
append ftape=1,fc10 ftape=4,tracing
5. Example module parameter setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To do the same, but with ftape compiled as a loadable kernel
module, add the following line to `/etc/modprobe.conf':
options ftape ft_probe_fc10=1 ft_tracing=4
*******************************************************************************
D. Support and contacts
====================
Ftape is distributed under the GNU General Public License. There is
absolutely no warranty for this software. However, you can reach
the current maintainer of the ftape package under the email address
given in the MAINTAINERS file which is located in the top level
directory of the Linux kernel source tree. There you'll find also
the relevant mailing list to use as a discussion forum and the web
page to query for the most recent documentation, related work and
development versions of ftape.
Changelog:
==========
~1996: Original Document
10-24-2004: General cleanup and updating, noting additional module options.
James Nelson <james4765@gmail.com>
Documentation/fujitsu/frv/gdbstub.txt
浏览文件 @ c4366889
......@@ -59,7 +59,7 @@ the following things on the "Kernel Hacking" tab:
Then build as usual, download to the board and execute. Note that if
"Immediate activation" was selected, then the kernel will wait for GDB to
attach. If not, then the kernel will boot immediately and GDB will have to
interupt it or wait for an exception to occur if before doing anything with
interrupt it or wait for an exception to occur before doing anything with
the kernel.
......
Documentation/fujitsu/frv/kernel-ABI.txt
浏览文件 @ c4366889
......@@ -156,7 +156,7 @@ with the main kernel in this regard. Hence the debug mode code (gdbstub) is
almost completely self-contained. The only external code used is the
sprintf family of functions.
Futhermore, break.S is so complicated because single-step mode does not
Furthermore, break.S is so complicated because single-step mode does not
switch off on entry to an exception. That means unless manually disabled,
single-stepping will blithely go on stepping into things like interrupts.
See gdbstub.txt for more information.
......
Documentation/hwmon/adm9240
浏览文件 @ c4366889
......@@ -24,7 +24,7 @@ Authors:
Frodo Looijaard <frodol@dds.nl>,
Philip Edelbrock <phil@netroedge.com>,
Michiel Rook <michiel@grendelproject.nl>,
Grant Coady <gcoady@gmail.com> with guidance
Grant Coady <gcoady.lk@gmail.com> with guidance
from Jean Delvare <khali@linux-fr.org>
Interface
......
Documentation/hwmon/f71805f
浏览文件 @ c4366889
......@@ -17,7 +17,7 @@ Thanks to Kris Chen from Fintek for answering technical questions and
providing additional documentation.
Thanks to Chris Lin from Jetway for providing wiring schematics and
anwsering technical questions.
answering technical questions.
Description
......
Documentation/hwmon/k8temp
浏览文件 @ c4366889
......@@ -2,7 +2,7 @@ Kernel driver k8temp
====================
Supported chips:
* AMD K8 CPU
* AMD Athlon64/FX or Opteron CPUs
Prefix: 'k8temp'
Addresses scanned: PCI space
Datasheet: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/32559.pdf
......@@ -13,10 +13,13 @@ Contact: Rudolf Marek <r.marek@sh.cvut.cz>
Description
-----------
This driver permits reading temperature sensor(s) embedded inside AMD K8 CPUs.
Official documentation says that it works from revision F of K8 core, but
in fact it seems to be implemented for all revisions of K8 except the first
two revisions (SH-B0 and SH-B3).
This driver permits reading temperature sensor(s) embedded inside AMD K8
family CPUs (Athlon64/FX, Opteron). Official documentation says that it works
from revision F of K8 core, but in fact it seems to be implemented for all
revisions of K8 except the first two revisions (SH-B0 and SH-B3).
Please note that you will need at least lm-sensors 2.10.1 for proper userspace
support.
There can be up to four temperature sensors inside single CPU. The driver
will auto-detect the sensors and will display only temperatures from
......
Documentation/hwmon/smsc47m1
浏览文件 @ c4366889
......@@ -2,12 +2,14 @@ Kernel driver smsc47m1
======================
Supported chips:
* SMSC LPC47B27x, LPC47M10x, LPC47M13x, LPC47M14x, LPC47M15x and LPC47M192
* SMSC LPC47B27x, LPC47M112, LPC47M10x, LPC47M13x, LPC47M14x,
LPC47M15x and LPC47M192
Addresses scanned: none, address read from Super I/O config space
Prefix: 'smsc47m1'
Datasheets:
http://www.smsc.com/main/datasheets/47b27x.pdf
http://www.smsc.com/main/datasheets/47m10x.pdf
http://www.smsc.com/main/datasheets/47m112.pdf
http://www.smsc.com/main/tools/discontinued/47m13x.pdf
http://www.smsc.com/main/datasheets/47m14x.pdf
http://www.smsc.com/main/tools/discontinued/47m15x.pdf
......
Documentation/hwmon/w83627ehf
浏览文件 @ c4366889
......@@ -26,7 +26,7 @@ fan control mode).
Temperatures are measured in degrees Celsius and measurement resolution is 1
degC for temp1 and 0.5 degC for temp2 and temp3. An alarm is triggered when
the temperature gets higher than high limit; it stays on until the temperature
falls below the Hysteresis value.
falls below the hysteresis value.
Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
triggered if the rotation speed has dropped below a programmable limit. Fan
......@@ -67,9 +67,9 @@ Thermal Cruise mode
If the temperature is in the range defined by:
pwm[1-4]_target - set target temperature, unit millidegree Celcius
pwm[1-4]_target - set target temperature, unit millidegree Celsius
(range 0 - 127000)
pwm[1-4]_tolerance - tolerance, unit millidegree Celcius (range 0 - 15000)
pwm[1-4]_tolerance - tolerance, unit millidegree Celsius (range 0 - 15000)
there are no changes to fan speed. Once the temperature leaves the interval,
fan speed increases (temp is higher) or decreases if lower than desired.
......
Documentation/i2c/busses/i2c-amd8111
浏览文件 @ c4366889
......@@ -5,7 +5,7 @@ Supported adapters:
Datasheets:
AMD datasheet not yet available, but almost everything can be found
in publically available ACPI 2.0 specification, which the adapter
in the publicly available ACPI 2.0 specification, which the adapter
follows.
Author: Vojtech Pavlik <vojtech@suse.cz>
......
Documentation/i2c/busses/i2c-i801
浏览文件 @ c4366889
......@@ -9,7 +9,10 @@ Supported adapters:
* Intel 82801EB/ER (ICH5) (HW PEC supported, 32 byte buffer not supported)
* Intel 6300ESB
* Intel 82801FB/FR/FW/FRW (ICH6)
* Intel ICH7
* Intel 82801G (ICH7)
* Intel 631xESB/632xESB (ESB2)
* Intel 82801H (ICH8)
* Intel ICH9
Datasheets: Publicly available at the Intel website
Authors:
......
Documentation/i2c/busses/i2c-nforce2
浏览文件 @ c4366889
......@@ -10,11 +10,11 @@ Supported adapters:
* nForce4 MCP51 10de:0264
* nForce4 MCP55 10de:0368
Datasheet: not publically available, but seems to be similar to the
Datasheet: not publicly available, but seems to be similar to the
AMD-8111 SMBus 2.0 adapter.
Authors:
Hans-Frieder Vogt <hfvogt@arcor.de>,
Hans-Frieder Vogt <hfvogt@gmx.net>,
Thomas Leibold <thomas@plx.com>,
Patrick Dreker <patrick@dreker.de>
......@@ -38,7 +38,7 @@ Notes
-----
The SMBus adapter in the nForce2 chipset seems to be very similar to the
SMBus 2.0 adapter in the AMD-8111 southbridge. However, I could only get
SMBus 2.0 adapter in the AMD-8111 south bridge. However, I could only get
the driver to work with direct I/O access, which is different to the EC
interface of the AMD-8111. Tested on Asus A7N8X. The ACPI DSDT table of the
Asus A7N8X lists two SMBuses, both of which are supported by this driver.
Documentation/i386/boot.txt
浏览文件 @ c4366889
......@@ -2,7 +2,7 @@
----------------------------
H. Peter Anvin <hpa@zytor.com>
Last update 2005-09-02
Last update 2006-11-17
On the i386 platform, the Linux kernel uses a rather complicated boot
convention. This has evolved partially due to historical aspects, as
......@@ -35,6 +35,8 @@ Protocol 2.03: (Kernel 2.4.18-pre1) Explicitly makes the highest possible
initrd address available to the bootloader.
Protocol 2.04: (Kernel 2.6.14) Extend the syssize field to four bytes.
Protocol 2.05: (Kernel 2.6.20) Make protected mode kernel relocatable.
Introduce relocatable_kernel and kernel_alignment fields.
**** MEMORY LAYOUT
......@@ -129,6 +131,8 @@ Offset Proto Name Meaning
0226/2 N/A pad1 Unused
0228/4 2.02+ cmd_line_ptr 32-bit pointer to the kernel command line
022C/4 2.03+ initrd_addr_max Highest legal initrd address
0230/4 2.05+ kernel_alignment Physical addr alignment required for kernel
0234/1 2.05+ relocatable_kernel Whether kernel is relocatable or not
(1) For backwards compatibility, if the setup_sects field contains 0, the
real value is 4.
......
Documentation/ide.txt
浏览文件 @ c4366889
......@@ -390,5 +390,5 @@ mlord@pobox.com
Wed Apr 17 22:52:44 CEST 2002 edited by Marcin Dalecki, the current
maintainer.
Wed Aug 20 22:31:29 CEST 2003 updated ide boot uptions to current ide.c
Wed Aug 20 22:31:29 CEST 2003 updated ide boot options to current ide.c
comments at 2.6.0-test4 time. Maciej Soltysiak <solt@dns.toxicfilms.tv>
Documentation/input/amijoy.txt
浏览文件 @ c4366889
......@@ -91,8 +91,8 @@ JOY1DAT Y7 Y6 Y5 Y4 Y3 Y2 Y1 Y0 X7 X6 X5 X4 X3 X2 X1 X0
| 1 | M0HQ | JOY0DAT Horizontal Clock (quadrature) |
| 2 | M0V | JOY0DAT Vertical Clock |
| 3 | M0VQ | JOY0DAT Vertical Clock (quadrature) |
| 4 | M1V | JOY1DAT Horizontall Clock |
| 5 | M1VQ | JOY1DAT Horizontall Clock (quadrature) |
| 4 | M1V | JOY1DAT Horizontal Clock |
| 5 | M1VQ | JOY1DAT Horizontal Clock (quadrature) |
| 6 | M1V | JOY1DAT Vertical Clock |
| 7 | M1VQ | JOY1DAT Vertical Clock (quadrature) |
+--------+----------+-----------------------------------------+
......
Documentation/input/atarikbd.txt
浏览文件 @ c4366889
......@@ -103,7 +103,7 @@ LEFT=0x74 & RIGHT=0x75).
5.1 Joystick Event Reporting
In this mode, the ikbd generates a record whever the joystick position is
In this mode, the ikbd generates a record whenever the joystick position is
changed (i.e. for each opening or closing of a joystick switch or trigger).
The joystick event record is two bytes of the form:
......@@ -277,8 +277,8 @@ default to 1 at RESET (or power-up).
9.7 SET MOUSE SCALE
0x0C
X ; horizontal mouse ticks per internel X
Y ; vertical mouse ticks per internel Y
X ; horizontal mouse ticks per internal X
Y ; vertical mouse ticks per internal Y
This command sets the scale factor for the ABSOLUTE MOUSE POSITIONING mode.
In this mode, the specified number of mouse phase changes ('clicks') must
......@@ -323,7 +323,7 @@ mouse position.
0x0F
This command makes the origin of the Y axis to be at the bottom of the
logical coordinate system internel to the ikbd for all relative or absolute
logical coordinate system internal to the ikbd for all relative or absolute
mouse motion. This causes mouse motion toward the user to be negative in sign
and away from the user to be positive.
......@@ -597,8 +597,8 @@ mode or FIRE BUTTON MONITORING mode.
10. SCAN CODES
The key scan codes return by the ikbd are chosen to simplify the
implementaion of GSX.
The key scan codes returned by the ikbd are chosen to simplify the
implementation of GSX.
GSX Standard Keyboard Mapping.
......
Documentation/input/xpad.txt
浏览文件 @ c4366889
......@@ -3,20 +3,37 @@ xpad - Linux USB driver for X-Box gamepads
This is the very first release of a driver for X-Box gamepads.
Basically, this was hacked away in just a few hours, so don't expect
miracles.
In particular, there is currently NO support for the rumble pack.
You won't find many ff-aware linux applications anyway.
0. Status
---------
0. Notes
--------
Driver updated for kernel 2.6.17.11. (Based on a patch for 2.6.11.4.)
For now, this driver has only been tested on just one Linux-Box.
This one is running a 2.4.18 kernel with usb-uhci on an amd athlon 600.
The number of buttons/axes reported varies based on 3 things:
- if you are using a known controller
- if you are using a known dance pad
- if using an unknown device (one not listed below), what you set in the
module configuration for "Map D-PAD to buttons rather than axes for unknown
pads" (module option dpad_to_buttons)
The jstest-program from joystick-1.2.15 (jstest-version 2.1.0) reports
8 axes and 10 buttons.
If you set dpad_to_buttons to 0 and you are using an unknown device (one
not listed below), the driver will map the directional pad to axes (X/Y),
if you said N it will map the d-pad to buttons, which is needed for dance
style games to function correctly. The default is Y.
dpad_to_buttons has no effect for known pads.
0.1 Normal Controllers
----------------------
With a normal controller, the directional pad is mapped to its own X/Y axes.
The jstest-program from joystick-1.2.15 (jstest-version 2.1.0) will report 8
axes and 10 buttons.
Alls 8 axes work, though they all have the same range (-32768..32767)
All 8 axes work, though they all have the same range (-32768..32767)
and the zero-setting is not correct for the triggers (I don't know if that
is some limitation of jstest, since the input device setup should be fine. I
didn't have a look at jstest itself yet).
......@@ -30,16 +47,50 @@ in game functionality were OK. However, I find it rather difficult to
play first person shooters with a pad. Your mileage may vary.
0.2 Xbox Dance Pads
-------------------
When using a known dance pad, jstest will report 6 axes and 14 buttons.
For dance style pads (like the redoctane pad) several changes
have been made. The old driver would map the d-pad to axes, resulting
in the driver being unable to report when the user was pressing both
left+right or up+down, making DDR style games unplayable.
Known dance pads automatically map the d-pad to buttons and will work
correctly out of the box.
If your dance pad is recognized by the driver but is using axes instead
of buttons, see section 0.3 - Unknown Controllers
I've tested this with Stepmania, and it works quite well.
0.3 Unkown Controllers
----------------------
If you have an unkown xbox controller, it should work just fine with
the default settings.
HOWEVER if you have an unknown dance pad not listed below, it will not
work UNLESS you set "dpad_to_buttons" to 1 in the module configuration.
PLEASE if you have an unkown controller, email Dom <binary1230@yahoo.com> with
a dump from /proc/bus/usb and a description of the pad (manufacturer, country,
whether it is a dance pad or normal controller) so that we can add your pad
to the list of supported devices, ensuring that it will work out of the
box in the future.
1. USB adapter
--------------
Before you can actually use the driver, you need to get yourself an
adapter cable to connect the X-Box controller to your Linux-Box.
adapter cable to connect the X-Box controller to your Linux-Box. You
can buy these online fairly cheap, or build your own.
Such a cable is pretty easy to build. The Controller itself is a USB compound
device (a hub with three ports for two expansion slots and the controller
device) with the only difference in a nonstandard connector (5 pins vs. 4 on
standard USB connector).
Such a cable is pretty easy to build. The Controller itself is a USB
compound device (a hub with three ports for two expansion slots and
the controller device) with the only difference in a nonstandard connector
(5 pins vs. 4 on standard USB connector).
You just need to solder a USB connector onto the cable and keep the
yellow wire unconnected. The other pins have the same order on both
......@@ -51,36 +102,36 @@ original one. You can buy an extension cable and cut that instead. That way,
you can still use the controller with your X-Box, if you have one ;)
2. driver installation
2. Driver Installation
----------------------
Once you have the adapter cable and the controller is connected, you need
to load your USB subsystem and should cat /proc/bus/usb/devices.
There should be an entry like the one at the end [4].
Currently (as of version 0.0.4), the following three devices are included:
Currently (as of version 0.0.6), the following devices are included:
original Microsoft XBOX controller (US), vendor=0x045e, product=0x0202
smaller Microsoft XBOX controller (US), vendor=0x045e, product=0x0289
original Microsoft XBOX controller (Japan), vendor=0x045e, product=0x0285
InterAct PowerPad Pro (Germany), vendor=0x05fd, product=0x107a
RedOctane Xbox Dance Pad (US), vendor=0x0c12, product=0x8809
If you have another controller that is not listed above and is not recognized
by the driver, please drop me a line with the appropriate info (that is, include
the name, vendor and product ID, as well as the country where you bought it;
sending the whole dump out of /proc/bus/usb/devices along would be even better).
The driver should work with xbox pads not listed above as well, however
you will need to do something extra for dance pads to work.
In theory, the driver should work with other controllers than mine
(InterAct PowerPad pro, bought in Germany) just fine, but I cannot test this
for I only have this one controller.
If you have a controller not listed above, see 0.3 - Unknown Controllers
If you compiled and installed the driver, test the functionality:
> modprobe xpad
> modprobe joydev
> jstest /dev/js0
There should be a single line showing 18 inputs (8 axes, 10 buttons), and
it's values should change if you move the sticks and push the buttons.
If you're using a normal controller, there should be a single line showing
18 inputs (8 axes, 10 buttons), and its values should change if you move
the sticks and push the buttons. If you're using a dance pad, it should
show 20 inputs (6 axes, 14 buttons).
It works? Voila, your done ;)
It works? Voila, you're done ;)
3. Thanks
......@@ -111,6 +162,22 @@ I: If#= 0 Alt= 0 #EPs= 2 Cls=58(unk. ) Sub=42 Prot=00 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl= 10ms
E: Ad=02(O) Atr=03(Int.) MxPS= 32 Ivl= 10ms
5. /proc/bus/usb/devices - dump from Redoctane Xbox Dance Pad (US):
T: Bus=01 Lev=02 Prnt=09 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0c12 ProdID=8809 Rev= 0.01
S: Product=XBOX DDR
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=58(unk. ) Sub=42 Prot=00 Driver=xpad
E: Ad=82(I) Atr=03(Int.) MxPS= 32 Ivl=4ms
E: Ad=02(O) Atr=03(Int.) MxPS= 32 Ivl=4ms
--
Marko Friedemann <mfr@bmx-chemnitz.de>
2002-07-16
- original doc
Dominic Cerquetti <binary1230@yahoo.com>
2005-03-19
- added stuff for dance pads, new d-pad->axes mappings
Documentation/input/yealink.txt
浏览文件 @ c4366889
......@@ -134,7 +134,7 @@ Reading /sys/../lineX will return the format string with its current value:
888888888888
Linux Rocks!
Writing to /sys/../lineX will set the coresponding LCD line.
Writing to /sys/../lineX will set the corresponding LCD line.
- Excess characters are ignored.
- If less characters are written than allowed, the remaining digits are
unchanged.
......
Documentation/ioctl-number.txt
浏览文件 @ c4366889
......@@ -191,3 +191,5 @@ Code Seq# Include File Comments
<mailto:aherrman@de.ibm.com>
0xF3 00-3F video/sisfb.h sisfb (in development)
<mailto:thomas@winischhofer.net>
0xF4 00-1F video/mbxfb.h mbxfb
<mailto:raph@8d.com>
Documentation/ioctl/cdrom.txt
浏览文件 @ c4366889
......@@ -735,7 +735,7 @@ CDROM_DISC_STATUS Get disc type, etc.
Ok, this is where problems start. The current interface for
the CDROM_DISC_STATUS ioctl is flawed. It makes the false
assumption that CDs are all CDS_DATA_1 or all CDS_AUDIO, etc.
Unfortunatly, while this is often the case, it is also
Unfortunately, while this is often the case, it is also
very common for CDs to have some tracks with data, and some
tracks with audio. Just because I feel like it, I declare
the following to be the best way to cope. If the CD has
......
Documentation/ioctl/ioctl-decoding.txt 0 → 100644
浏览文件 @ c4366889
To decode a hex IOCTL code:
Most architecures use this generic format, but check
include/ARCH/ioctl.h for specifics, e.g. powerpc
uses 3 bits to encode read/write and 13 bits for size.
bits meaning
31-30 00 - no parameters: uses _IO macro
10 - read: _IOR
01 - write: _IOW
11 - read/write: _IOWR
29-16 size of arguments
15-8 ascii character supposedly
unique to each driver
7-0 function #
So for example 0x82187201 is a read with arg length of 0x218,
character 'r' function 1. Grepping the source reveals this is:
#define VFAT_IOCTL_READDIR_BOTH _IOR('r', 1, struct dirent [2])
Documentation/kbuild/makefiles.txt
浏览文件 @ c4366889
......@@ -227,9 +227,9 @@ more details, with real examples.
be included in a library, lib.a.
All objects listed with lib-y are combined in a single
library for that directory.
Objects that are listed in obj-y and additionaly listed in
lib-y will not be included in the library, since they will anyway
be accessible.
Objects that are listed in obj-y and additionally listed in
lib-y will not be included in the library, since they will
be accessible anyway.
For consistency, objects listed in lib-m will be included in lib.a.
Note that the same kbuild makefile may list files to be built-in
......@@ -535,7 +535,7 @@ Both possibilities are described in the following.
Host programs can be made up based on composite objects.
The syntax used to define composite objects for host programs is
similar to the syntax used for kernel objects.
$(<executeable>-objs) lists all objects used to link the final
$(<executable>-objs) lists all objects used to link the final
executable.
Example:
......@@ -1022,7 +1022,7 @@ When kbuild executes, the following steps are followed (roughly):
In this example, there are two possible targets, requiring different
options to the linker. The linker options are specified using the
LDFLAGS_$@ syntax - one for each potential target.
$(targets) are assinged all potential targets, by which kbuild knows
$(targets) are assigned all potential targets, by which kbuild knows
the targets and will:
1) check for commandline changes
2) delete target during make clean
......
Documentation/kernel-doc-nano-HOWTO.txt
浏览文件 @ c4366889
......@@ -17,7 +17,7 @@ are:
special place-holders for where the extracted documentation should
go.
- scripts/docproc.c
- scripts/basic/docproc.c
This is a program for converting SGML template files into SGML
files. When a file is referenced it is searched for symbols
......
Documentation/kernel-parameters.txt
浏览文件 @ c4366889
......@@ -164,6 +164,10 @@ and is between 256 and 4096 characters. It is defined in the file
acpi_skip_timer_override [HW,ACPI]
Recognize and ignore IRQ0/pin2 Interrupt Override.
For broken nForce2 BIOS resulting in XT-PIC timer.
acpi_use_timer_override [HW,ACPI}
Use timer override. For some broken Nvidia NF5 boards
that require a timer override, but don't have
HPET
acpi_dbg_layer= [HW,ACPI]
Format: <int>
......@@ -544,6 +548,13 @@ and is between 256 and 4096 characters. It is defined in the file
eurwdt= [HW,WDT] Eurotech CPU-1220/1410 onboard watchdog.
Format: <io>[,<irq>]
failslab=
fail_page_alloc=
fail_make_request=[KNL]
General fault injection mechanism.
Format: <interval>,<probability>,<space>,<times>
See also /Documentation/fault-injection/.
fd_mcs= [HW,SCSI]
See header of drivers/scsi/fd_mcs.c.
......@@ -553,9 +564,6 @@ and is between 256 and 4096 characters. It is defined in the file
floppy= [HW]
See Documentation/floppy.txt.
ftape= [HW] Floppy Tape subsystem debugging options.
See Documentation/ftape.txt.
gamecon.map[2|3]=
[HW,JOY] Multisystem joystick and NES/SNES/PSX pad
support via parallel port (up to 5 devices per port)
......@@ -598,8 +606,6 @@ and is between 256 and 4096 characters. It is defined in the file
hugepages= [HW,IA-32,IA-64] Maximal number of HugeTLB pages.
noirqbalance [IA-32,SMP,KNL] Disable kernel irq balancing
i8042.direct [HW] Put keyboard port into non-translated mode
i8042.dumbkbd [HW] Pretend that controller can only read data from
keyboard and cannot control its state
......@@ -649,6 +655,10 @@ and is between 256 and 4096 characters. It is defined in the file
idle= [HW]
Format: idle=poll or idle=halt
ignore_loglevel [KNL]
Ignore loglevel setting - this will print /all/
kernel messages to the console. Useful for debugging.
ihash_entries= [KNL]
Set number of hash buckets for inode cache.
......@@ -713,7 +723,12 @@ and is between 256 and 4096 characters. It is defined in the file
Format: <RDP>,<reset>,<pci_scan>,<verbosity>
isolcpus= [KNL,SMP] Isolate CPUs from the general scheduler.
Format: <cpu number>,...,<cpu number>
Format:
<cpu number>,...,<cpu number>
or
<cpu number>-<cpu number> (must be a positive range in ascending order)
or a mixture
<cpu number>,...,<cpu number>-<cpu number>
This option can be used to specify one or more CPUs
to isolate from the general SMP balancing and scheduling
algorithms. The only way to move a process onto or off
......@@ -1011,6 +1026,10 @@ and is between 256 and 4096 characters. It is defined in the file
emulation library even if a 387 maths coprocessor
is present.
noaliencache [MM, NUMA] Disables the allcoation of alien caches in
the slab allocator. Saves per-node memory, but will
impact performance on real NUMA hardware.
noalign [KNL,ARM]
noapic [SMP,APIC] Tells the kernel to not make use of any
......@@ -1051,9 +1070,14 @@ and is between 256 and 4096 characters. It is defined in the file
in certain environments such as networked servers or
real-time systems.
noirqbalance [IA-32,SMP,KNL] Disable kernel irq balancing
noirqdebug [IA-32] Disables the code which attempts to detect and
disable unhandled interrupt sources.
no_timer_check [IA-32,X86_64,APIC] Disables the code which tests for
broken timer IRQ sources.
noisapnp [ISAPNP] Disables ISA PnP code.
noinitrd [RAM] Tells the kernel not to load any configured
......@@ -1231,6 +1255,11 @@ and is between 256 and 4096 characters. It is defined in the file
machine check when some devices' config space
is read. But various workarounds are disabled
and some IOMMU drivers will not work.
bfsort Sort PCI devices into breadth-first order.
This sorting is done to get a device
order compatible with older (<= 2.4) kernels.
nobfsort Don't sort PCI devices into breadth-first order.
pcmv= [HW,PCMCIA] BadgePAD 4
pd. [PARIDE]
......@@ -1279,6 +1308,7 @@ and is between 256 and 4096 characters. It is defined in the file
Param: "schedule" - profile schedule points.
Param: <number> - step/bucket size as a power of 2 for
statistical time based profiling.
Param: "sleep" - profile D-state sleeping (millisecs)
processor.max_cstate= [HW,ACPI]
Limit processor to maximum C-state
......@@ -1360,6 +1390,12 @@ and is between 256 and 4096 characters. It is defined in the file
resume= [SWSUSP]
Specify the partition device for software suspend
resume_offset= [SWSUSP]
Specify the offset from the beginning of the partition
given by "resume=" at which the swap header is located,
in <PAGE_SIZE> units (needed only for swap files).
See Documentation/power/swsusp-and-swap-files.txt
rhash_entries= [KNL,NET]
Set number of hash buckets for route cache
......@@ -1410,6 +1446,11 @@ and is between 256 and 4096 characters. It is defined in the file
scsi_logging= [SCSI]
scsi_mod.scan= [SCSI] sync (default) scans SCSI busses as they are
discovered. async scans them in kernel threads,
allowing boot to proceed. none ignores them, expecting
user space to do the scan.
selinux [SELINUX] Disable or enable SELinux at boot time.
Format: { "0" | "1" }
See security/selinux/Kconfig help text.
......@@ -1721,6 +1762,9 @@ and is between 256 and 4096 characters. It is defined in the file
norandmaps Don't use address space randomization
Equivalent to echo 0 > /proc/sys/kernel/randomize_va_space
unwind_debug=N N > 0 will enable dwarf2 unwinder debugging
This is useful to get more information why
you got a "dwarf2 unwinder stuck"
______________________________________________________________________
......
Documentation/keys.txt
浏览文件 @ c4366889
......@@ -304,7 +304,7 @@ about the status of the key service:
R Revoked
D Dead
Q Contributes to user's quota
U Under contruction by callback to userspace
U Under construction by callback to userspace
N Negative key
This file must be enabled at kernel configuration time as it allows anyone
......
Documentation/kprobes.txt
浏览文件 @ c4366889
......@@ -442,9 +442,10 @@ static int __init kprobe_init(void)
kp.fault_handler = handler_fault;
kp.symbol_name = "do_fork";
if ((ret = register_kprobe(&kp) < 0)) {
ret = register_kprobe(&kp);
if (ret < 0) {
printk("register_kprobe failed, returned %d\n", ret);
return -1;
return ret;
}
printk("kprobe registered\n");
return 0;
......
Documentation/laptop-mode.txt
浏览文件 @ c4366889
......@@ -121,7 +121,7 @@ contains the following options:
MAX_AGE:
Maximum time, in seconds, of hard drive spindown time that you are
confortable with. Worst case, it's possible that you could lose this
comfortable with. Worst case, it's possible that you could lose this
amount of work if your battery fails while you're in laptop mode.
MINIMUM_BATTERY_MINUTES:
......@@ -235,7 +235,7 @@ It should be installed as /etc/default/laptop-mode on Debian, and as
--------------------CONFIG FILE BEGIN-------------------------------------------
# Maximum time, in seconds, of hard drive spindown time that you are
# confortable with. Worst case, it's possible that you could lose this
# comfortable with. Worst case, it's possible that you could lose this
# amount of work if your battery fails you while in laptop mode.
#MAX_AGE=600
......@@ -350,7 +350,7 @@ fi
# set defaults instead:
# Maximum time, in seconds, of hard drive spindown time that you are
# confortable with. Worst case, it's possible that you could lose this
# comfortable with. Worst case, it's possible that you could lose this
# amount of work if your battery fails you while in laptop mode.
MAX_AGE=${MAX_AGE:-'600'}
......@@ -699,7 +699,7 @@ ACPI integration
Dax Kelson submitted this so that the ACPI acpid daemon will
kick off the laptop_mode script and run hdparm. The part that
automatically disables laptop mode when the battery is low was
writen by Jan Topinski.
written by Jan Topinski.
-----------------/etc/acpi/events/ac_adapter BEGIN------------------------------
event=ac_adapter
......
Documentation/memory-barriers.txt
浏览文件 @ c4366889
......@@ -212,7 +212,7 @@ There are some minimal guarantees that may be expected of a CPU:
STORE *X = c, d = LOAD *X
(Loads and stores overlap if they are targetted at overlapping pieces of
(Loads and stores overlap if they are targeted at overlapping pieces of
memory).
And there are a number of things that _must_ or _must_not_ be assumed:
......@@ -1016,7 +1016,7 @@ There are some more advanced barrier functions:
(*) set_mb(var, value)
This assigns the value to the variable and then inserts at least a write
This assigns the value to the variable and then inserts a full memory
barrier after it, depending on the function. It isn't guaranteed to
insert anything more than a compiler barrier in a UP compilation.
......@@ -1898,7 +1898,7 @@ queue before processing any further requests:
smp_wmb();
<A:modify v=2> <C:busy>
<C:queue v=2>
p = &b; q = p;
p = &v; q = p;
<D:request p>
<B:modify p=&v> <D:commit p=&v>
<D:read p>
......
Documentation/mips/time.README
浏览文件 @ c4366889
......@@ -38,19 +38,14 @@ The new time code provide the following services:
a) Implements functions required by Linux common code:
time_init
do_gettimeofday
do_settimeofday
b) provides an abstraction of RTC and null RTC implementation as default.
extern unsigned long (*rtc_get_time)(void);
extern int (*rtc_set_time)(unsigned long);
c) a set of gettimeoffset functions for different CPUs and different
needs.
d) high-level and low-level timer interrupt routines where the timer
interrupt source may or may not be the CPU timer. The high-level
routine is dispatched through do_IRQ() while the low-level is
c) high-level and low-level timer interrupt routines where the timer
interrupt source may or may not be the CPU timer. The high-level
routine is dispatched through do_IRQ() while the low-level is
dispatched in assemably code (usually int-handler.S)
......@@ -63,7 +58,7 @@ the following functions or values:
a) board_time_init - a function pointer. Invoked at the beginnig of
time_init(). It is optional.
1. (optional) set up RTC routines
2. (optional) calibrate and set the mips_counter_frequency
2. (optional) calibrate and set the mips_hpt_frequency
b) plat_timer_setup - a function pointer. Invoked at the end of time_init()
1. (optional) over-ride any decisions made in time_init()
......@@ -72,9 +67,8 @@ the following functions or values:
c) (optional) board-specific RTC routines.
d) (optional) mips_counter_frequency - It must be definied if the board
is using CPU counter for timer interrupt or it is using fixed rate
gettimeoffset().
d) (optional) mips_hpt_frequency - It must be definied if the board
is using CPU counter for timer interrupt.
PORTING GUIDE
......@@ -89,22 +83,12 @@ Step 1: decide how you like to implement the time services.
If the answer is no, you need a timer to provide the timer interrupt
at 100 HZ speed.
You cannot use the fast gettimeoffset functions, i.e.,
unsigned long fixed_rate_gettimeoffset(void);
unsigned long calibrate_div32_gettimeoffset(void);
unsigned long calibrate_div64_gettimeoffset(void);
You can use null_gettimeoffset() will gives the same time resolution as
jiffy. Or you can implement your own gettimeoffset (probably based on
some ad hoc hardware on your machine.)
c) The following sub steps assume your CPU has counter register.
Do you plan to use the CPU counter register as the timer interrupt
or use an exnternal timer?
In order to use CPU counter register as the timer interrupt source, you
must know the counter speed (mips_counter_frequency). It is usually the
must know the counter speed (mips_hpt_frequency). It is usually the
same as the CPU speed or an integral divisor of it.
d) decide on whether you want to use high-level or low-level timer
......@@ -121,10 +105,10 @@ Step 3: implement rtc routines, board_time_init() and plat_timer_setup()
if needed.
board_time_init() -
a) (optional) set up RTC routines,
b) (optional) calibrate and set the mips_counter_frequency
(only needed if you intended to use fixed_rate_gettimeoffset
or use cpu counter as timer interrupt source)
a) (optional) set up RTC routines,
b) (optional) calibrate and set the mips_hpt_frequency
(only needed if you intended to use cpu counter as timer interrupt
source)
plat_timer_setup() -
a) (optional) over-write any choices made above by time_init().
......@@ -154,8 +138,8 @@ for some of the functions in time.c.
For example, you may define your own timer interrupt routine, which does
some of its own processing and then calls timer_interrupt().
You can also over-ride any of the built-in functions (gettimeoffset,
RTC routines and/or timer interrupt routine).
You can also over-ride any of the built-in functions (RTC routines
and/or timer interrupt routine).
PORTING NOTES FOR SMP
......@@ -187,10 +171,3 @@ You need to decide on your timer interrupt sources.
You can also do the low-level version of those interrupt routines,
following similar dispatching routes described above.
Note about do_gettimeoffset():
It is very likely the CPU counter registers are not sync'ed up in a SMP box.
Therefore you cannot really use the many of the existing routines that
are based on CPU counter. You should wirte your own gettimeoffset rouinte
if you want intra-jiffy resolution.
Documentation/networking/00-INDEX
浏览文件 @ c4366889
......@@ -58,6 +58,8 @@ fore200e.txt
- FORE Systems PCA-200E/SBA-200E ATM NIC driver info.
framerelay.txt
- info on using Frame Relay/Data Link Connection Identifier (DLCI).
generic_netlink.txt
- info on Generic Netlink
ip-sysctl.txt
- /proc/sys/net/ipv4/* variables
ip_dynaddr.txt
......
Documentation/networking/NAPI_HOWTO.txt
浏览文件 @ c4366889
......@@ -95,8 +95,8 @@ There are two types of event register ACK mechanisms.
Move all to dev->poll()
C) Ability to detect new work correctly.
NAPI works by shutting down event interrupts when theres work and
turning them on when theres none.
NAPI works by shutting down event interrupts when there's work and
turning them on when there's none.
New packets might show up in the small window while interrupts were being
re-enabled (refer to appendix 2). A packet might sneak in during the period
we are enabling interrupts. We only get to know about such a packet when the
......@@ -114,7 +114,7 @@ Locking rules and environmental guarantees
only one CPU can pick the initial interrupt and hence the initial
netif_rx_schedule(dev);
- The core layer invokes devices to send packets in a round robin format.
This implies receive is totaly lockless because of the guarantee only that
This implies receive is totally lockless because of the guarantee that only
one CPU is executing it.
- contention can only be the result of some other CPU accessing the rx
ring. This happens only in close() and suspend() (when these methods
......@@ -510,7 +510,7 @@ static int my_poll (struct net_device *dev, int *budget)
an interrupt will be generated */
goto done;
}
/* done! at least thats what it looks like ;->
/* done! at least that's what it looks like ;->
if new packets came in after our last check on status bits
they'll be caught by the while check and we go back and clear them
since we havent exceeded our quota */
......@@ -535,11 +535,11 @@ done:
* 1. it can race with disabling irqs in irq handler (which are done to
* schedule polls)
* 2. it can race with dis/enabling irqs in other poll threads
* 3. if an irq raised after the begining of the outer beginning
* loop(marked in the code above), it will be immediately
* 3. if an irq raised after the beginning of the outer beginning
* loop (marked in the code above), it will be immediately
* triggered here.
*
* Summarizing: the logic may results in some redundant irqs both
* Summarizing: the logic may result in some redundant irqs both
* due to races in masking and due to too late acking of already
* processed irqs. The good news: no events are ever lost.
*/
......@@ -601,7 +601,7 @@ a)
5) dev->close() and dev->suspend() issues
==========================================
The driver writter neednt worry about this. The top net layer takes
The driver writer needn't worry about this; the top net layer takes
care of it.
6) Adding new Stats to /proc
......@@ -622,9 +622,9 @@ FC should be programmed to apply in the case when the system cant pull out
packets fast enough i.e send a pause only when you run out of rx buffers.
Note FC in itself is a good solution but we have found it to not be
much of a commodity feature (both in NICs and switches) and hence falls
under the same category as using NIC based mitigation. Also experiments
indicate that its much harder to resolve the resource allocation
issue (aka lazy receiving that NAPI offers) and hence quantify its usefullness
under the same category as using NIC based mitigation. Also, experiments
indicate that it's much harder to resolve the resource allocation
issue (aka lazy receiving that NAPI offers) and hence quantify its usefulness
proved harder. In any case, FC works even better with NAPI but is not
necessary.
......@@ -678,10 +678,10 @@ routine:
CSR5 bit of interest is only the rx status.
If you look at the last if statement:
you just finished grabbing all the packets from the rx ring .. you check if
status bit says theres more packets just in ... it says none; you then
status bit says there are more packets just in ... it says none; you then
enable rx interrupts again; if a new packet just came in during this check,
we are counting that CSR5 will be set in that small window of opportunity
and that by re-enabling interrupts, we would actually triger an interrupt
and that by re-enabling interrupts, we would actually trigger an interrupt
to register the new packet for processing.
[The above description nay be very verbose, if you have better wording
......
Documentation/networking/cs89x0.txt
浏览文件 @ c4366889
......@@ -248,7 +248,7 @@ c) The driver's hardware probe routine is designed to avoid
with device probing. To avoid this behaviour, add one
to the `io=' module parameter. This doesn't actually change
the I/O address, but it is a flag to tell the driver
topartially initialise the hardware before trying to
to partially initialise the hardware before trying to
identify the card. This could be dangerous if you are
not sure that there is a cs89x0 card at the provided address.
......@@ -620,8 +620,8 @@ I/O Address Device IRQ Device
12 Mouse (PS/2)
Memory Address Device 13 Math Coprocessor
-------------- --------------------- 14 Hard Disk controller
A000-BFFF EGA Graphics Adpater
A000-C7FF VGA Graphics Adpater
A000-BFFF EGA Graphics Adapter
A000-C7FF VGA Graphics Adapter
B000-BFFF Mono Graphics Adapter
B800-BFFF Color Graphics Adapter
E000-FFFF AT BIOS
......
Documentation/networking/dccp.txt
浏览文件 @ c4366889
......@@ -19,40 +19,92 @@ for real time and multimedia traffic.
It has a base protocol and pluggable congestion control IDs (CCIDs).
It is at draft RFC status and the homepage for DCCP as a protocol is at:
http://www.icir.org/kohler/dcp/
It is at proposed standard RFC status and the homepage for DCCP as a protocol
is at:
http://www.read.cs.ucla.edu/dccp/
Missing features
================
The DCCP implementation does not currently have all the features that are in
the draft RFC.
the RFC.
In particular the following are missing:
- CCID2 support
- feature negotiation
When testing against other implementations it appears that elapsed time
options are not coded compliant to the specification.
The known bugs are at:
http://linux-net.osdl.org/index.php/TODO#DCCP
Socket options
==============
DCCP_SOCKOPT_PACKET_SIZE is used for CCID3 to set default packet size for
calculations.
DCCP_SOCKOPT_SERVICE sets the service. The specification mandates use of
service codes (RFC 4340, sec. 8.1.2); if this socket option is not set,
the socket will fall back to 0 (which means that no meaningful service code
is present). Connecting sockets set at most one service option; for
listening sockets, multiple service codes can be specified.
DCCP_SOCKOPT_SEND_CSCOV and DCCP_SOCKOPT_RECV_CSCOV are used for setting the
partial checksum coverage (RFC 4340, sec. 9.2). The default is that checksums
always cover the entire packet and that only fully covered application data is
accepted by the receiver. Hence, when using this feature on the sender, it must
be enabled at the receiver, too with suitable choice of CsCov.
DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
range 0..15 are acceptable. The default setting is 0 (full coverage),
values between 1..15 indicate partial coverage.
DCCP_SOCKOPT_SEND_CSCOV is for the receiver and has a different meaning: it
sets a threshold, where again values 0..15 are acceptable. The default
of 0 means that all packets with a partial coverage will be discarded.
Values in the range 1..15 indicate that packets with minimally such a
coverage value are also acceptable. The higher the number, the more
restrictive this setting (see [RFC 4340, sec. 9.2.1]).
Sysctl variables
================
Several DCCP default parameters can be managed by the following sysctls
(sysctl net.dccp.default or /proc/sys/net/dccp/default):
request_retries
The number of active connection initiation retries (the number of
Requests minus one) before timing out. In addition, it also governs
the behaviour of the other, passive side: this variable also sets
the number of times DCCP repeats sending a Response when the initial
handshake does not progress from RESPOND to OPEN (i.e. when no Ack
is received after the initial Request). This value should be greater
than 0, suggested is less than 10. Analogue of tcp_syn_retries.
retries1
How often a DCCP Response is retransmitted until the listening DCCP
side considers its connecting peer dead. Analogue of tcp_retries1.
retries2
The number of times a general DCCP packet is retransmitted. This has
importance for retransmitted acknowledgments and feature negotiation,
data packets are never retransmitted. Analogue of tcp_retries2.
send_ndp = 1
Whether or not to send NDP count options (sec. 7.7.2).
send_ackvec = 1
Whether or not to send Ack Vector options (sec. 11.5).
ack_ratio = 2
The default Ack Ratio (sec. 11.3) to use.
tx_ccid = 2
Default CCID for the sender-receiver half-connection.
rx_ccid = 2
Default CCID for the receiver-sender half-connection.
seq_window = 100
The initial sequence window (sec. 7.5.2).
tx_qlen = 5
The size of the transmit buffer in packets. A value of 0 corresponds
to an unbounded transmit buffer.
Notes
=====
SELinux does not yet have support for DCCP. You will need to turn it off or
else you will get EACCES.
DCCP does not travel through NAT successfully at present. This is because
the checksum covers the psuedo-header as per TCP and UDP. It should be
relatively trivial to add Linux NAT support for DCCP.
DCCP does not travel through NAT successfully at present on many boxes. This is
because the checksum covers the psuedo-header as per TCP and UDP. Linux NAT
support for DCCP has been added.
Documentation/networking/e1000.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/networking/generic_netlink.txt 0 → 100644
浏览文件 @ c4366889
A wiki document on how to use Generic Netlink can be found here:
* http://linux-net.osdl.org/index.php/Generic_Netlink_HOWTO
Documentation/networking/ip-sysctl.txt
浏览文件 @ c4366889
......@@ -101,6 +101,11 @@ inet_peer_gc_maxtime - INTEGER
TCP variables:
somaxconn - INTEGER
Limit of socket listen() backlog, known in userspace as SOMAXCONN.
Defaults to 128. See also tcp_max_syn_backlog for additional tuning
for TCP sockets.
tcp_abc - INTEGER
Controls Appropriate Byte Count (ABC) defined in RFC3465.
ABC is a way of increasing congestion window (cwnd) more slowly
......@@ -112,48 +117,51 @@ tcp_abc - INTEGER
of two segments to compensate for delayed acknowledgments.
Default: 0 (off)
tcp_syn_retries - INTEGER
Number of times initial SYNs for an active TCP connection attempt
will be retransmitted. Should not be higher than 255. Default value
is 5, which corresponds to ~180seconds.
tcp_abort_on_overflow - BOOLEAN
If listening service is too slow to accept new connections,
reset them. Default state is FALSE. It means that if overflow
occurred due to a burst, connection will recover. Enable this
option _only_ if you are really sure that listening daemon
cannot be tuned to accept connections faster. Enabling this
option can harm clients of your server.
tcp_synack_retries - INTEGER
Number of times SYNACKs for a passive TCP connection attempt will
be retransmitted. Should not be higher than 255. Default value
is 5, which corresponds to ~180seconds.
tcp_adv_win_scale - INTEGER
Count buffering overhead as bytes/2^tcp_adv_win_scale
(if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
if it is <= 0.
Default: 2
tcp_keepalive_time - INTEGER
How often TCP sends out keepalive messages when keepalive is enabled.
Default: 2hours.
tcp_allowed_congestion_control - STRING
Show/set the congestion control choices available to non-privileged
processes. The list is a subset of those listed in
tcp_available_congestion_control.
Default is "reno" and the default setting (tcp_congestion_control).
tcp_keepalive_probes - INTEGER
How many keepalive probes TCP sends out, until it decides that the
connection is broken. Default value: 9.
tcp_app_win - INTEGER
Reserve max(window/2^tcp_app_win, mss) of window for application
buffer. Value 0 is special, it means that nothing is reserved.
Default: 31
tcp_keepalive_intvl - INTEGER
How frequently the probes are send out. Multiplied by
tcp_keepalive_probes it is time to kill not responding connection,
after probes started. Default value: 75sec i.e. connection
will be aborted after ~11 minutes of retries.
tcp_available_congestion_control - STRING
Shows the available congestion control choices that are registered.
More congestion control algorithms may be available as modules,
but not loaded.
tcp_retries1 - INTEGER
How many times to retry before deciding that something is wrong
and it is necessary to report this suspicion to network layer.
Minimal RFC value is 3, it is default, which corresponds
to ~3sec-8min depending on RTO.
tcp_congestion_control - STRING
Set the congestion control algorithm to be used for new
connections. The algorithm "reno" is always available, but
additional choices may be available based on kernel configuration.
Default is set as part of kernel configuration.
tcp_retries2 - INTEGER
How may times to retry before killing alive TCP connection.
RFC1122 says that the limit should be longer than 100 sec.
It is too small number. Default value 15 corresponds to ~13-30min
depending on RTO.
tcp_dsack - BOOLEAN
Allows TCP to send "duplicate" SACKs.
tcp_orphan_retries - INTEGER
How may times to retry before killing TCP connection, closed
by our side. Default value 7 corresponds to ~50sec-16min
depending on RTO. If you machine is loaded WEB server,
you should think about lowering this value, such sockets
may consume significant resources. Cf. tcp_max_orphans.
tcp_ecn - BOOLEAN
Enable Explicit Congestion Notification in TCP.
tcp_fack - BOOLEAN
Enable FACK congestion avoidance and fast retransmission.
The value is not used, if tcp_sack is not enabled.
tcp_fin_timeout - INTEGER
Time to hold socket in state FIN-WAIT-2, if it was closed
......@@ -166,24 +174,33 @@ tcp_fin_timeout - INTEGER
because they eat maximum 1.5K of memory, but they tend
to live longer. Cf. tcp_max_orphans.
tcp_max_tw_buckets - INTEGER
Maximal number of timewait sockets held by system simultaneously.
If this number is exceeded time-wait socket is immediately destroyed
and warning is printed. This limit exists only to prevent
simple DoS attacks, you _must_ not lower the limit artificially,
but rather increase it (probably, after increasing installed memory),
if network conditions require more than default value.
tcp_frto - BOOLEAN
Enables F-RTO, an enhanced recovery algorithm for TCP retransmission
timeouts. It is particularly beneficial in wireless environments
where packet loss is typically due to random radio interference
rather than intermediate router congestion.
tcp_tw_recycle - BOOLEAN
Enable fast recycling TIME-WAIT sockets. Default value is 0.
It should not be changed without advice/request of technical
experts.
tcp_keepalive_time - INTEGER
How often TCP sends out keepalive messages when keepalive is enabled.
Default: 2hours.
tcp_tw_reuse - BOOLEAN
Allow to reuse TIME-WAIT sockets for new connections when it is
safe from protocol viewpoint. Default value is 0.
It should not be changed without advice/request of technical
experts.
tcp_keepalive_probes - INTEGER
How many keepalive probes TCP sends out, until it decides that the
connection is broken. Default value: 9.
tcp_keepalive_intvl - INTEGER
How frequently the probes are send out. Multiplied by
tcp_keepalive_probes it is time to kill not responding connection,
after probes started. Default value: 75sec i.e. connection
will be aborted after ~11 minutes of retries.
tcp_low_latency - BOOLEAN
If set, the TCP stack makes decisions that prefer lower
latency as opposed to higher throughput. By default, this
option is not set meaning that higher throughput is preferred.
An example of an application where this default should be
changed would be a Beowulf compute cluster.
Default: 0
tcp_max_orphans - INTEGER
Maximal number of TCP sockets not attached to any user file handle,
......@@ -197,41 +214,6 @@ tcp_max_orphans - INTEGER
more aggressively. Let me to remind again: each orphan eats
up to ~64K of unswappable memory.
tcp_abort_on_overflow - BOOLEAN
If listening service is too slow to accept new connections,
reset them. Default state is FALSE. It means that if overflow
occurred due to a burst, connection will recover. Enable this
option _only_ if you are really sure that listening daemon
cannot be tuned to accept connections faster. Enabling this
option can harm clients of your server.
tcp_syncookies - BOOLEAN
Only valid when the kernel was compiled with CONFIG_SYNCOOKIES
Send out syncookies when the syn backlog queue of a socket
overflows. This is to prevent against the common 'syn flood attack'
Default: FALSE
Note, that syncookies is fallback facility.
It MUST NOT be used to help highly loaded servers to stand
against legal connection rate. If you see synflood warnings
in your logs, but investigation shows that they occur
because of overload with legal connections, you should tune
another parameters until this warning disappear.
See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
syncookies seriously violate TCP protocol, do not allow
to use TCP extensions, can result in serious degradation
of some services (f.e. SMTP relaying), visible not by you,
but your clients and relays, contacting you. While you see
synflood warnings in logs not being really flooded, your server
is seriously misconfigured.
tcp_stdurg - BOOLEAN
Use the Host requirements interpretation of the TCP urg pointer field.
Most hosts use the older BSD interpretation, so if you turn this on
Linux might not communicate correctly with them.
Default: FALSE
tcp_max_syn_backlog - INTEGER
Maximal number of remembered connection requests, which are
still did not receive an acknowledgment from connecting client.
......@@ -239,24 +221,34 @@ tcp_max_syn_backlog - INTEGER
and 128 for low memory machines. If server suffers of overload,
try to increase this number.
tcp_window_scaling - BOOLEAN
Enable window scaling as defined in RFC1323.
tcp_max_tw_buckets - INTEGER
Maximal number of timewait sockets held by system simultaneously.
If this number is exceeded time-wait socket is immediately destroyed
and warning is printed. This limit exists only to prevent
simple DoS attacks, you _must_ not lower the limit artificially,
but rather increase it (probably, after increasing installed memory),
if network conditions require more than default value.
tcp_timestamps - BOOLEAN
Enable timestamps as defined in RFC1323.
tcp_mem - vector of 3 INTEGERs: min, pressure, max
min: below this number of pages TCP is not bothered about its
memory appetite.
tcp_sack - BOOLEAN
Enable select acknowledgments (SACKS).
pressure: when amount of memory allocated by TCP exceeds this number
of pages, TCP moderates its memory consumption and enters memory
pressure mode, which is exited when memory consumption falls
under "min".
tcp_fack - BOOLEAN
Enable FACK congestion avoidance and fast retransmission.
The value is not used, if tcp_sack is not enabled.
max: number of pages allowed for queueing by all TCP sockets.
tcp_dsack - BOOLEAN
Allows TCP to send "duplicate" SACKs.
Defaults are calculated at boot time from amount of available
memory.
tcp_ecn - BOOLEAN
Enable Explicit Congestion Notification in TCP.
tcp_orphan_retries - INTEGER
How may times to retry before killing TCP connection, closed
by our side. Default value 7 corresponds to ~50sec-16min
depending on RTO. If you machine is loaded WEB server,
you should think about lowering this value, such sockets
may consume significant resources. Cf. tcp_max_orphans.
tcp_reordering - INTEGER
Maximal reordering of packets in a TCP stream.
......@@ -267,20 +259,23 @@ tcp_retrans_collapse - BOOLEAN
On retransmit try to send bigger packets to work around bugs in
certain TCP stacks.
tcp_wmem - vector of 3 INTEGERs: min, default, max
min: Amount of memory reserved for send buffers for TCP socket.
Each TCP socket has rights to use it due to fact of its birth.
Default: 4K
tcp_retries1 - INTEGER
How many times to retry before deciding that something is wrong
and it is necessary to report this suspicion to network layer.
Minimal RFC value is 3, it is default, which corresponds
to ~3sec-8min depending on RTO.
default: Amount of memory allowed for send buffers for TCP socket
by default. This value overrides net.core.wmem_default used
by other protocols, it is usually lower than net.core.wmem_default.
Default: 16K
tcp_retries2 - INTEGER
How may times to retry before killing alive TCP connection.
RFC1122 says that the limit should be longer than 100 sec.
It is too small number. Default value 15 corresponds to ~13-30min
depending on RTO.
max: Maximal amount of memory allowed for automatically selected
send buffers for TCP socket. This value does not override
net.core.wmem_max, "static" selection via SO_SNDBUF does not use this.
Default: 128K
tcp_rfc1337 - BOOLEAN
If set, the TCP stack behaves conforming to RFC1337. If unset,
we are not conforming to RFC, but prevent TCP TIME_WAIT
assassination.
Default: 0
tcp_rmem - vector of 3 INTEGERs: min, default, max
min: Minimal size of receive buffer used by TCP sockets.
......@@ -299,67 +294,91 @@ tcp_rmem - vector of 3 INTEGERs: min, default, max
net.core.rmem_max, "static" selection via SO_RCVBUF does not use this.
Default: 87380*2 bytes.
tcp_mem - vector of 3 INTEGERs: min, pressure, max
min: below this number of pages TCP is not bothered about its
memory appetite.
tcp_sack - BOOLEAN
Enable select acknowledgments (SACKS).
pressure: when amount of memory allocated by TCP exceeds this number
of pages, TCP moderates its memory consumption and enters memory
pressure mode, which is exited when memory consumption falls
under "min".
tcp_slow_start_after_idle - BOOLEAN
If set, provide RFC2861 behavior and time out the congestion
window after an idle period. An idle period is defined at
the current RTO. If unset, the congestion window will not
be timed out after an idle period.
Default: 1
max: number of pages allowed for queueing by all TCP sockets.
tcp_stdurg - BOOLEAN
Use the Host requirements interpretation of the TCP urg pointer field.
Most hosts use the older BSD interpretation, so if you turn this on
Linux might not communicate correctly with them.
Default: FALSE
Defaults are calculated at boot time from amount of available
memory.
tcp_synack_retries - INTEGER
Number of times SYNACKs for a passive TCP connection attempt will
be retransmitted. Should not be higher than 255. Default value
is 5, which corresponds to ~180seconds.
tcp_app_win - INTEGER
Reserve max(window/2^tcp_app_win, mss) of window for application
buffer. Value 0 is special, it means that nothing is reserved.
Default: 31
tcp_syncookies - BOOLEAN
Only valid when the kernel was compiled with CONFIG_SYNCOOKIES
Send out syncookies when the syn backlog queue of a socket
overflows. This is to prevent against the common 'syn flood attack'
Default: FALSE
tcp_adv_win_scale - INTEGER
Count buffering overhead as bytes/2^tcp_adv_win_scale
(if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
if it is <= 0.
Default: 2
Note, that syncookies is fallback facility.
It MUST NOT be used to help highly loaded servers to stand
against legal connection rate. If you see synflood warnings
in your logs, but investigation shows that they occur
because of overload with legal connections, you should tune
another parameters until this warning disappear.
See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
tcp_rfc1337 - BOOLEAN
If set, the TCP stack behaves conforming to RFC1337. If unset,
we are not conforming to RFC, but prevent TCP TIME_WAIT
assassination.
Default: 0
syncookies seriously violate TCP protocol, do not allow
to use TCP extensions, can result in serious degradation
of some services (f.e. SMTP relaying), visible not by you,
but your clients and relays, contacting you. While you see
synflood warnings in logs not being really flooded, your server
is seriously misconfigured.
tcp_low_latency - BOOLEAN
If set, the TCP stack makes decisions that prefer lower
latency as opposed to higher throughput. By default, this
option is not set meaning that higher throughput is preferred.
An example of an application where this default should be
changed would be a Beowulf compute cluster.
Default: 0
tcp_syn_retries - INTEGER
Number of times initial SYNs for an active TCP connection attempt
will be retransmitted. Should not be higher than 255. Default value
is 5, which corresponds to ~180seconds.
tcp_timestamps - BOOLEAN
Enable timestamps as defined in RFC1323.
tcp_tso_win_divisor - INTEGER
This allows control over what percentage of the congestion window
can be consumed by a single TSO frame.
The setting of this parameter is a choice between burstiness and
building larger TSO frames.
Default: 3
This allows control over what percentage of the congestion window
can be consumed by a single TSO frame.
The setting of this parameter is a choice between burstiness and
building larger TSO frames.
Default: 3
tcp_frto - BOOLEAN
Enables F-RTO, an enhanced recovery algorithm for TCP retransmission
timeouts. It is particularly beneficial in wireless environments
where packet loss is typically due to random radio interference
rather than intermediate router congestion.
tcp_tw_recycle - BOOLEAN
Enable fast recycling TIME-WAIT sockets. Default value is 0.
It should not be changed without advice/request of technical
experts.
tcp_congestion_control - STRING
Set the congestion control algorithm to be used for new
connections. The algorithm "reno" is always available, but
additional choices may be available based on kernel configuration.
tcp_tw_reuse - BOOLEAN
Allow to reuse TIME-WAIT sockets for new connections when it is
safe from protocol viewpoint. Default value is 0.
It should not be changed without advice/request of technical
experts.
somaxconn - INTEGER
Limit of socket listen() backlog, known in userspace as SOMAXCONN.
Defaults to 128. See also tcp_max_syn_backlog for additional tuning
for TCP sockets.
tcp_window_scaling - BOOLEAN
Enable window scaling as defined in RFC1323.
tcp_wmem - vector of 3 INTEGERs: min, default, max
min: Amount of memory reserved for send buffers for TCP socket.
Each TCP socket has rights to use it due to fact of its birth.
Default: 4K
default: Amount of memory allowed for send buffers for TCP socket
by default. This value overrides net.core.wmem_default used
by other protocols, it is usually lower than net.core.wmem_default.
Default: 16K
max: Maximal amount of memory allowed for automatically selected
send buffers for TCP socket. This value does not override
net.core.wmem_max, "static" selection via SO_SNDBUF does not use this.
Default: 128K
tcp_workaround_signed_windows - BOOLEAN
If set, assume no receipt of a window scaling option means the
......@@ -368,13 +387,6 @@ tcp_workaround_signed_windows - BOOLEAN
not receive a window scaling option from them.
Default: 0
tcp_slow_start_after_idle - BOOLEAN
If set, provide RFC2861 behavior and time out the congestion
window after an idle period. An idle period is defined at
the current RTO. If unset, the congestion window will not
be timed out after an idle period.
Default: 1
CIPSOv4 Variables:
cipso_cache_enable - BOOLEAN
......@@ -974,4 +986,3 @@ no_cong_thresh FIXME
slot_timeout FIXME
warn_noreply_time FIXME
$Id: ip-sysctl.txt,v 1.20 2001/12/13 09:00:18 davem Exp $
Documentation/networking/iphase.txt
浏览文件 @ c4366889
......@@ -81,7 +81,7 @@ Installation
1M. The RAM size decides the number of buffers and buffer size. The default
size and number of buffers are set as following:
Totol Rx RAM Tx RAM Rx Buf Tx Buf Rx buf Tx buf
Total Rx RAM Tx RAM Rx Buf Tx Buf Rx buf Tx buf
RAM size size size size size cnt cnt
-------- ------ ------ ------ ------ ------ ------
128K 64K 64K 10K 10K 6 6
......
Documentation/networking/packet_mmap.txt
浏览文件 @ c4366889
......@@ -284,7 +284,7 @@ the necessary memory, so normally limits can be reached.
-------------------
If you check the source code you will see that what I draw here as a frame
is not only the link level frame. At the begining of each frame there is a
is not only the link level frame. At the beginning of each frame there is a
header called struct tpacket_hdr used in PACKET_MMAP to hold link level's frame
meta information like timestamp. So what we draw here a frame it's really
the following (from include/linux/if_packet.h):
......
Documentation/networking/phy.txt
浏览文件 @ c4366889
-------
PHY Abstraction Layer
(Updated 2005-07-21)
(Updated 2006-11-30)
Purpose
......@@ -97,11 +97,12 @@ Letting the PHY Abstraction Layer do Everything
Next, you need to know the device name of the PHY connected to this device.
The name will look something like, "phy0:0", where the first number is the
bus id, and the second is the PHY's address on that bus.
bus id, and the second is the PHY's address on that bus. Typically,
the bus is responsible for making its ID unique.
Now, to connect, just call this function:
phydev = phy_connect(dev, phy_name, &adjust_link, flags);
phydev = phy_connect(dev, phy_name, &adjust_link, flags, interface);
phydev is a pointer to the phy_device structure which represents the PHY. If
phy_connect is successful, it will return the pointer. dev, here, is the
......@@ -115,6 +116,10 @@ Letting the PHY Abstraction Layer do Everything
This is useful if the system has put hardware restrictions on
the PHY/controller, of which the PHY needs to be aware.
interface is a u32 which specifies the connection type used
between the controller and the PHY. Examples are GMII, MII,
RGMII, and SGMII. For a full list, see include/linux/phy.h
Now just make sure that phydev->supported and phydev->advertising have any
values pruned from them which don't make sense for your controller (a 10/100
controller may be connected to a gigabit capable PHY, so you would need to
......@@ -191,7 +196,7 @@ Doing it all yourself
start, or disables then frees them for stop.
struct phy_device * phy_attach(struct net_device *dev, const char *phy_id,
u32 flags);
u32 flags, phy_interface_t interface);
Attaches a network device to a particular PHY, binding the PHY to a generic
driver if none was found during bus initialization. Passes in
......
Documentation/networking/pktgen.txt
浏览文件 @ c4366889
......@@ -63,8 +63,8 @@ Current:
Result: OK: 13101142(c12220741+d880401) usec, 10000000 (60byte,0frags)
763292pps 390Mb/sec (390805504bps) errors: 39664
Confguring threads and devices
==============================
Configuring threads and devices
================================
This is done via the /proc interface easiest done via pgset in the scripts
Examples:
......@@ -116,7 +116,7 @@ Examples:
there must be no spaces between the
arguments. Leading zeros are required.
Do not set the bottom of stack bit,
thats done automatically. If you do
that's done automatically. If you do
set the bottom of stack bit, that
indicates that you want to randomly
generate that address and the flag
......
Documentation/networking/proc_net_tcp.txt
浏览文件 @ c4366889
......@@ -25,7 +25,7 @@ up into 3 parts because of the length of the line):
1000 0 54165785 4 cd1e6040 25 4 27 3 -1
| | | | | | | | | |--> slow start size threshold,
| | | | | | | | | or -1 if the treshold
| | | | | | | | | or -1 if the threshold
| | | | | | | | | is >= 0xFFFF
| | | | | | | | |----> sending congestion window
| | | | | | | |-------> (ack.quick<<1)|ack.pingpong
......
Documentation/networking/sk98lin.txt
浏览文件 @ c4366889
......@@ -346,7 +346,7 @@ Possible modes:
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 utilizaton decreases again (or if the network load is
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
......
Documentation/networking/slicecom.txt
浏览文件 @ c4366889
......@@ -126,7 +126,7 @@ comx0/boardnum - board number of the SliceCom in the PC (using the 'natural'
Though the options below are to be set on a single interface, they apply to the
whole board. The restriction, to use them on 'UP' interfaces, is because the
command sequence below could lead to unpredicable results.
command sequence below could lead to unpredictable results.
# echo 0 >boardnum
# echo internal >clock_source
......
Documentation/networking/udplite.txt 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
Documentation/pnp.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/power/interface.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/power/pci.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/power/s2ram.txt 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
Documentation/power/states.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/power/swsusp-and-swap-files.txt 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
Documentation/power/swsusp.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/powerpc/mpc52xx-device-tree-bindings.txt 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
Documentation/robust-futex-ABI.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/robust-futexes.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/rtc.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/s390/CommonIO
浏览文件 @ c4366889
此差异已折叠。
Documentation/s390/Debugging390.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/s390/cds.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/s390/driver-model.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/s390/s390dbf.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/aic79xx.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/aic7xxx_old.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/ibmmca.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/in2000.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/libsas.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/ncr53c8xx.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/scsi-changer.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/scsi_eh.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/st.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/scsi/sym53c8xx_2.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/sharedsubtree.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/spi/pxa2xx
浏览文件 @ c4366889
此差异已折叠。
Documentation/sysctl/fs.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/usb/hiddev.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/usb/rio.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/usb/usb-serial.txt
浏览文件 @ c4366889
此差异已折叠。
Documentation/video4linux/cafe_ccic 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
Documentation/video4linux/zr36120.txt 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
MAINTAINERS
浏览文件 @ c4366889
此差异已折叠。
Makefile
浏览文件 @ c4366889
此差异已折叠。
README
浏览文件 @ c4366889
此差异已折叠。
REPORTING-BUGS
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/kernel/pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/kernel/srm_env.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/kernel/sys_miata.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/kernel/sys_nautilus.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/lib/csum_partial_copy.c
浏览文件 @ c4366889
此差异已折叠。
arch/alpha/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ c4366889
此差异已折叠。
arch/arm/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/arm/common/dmabounce.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/common/gic.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/common/locomo.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/common/sa1111.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/common/sharpsl_pm.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/common/vic.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/assabet_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/at91sam9260ek_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/at91sam9261ek_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/ateb9200_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/badge4_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/carmeva_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/cerfcube_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/collie_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/corgi_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/csb337_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/csb637_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/ep93xx_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/h3600_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/h7202_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/hackkit_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/iop13xx_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/iop32x_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/iop33x_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/ixp2000_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/ixp23xx_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/ixp4xx_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/kafa_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/kb9202_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/lart_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/lpd270_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/lpd7a400_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/lpd7a404_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/lubbock_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/mx1ads_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/neponset_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/netx_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/onearm_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/pleb_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/pnx4008_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/realview_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/rpc_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/s3c2410_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/shark_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/simpad_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/configs/spitz_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/apm.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/asm-offsets.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/ecard.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/head-nommu.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/head.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/iwmmxt-notifier.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/signal.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/kernel/xscale-cp0.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-aaec2000/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/at91sam9260.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/at91sam9260_devices.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/at91sam9261.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/at91sam9261_devices.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/at91sam926x_time.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/board-dk.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/board-ek.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/board-sam9260ek.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/board-sam9261ek.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/clock.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/clock.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/generic.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/gpio.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-at91rm9200/pm.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-clps711x/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-clps7500/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ebsa110/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ebsa110/io.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ep93xx/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ep93xx/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ep93xx/adssphere.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ep93xx/edb9302a.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-footbridge/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-footbridge/dc21285.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-footbridge/isa-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-h720x/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-h720x/cpu-h7202.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-imx/generic.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-imx/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-imx/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-integrator/platsmp.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/Kconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/Makefile 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/Makefile.boot 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/io.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/iq81340mc.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/iq81340sc.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/irq.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/pci.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/setup.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop13xx/time.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop32x/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop32x/n2100.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-iop33x/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp2000/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp2000/ixdp2400.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp2000/ixdp2800.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp2000/ixdp2x00.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp2000/ixdp2x01.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp2000/pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp23xx/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp23xx/ixdp2351.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp23xx/pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp4xx/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-l7200/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-lh7a40x/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-lh7a40x/common.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-lh7a40x/irq-lh7a400.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-lh7a40x/irq-lh7a404.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-netx/generic.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap1/devices.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap1/fpga.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap1/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap1/leds-osk.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap2/board-h4.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-omap2/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pnx4008/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pnx4008/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pnx4008/i2c.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pnx4008/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/akita-ioexp.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/generic.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/pm.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-pxa/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-realview/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-realview/core.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-rpc/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/bast-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/dma.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/gpio.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/irq.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/mach-h1940.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/mach-osiris.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/mach-rx3715.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/mach-vr1000.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410-pm.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/s3c2440-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-s3c2410/s3c244x-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-sa1100/cpu-sa1110.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-sa1100/generic.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-sa1100/h3600.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-sa1100/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-sa1100/neponset.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-sa1100/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-shark/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mach-versatile/core.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/consistent.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/mm.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/nommu.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm1020.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm1020e.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm1022.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm1026.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm6_7.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm720.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm740.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm7tdmi.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm920.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm922.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm925.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm926.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm940.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm946.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-arm9tdmi.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-sa110.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-sa1100.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-v6.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-xsc3.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/mm/proc-xscale.S
浏览文件 @ c4366889
此差异已折叠。
arch/arm/oprofile/op_counter.h
浏览文件 @ c4366889
此差异已折叠。
arch/arm/oprofile/op_model_xscale.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ c4366889
此差异已折叠。
arch/arm/vfp/vfpdouble.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm/vfp/vfpmodule.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm26/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/arm26/kernel/ecard.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm26/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/arm26/mm/memc.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/boards/atstk1000/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/boot/images/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/avr32_ksyms.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/head.S
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/kprobes.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/module.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/process.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/ptrace.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/signal.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/syscall-stubs.S
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/syscall_table.S
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/kernel/vmlinux.lds.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/lib/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/lib/delay.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/lib/findbit.S
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/lib/io-readsb.S 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/lib/io-writesb.S 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/at32ap7000.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/extint.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/hsmc.h
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/intc.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/intc.h
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/pio.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/pio.h
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mach-at32ap/sm.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/avr32/mach-at32ap/sm.h
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mm/dma-coherent.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mm/init.c
浏览文件 @ c4366889
此差异已折叠。
arch/avr32/mm/ioremap.c
浏览文件 @ c4366889
此差异已折叠。
arch/cris/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/cris/arch-v10/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/cris/arch-v10/drivers/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/cris/arch-v10/drivers/eeprom.c
浏览文件 @ c4366889
此差异已折叠。
arch/cris/arch-v10/drivers/i2c.c
浏览文件 @ c4366889
此差异已折叠。
arch/cris/arch-v10/kernel/kgdb.c
浏览文件 @ c4366889
此差异已折叠。
arch/cris/arch-v32/drivers/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/cris/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/frv/kernel/futex.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/kernel/pm.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/kernel/signal.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/frv/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/mm/elf-fdpic.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/frv/mm/pgalloc.c
浏览文件 @ c4366889
此差异已折叠。
arch/h8300/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/h8300/kernel/h8300_ksyms.c
浏览文件 @ c4366889
此差异已折叠。
arch/h8300/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/h8300/kernel/signal.c
浏览文件 @ c4366889
此差异已折叠。
arch/h8300/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/h8300/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/i386/Kconfig.cpu
浏览文件 @ c4366889
此差异已折叠。
arch/i386/Kconfig.debug
浏览文件 @ c4366889
此差异已折叠。
arch/i386/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/i386/Makefile.cpu
浏览文件 @ c4366889
此差异已折叠。
arch/i386/boot/compressed/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/i386/boot/compressed/head.S
浏览文件 @ c4366889
此差异已折叠。
arch/i386/boot/compressed/misc.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/boot/compressed/relocs.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/i386/boot/compressed/vmlinux.lds 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/i386/boot/setup.S
浏览文件 @ c4366889
此差异已折叠。
arch/i386/defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/acpi/boot.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/acpi/cstate.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/acpi/earlyquirk.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/alternative.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/apic.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/apm.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/asm-offsets.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/amd.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/intel.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/amd.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/centaur.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/cyrix.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/generic.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/if.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/main.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/mtrr/mtrr.h
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpu/proc.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/cpuid.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/crash.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/e820.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/efi.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/entry.S
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/head.S
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/hpet.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/i8253.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/i8259.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/io_apic.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/kprobes.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/ldt.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/mca.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/microcode.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/module.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/mpparse.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/msr.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/nmi.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/paravirt.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/pci-dma.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/process.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/ptrace.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/quirks.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/reboot.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/signal.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/smp.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/smpboot.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/sysenter.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/time_hpet.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/topology.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/traps.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/tsc.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/vm86.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/i386/lib/usercopy.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mach-generic/probe.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mach-visws/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mach-visws/visws_apic.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/math-emu/fpu_emu.h
浏览文件 @ c4366889
此差异已折叠。
arch/i386/math-emu/fpu_entry.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/math-emu/fpu_system.h
浏览文件 @ c4366889
此差异已折叠。
arch/i386/math-emu/load_store.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/math-emu/reg_ld_str.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/boot_ioremap.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/discontig.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/highmem.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/hugetlbpage.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/init.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/pageattr.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/mm/pgtable.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/early.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/fixup.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/i386.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/mmconfig.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/pcbios.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/pci/pci.h
浏览文件 @ c4366889
此差异已折叠。
arch/i386/power/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/i386/power/cpu.c
浏览文件 @ c4366889
此差异已折叠。
arch/i386/power/suspend.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/i386/power/swsusp.S
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/configs/sn2_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/hp/sim/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/hp/sim/hpsim_irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/hp/sim/simserial.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/ia32/binfmt_elf32.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/ia32/ia32_support.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/ia32/ia32priv.h
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/crash.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/efi.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/ia64_ksyms.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/iosapic.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/irq_ia64.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/irq_lsapic.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/kprobes.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/machine_kexec.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/mca.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/mca_drv.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/pal.S
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/palinfo.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/relocate_kernel.S 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/sal.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/salinfo.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/smp.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/smpboot.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/topology.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/lib/csum_partial_copy.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/lib/ip_fast_csum.S
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/mm/hugetlbpage.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/pci/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/pci/fixup.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/bte.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/io_acpi_init.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/io_common.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/io_init.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/iomv.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/msi_sn.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/kernel/tiocx.c
浏览文件 @ c4366889
此差异已折叠。
arch/ia64/sn/pci/tioce_provider.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/kernel/entry.S
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/kernel/io_opsput.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/kernel/setup_opsput.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/kernel/signal.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/lib/csum_partial_copy.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/mm/discontig.c
浏览文件 @ c4366889
此差异已折叠。
arch/m32r/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/amiga/chipram.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/atari/hades-pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/atari/stdma.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/kernel/sun3-head.S
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/kernel/vmlinux-std.lds
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/kernel/vmlinux-sun3.lds
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/mm/memory.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68k/mm/sun3mmu.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/m68k_ksyms.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/process.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/sys_m68k.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/traps.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/platform/5307/head.S
浏览文件 @ c4366889
此差异已折叠。
arch/m68knommu/platform/5307/ints.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/au1000/common/dbdma.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/au1000/common/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/au1000/common/prom.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/au1000/common/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/au1000/common/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/cobalt/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/cobalt/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/atlas_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/bigsur_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/cobalt_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/db1000_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/db1100_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/db1200_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/db1500_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/db1550_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/ddb5477_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/e55_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/emma2rh_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/ev64120_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/excite_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/ip22_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/ip27_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/ip32_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/jazz_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/jmr3927_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/malta_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/mipssim_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/mpc30x_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/ocelot_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/pb1100_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/pb1500_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/pb1550_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/pnx8550-stb810_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/qemu_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/rm200_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/sead_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/tb0226_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/tb0229_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/tb0287_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/workpad_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/configs/wrppmc_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/ecc-berr.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/int-handler.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/ioasic-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/kn01-berr.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/kn02-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/dec/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/mips/gt64120/common/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/gt64120/ev64120/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/gt64120/ev64120/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/jazz/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/jmr3927/rbhma3100/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/jmr3927/rbhma3100/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/asm-offsets.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/binfmt_elfn32.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/binfmt_elfo32.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/cpu-probe.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/dma-no-isa.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/mips/kernel/entry.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/genex.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/head.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/i8259.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irixelf.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irq-msc01.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irq-mv6434x.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irq-rm7000.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irq-rm9000.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/irq_cpu.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/kspd.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/machine_kexec.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/module.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/process.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/r4k_switch.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/relocate_kernel.S 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/reset.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/rtlx.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/scall32-o32.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/scall64-64.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/scall64-n32.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/scall64-o32.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/signal_n32.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/smp-mt.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/smp.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/smtc-asm.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/smtc.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/stacktrace.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/sysirix.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/topology.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/traps.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/mips/kernel/vpe.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lasat/interrupt.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lasat/sysctl.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lib-32/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lib-64/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lib-64/csum_partial.S 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/mips/lib-64/dump_tlb.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lib/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/lib/csum_partial_copy.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mips-boards/generic/pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/c-r4k.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/c-sb1.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/cache.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/dma-coherent.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/dma-ip27.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/dma-ip32.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/dma-noncoherent.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/highmem.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/init.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/ioremap.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/pg-r4k.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/pgtable-32.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/pgtable-64.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/mm/tlbex.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_3/platform.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_3/prom.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_3/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_c/platform.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_c/prom.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_c/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/momentum/ocelot_g/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/oprofile/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/oprofile/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/oprofile/op_impl.h
浏览文件 @ c4366889
此差异已折叠。
arch/mips/pci/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/mips/pci/fixup-cobalt.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/pci/fixup-ev64120.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/mips/pci/fixup-pnx8550.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/pci/ops-gt64111.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/pci/pci-ev64120.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/philips/pnx8550/stb810/Makefile 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/philips/pnx8550/stb810/board_setup.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/philips/pnx8550/stb810/irqmap.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/philips/pnx8550/stb810/prom_init.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/pmc-sierra/yosemite/smp.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sgi-ip22/ip22-eisa.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sgi-ip22/ip22-int.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sgi-ip27/ip27-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sgi-ip27/ip27-timer.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sgi-ip32/ip32-irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sgi-ip32/ip32-reset.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sibyte/bcm1480/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sibyte/bcm1480/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sibyte/sb1250/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sibyte/sb1250/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sibyte/swarm/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/sni/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/tx4927/common/smsc_fdc37m81x.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/mips/tx4938/common/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/tx4938/common/setup.c
浏览文件 @ c4366889
此差异已折叠。
arch/mips/vr41xx/common/icu.c
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/hpux/sys_hpux.c
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/kernel/binfmt_elf32.c
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/lib/checksum.c
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/parisc/mm/ioremap.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/.gitignore 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/.gitignore
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/dts/kuroboxHG.dts 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/dts/lite5200.dts 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/dts/lite5200b.dts 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/flatdevtree.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/flatdevtree.h
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/flatdevtree_env.h 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/flatdevtree_misc.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/io.h 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/main.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/mktree.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/ns16550.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/of.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/ops.h
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/serial.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/simple_alloc.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/stdio.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/util.S 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/wrapper
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/zImage.coff.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/boot/zImage.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/configs/cell_defconfig
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/configs/linkstation_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/configs/lite5200_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/configs/ps3_defconfig 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/btext.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/crash.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/dma_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/head_32.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/ibmebus.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/idle.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/idle_power4.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/io.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/iomap.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/iommu.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/kprobes.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/misc_32.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/misc_64.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/module_32.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/module_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/of_device.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/of_platform.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/pci_32.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/pci_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/pci_direct_iommu.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/powerpc/kernel/pci_iommu.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/powerpc/kernel/perfmon_fsl_booke.c 已删除 100644 → 0
浏览文件 @ db2fb9db
此差异已折叠。
arch/powerpc/kernel/pmc.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/proc_ppc64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/process.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/rtas_flash.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/rtas_pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/signal_32.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/smp-tbsync.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/sys_ppc32.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/sysfs.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/vdso.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/lib/sstep.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/fault.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/hash_native_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/hugetlbpage.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/init_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/pgtable_32.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/pgtable_64.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/mm/slb.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/oprofile/Makefile
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/oprofile/common.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/oprofile/op_model_cell.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/Makefile 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/efika-pci.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/efika-setup.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/efika.h 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/lite5200.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/mpc52xx_common.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/mpc52xx_pic.c 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/52xx/mpc52xx_pic.h 0 → 100644
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/83xx/Kconfig
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/83xx/pci.c
浏览文件 @ c4366889
此差异已折叠。
arch/powerpc/platforms/85xx/misc.c
浏览文件 @ c4366889
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或