Skip to content

K
kernel_linux

OpenHarmony / kernel_linux
上一次同步 4 年多

通知 15
Star 8
Fork 2
K
kernel_linux
提交 36d99df2 编写于 作者: S Steve French
浏览文件
操作

Merge branch 'master' of /pub/scm/linux/kernel/git/torvalds/linux-2.6

上级 076d8423 3dc50637
展开全部 隐藏空白更改
内联 并排
Showing with 52661 addition and 32304 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
Documentation/00-INDEX
浏览文件 @ 36d99df2
......@@ -25,8 +25,6 @@ DMA-API.txt
- DMA API, pci_ API & extensions for non-consistent memory machines.
DMA-ISA-LPC.txt
- How to do DMA with ISA (and LPC) devices.
DMA-mapping.txt
- info for PCI drivers using DMA portably across all platforms.
DocBook/
- directory with DocBook templates etc. for kernel documentation.
HOWTO
......@@ -43,8 +41,6 @@ ManagementStyle
- how to (attempt to) manage kernel hackers.
MSI-HOWTO.txt
- the Message Signaled Interrupts (MSI) Driver Guide HOWTO and FAQ.
PCIEBUS-HOWTO.txt
- a guide describing the PCI Express Port Bus driver.
RCU/
- directory with info on RCU (read-copy update).
README.DAC960
......@@ -167,10 +163,8 @@ highuid.txt
- notes on the change from 16 bit to 32 bit user/group IDs.
hpet.txt
- High Precision Event Timer Driver for Linux.
hrtimer/
- info on the timer_stats debugging facility for timer (ab)use.
hrtimers/
- info on the hrtimers subsystem for high-resolution kernel timers.
timers/
- info on the timer related topics
hw_random.txt
- info on Linux support for random number generator in i8xx chipsets.
hwmon/
......@@ -287,12 +281,6 @@ parport.txt
- how to use the parallel-port driver.
parport-lowlevel.txt
- description and usage of the low level parallel port functions.
pci-error-recovery.txt
- info on PCI error recovery.
pci.txt
- info on the PCI subsystem for device driver authors.
pcieaer-howto.txt
- the PCI Express Advanced Error Reporting Driver Guide HOWTO.
pcmcia/
- info on the Linux PCMCIA driver.
pi-futex.txt
......
Documentation/ABI/obsolete/o2cb 0 → 100644
浏览文件 @ 36d99df2
What: /sys/o2cb symlink
Date: Dec 2005
KernelVersion: 2.6.16
Contact: ocfs2-devel@oss.oracle.com
Description: This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink will
be removed when new versions of ocfs2-tools which know to look
in /sys/fs/o2cb are sufficiently prevalent. Don't code new
software to look here, it should try /sys/fs/o2cb instead.
See Documentation/ABI/stable/o2cb for more information on usage.
Users: ocfs2-tools. It's sufficient to mail proposed changes to
ocfs2-devel@oss.oracle.com.
Documentation/ABI/stable/o2cb 0 → 100644
浏览文件 @ 36d99df2
What: /sys/fs/o2cb/ (was /sys/o2cb)
Date: Dec 2005
KernelVersion: 2.6.16
Contact: ocfs2-devel@oss.oracle.com
Description: Ocfs2-tools looks at 'interface-revision' for versioning
information. Each logmask/ file controls a set of debug prints
and can be written into with the strings "allow", "deny", or
"off". Reading the file returns the current state.
Users: ocfs2-tools. It's sufficient to mail proposed changes to
ocfs2-devel@oss.oracle.com.
Documentation/ABI/testing/sysfs-bus-pci 0 → 100644
浏览文件 @ 36d99df2
What: /sys/bus/pci/devices/.../vpd
Date: February 2008
Contact: Ben Hutchings <bhutchings@solarflare.com>
Description:
A file named vpd in a device directory will be a
binary file containing the Vital Product Data for the
device. It should follow the VPD format defined in
PCI Specification 2.1 or 2.2, but users should consider
that some devices may have malformatted data. If the
underlying VPD has a writable section then the
corresponding section of this file will be writable.
Documentation/ABI/testing/sysfs-ibft 0 → 100644
浏览文件 @ 36d99df2
What: /sys/firmware/ibft/initiator
Date: November 2007
Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
Description: The /sys/firmware/ibft/initiator directory will contain
files that expose the iSCSI Boot Firmware Table initiator data.
Usually this contains the Initiator name.
What: /sys/firmware/ibft/targetX
Date: November 2007
Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
Description: The /sys/firmware/ibft/targetX directory will contain
files that expose the iSCSI Boot Firmware Table target data.
Usually this contains the target's IP address, boot LUN,
target name, and what NIC it is associated with. It can also
contain the CHAP name (and password), the reverse CHAP
name (and password)
What: /sys/firmware/ibft/ethernetX
Date: November 2007
Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
Description: The /sys/firmware/ibft/ethernetX directory will contain
files that expose the iSCSI Boot Firmware Table NIC data.
This can this can the IP address, MAC, and gateway of the NIC.
Documentation/ABI/testing/sysfs-ocfs2 0 → 100644
浏览文件 @ 36d99df2
What: /sys/fs/ocfs2/
Date: April 2008
Contact: ocfs2-devel@oss.oracle.com
Description:
The /sys/fs/ocfs2 directory contains knobs used by the
ocfs2-tools to interact with the filesystem.
What: /sys/fs/ocfs2/max_locking_protocol
Date: April 2008
Contact: ocfs2-devel@oss.oracle.com
Description:
The /sys/fs/ocfs2/max_locking_protocol file displays version
of ocfs2 locking supported by the filesystem. This version
covers how ocfs2 uses distributed locking between cluster
nodes.
The protocol version has a major and minor number. Two
cluster nodes can interoperate if they have an identical
major number and an overlapping minor number - thus,
a node with version 1.10 can interoperate with a node
sporting version 1.8, as long as both use the 1.8 protocol.
Reading from this file returns a single line, the major
number and minor number joined by a period, eg "1.10".
This file is read-only. The value is compiled into the
driver.
What: /sys/fs/ocfs2/loaded_cluster_plugins
Date: April 2008
Contact: ocfs2-devel@oss.oracle.com
Description:
The /sys/fs/ocfs2/loaded_cluster_plugins file describes
the available plugins to support ocfs2 cluster operation.
A cluster plugin is required to use ocfs2 in a cluster.
There are currently two available plugins:
* 'o2cb' - The classic o2cb cluster stack that ocfs2 has
used since its inception.
* 'user' - A plugin supporting userspace cluster software
in conjunction with fs/dlm.
Reading from this file returns the names of all loaded
plugins, one per line.
This file is read-only. Its contents may change as
plugins are loaded or removed.
What: /sys/fs/ocfs2/active_cluster_plugin
Date: April 2008
Contact: ocfs2-devel@oss.oracle.com
Description:
The /sys/fs/ocfs2/active_cluster_plugin displays which
cluster plugin is currently in use by the filesystem.
The active plugin will appear in the loaded_cluster_plugins
file as well. Only one plugin can be used at a time.
Reading from this file returns the name of the active plugin
on a single line.
This file is read-only. Which plugin is active depends on
the cluster stack in use. The contents may change
when all filesystems are unmounted and the cluster stack
is changed.
What: /sys/fs/ocfs2/cluster_stack
Date: April 2008
Contact: ocfs2-devel@oss.oracle.com
Description:
The /sys/fs/ocfs2/cluster_stack file contains the name
of current ocfs2 cluster stack. This value is set by
userspace tools when bringing the cluster stack online.
Cluster stack names are 4 characters in length.
When the 'o2cb' cluster stack is used, the 'o2cb' cluster
plugin is active. All other cluster stacks use the 'user'
cluster plugin.
Reading from this file returns the name of the current
cluster stack on a single line.
Writing a new stack name to this file changes the current
cluster stack unless there are mounted ocfs2 filesystems.
If there are mounted filesystems, attempts to change the
stack return an error.
Users:
ocfs2-tools <ocfs2-tools-devel@oss.oracle.com>
Documentation/DocBook/Makefile
浏览文件 @ 36d99df2
......@@ -9,9 +9,10 @@
DOCBOOKS := wanbook.xml z8530book.xml mcabook.xml videobook.xml \
kernel-hacking.xml kernel-locking.xml deviceiobook.xml \
procfs-guide.xml writing_usb_driver.xml networking.xml \
kernel-api.xml filesystems.xml lsm.xml usb.xml \
kernel-api.xml filesystems.xml lsm.xml usb.xml kgdb.xml \
gadget.xml libata.xml mtdnand.xml librs.xml rapidio.xml \
genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml
genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
mac80211.xml
###
# The build process is as follows (targets):
......
Documentation/DocBook/kernel-api.tmpl
浏览文件 @ 36d99df2
......@@ -297,11 +297,6 @@ X!Earch/x86/kernel/mca_32.c
!Ikernel/acct.c
</chapter>
<chapter id="pmfuncs">
<title>Power Management</title>
!Ekernel/power/pm.c
</chapter>
<chapter id="devdrivers">
<title>Device drivers infrastructure</title>
<sect1><title>Device Drivers Base</title>
......
Documentation/DocBook/kernel-locking.tmpl
浏览文件 @ 36d99df2
......@@ -241,7 +241,7 @@
</para>
<para>
The third type is a semaphore
(<filename class="headerfile">include/asm/semaphore.h</filename>): it
(<filename class="headerfile">include/linux/semaphore.h</filename>): it
can have more than one holder at any time (the number decided at
initialization time), although it is most commonly used as a
single-holder lock (a mutex). If you can't get a semaphore, your
......@@ -290,7 +290,7 @@
<para>
If you have a data structure which is only ever accessed from
user context, then you can use a simple semaphore
(<filename>linux/asm/semaphore.h</filename>) to protect it. This
(<filename>linux/linux/semaphore.h</filename>) to protect it. This
is the most trivial case: you initialize the semaphore to the number
of resources available (usually 1), and call
<function>down_interruptible()</function> to grab the semaphore, and
......@@ -854,7 +854,7 @@ The change is shown below, in standard patch format: the
};
-static DEFINE_MUTEX(cache_lock);
+static spinlock_t cache_lock = SPIN_LOCK_UNLOCKED;
+static DEFINE_SPINLOCK(cache_lock);
static LIST_HEAD(cache);
static unsigned int cache_num = 0;
#define MAX_CACHE_SIZE 10
......@@ -1238,7 +1238,7 @@ Here is the "lock-per-object" implementation:
- int popularity;
};
static spinlock_t cache_lock = SPIN_LOCK_UNLOCKED;
static DEFINE_SPINLOCK(cache_lock);
@@ -77,6 +84,7 @@
obj-&gt;id = id;
obj-&gt;popularity = 0;
......@@ -1656,7 +1656,7 @@ the amount of locking which needs to be done.
#include &lt;linux/slab.h&gt;
#include &lt;linux/string.h&gt;
+#include &lt;linux/rcupdate.h&gt;
#include &lt;asm/semaphore.h&gt;
#include &lt;linux/semaphore.h&gt;
#include &lt;asm/errno.h&gt;
struct object
......
Documentation/DocBook/kgdb.tmpl 0 → 100644
浏览文件 @ 36d99df2
<?xml version="1.0" encoding="UTF-8"?>
<!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="kgdbOnLinux">
<bookinfo>
<title>Using kgdb and the kgdb Internals</title>
<authorgroup>
<author>
<firstname>Jason</firstname>
<surname>Wessel</surname>
<affiliation>
<address>
<email>jason.wessel@windriver.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<authorgroup>
<author>
<firstname>Tom</firstname>
<surname>Rini</surname>
<affiliation>
<address>
<email>trini@kernel.crashing.org</email>
</address>
</affiliation>
</author>
</authorgroup>
<authorgroup>
<author>
<firstname>Amit S.</firstname>
<surname>Kale</surname>
<affiliation>
<address>
<email>amitkale@linsyssoft.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<copyright>
<year>2008</year>
<holder>Wind River Systems, Inc.</holder>
</copyright>
<copyright>
<year>2004-2005</year>
<holder>MontaVista Software, Inc.</holder>
</copyright>
<copyright>
<year>2004</year>
<holder>Amit S. Kale</holder>
</copyright>
<legalnotice>
<para>
This file is licensed under the terms of the GNU General Public License
version 2. This program is licensed "as is" without any warranty of any
kind, whether express or implied.
</para>
</legalnotice>
</bookinfo>
<toc></toc>
<chapter id="Introduction">
<title>Introduction</title>
<para>
kgdb is a source level debugger for linux kernel. It is used along
with gdb to debug a linux kernel. The expectation is that gdb can
be used to "break in" to the kernel to inspect memory, variables
and look through a cal stack information similar to what an
application developer would use gdb for. It is possible to place
breakpoints in kernel code and perform some limited execution
stepping.
</para>
<para>
Two machines are required for using kgdb. One of these machines is a
development machine and the other is a test machine. The kernel
to be debugged runs on the test machine. The development machine
runs an instance of gdb against the vmlinux file which contains
the symbols (not boot image such as bzImage, zImage, uImage...).
In gdb the developer specifies the connection parameters and
connects to kgdb. Depending on which kgdb I/O modules exist in
the kernel for a given architecture, it may be possible to debug
the test machine's kernel with the development machine using a
rs232 or ethernet connection.
</para>
</chapter>
<chapter id="CompilingAKernel">
<title>Compiling a kernel</title>
<para>
To enable <symbol>CONFIG_KGDB</symbol>, look under the "Kernel debugging"
and then select "KGDB: kernel debugging with remote gdb".
</para>
<para>
Next you should choose one of more I/O drivers to interconnect debugging
host and debugged target. Early boot debugging requires a KGDB
I/O driver that supports early debugging and the driver must be
built into the kernel directly. Kgdb I/O driver configuration
takes place via kernel or module parameters, see following
chapter.
</para>
<para>
The kgdb test compile options are described in the kgdb test suite chapter.
</para>
</chapter>
<chapter id="EnableKGDB">
<title>Enable kgdb for debugging</title>
<para>
In order to use kgdb you must activate it by passing configuration
information to one of the kgdb I/O drivers. If you do not pass any
configuration information kgdb will not do anything at all. Kgdb
will only actively hook up to the kernel trap hooks if a kgdb I/O
driver is loaded and configured. If you unconfigure a kgdb I/O
driver, kgdb will unregister all the kernel hook points.
</para>
<para>
All drivers can be reconfigured at run time, if
<symbol>CONFIG_SYSFS</symbol> and <symbol>CONFIG_MODULES</symbol>
are enabled, by echo'ing a new config string to
<constant>/sys/module/&lt;driver&gt;/parameter/&lt;option&gt;</constant>.
The driver can be unconfigured by passing an empty string. You cannot
change the configuration while the debugger is attached. Make sure
to detach the debugger with the <constant>detach</constant> command
prior to trying unconfigure a kgdb I/O driver.
</para>
<sect1 id="kgdbwait">
<title>Kernel parameter: kgdbwait</title>
<para>
The Kernel command line option <constant>kgdbwait</constant> makes
kgdb wait for a debugger connection during booting of a kernel. You
can only use this option you compiled a kgdb I/O driver into the
kernel and you specified the I/O driver configuration as a kernel
command line option. The kgdbwait parameter should always follow the
configuration parameter for the kgdb I/O driver in the kernel
command line else the I/O driver will not be configured prior to
asking the kernel to use it to wait.
</para>
<para>
The kernel will stop and wait as early as the I/O driver and
architecture will allow when you use this option. If you build the
kgdb I/O driver as a kernel module kgdbwait will not do anything.
</para>
</sect1>
<sect1 id="kgdboc">
<title>Kernel parameter: kgdboc</title>
<para>
The kgdboc driver was originally an abbreviation meant to stand for
"kgdb over console". Kgdboc is designed to work with a single
serial port. It was meant to cover the circumstance
where you wanted to use a serial console as your primary console as
well as using it to perform kernel debugging. Of course you can
also use kgdboc without assigning a console to the same port.
</para>
<sect2 id="UsingKgdboc">
<title>Using kgdboc</title>
<para>
You can configure kgdboc via sysfs or a module or kernel boot line
parameter depending on if you build with CONFIG_KGDBOC as a module
or built-in.
<orderedlist>
<listitem><para>From the module load or build-in</para>
<para><constant>kgdboc=&lt;tty-device&gt;,[baud]</constant></para>
<para>
The example here would be if your console port was typically ttyS0, you would use something like <constant>kgdboc=ttyS0,115200</constant> or on the ARM Versatile AB you would likely use <constant>kgdboc=ttyAMA0,115200</constant>
</para>
</listitem>
<listitem><para>From sysfs</para>
<para><constant>echo ttyS0 &gt; /sys/module/kgdboc/parameters/kgdboc</constant></para>
</listitem>
</orderedlist>
</para>
<para>
NOTE: Kgdboc does not support interrupting the target via the
gdb remote protocol. You must manually send a sysrq-g unless you
have a proxy that splits console output to a terminal problem and
has a separate port for the debugger to connect to that sends the
sysrq-g for you.
</para>
<para>When using kgdboc with no debugger proxy, you can end up
connecting the debugger for one of two entry points. If an
exception occurs after you have loaded kgdboc a message should print
on the console stating it is waiting for the debugger. In case you
disconnect your terminal program and then connect the debugger in
its place. If you want to interrupt the target system and forcibly
enter a debug session you have to issue a Sysrq sequence and then
type the letter <constant>g</constant>. Then you disconnect the
terminal session and connect gdb. Your options if you don't like
this are to hack gdb to send the sysrq-g for you as well as on the
initial connect, or to use a debugger proxy that allows an
unmodified gdb to do the debugging.
</para>
</sect2>
</sect1>
<sect1 id="kgdbcon">
<title>Kernel parameter: kgdbcon</title>
<para>
Kgdb supports using the gdb serial protocol to send console messages
to the debugger when the debugger is connected and running. There
are two ways to activate this feature.
<orderedlist>
<listitem><para>Activate with the kernel command line option:</para>
<para><constant>kgdbcon</constant></para>
</listitem>
<listitem><para>Use sysfs before configuring an io driver</para>
<para>
<constant>echo 1 &gt; /sys/module/kgdb/parameters/kgdb_use_con</constant>
</para>
<para>
NOTE: If you do this after you configure the kgdb I/O driver, the
setting will not take effect until the next point the I/O is
reconfigured.
</para>
</listitem>
</orderedlist>
</para>
<para>
IMPORTANT NOTE: Using this option with kgdb over the console
(kgdboc) or kgdb over ethernet (kgdboe) is not supported.
</para>
</sect1>
</chapter>
<chapter id="ConnectingGDB">
<title>Connecting gdb</title>
<para>
If you are using kgdboc, you need to have used kgdbwait as a boot
argument, issued a sysrq-g, or the system you are going to debug
has already taken an exception and is waiting for the debugger to
attach before you can connect gdb.
</para>
<para>
If you are not using different kgdb I/O driver other than kgdboc,
you should be able to connect and the target will automatically
respond.
</para>
<para>
Example (using a serial port):
</para>
<programlisting>
% gdb ./vmlinux
(gdb) set remotebaud 115200
(gdb) target remote /dev/ttyS0
</programlisting>
<para>
Example (kgdb to a terminal server):
</para>
<programlisting>
% gdb ./vmlinux
(gdb) target remote udp:192.168.2.2:6443
</programlisting>
<para>
Example (kgdb over ethernet):
</para>
<programlisting>
% gdb ./vmlinux
(gdb) target remote udp:192.168.2.2:6443
</programlisting>
<para>
Once connected, you can debug a kernel the way you would debug an
application program.
</para>
<para>
If you are having problems connecting or something is going
seriously wrong while debugging, it will most often be the case
that you want to enable gdb to be verbose about its target
communications. You do this prior to issuing the <constant>target
remote</constant> command by typing in: <constant>set remote debug 1</constant>
</para>
</chapter>
<chapter id="KGDBTestSuite">
<title>kgdb Test Suite</title>
<para>
When kgdb is enabled in the kernel config you can also elect to
enable the config parameter KGDB_TESTS. Turning this on will
enable a special kgdb I/O module which is designed to test the
kgdb internal functions.
</para>
<para>
The kgdb tests are mainly intended for developers to test the kgdb
internals as well as a tool for developing a new kgdb architecture
specific implementation. These tests are not really for end users
of the Linux kernel. The primary source of documentation would be
to look in the drivers/misc/kgdbts.c file.
</para>
<para>
The kgdb test suite can also be configured at compile time to run
the core set of tests by setting the kernel config parameter
KGDB_TESTS_ON_BOOT. This particular option is aimed at automated
regression testing and does not require modifying the kernel boot
config arguments. If this is turned on, the kgdb test suite can
be disabled by specifying "kgdbts=" as a kernel boot argument.
</para>
</chapter>
<chapter id="CommonBackEndReq">
<title>KGDB Internals</title>
<sect1 id="kgdbArchitecture">
<title>Architecture Specifics</title>
<para>
Kgdb is organized into three basic components:
<orderedlist>
<listitem><para>kgdb core</para>
<para>
The kgdb core is found in kernel/kgdb.c. It contains:
<itemizedlist>
<listitem><para>All the logic to implement the gdb serial protocol</para></listitem>
<listitem><para>A generic OS exception handler which includes sync'ing the processors into a stopped state on an multi cpu system.</para></listitem>
<listitem><para>The API to talk to the kgdb I/O drivers</para></listitem>
<listitem><para>The API to make calls to the arch specific kgdb implementation</para></listitem>
<listitem><para>The logic to perform safe memory reads and writes to memory while using the debugger</para></listitem>
<listitem><para>A full implementation for software breakpoints unless overridden by the arch</para></listitem>
</itemizedlist>
</para>
</listitem>
<listitem><para>kgdb arch specific implementation</para>
<para>
This implementation is generally found in arch/*/kernel/kgdb.c.
As an example, arch/x86/kernel/kgdb.c contains the specifics to
implement HW breakpoint as well as the initialization to
dynamically register and unregister for the trap handlers on
this architecture. The arch specific portion implements:
<itemizedlist>
<listitem><para>contains an arch specific trap catcher which
invokes kgdb_handle_exception() to start kgdb about doing its
work</para></listitem>
<listitem><para>translation to and from gdb specific packet format to pt_regs</para></listitem>
<listitem><para>Registration and unregistration of architecture specific trap hooks</para></listitem>
<listitem><para>Any special exception handling and cleanup</para></listitem>
<listitem><para>NMI exception handling and cleanup</para></listitem>
<listitem><para>(optional)HW breakpoints</para></listitem>
</itemizedlist>
</para>
</listitem>
<listitem><para>kgdb I/O driver</para>
<para>
Each kgdb I/O driver has to provide an implemenation for the following:
<itemizedlist>
<listitem><para>configuration via builtin or module</para></listitem>
<listitem><para>dynamic configuration and kgdb hook registration calls</para></listitem>
<listitem><para>read and write character interface</para></listitem>
<listitem><para>A cleanup handler for unconfiguring from the kgdb core</para></listitem>
<listitem><para>(optional) Early debug methodology</para></listitem>
</itemizedlist>
Any given kgdb I/O driver has to operate very closely with the
hardware and must do it in such a way that does not enable
interrupts or change other parts of the system context without
completely restoring them. The kgdb core will repeatedly "poll"
a kgdb I/O driver for characters when it needs input. The I/O
driver is expected to return immediately if there is no data
available. Doing so allows for the future possibility to touch
watch dog hardware in such a way as to have a target system not
reset when these are enabled.
</para>
</listitem>
</orderedlist>
</para>
<para>
If you are intent on adding kgdb architecture specific support
for a new architecture, the architecture should define
<constant>HAVE_ARCH_KGDB</constant> in the architecture specific
Kconfig file. This will enable kgdb for the architecture, and
at that point you must create an architecture specific kgdb
implementation.
</para>
<para>
There are a few flags which must be set on every architecture in
their &lt;asm/kgdb.h&gt; file. These are:
<itemizedlist>
<listitem>
<para>
NUMREGBYTES: The size in bytes of all of the registers, so
that we can ensure they will all fit into a packet.
</para>
<para>
BUFMAX: The size in bytes of the buffer GDB will read into.
This must be larger than NUMREGBYTES.
</para>
<para>
CACHE_FLUSH_IS_SAFE: Set to 1 if it is always safe to call
flush_cache_range or flush_icache_range. On some architectures,
these functions may not be safe to call on SMP since we keep other
CPUs in a holding pattern.
</para>
</listitem>
</itemizedlist>
</para>
<para>
There are also the following functions for the common backend,
found in kernel/kgdb.c, that must be supplied by the
architecture-specific backend unless marked as (optional), in
which case a default function maybe used if the architecture
does not need to provide a specific implementation.
</para>
!Iinclude/linux/kgdb.h
</sect1>
<sect1 id="kgdbocDesign">
<title>kgdboc internals</title>
<para>
The kgdboc driver is actually a very thin driver that relies on the
underlying low level to the hardware driver having "polling hooks"
which the to which the tty driver is attached. In the initial
implementation of kgdboc it the serial_core was changed to expose a
low level uart hook for doing polled mode reading and writing of a
single character while in an atomic context. When kgdb makes an I/O
request to the debugger, kgdboc invokes a call back in the serial
core which in turn uses the call back in the uart driver. It is
certainly possible to extend kgdboc to work with non-uart based
consoles in the future.
</para>
<para>
When using kgdboc with a uart, the uart driver must implement two callbacks in the <constant>struct uart_ops</constant>. Example from drivers/8250.c:<programlisting>
#ifdef CONFIG_CONSOLE_POLL
.poll_get_char = serial8250_get_poll_char,
.poll_put_char = serial8250_put_poll_char,
#endif
</programlisting>
Any implementation specifics around creating a polling driver use the
<constant>#ifdef CONFIG_CONSOLE_POLL</constant>, as shown above.
Keep in mind that polling hooks have to be implemented in such a way
that they can be called from an atomic context and have to restore
the state of the uart chip on return such that the system can return
to normal when the debugger detaches. You need to be very careful
with any kind of lock you consider, because failing here is most
going to mean pressing the reset button.
</para>
</sect1>
</chapter>
<chapter id="credits">
<title>Credits</title>
<para>
The following people have contributed to this document:
<orderedlist>
<listitem><para>Amit Kale<email>amitkale@linsyssoft.com</email></para></listitem>
<listitem><para>Tom Rini<email>trini@kernel.crashing.org</email></para></listitem>
</orderedlist>
In March 2008 this document was completely rewritten by:
<itemizedlist>
<listitem><para>Jason Wessel<email>jason.wessel@windriver.com</email></para></listitem>
</itemizedlist>
</para>
</chapter>
</book>
Documentation/DocBook/mac80211.tmpl 0 → 100644
浏览文件 @ 36d99df2
<?xml version="1.0" encoding="UTF-8"?>
<!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="mac80211-developers-guide">
<bookinfo>
<title>The mac80211 subsystem for kernel developers</title>
<authorgroup>
<author>
<firstname>Johannes</firstname>
<surname>Berg</surname>
<affiliation>
<address><email>johannes@sipsolutions.net</email></address>
</affiliation>
</author>
</authorgroup>
<copyright>
<year>2007</year>
<year>2008</year>
<holder>Johannes Berg</holder>
</copyright>
<legalnotice>
<para>
This documentation is free software; you can redistribute
it and/or modify it under the terms of the GNU General Public
License version 2 as published by the Free Software Foundation.
</para>
<para>
This documentation 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 documentation; 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.
</para>
</legalnotice>
<abstract>
!Pinclude/net/mac80211.h Introduction
!Pinclude/net/mac80211.h Warning
</abstract>
</bookinfo>
<toc></toc>
<!--
Generally, this document shall be ordered by increasing complexity.
It is important to note that readers should be able to read only
the first few sections to get a working driver and only advanced
usage should require reading the full document.
-->
<part>
<title>The basic mac80211 driver interface</title>
<partintro>
<para>
You should read and understand the information contained
within this part of the book while implementing a driver.
In some chapters, advanced usage is noted, that may be
skipped at first.
</para>
<para>
This part of the book only covers station and monitor mode
functionality, additional information required to implement
the other modes is covered in the second part of the book.
</para>
</partintro>
<chapter id="basics">
<title>Basic hardware handling</title>
<para>TBD</para>
<para>
This chapter shall contain information on getting a hw
struct allocated and registered with mac80211.
</para>
<para>
Since it is required to allocate rates/modes before registering
a hw struct, this chapter shall also contain information on setting
up the rate/mode structs.
</para>
<para>
Additionally, some discussion about the callbacks and
the general programming model should be in here, including
the definition of ieee80211_ops which will be referred to
a lot.
</para>
<para>
Finally, a discussion of hardware capabilities should be done
with references to other parts of the book.
</para>
<!-- intentionally multiple !F lines to get proper order -->
!Finclude/net/mac80211.h ieee80211_hw
!Finclude/net/mac80211.h ieee80211_hw_flags
!Finclude/net/mac80211.h SET_IEEE80211_DEV
!Finclude/net/mac80211.h SET_IEEE80211_PERM_ADDR
!Finclude/net/mac80211.h ieee80211_ops
!Finclude/net/mac80211.h ieee80211_alloc_hw
!Finclude/net/mac80211.h ieee80211_register_hw
!Finclude/net/mac80211.h ieee80211_get_tx_led_name
!Finclude/net/mac80211.h ieee80211_get_rx_led_name
!Finclude/net/mac80211.h ieee80211_get_assoc_led_name
!Finclude/net/mac80211.h ieee80211_get_radio_led_name
!Finclude/net/mac80211.h ieee80211_unregister_hw
!Finclude/net/mac80211.h ieee80211_free_hw
</chapter>
<chapter id="phy-handling">
<title>PHY configuration</title>
<para>TBD</para>
<para>
This chapter should describe PHY handling including
start/stop callbacks and the various structures used.
</para>
!Finclude/net/mac80211.h ieee80211_conf
!Finclude/net/mac80211.h ieee80211_conf_flags
</chapter>
<chapter id="iface-handling">
<title>Virtual interfaces</title>
<para>TBD</para>
<para>
This chapter should describe virtual interface basics
that are relevant to the driver (VLANs, MGMT etc are not.)
It should explain the use of the add_iface/remove_iface
callbacks as well as the interface configuration callbacks.
</para>
<para>Things related to AP mode should be discussed there.</para>
<para>
Things related to supporting multiple interfaces should be
in the appropriate chapter, a BIG FAT note should be here about
this though and the recommendation to allow only a single
interface in STA mode at first!
</para>
!Finclude/net/mac80211.h ieee80211_if_types
!Finclude/net/mac80211.h ieee80211_if_init_conf
!Finclude/net/mac80211.h ieee80211_if_conf
</chapter>
<chapter id="rx-tx">
<title>Receive and transmit processing</title>
<sect1>
<title>what should be here</title>
<para>TBD</para>
<para>
This should describe the receive and transmit
paths in mac80211/the drivers as well as
transmit status handling.
</para>
</sect1>
<sect1>
<title>Frame format</title>
!Pinclude/net/mac80211.h Frame format
</sect1>
<sect1>
<title>Alignment issues</title>
<para>TBD</para>
</sect1>
<sect1>
<title>Calling into mac80211 from interrupts</title>
!Pinclude/net/mac80211.h Calling mac80211 from interrupts
</sect1>
<sect1>
<title>functions/definitions</title>
!Finclude/net/mac80211.h ieee80211_rx_status
!Finclude/net/mac80211.h mac80211_rx_flags
!Finclude/net/mac80211.h ieee80211_tx_control
!Finclude/net/mac80211.h ieee80211_tx_status_flags
!Finclude/net/mac80211.h ieee80211_rx
!Finclude/net/mac80211.h ieee80211_rx_irqsafe
!Finclude/net/mac80211.h ieee80211_tx_status
!Finclude/net/mac80211.h ieee80211_tx_status_irqsafe
!Finclude/net/mac80211.h ieee80211_rts_get
!Finclude/net/mac80211.h ieee80211_rts_duration
!Finclude/net/mac80211.h ieee80211_ctstoself_get
!Finclude/net/mac80211.h ieee80211_ctstoself_duration
!Finclude/net/mac80211.h ieee80211_generic_frame_duration
!Finclude/net/mac80211.h ieee80211_get_hdrlen_from_skb
!Finclude/net/mac80211.h ieee80211_get_hdrlen
!Finclude/net/mac80211.h ieee80211_wake_queue
!Finclude/net/mac80211.h ieee80211_stop_queue
!Finclude/net/mac80211.h ieee80211_start_queues
!Finclude/net/mac80211.h ieee80211_stop_queues
!Finclude/net/mac80211.h ieee80211_wake_queues
</sect1>
</chapter>
<chapter id="filters">
<title>Frame filtering</title>
!Pinclude/net/mac80211.h Frame filtering
!Finclude/net/mac80211.h ieee80211_filter_flags
</chapter>
</part>
<part id="advanced">
<title>Advanced driver interface</title>
<partintro>
<para>
Information contained within this part of the book is
of interest only for advanced interaction of mac80211
with drivers to exploit more hardware capabilities and
improve performance.
</para>
</partintro>
<chapter id="hardware-crypto-offload">
<title>Hardware crypto acceleration</title>
!Pinclude/net/mac80211.h Hardware crypto acceleration
<!-- intentionally multiple !F lines to get proper order -->
!Finclude/net/mac80211.h set_key_cmd
!Finclude/net/mac80211.h ieee80211_key_conf
!Finclude/net/mac80211.h ieee80211_key_alg
!Finclude/net/mac80211.h ieee80211_key_flags
</chapter>
<chapter id="qos">
<title>Multiple queues and QoS support</title>
<para>TBD</para>
!Finclude/net/mac80211.h ieee80211_tx_queue_params
!Finclude/net/mac80211.h ieee80211_tx_queue_stats_data
!Finclude/net/mac80211.h ieee80211_tx_queue
</chapter>
<chapter id="AP">
<title>Access point mode support</title>
<para>TBD</para>
<para>Some parts of the if_conf should be discussed here instead</para>
<para>
Insert notes about VLAN interfaces with hw crypto here or
in the hw crypto chapter.
</para>
!Finclude/net/mac80211.h ieee80211_get_buffered_bc
!Finclude/net/mac80211.h ieee80211_beacon_get
</chapter>
<chapter id="multi-iface">
<title>Supporting multiple virtual interfaces</title>
<para>TBD</para>
<para>
Note: WDS with identical MAC address should almost always be OK
</para>
<para>
Insert notes about having multiple virtual interfaces with
different MAC addresses here, note which configurations are
supported by mac80211, add notes about supporting hw crypto
with it.
</para>
</chapter>
<chapter id="hardware-scan-offload">
<title>Hardware scan offload</title>
<para>TBD</para>
!Finclude/net/mac80211.h ieee80211_scan_completed
</chapter>
</part>
<part id="rate-control">
<title>Rate control interface</title>
<partintro>
<para>TBD</para>
<para>
This part of the book describes the rate control algorithm
interface and how it relates to mac80211 and drivers.
</para>
</partintro>
<chapter id="dummy">
<title>dummy chapter</title>
<para>TBD</para>
</chapter>
</part>
<part id="internal">
<title>Internals</title>
<partintro>
<para>TBD</para>
<para>
This part of the book describes mac80211 internals.
</para>
</partintro>
<chapter id="key-handling">
<title>Key handling</title>
<sect1>
<title>Key handling basics</title>
!Pnet/mac80211/key.c Key handling basics
</sect1>
<sect1>
<title>MORE TBD</title>
<para>TBD</para>
</sect1>
</chapter>
<chapter id="rx-processing">
<title>Receive processing</title>
<para>TBD</para>
</chapter>
<chapter id="tx-processing">
<title>Transmit processing</title>
<para>TBD</para>
</chapter>
<chapter id="sta-info">
<title>Station info handling</title>
<sect1>
<title>Programming information</title>
!Fnet/mac80211/sta_info.h sta_info
!Fnet/mac80211/sta_info.h ieee80211_sta_info_flags
</sect1>
<sect1>
<title>STA information lifetime rules</title>
!Pnet/mac80211/sta_info.c STA information lifetime rules
</sect1>
</chapter>
<chapter id="synchronisation">
<title>Synchronisation</title>
<para>TBD</para>
<para>Locking, lots of RCU</para>
</chapter>
</part>
</book>
Documentation/DocBook/writing_usb_driver.tmpl
浏览文件 @ 36d99df2
......@@ -100,8 +100,8 @@
useful documents, at the USB home page (see Resources). An excellent
introduction to the Linux USB subsystem can be found at the USB Working
Devices List (see Resources). It explains how the Linux USB subsystem is
structured and introduces the reader to the concept of USB urbs, which
are essential to USB drivers.
structured and introduces the reader to the concept of USB urbs
(USB Request Blocks), which are essential to USB drivers.
</para>
<para>
The first thing a Linux USB driver needs to do is register itself with
......@@ -162,8 +162,8 @@ static int __init usb_skel_init(void)
module_init(usb_skel_init);
</programlisting>
<para>
When the driver is unloaded from the system, it needs to unregister
itself with the USB subsystem. This is done with the usb_unregister
When the driver is unloaded from the system, it needs to deregister
itself with the USB subsystem. This is done with the usb_deregister
function:
</para>
<programlisting>
......@@ -232,7 +232,7 @@ static int skel_probe(struct usb_interface *interface,
were passed to the USB subsystem will be called from a user program trying
to talk to the device. The first function called will be open, as the
program tries to open the device for I/O. We increment our private usage
count and save off a pointer to our internal structure in the file
count and save a pointer to our internal structure in the file
structure. This is done so that future calls to file operations will
enable the driver to determine which device the user is addressing. All
of this is done with the following code:
......@@ -252,8 +252,8 @@ file->private_data = dev;
send to the device based on the size of the write urb it has created (this
size depends on the size of the bulk out end point that the device has).
Then it copies the data from user space to kernel space, points the urb to
the data and submits the urb to the USB subsystem. This can be shown in
he following code:
the data and submits the urb to the USB subsystem. This can be seen in
the following code:
</para>
<programlisting>
/* we can only write as much as 1 urb will hold */
......
Documentation/PCI/00-INDEX 0 → 100644
浏览文件 @ 36d99df2
00-INDEX
- this file
PCI-DMA-mapping.txt
- info for PCI drivers using DMA portably across all platforms
PCIEBUS-HOWTO.txt
- a guide describing the PCI Express Port Bus driver
pci-error-recovery.txt
- info on PCI error recovery
pci.txt
- info on the PCI subsystem for device driver authors
pcieaer-howto.txt
- the PCI Express Advanced Error Reporting Driver Guide HOWTO
Documentation/PCIEBUS-HOWTO.txt → Documentation/PCI/PCIEBUS-HOWTO.txt
浏览文件 @ 36d99df2
......@@ -56,9 +56,9 @@ advantages of using the PCI Express Port Bus driver are listed below:
- Allow service drivers implemented in an independent
staged approach.
- Allow one service driver to run on multiple PCI-PCI Bridge
Port devices.
Port devices.
- Manage and distribute resources of a PCI-PCI Bridge Port
device to requested service drivers.
......@@ -82,7 +82,7 @@ Model requires some minimal changes on existing service drivers that
imposes no impact on the functionality of existing service drivers.
A service driver is required to use the two APIs shown below to
register its service with the PCI Express Port Bus driver (see
register its service with the PCI Express Port Bus driver (see
section 5.2.1 & 5.2.2). It is important that a service driver
initializes the pcie_port_service_driver data structure, included in
header file /include/linux/pcieport_if.h, before calling these APIs.
......@@ -137,7 +137,7 @@ driver.
static int __init aerdrv_service_init(void)
{
int retval = 0;
retval = pcie_port_service_register(&root_aerdrv);
if (!retval) {
/*
......@@ -147,7 +147,7 @@ static int __init aerdrv_service_init(void)
return retval;
}
static void __exit aerdrv_service_exit(void)
static void __exit aerdrv_service_exit(void)
{
pcie_port_service_unregister(&root_aerdrv);
}
......@@ -175,7 +175,7 @@ same physical Root Port. Both service drivers call pci_enable_msi to
request MSI based interrupts. A service driver may not know whether
any other service drivers have run on this Root Port. If either one
of them calls pci_disable_msi, it puts the other service driver
in a wrong interrupt mode.
in a wrong interrupt mode.
To avoid this situation all service drivers are not permitted to
switch interrupt mode on its device. The PCI Express Port Bus driver
......
Documentation/pci.txt → Documentation/PCI/pci.txt
浏览文件 @ 36d99df2
......@@ -119,7 +119,7 @@ initialization with a pointer to a structure describing the driver
the power state of a device before reboot.
e.g. drivers/net/e100.c.
err_handler See Documentation/pci-error-recovery.txt
err_handler See Documentation/PCI/pci-error-recovery.txt
The ID table is an array of struct pci_device_id entries ending with an
......
Documentation/pcieaer-howto.txt → Documentation/PCI/pcieaer-howto.txt
浏览文件 @ 36d99df2
......@@ -13,7 +13,7 @@ Reporting (AER) driver and provides information on how to use it, as
well as how to enable the drivers of endpoint devices to conform with
PCI Express AER driver.
1.2 Copyright © Intel Corporation 2006.
1.2 Copyright © Intel Corporation 2006.
1.3 What is the PCI Express AER Driver?
......
Documentation/SubmittingPatches
浏览文件 @ 36d99df2
......@@ -183,7 +183,7 @@ Even if the maintainer did not respond in step #4, make sure to ALWAYS
copy the maintainer when you change their code.
For small patches you may want to CC the Trivial Patch Monkey
trivial@kernel.org managed by Adrian Bunk; which collects "trivial"
trivial@kernel.org managed by Jesper Juhl; which collects "trivial"
patches. Trivial patches must qualify for one of the following rules:
Spelling fixes in documentation
Spelling fixes which could break grep(1)
......@@ -196,7 +196,7 @@ patches. Trivial patches must qualify for one of the following rules:
since people copy, as long as it's trivial)
Any fix by the author/maintainer of the file (ie. patch monkey
in re-transmission mode)
URL: <http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/>
URL: <http://www.kernel.org/pub/linux/kernel/people/juhl/trivial/>
......
Documentation/block/biodoc.txt
浏览文件 @ 36d99df2
......@@ -1097,7 +1097,7 @@ lock themselves, if required. Drivers that explicitly used the
io_request_lock for serialization need to be modified accordingly.
Usually it's as easy as adding a global lock:
static spinlock_t my_driver_lock = SPIN_LOCK_UNLOCKED;
static DEFINE_SPINLOCK(my_driver_lock);
and passing the address to that lock to blk_init_queue().
......
Documentation/cdrom/cdrom-standard.tex
浏览文件 @ 36d99df2
......@@ -777,7 +777,7 @@ Note that a driver must have one static structure, $<device>_dops$, while
it may have as many structures $<device>_info$ as there are minor devices
active. $Register_cdrom()$ builds a linked list from these.
\subsection{$Int\ unregister_cdrom(struct\ cdrom_device_info * cdi)$}
\subsection{$Void\ unregister_cdrom(struct\ cdrom_device_info * cdi)$}
Unregistering device $cdi$ with minor number $MINOR(cdi\to dev)$ removes
the minor device from the list. If it was the last registered minor for
......
Documentation/cli-sti-removal.txt
浏览文件 @ 36d99df2
......@@ -43,7 +43,7 @@ would execute while the cli()-ed section is executing.
but from now on a more direct method of locking has to be used:
spinlock_t driver_lock = SPIN_LOCK_UNLOCKED;
DEFINE_SPINLOCK(driver_lock);
struct driver_data;
irq_handler (...)
......
Documentation/cpusets.txt
浏览文件 @ 36d99df2
......@@ -8,6 +8,7 @@ Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
Modified by Paul Jackson <pj@sgi.com>
Modified by Christoph Lameter <clameter@sgi.com>
Modified by Paul Menage <menage@google.com>
Modified by Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
CONTENTS:
=========
......@@ -20,7 +21,8 @@ CONTENTS:
1.5 What is memory_pressure ?
1.6 What is memory spread ?
1.7 What is sched_load_balance ?
1.8 How do I use cpusets ?
1.8 What is sched_relax_domain_level ?
1.9 How do I use cpusets ?
2. Usage Examples and Syntax
2.1 Basic Usage
2.2 Adding/removing cpus
......@@ -497,7 +499,73 @@ the cpuset code to update these sched domains, it compares the new
partition requested with the current, and updates its sched domains,
removing the old and adding the new, for each change.
1.8 How do I use cpusets ?
1.8 What is sched_relax_domain_level ?
--------------------------------------
In sched domain, the scheduler migrates tasks in 2 ways; periodic load
balance on tick, and at time of some schedule events.
When a task is woken up, scheduler try to move the task on idle CPU.
For example, if a task A running on CPU X activates another task B
on the same CPU X, and if CPU Y is X's sibling and performing idle,
then scheduler migrate task B to CPU Y so that task B can start on
CPU Y without waiting task A on CPU X.
And if a CPU run out of tasks in its runqueue, the CPU try to pull
extra tasks from other busy CPUs to help them before it is going to
be idle.
Of course it takes some searching cost to find movable tasks and/or
idle CPUs, the scheduler might not search all CPUs in the domain
everytime. In fact, in some architectures, the searching ranges on
events are limited in the same socket or node where the CPU locates,
while the load balance on tick searchs all.
For example, assume CPU Z is relatively far from CPU X. Even if CPU Z
is idle while CPU X and the siblings are busy, scheduler can't migrate
woken task B from X to Z since it is out of its searching range.
As the result, task B on CPU X need to wait task A or wait load balance
on the next tick. For some applications in special situation, waiting
1 tick may be too long.
The 'sched_relax_domain_level' file allows you to request changing
this searching range as you like. This file takes int value which
indicates size of searching range in levels ideally as follows,
otherwise initial value -1 that indicates the cpuset has no request.
-1 : no request. use system default or follow request of others.
0 : no search.
1 : search siblings (hyperthreads in a core).
2 : search cores in a package.
3 : search cpus in a node [= system wide on non-NUMA system]
( 4 : search nodes in a chunk of node [on NUMA system] )
( 5~ : search system wide [on NUMA system])
This file is per-cpuset and affect the sched domain where the cpuset
belongs to. Therefore if the flag 'sched_load_balance' of a cpuset
is disabled, then 'sched_relax_domain_level' have no effect since
there is no sched domain belonging the cpuset.
If multiple cpusets are overlapping and hence they form a single sched
domain, the largest value among those is used. Be careful, if one
requests 0 and others are -1 then 0 is used.
Note that modifying this file will have both good and bad effects,
and whether it is acceptable or not will be depend on your situation.
Don't modify this file if you are not sure.
If your situation is:
- The migration costs between each cpu can be assumed considerably
small(for you) due to your special application's behavior or
special hardware support for CPU cache etc.
- The searching cost doesn't have impact(for you) or you can make
the searching cost enough small by managing cpuset to compact etc.
- The latency is required even it sacrifices cache hit rate etc.
then increasing 'sched_relax_domain_level' would benefit you.
1.9 How do I use cpusets ?
--------------------------
In order to minimize the impact of cpusets on critical kernel
......
Documentation/debugging-via-ohci1394.txt
浏览文件 @ 36d99df2
......@@ -41,15 +41,19 @@ to a working state and enables physical DMA by default for all remote nodes.
This can be turned off by ohci1394's module parameter phys_dma=0.
The alternative firewire-ohci driver in drivers/firewire uses filtered physical
DMA, hence is not yet suitable for remote debugging.
DMA by default, which is more secure but not suitable for remote debugging.
Compile the driver with CONFIG_FIREWIRE_OHCI_REMOTE_DMA (Kernel hacking menu:
Remote debugging over FireWire with firewire-ohci) to get unfiltered physical
DMA.
Because ohci1394 depends on the PCI enumeration to be completed, an
initialization routine which runs pretty early (long before console_init()
which makes the printk buffer appear on the console can be called) was written.
Because ohci1394 and firewire-ohci depend on the PCI enumeration to be
completed, an initialization routine which runs pretty early has been
implemented for x86. This routine runs long before console_init() can be
called, i.e. before the printk buffer appears on the console.
To activate it, enable CONFIG_PROVIDE_OHCI1394_DMA_INIT (Kernel hacking menu:
Provide code for enabling DMA over FireWire early on boot) and pass the
parameter "ohci1394_dma=early" to the recompiled kernel on boot.
Remote debugging over FireWire early on boot) and pass the parameter
"ohci1394_dma=early" to the recompiled kernel on boot.
Tools
-----
......
Documentation/dontdiff
浏览文件 @ 36d99df2
......@@ -47,7 +47,6 @@
.mm
53c700_d.h
53c8xx_d.h*
BitKeeper
COPYING
CREDITS
CVS
......
Documentation/early-userspace/README
浏览文件 @ 36d99df2
......@@ -89,8 +89,8 @@ the 2.7 era (it missed the boat for 2.5).
You can obtain somewhat infrequent snapshots of klibc from
ftp://ftp.kernel.org/pub/linux/libs/klibc/
For active users, you are better off using the klibc BitKeeper
repositories, at http://klibc.bkbits.net/
For active users, you are better off using the klibc git
repository, at http://git.kernel.org/?p=libs/klibc/klibc.git
The standalone klibc distribution currently provides three components,
in addition to the klibc library:
......
Documentation/feature-removal-schedule.txt
浏览文件 @ 36d99df2
......@@ -203,16 +203,8 @@ Who: linuxppc-dev@ozlabs.org
---------------------------
What: sk98lin network driver
When: Feburary 2008
Why: In kernel tree version of driver is unmaintained. Sk98lin driver
replaced by the skge driver.
Who: Stephen Hemminger <shemminger@linux-foundation.org>
---------------------------
What: i386/x86_64 bzImage symlinks
When: April 2008
When: April 2010
Why: The i386/x86_64 merge provides a symlink to the old bzImage
location so not yet updated user space tools, e.g. package
......@@ -221,8 +213,6 @@ Who: Thomas Gleixner <tglx@linutronix.de>
---------------------------
---------------------------
What: i2c-i810, i2c-prosavage and i2c-savage4
When: May 2008
Why: These drivers are superseded by i810fb, intelfb and savagefb.
......@@ -230,33 +220,6 @@ Who: Jean Delvare <khali@linux-fr.org>
---------------------------
What: bcm43xx wireless network driver
When: 2.6.26
Files: drivers/net/wireless/bcm43xx
Why: This driver's functionality has been replaced by the
mac80211-based b43 and b43legacy drivers.
Who: John W. Linville <linville@tuxdriver.com>
---------------------------
What: ieee80211 softmac wireless networking component
When: 2.6.26 (or after removal of bcm43xx and port of zd1211rw to mac80211)
Files: net/ieee80211/softmac
Why: No in-kernel drivers will depend on it any longer.
Who: John W. Linville <linville@tuxdriver.com>
---------------------------
What: rc80211-simple rate control algorithm for mac80211
When: 2.6.26
Files: net/mac80211/rc80211-simple.c
Why: This algorithm was provided for reference but always exhibited bad
responsiveness and performance and has some serious flaws. It has been
replaced by rc80211-pid.
Who: Stefano Brivio <stefano.brivio@polimi.it>
---------------------------
What (Why):
- include/linux/netfilter_ipv4/ipt_TOS.h ipt_tos.h header files
(superseded by xt_TOS/xt_tos target & match)
......@@ -298,17 +261,6 @@ Who: Michael Buesch <mb@bu3sch.de>
---------------------------
What: Solaris/SunOS syscall and binary support on Sparc
When: 2.6.26
Why: Largely unmaintained and almost entirely unused. File system
layering used to divert library and dynamic linker searches to
/usr/gnemul is extremely buggy and unfixable. Making it work
is largely pointless as without a lot of work only the most
trivial of Solaris binaries can work with the emulation code.
Who: David S. Miller <davem@davemloft.net>
---------------------------
What: init_mm export
When: 2.6.26
Why: Not used in-tree. The current out-of-tree users used it to
......@@ -318,3 +270,28 @@ Why: Not used in-tree. The current out-of-tree users used it to
code / infrastructure should be in the kernel and not in some
out-of-tree driver.
Who: Thomas Gleixner <tglx@linutronix.de>
----------------------------
What: usedac i386 kernel parameter
When: 2.6.27
Why: replaced by allowdac and no dac combination
Who: Glauber Costa <gcosta@redhat.com>
---------------------------
What: /sys/o2cb symlink
When: January 2010
Why: /sys/fs/o2cb is the proper location for this information - /sys/o2cb
exists as a symlink for backwards compatibility for old versions of
ocfs2-tools. 2 years should be sufficient time to phase in new versions
which know to look in /sys/fs/o2cb.
Who: ocfs2-devel@oss.oracle.com
---------------------------
What: asm/semaphore.h
When: 2.6.26
Why: Implementation became generic; users should now include
linux/semaphore.h instead.
Who: Matthew Wilcox <willy@linux.intel.com>
Documentation/filesystems/proc.txt
浏览文件 @ 36d99df2
......@@ -43,6 +43,7 @@ Table of Contents
2.13 /proc/<pid>/oom_score - Display current oom-killer score
2.14 /proc/<pid>/io - Display the IO accounting fields
2.15 /proc/<pid>/coredump_filter - Core dump filtering settings
2.16 /proc/<pid>/mountinfo - Information about mounts
------------------------------------------------------------------------------
Preface
......@@ -2348,4 +2349,41 @@ For example:
$ echo 0x7 > /proc/self/coredump_filter
$ ./some_program
2.16 /proc/<pid>/mountinfo - Information about mounts
--------------------------------------------------------
This file contains lines of the form:
36 35 98:0 /mnt1 /mnt2 rw,noatime master:1 - ext3 /dev/root rw,errors=continue
(1)(2)(3) (4) (5) (6) (7) (8) (9) (10) (11)
(1) mount ID: unique identifier of the mount (may be reused after umount)
(2) parent ID: ID of parent (or of self for the top of the mount tree)
(3) major:minor: value of st_dev for files on filesystem
(4) root: root of the mount within the filesystem
(5) mount point: mount point relative to the process's root
(6) mount options: per mount options
(7) optional fields: zero or more fields of the form "tag[:value]"
(8) separator: marks the end of the optional fields
(9) filesystem type: name of filesystem of the form "type[.subtype]"
(10) mount source: filesystem specific information or "none"
(11) super options: per super block options
Parsers should ignore all unrecognised optional fields. Currently the
possible optional fields are:
shared:X mount is shared in peer group X
master:X mount is slave to peer group X
propagate_from:X mount is slave and receives propagation from peer group X (*)
unbindable mount is unbindable
(*) X is the closest dominant peer group under the process's root. If
X is the immediate master of the mount, or if there's no dominant peer
group under the same root, then only the "master:X" field is present
and not the "propagate_from:X" field.
For more information on mount propagation see:
Documentation/filesystems/sharedsubtree.txt
------------------------------------------------------------------------------
Documentation/filesystems/sysfs.txt
浏览文件 @ 36d99df2
......@@ -176,8 +176,10 @@ implementations:
Recall that an attribute should only be exporting one value, or an
array of similar values, so this shouldn't be that expensive.
This allows userspace to do partial reads and seeks arbitrarily over
the entire file at will.
This allows userspace to do partial reads and forward seeks
arbitrarily over the entire file at will. If userspace seeks back to
zero or does a pread(2) with an offset of '0' the show() method will
be called again, rearmed, to fill the buffer.
- On write(2), sysfs expects the entire buffer to be passed during the
first write. Sysfs then passes the entire buffer to the store()
......@@ -192,6 +194,9 @@ implementations:
Other notes:
- Writing causes the show() method to be rearmed regardless of current
file position.
- The buffer will always be PAGE_SIZE bytes in length. On i386, this
is 4096.
......
Documentation/filesystems/xfs.txt
浏览文件 @ 36d99df2
......@@ -52,16 +52,15 @@ When mounting an XFS filesystem, the following options are accepted.
and also gets the setgid bit set if it is a directory itself.
ihashsize=value
Sets the number of hash buckets available for hashing the
in-memory inodes of the specified mount point. If a value
of zero is used, the value selected by the default algorithm
will be displayed in /proc/mounts.
In memory inode hashes have been removed, so this option has
no function as of August 2007. Option is deprecated.
ikeep/noikeep
When inode clusters are emptied of inodes, keep them around
on the disk (ikeep) - this is the traditional XFS behaviour
and is still the default for now. Using the noikeep option,
inode clusters are returned to the free space pool.
When ikeep is specified, XFS does not delete empty inode clusters
and keeps them around on disk. ikeep is the traditional XFS
behaviour. When noikeep is specified, empty inode clusters
are returned to the free space pool. The default is noikeep for
non-DMAPI mounts, while ikeep is the default when DMAPI is in use.
inode64
Indicates that XFS is allowed to create inodes at any location
......
Documentation/highuid.txt
浏览文件 @ 36d99df2
......@@ -28,8 +28,6 @@ What's left to be done for 32-bit UIDs on all Linux architectures:
uses the 32-bit UID system calls properly otherwise.
This affects at least:
SunOS emulation
Solaris emulation
iBCS on Intel
sparc32 emulation on sparc64
......
Documentation/i386/boot.txt
浏览文件 @ 36d99df2
......@@ -170,6 +170,8 @@ Offset Proto Name Meaning
0238/4 2.06+ cmdline_size Maximum size of the kernel command line
023C/4 2.07+ hardware_subarch Hardware subarchitecture
0240/8 2.07+ hardware_subarch_data Subarchitecture-specific data
0248/4 2.08+ payload_offset Offset of kernel payload
024C/4 2.08+ payload_length Length of kernel payload
(1) For backwards compatibility, if the setup_sects field contains 0, the
real value is 4.
......@@ -512,6 +514,32 @@ Protocol: 2.07+
A pointer to data that is specific to hardware subarch
Field name: payload_offset
Type: read
Offset/size: 0x248/4
Protocol: 2.08+
If non-zero then this field contains the offset from the end of the
real-mode code to the payload.
The payload may be compressed. The format of both the compressed and
uncompressed data should be determined using the standard magic
numbers. Currently only gzip compressed ELF is used.
Field name: payload_length
Type: read
Offset/size: 0x24c/4
Protocol: 2.08+
The length of the payload.
**** THE IMAGE CHECKSUM
From boot protocol version 2.08 onwards the CRC-32 is calculated over
the entire file using the characteristic polynomial 0x04C11DB7 and an
initial remainder of 0xffffffff. The checksum is appended to the
file; therefore the CRC of the file up to the limit specified in the
syssize field of the header is always 0.
**** THE KERNEL COMMAND LINE
......
Documentation/ide/ide.txt
浏览文件 @ 36d99df2
......@@ -71,29 +71,6 @@ This driver automatically probes for most IDE interfaces (including all PCI
ones), for the drives/geometries attached to those interfaces, and for the IRQ
lines being used by the interfaces (normally 14, 15 for ide0/ide1).
For special cases, interfaces may be specified using kernel "command line"
options. For example,
ide3=0x168,0x36e,10 /* ioports 0x168-0x16f,0x36e, irq 10 */
Normally the irq number need not be specified, as ide.c will probe for it:
ide3=0x168,0x36e /* ioports 0x168-0x16f,0x36e */
The standard port, and irq values are these:
ide0=0x1f0,0x3f6,14
ide1=0x170,0x376,15
ide2=0x1e8,0x3ee,11
ide3=0x168,0x36e,10
Note that the first parameter reserves 8 contiguous ioports, whereas the
second value denotes a single ioport. If in doubt, do a 'cat /proc/ioports'.
In all probability the device uses these ports and IRQs if it is attached
to the appropriate ide channel. Pass the parameter for the correct ide
channel to the kernel, as explained above.
Any number of interfaces may share a single IRQ if necessary, at a slight
performance penalty, whether on separate cards or a single VLB card.
The IDE driver automatically detects and handles this. However, this may
......@@ -184,13 +161,6 @@ provided it is mounted with the default block size of 1024 (as above).
Please pass on any feedback on any of this stuff to the maintainer,
whose address can be found in linux/MAINTAINERS.
Note that if BOTH hd.c and ide.c are configured into the kernel,
hd.c will normally be allowed to control the primary IDE interface.
This is useful for older hardware that may be incompatible with ide.c,
and still allows newer hardware to run on the 2nd/3rd/4th IDE ports
under control of ide.c. To have ide.c also "take over" the primary
IDE port in this situation, use the "command line" parameter: ide0=0x1f0
The IDE driver is modularized. The high level disk/CD-ROM/tape/floppy
drivers can always be compiled as loadable modules, the chipset drivers
can only be compiled into the kernel, and the core code (ide.c) can be
......@@ -206,7 +176,7 @@ When ide.c is used as a module, you can pass command line parameters to the
driver using the "options=" keyword to insmod, while replacing any ',' with
';'. For example:
insmod ide.o options="ide0=serialize ide1=serialize ide2=0x1e8;0x3ee;11"
insmod ide.o options="hda=nodma hdb=nodma"
================================================================================
......@@ -247,21 +217,11 @@ Summary of ide driver parameters for kernel command line
As for VLB, it is safest to not specify it.
Bigger values are safer than smaller ones.
"idex=base" : probe for an interface at the addr specified,
where "base" is usually 0x1f0 or 0x170
and "ctl" is assumed to be "base"+0x206
"idex=base,ctl" : specify both base and ctl
"idex=base,ctl,irq" : specify base, ctl, and irq number
"idex=serialize" : do not overlap operations on idex. Please note
that you will have to specify this option for
both the respective primary and secondary channel
to take effect.
"idex=four" : four drives on idex and ide(x^1) share same ports
"idex=reset" : reset interface after probe
"idex=ata66" : informs the interface that it has an 80c cable
......@@ -269,8 +229,6 @@ Summary of ide driver parameters for kernel command line
ability to bit test for detection is currently
unknown.
"ide=reverse" : formerly called to pci sub-system, but now local.
"ide=doubler" : probe/support IDE doublers on Amiga
There may be more options than shown -- use the source, Luke!
......@@ -290,6 +248,9 @@ Also for legacy CMD640 host driver (cmd640) you need to use "probe_vlb"
kernel paremeter to enable probing for VLB version of the chipset (PCI ones
are detected automatically).
You also need to use "probe" kernel parameter for ide-4drives driver
(support for IDE generic chipset with four drives on one port).
================================================================================
Some Terminology
......
Documentation/ide/warm-plug-howto.txt 0 → 100644
浏览文件 @ 36d99df2
IDE warm-plug HOWTO
===================
To warm-plug devices on a port 'idex':
# echo -n "1" > /sys/class/ide_port/idex/delete_devices
unplug old device(s) and plug new device(s)
# echo -n "1" > /sys/class/ide_port/idex/scan
done
Documentation/kernel-parameters.txt
浏览文件 @ 36d99df2
......@@ -366,6 +366,12 @@ and is between 256 and 4096 characters. It is defined in the file
possible to determine what the correct size should be.
This option provides an override for these situations.
security= [SECURITY] Choose a security module to enable at boot.
If this boot parameter is not specified, only the first
security module asking for security registration will be
loaded. An invalid security module name will be treated
as if no module has been chosen.
capability.disable=
[SECURITY] Disable capabilities. This would normally
be used only if an alternative security model is to be
......@@ -763,11 +769,11 @@ and is between 256 and 4096 characters. It is defined in the file
Format: <io>[,<membase>[,<icn_id>[,<icn_id2>]]]
ide= [HW] (E)IDE subsystem
Format: ide=nodma or ide=doubler or ide=reverse
Format: ide=nodma or ide=doubler
See Documentation/ide/ide.txt.
ide?= [HW] (E)IDE subsystem
Format: ide?=noprobe or chipset specific parameters.
Format: ide?=ata66 or chipset specific parameters.
See Documentation/ide/ide.txt.
idebus= [HW] (E)IDE subsystem - VLB/PCI bus speed
......@@ -812,6 +818,19 @@ and is between 256 and 4096 characters. It is defined in the file
inttest= [IA64]
iommu= [x86]
off
force
noforce
biomerge
panic
nopanic
merge
nomerge
forcesac
soft
intel_iommu= [DMAR] Intel IOMMU driver (DMAR) option
off
Disable intel iommu driver.
......@@ -828,6 +847,10 @@ and is between 256 and 4096 characters. It is defined in the file
than 32 bit addressing. The default is to look
for translation below 32 bit and if not available
then look in the higher range.
strict [Default Off]
With this option on every unmap_single operation will
result in a hardware IOTLB flush operation as opposed
to batching them for performance.
io_delay= [X86-32,X86-64] I/O delay method
0x80
......@@ -928,8 +951,15 @@ and is between 256 and 4096 characters. It is defined in the file
kstack=N [X86-32,X86-64] Print N words from the kernel stack
in oops dumps.
kgdboc= [HW] kgdb over consoles.
Requires a tty driver that supports console polling.
(only serial suported for now)
Format: <serial_device>[,baud]
l2cr= [PPC]
l3cr= [PPC]
lapic [X86-32,APIC] Enable the local APIC even if BIOS
disabled it.
......@@ -1134,6 +1164,11 @@ and is between 256 and 4096 characters. It is defined in the file
or
memmap=0x10000$0x18690000
memtest= [KNL,X86_64] Enable memtest
Format: <integer>
range: 0,4 : pattern number
default : 0 <disable>
meye.*= [HW] Set MotionEye Camera parameters
See Documentation/video4linux/meye.txt.
......@@ -1251,8 +1286,16 @@ and is between 256 and 4096 characters. It is defined in the file
noexec [IA-64]
noexec [X86-32,X86-64]
On X86-32 available only on PAE configured kernels.
noexec=on: enable non-executable mappings (default)
noexec=off: disable nn-executable mappings
noexec=off: disable non-executable mappings
noexec32 [X86-64]
This affects only 32-bit executables.
noexec32=on: enable non-executable mappings (default)
read doesn't imply executable mappings
noexec32=off: disable non-executable mappings
read implies executable mappings
nofxsr [BUGS=X86-32] Disables x86 floating point extended
register save and restore. The kernel will only save
......@@ -1339,6 +1382,10 @@ and is between 256 and 4096 characters. It is defined in the file
nowb [ARM]
nptcg= [IA64] Override max number of concurrent global TLB
purges which is reported from either PAL_VM_SUMMARY or
SAL PALO.
numa_zonelist_order= [KNL, BOOT] Select zonelist order for NUMA.
one of ['zone', 'node', 'default'] can be specified
This can be set from sysctl after boot.
......@@ -1428,10 +1475,6 @@ and is between 256 and 4096 characters. It is defined in the file
nomsi [MSI] If the PCI_MSI kernel config parameter is
enabled, this kernel boot option can be used to
disable the use of MSI interrupts system-wide.
nosort [X86-32] Don't sort PCI devices according to
order given by the PCI BIOS. This sorting is
done to get a device order compatible with
older kernels.
biosirq [X86-32] Use PCI BIOS calls to get the interrupt
routing table. These calls are known to be buggy
on several machines and they hang the machine
......
Documentation/laptops/acer-wmi.txt
浏览文件 @ 36d99df2
......@@ -80,7 +80,7 @@ once you enable the radio, will depend on your hardware and driver combination.
e.g. With the BCM4318 on the Acer Aspire 5020 series:
ndiswrapper: Light blinks on when transmitting
bcm43xx/b43: Solid light, blinks off when transmitting
b43: Solid light, blinks off when transmitting
Wireless radio control is unconditionally enabled - all Acer laptops that support
acer-wmi come with built-in wireless. However, should you feel so inclined to
......
Documentation/magic-number.txt
浏览文件 @ 36d99df2
......@@ -95,7 +95,6 @@ RFCOMM_TTY_MAGIC 0x6d02 net/bluetooth/rfcomm/tty.c
USB_SERIAL_PORT_MAGIC 0x7301 usb_serial_port drivers/usb/serial/usb-serial.h
CG_MAGIC 0x00090255 ufs_cylinder_group include/linux/ufs_fs.h
A2232_MAGIC 0x000a2232 gs_port drivers/char/ser_a2232.h
SOLARIS_SOCKET_MAGIC 0x000ADDED sol_socket_struct arch/sparc64/solaris/socksys.h
RPORT_MAGIC 0x00525001 r_port drivers/char/rocket_int.h
LSEMAGIC 0x05091998 lse drivers/fc4/fc.c
GDTIOCTL_MAGIC 0x06030f07 gdth_iowr_str drivers/scsi/gdth_ioctl.h
......
Documentation/memory-barriers.txt
浏览文件 @ 36d99df2
......@@ -430,8 +430,8 @@ There are certain things that the Linux kernel memory barriers do not guarantee:
[*] For information on bus mastering DMA and coherency please read:
Documentation/pci.txt
Documentation/DMA-mapping.txt
Documentation/PCI/pci.txt
Documentation/PCI/PCI-DMA-mapping.txt
Documentation/DMA-API.txt
......
Documentation/networking/00-INDEX
浏览文件 @ 36d99df2
......@@ -100,8 +100,6 @@ tuntap.txt
- TUN/TAP device driver, allowing user space Rx/Tx of packets.
vortex.txt
- info on using 3Com Vortex (3c590, 3c592, 3c595, 3c597) Ethernet cards.
wan-router.txt
- WAN router documentation
wavelan.txt
- AT&T GIS (nee NCR) WaveLAN card: An Ethernet-like radio transceiver
x25.txt
......
Documentation/networking/bcm43xx.txt 已删除 100644 → 0
浏览文件 @ 076d8423
BCM43xx Linux Driver Project
============================
Introduction
------------
Many of the wireless devices found in modern notebook computers are
based on the wireless chips produced by Broadcom. These devices have
been a problem for Linux users as there is no open-source driver
available. In addition, Broadcom has not released specifications
for the device, and driver availability has been limited to the
binary-only form used in the GPL versions of AP hardware such as the
Linksys WRT54G, and the Windows and OS X drivers. Before this project
began, the only way to use these devices were to use the Windows or
OS X drivers with either the Linuxant or ndiswrapper modules. There
is a strong penalty if this method is used as loading the binary-only
module "taints" the kernel, and no kernel developer will help diagnose
any kernel problems.
Development
-----------
This driver has been developed using
a clean-room technique that is described at
http://bcm-specs.sipsolutions.net/ReverseEngineeringProcess. For legal
reasons, none of the clean-room crew works on the on the Linux driver,
and none of the Linux developers sees anything but the specifications,
which are the ultimate product of the reverse-engineering group.
Software
--------
Since the release of the 2.6.17 kernel, the bcm43xx driver has been
distributed with the kernel source, and is prebuilt in most, if not
all, distributions. There is, however, additional software that is
required. The firmware used by the chip is the intellectual property
of Broadcom and they have not given the bcm43xx team redistribution
rights to this firmware. Since we cannot legally redistribute
the firmware we cannot include it with the driver. Furthermore, it
cannot be placed in the downloadable archives of any distributing
organization; therefore, the user is responsible for obtaining the
firmware and placing it in the appropriate location so that the driver
can find it when initializing.
To help with this process, the bcm43xx developers provide a separate
program named bcm43xx-fwcutter to "cut" the firmware out of a
Windows or OS X driver and write the extracted files to the proper
location. This program is usually provided with the distribution;
however, it may be downloaded from
http://developer.berlios.de/project/showfiles.php?group_id=4547
The firmware is available in two versions. V3 firmware is used with
the in-kernel bcm43xx driver that uses a software MAC layer called
SoftMAC, and will have a microcode revision of 0x127 or smaller. The
V4 firmware is used by an out-of-kernel driver employing a variation of
the Devicescape MAC layer known as d80211. Once bcm43xx-d80211 reaches
a satisfactory level of development, it will replace bcm43xx-softmac
in the kernel as it is much more flexible and powerful.
A source for the latest V3 firmware is
http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
Once this file is downloaded, the command
'bcm43xx-fwcutter -w <dir> <filename>'
will extract the microcode and write it to directory
<dir>. The correct directory will depend on your distribution;
however, most use '/lib/firmware'. Once this step is completed,
the bcm3xx driver should load when the system is booted. To see
any messages relating to the driver, issue the command 'dmesg |
grep bcm43xx' from a terminal window. If there are any problems,
please send that output to Bcm43xx-dev@lists.berlios.de.
Although the driver has been in-kernel since 2.6.17, the earliest
version is quite limited in its capability. Patches that include
all features of later versions are available for the stable kernel
versions from 2.6.18. These will be needed if you use a BCM4318,
or a PCI Express version (BCM4311 and BCM4312). In addition, if you
have an early BCM4306 and more than 1 GB RAM, your kernel will need
to be patched. These patches, which are being updated regularly,
are available at ftp://lwfinger.dynalias.org/patches. Look for
combined_2.6.YY.patch. Of course you will need kernel source downloaded
from kernel.org, or the source from your distribution.
If you build your own kernel, please enable CONFIG_BCM43XX_DEBUG
and CONFIG_IEEE80211_SOFTMAC_DEBUG. The log information provided is
essential for solving any problems.
Documentation/networking/wan-router.txt 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
Documentation/power/devices.txt
浏览文件 @ 36d99df2
......@@ -196,6 +196,11 @@ its parent; and can't be removed or suspended after that parent.
The policy is that the device tree should match hardware bus topology.
(Or at least the control bus, for devices which use multiple busses.)
In particular, this means that a device registration may fail if the parent of
the device is suspending (ie. has been chosen by the PM core as the next
device to suspend) or has already suspended, as well as after all of the other
devices have been suspended. Device drivers must be prepared to cope with such
situations.
Suspending Devices
......
Documentation/powerpc/phyp-assisted-dump.txt 0 → 100644
浏览文件 @ 36d99df2
Hypervisor-Assisted Dump
------------------------
November 2007
The goal of hypervisor-assisted dump is to enable the dump of
a crashed system, and to do so from a fully-reset system, and
to minimize the total elapsed time until the system is back
in production use.
As compared to kdump or other strategies, hypervisor-assisted
dump offers several strong, practical advantages:
-- Unlike kdump, the system has been reset, and loaded
with a fresh copy of the kernel. In particular,
PCI and I/O devices have been reinitialized and are
in a clean, consistent state.
-- As the dump is performed, the dumped memory becomes
immediately available to the system for normal use.
-- After the dump is completed, no further reboots are
required; the system will be fully usable, and running
in it's normal, production mode on it normal kernel.
The above can only be accomplished by coordination with,
and assistance from the hypervisor. The procedure is
as follows:
-- When a system crashes, the hypervisor will save
the low 256MB of RAM to a previously registered
save region. It will also save system state, system
registers, and hardware PTE's.
-- After the low 256MB area has been saved, the
hypervisor will reset PCI and other hardware state.
It will *not* clear RAM. It will then launch the
bootloader, as normal.
-- The freshly booted kernel will notice that there
is a new node (ibm,dump-kernel) in the device tree,
indicating that there is crash data available from
a previous boot. It will boot into only 256MB of RAM,
reserving the rest of system memory.
-- Userspace tools will parse /sys/kernel/release_region
and read /proc/vmcore to obtain the contents of memory,
which holds the previous crashed kernel. The userspace
tools may copy this info to disk, or network, nas, san,
iscsi, etc. as desired.
For Example: the values in /sys/kernel/release-region
would look something like this (address-range pairs).
CPU:0x177fee000-0x10000: HPTE:0x177ffe020-0x1000: /
DUMP:0x177fff020-0x10000000, 0x10000000-0x16F1D370A
-- As the userspace tools complete saving a portion of
dump, they echo an offset and size to
/sys/kernel/release_region to release the reserved
memory back to general use.
An example of this is:
"echo 0x40000000 0x10000000 > /sys/kernel/release_region"
which will release 256MB at the 1GB boundary.
Please note that the hypervisor-assisted dump feature
is only available on Power6-based systems with recent
firmware versions.
Implementation details:
----------------------
During boot, a check is made to see if firmware supports
this feature on this particular machine. If it does, then
we check to see if a active dump is waiting for us. If yes
then everything but 256 MB of RAM is reserved during early
boot. This area is released once we collect a dump from user
land scripts that are run. If there is dump data, then
the /sys/kernel/release_region file is created, and
the reserved memory is held.
If there is no waiting dump data, then only the highest
256MB of the ram is reserved as a scratch area. This area
is *not* released: this region will be kept permanently
reserved, so that it can act as a receptacle for a copy
of the low 256MB in the case a crash does occur. See,
however, "open issues" below, as to whether
such a reserved region is really needed.
Currently the dump will be copied from /proc/vmcore to a
a new file upon user intervention. The starting address
to be read and the range for each data point in provided
in /sys/kernel/release_region.
The tools to examine the dump will be same as the ones
used for kdump.
General notes:
--------------
Security: please note that there are potential security issues
with any sort of dump mechanism. In particular, plaintext
(unencrypted) data, and possibly passwords, may be present in
the dump data. Userspace tools must take adequate precautions to
preserve security.
Open issues/ToDo:
------------
o The various code paths that tell the hypervisor that a crash
occurred, vs. it simply being a normal reboot, should be
reviewed, and possibly clarified/fixed.
o Instead of using /sys/kernel, should there be a /sys/dump
instead? There is a dump_subsys being created by the s390 code,
perhaps the pseries code should use a similar layout as well.
o Is reserving a 256MB region really required? The goal of
reserving a 256MB scratch area is to make sure that no
important crash data is clobbered when the hypervisor
save low mem to the scratch area. But, if one could assure
that nothing important is located in some 256MB area, then
it would not need to be reserved. Something that can be
improved in subsequent versions.
o Still working the kdump team to integrate this with kdump,
some work remains but this would not affect the current
patches.
o Still need to write a shell script, to copy the dump away.
Currently I am parsing it manually.
Documentation/prctl/disable-tsc-ctxt-sw-stress-test.c 0 → 100644
浏览文件 @ 36d99df2
/*
* Tests for prctl(PR_GET_TSC, ...) / prctl(PR_SET_TSC, ...)
*
* Tests if the control register is updated correctly
* at context switches
*
* Warning: this test will cause a very high load for a few seconds
*
*/
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <inttypes.h>
#include <wait.h>
#include <sys/prctl.h>
#include <linux/prctl.h>
/* Get/set the process' ability to use the timestamp counter instruction */
#ifndef PR_GET_TSC
#define PR_GET_TSC 25
#define PR_SET_TSC 26
# define PR_TSC_ENABLE 1 /* allow the use of the timestamp counter */
# define PR_TSC_SIGSEGV 2 /* throw a SIGSEGV instead of reading the TSC */
#endif
uint64_t rdtsc() {
uint32_t lo, hi;
/* We cannot use "=A", since this would use %rax on x86_64 */
__asm__ __volatile__ ("rdtsc" : "=a" (lo), "=d" (hi));
return (uint64_t)hi << 32 | lo;
}
void sigsegv_expect(int sig)
{
/* */
}
void segvtask(void)
{
if (prctl(PR_SET_TSC, PR_TSC_SIGSEGV) < 0)
{
perror("prctl");
exit(0);
}
signal(SIGSEGV, sigsegv_expect);
alarm(10);
rdtsc();
fprintf(stderr, "FATAL ERROR, rdtsc() succeeded while disabled\n");
exit(0);
}
void sigsegv_fail(int sig)
{
fprintf(stderr, "FATAL ERROR, rdtsc() failed while enabled\n");
exit(0);
}
void rdtsctask(void)
{
if (prctl(PR_SET_TSC, PR_TSC_ENABLE) < 0)
{
perror("prctl");
exit(0);
}
signal(SIGSEGV, sigsegv_fail);
alarm(10);
for(;;) rdtsc();
}
int main(int argc, char **argv)
{
int n_tasks = 100, i;
fprintf(stderr, "[No further output means we're allright]\n");
for (i=0; i<n_tasks; i++)
if (fork() == 0)
{
if (i & 1)
segvtask();
else
rdtsctask();
}
for (i=0; i<n_tasks; i++)
wait(NULL);
exit(0);
}
Documentation/prctl/disable-tsc-on-off-stress-test.c 0 → 100644
浏览文件 @ 36d99df2
/*
* Tests for prctl(PR_GET_TSC, ...) / prctl(PR_SET_TSC, ...)
*
* Tests if the control register is updated correctly
* when set with prctl()
*
* Warning: this test will cause a very high load for a few seconds
*
*/
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <inttypes.h>
#include <wait.h>
#include <sys/prctl.h>
#include <linux/prctl.h>
/* Get/set the process' ability to use the timestamp counter instruction */
#ifndef PR_GET_TSC
#define PR_GET_TSC 25
#define PR_SET_TSC 26
# define PR_TSC_ENABLE 1 /* allow the use of the timestamp counter */
# define PR_TSC_SIGSEGV 2 /* throw a SIGSEGV instead of reading the TSC */
#endif
/* snippet from wikipedia :-) */
uint64_t rdtsc() {
uint32_t lo, hi;
/* We cannot use "=A", since this would use %rax on x86_64 */
__asm__ __volatile__ ("rdtsc" : "=a" (lo), "=d" (hi));
return (uint64_t)hi << 32 | lo;
}
int should_segv = 0;
void sigsegv_cb(int sig)
{
if (!should_segv)
{
fprintf(stderr, "FATAL ERROR, rdtsc() failed while enabled\n");
exit(0);
}
if (prctl(PR_SET_TSC, PR_TSC_ENABLE) < 0)
{
perror("prctl");
exit(0);
}
should_segv = 0;
rdtsc();
}
void task(void)
{
signal(SIGSEGV, sigsegv_cb);
alarm(10);
for(;;)
{
rdtsc();
if (should_segv)
{
fprintf(stderr, "FATAL ERROR, rdtsc() succeeded while disabled\n");
exit(0);
}
if (prctl(PR_SET_TSC, PR_TSC_SIGSEGV) < 0)
{
perror("prctl");
exit(0);
}
should_segv = 1;
}
}
int main(int argc, char **argv)
{
int n_tasks = 100, i;
fprintf(stderr, "[No further output means we're allright]\n");
for (i=0; i<n_tasks; i++)
if (fork() == 0)
task();
for (i=0; i<n_tasks; i++)
wait(NULL);
exit(0);
}
Documentation/prctl/disable-tsc-test.c 0 → 100644
浏览文件 @ 36d99df2
/*
* Tests for prctl(PR_GET_TSC, ...) / prctl(PR_SET_TSC, ...)
*
* Basic test to test behaviour of PR_GET_TSC and PR_SET_TSC
*/
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <inttypes.h>
#include <sys/prctl.h>
#include <linux/prctl.h>
/* Get/set the process' ability to use the timestamp counter instruction */
#ifndef PR_GET_TSC
#define PR_GET_TSC 25
#define PR_SET_TSC 26
# define PR_TSC_ENABLE 1 /* allow the use of the timestamp counter */
# define PR_TSC_SIGSEGV 2 /* throw a SIGSEGV instead of reading the TSC */
#endif
const char *tsc_names[] =
{
[0] = "[not set]",
[PR_TSC_ENABLE] = "PR_TSC_ENABLE",
[PR_TSC_SIGSEGV] = "PR_TSC_SIGSEGV",
};
uint64_t rdtsc() {
uint32_t lo, hi;
/* We cannot use "=A", since this would use %rax on x86_64 */
__asm__ __volatile__ ("rdtsc" : "=a" (lo), "=d" (hi));
return (uint64_t)hi << 32 | lo;
}
void sigsegv_cb(int sig)
{
int tsc_val = 0;
printf("[ SIG_SEGV ]\n");
printf("prctl(PR_GET_TSC, &tsc_val); ");
fflush(stdout);
if ( prctl(PR_GET_TSC, &tsc_val) == -1)
perror("prctl");
printf("tsc_val == %s\n", tsc_names[tsc_val]);
printf("prctl(PR_SET_TSC, PR_TSC_ENABLE)\n");
fflush(stdout);
if ( prctl(PR_SET_TSC, PR_TSC_ENABLE) == -1)
perror("prctl");
printf("rdtsc() == ");
}
int main(int argc, char **argv)
{
int tsc_val = 0;
signal(SIGSEGV, sigsegv_cb);
printf("rdtsc() == %llu\n", (unsigned long long)rdtsc());
printf("prctl(PR_GET_TSC, &tsc_val); ");
fflush(stdout);
if ( prctl(PR_GET_TSC, &tsc_val) == -1)
perror("prctl");
printf("tsc_val == %s\n", tsc_names[tsc_val]);
printf("rdtsc() == %llu\n", (unsigned long long)rdtsc());
printf("prctl(PR_SET_TSC, PR_TSC_ENABLE)\n");
fflush(stdout);
if ( prctl(PR_SET_TSC, PR_TSC_ENABLE) == -1)
perror("prctl");
printf("rdtsc() == %llu\n", (unsigned long long)rdtsc());
printf("prctl(PR_SET_TSC, PR_TSC_SIGSEGV)\n");
fflush(stdout);
if ( prctl(PR_SET_TSC, PR_TSC_SIGSEGV) == -1)
perror("prctl");
printf("rdtsc() == ");
fflush(stdout);
printf("%llu\n", (unsigned long long)rdtsc());
fflush(stdout);
exit(EXIT_SUCCESS);
}
Documentation/s390/s390dbf.txt
浏览文件 @ 36d99df2
......@@ -115,6 +115,27 @@ Return Value: Handle for generated debug area
Description: Allocates memory for a debug log
Must not be called within an interrupt handler
----------------------------------------------------------------------------
debug_info_t *debug_register_mode(char *name, int pages, int nr_areas,
int buf_size, mode_t mode, uid_t uid,
gid_t gid);
Parameter: name: Name of debug log (e.g. used for debugfs entry)
pages: Number of pages, which will be allocated per area
nr_areas: Number of debug areas
buf_size: Size of data area in each debug entry
mode: File mode for debugfs files. E.g. S_IRWXUGO
uid: User ID for debugfs files. Currently only 0 is
supported.
gid: Group ID for debugfs files. Currently only 0 is
supported.
Return Value: Handle for generated debug area
NULL if register failed
Description: Allocates memory for a debug log
Must not be called within an interrupt handler
---------------------------------------------------------------------------
void debug_unregister (debug_info_t * id);
......
Documentation/scheduler/sched-rt-group.txt
浏览文件 @ 36d99df2
Real-Time group scheduling
--------------------------
CONTENTS
========
Real-Time group scheduling.
1. Overview
1.1 The problem
1.2 The solution
2. The interface
2.1 System-wide settings
2.2 Default behaviour
2.3 Basis for grouping tasks
3. Future plans
The problem space:
In order to schedule multiple groups of realtime tasks each group must
be assigned a fixed portion of the CPU time available. Without a minimum
guarantee a realtime group can obviously fall short. A fuzzy upper limit
is of no use since it cannot be relied upon. Which leaves us with just
the single fixed portion.
1. Overview
===========
CPU time is divided by means of specifying how much time can be spent
running in a given period. Say a frame fixed realtime renderer must
deliver 25 frames a second, which yields a period of 0.04s. Now say
it will also have to play some music and respond to input, leaving it
with around 80% for the graphics. We can then give this group a runtime
of 0.8 * 0.04s = 0.032s.
This way the graphics group will have a 0.04s period with a 0.032s runtime
limit.
1.1 The problem
---------------
Now if the audio thread needs to refill the DMA buffer every 0.005s, but
needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s
= 0.00015s.
Realtime scheduling is all about determinism, a group has to be able to rely on
the amount of bandwidth (eg. CPU time) being constant. In order to schedule
multiple groups of realtime tasks, each group must be assigned a fixed portion
of the CPU time available. Without a minimum guarantee a realtime group can
obviously fall short. A fuzzy upper limit is of no use since it cannot be
relied upon. Which leaves us with just the single fixed portion.
1.2 The solution
----------------
The Interface:
CPU time is divided by means of specifying how much time can be spent running
in a given period. We allocate this "run time" for each realtime group which
the other realtime groups will not be permitted to use.
system wide:
Any time not allocated to a realtime group will be used to run normal priority
tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by
SCHED_OTHER.
/proc/sys/kernel/sched_rt_period_ms
/proc/sys/kernel/sched_rt_runtime_us
Let's consider an example: a frame fixed realtime renderer must deliver 25
frames a second, which yields a period of 0.04s per frame. Now say it will also
have to play some music and respond to input, leaving it with around 80% CPU
time dedicated for the graphics. We can then give this group a run time of 0.8
* 0.04s = 0.032s.
CONFIG_FAIR_USER_SCHED
This way the graphics group will have a 0.04s period with a 0.032s run time
limit. Now if the audio thread needs to refill the DMA buffer every 0.005s, but
needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s =
0.00015s. So this group can be scheduled with a period of 0.005s and a run time
of 0.00015s.
/sys/kernel/uids/<uid>/cpu_rt_runtime_us
The remaining CPU time will be used for user input and other tass. Because
realtime tasks have explicitly allocated the CPU time they need to perform
their tasks, buffer underruns in the graphocs or audio can be eliminated.
or
NOTE: the above example is not fully implemented as of yet (2.6.25). We still
lack an EDF scheduler to make non-uniform periods usable.
CONFIG_FAIR_CGROUP_SCHED
/cgroup/<cgroup>/cpu.rt_runtime_us
2. The Interface
================
[ time is specified in us because the interface is s32; this gives an
operating range of ~35m to 1us ]
The period takes values in [ 1, INT_MAX ], runtime in [ -1, INT_MAX - 1 ].
2.1 System wide settings
------------------------
A runtime of -1 specifies runtime == period, ie. no limit.
The system wide settings are configured under the /proc virtual file system:
New groups get the period from /proc/sys/kernel/sched_rt_period_us and
a runtime of 0.
/proc/sys/kernel/sched_rt_period_us:
The scheduling period that is equivalent to 100% CPU bandwidth
Settings are constrained to:
/proc/sys/kernel/sched_rt_runtime_us:
A global limit on how much time realtime scheduling may use. Even without
CONFIG_RT_GROUP_SCHED enabled, this will limit time reserved to realtime
processes. With CONFIG_RT_GROUP_SCHED it signifies the total bandwidth
available to all realtime groups.
* Time is specified in us because the interface is s32. This gives an
operating range from 1us to about 35 minutes.
* sched_rt_period_us takes values from 1 to INT_MAX.
* sched_rt_runtime_us takes values from -1 to (INT_MAX - 1).
* A run time of -1 specifies runtime == period, ie. no limit.
2.2 Default behaviour
---------------------
The default values for sched_rt_period_us (1000000 or 1s) and
sched_rt_runtime_us (950000 or 0.95s). This gives 0.05s to be used by
SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
realtime tasks will not lock up the machine but leave a little time to recover
it. By setting runtime to -1 you'd get the old behaviour back.
By default all bandwidth is assigned to the root group and new groups get the
period from /proc/sys/kernel/sched_rt_period_us and a run time of 0. If you
want to assign bandwidth to another group, reduce the root group's bandwidth
and assign some or all of the difference to another group.
Realtime group scheduling means you have to assign a portion of total CPU
bandwidth to the group before it will accept realtime tasks. Therefore you will
not be able to run realtime tasks as any user other than root until you have
done that, even if the user has the rights to run processes with realtime
priority!
2.3 Basis for grouping tasks
----------------------------
There are two compile-time settings for allocating CPU bandwidth. These are
configured using the "Basis for grouping tasks" multiple choice menu under
General setup > Group CPU Scheduler:
a. CONFIG_USER_SCHED (aka "Basis for grouping tasks" = "user id")
This lets you use the virtual files under
"/sys/kernel/uids/<uid>/cpu_rt_runtime_us" to control he CPU time reserved for
each user .
The other option is:
.o CONFIG_CGROUP_SCHED (aka "Basis for grouping tasks" = "Control groups")
This uses the /cgroup virtual file system and "/cgroup/<cgroup>/cpu.rt_runtime_us"
to control the CPU time reserved for each control group instead.
For more information on working with control groups, you should read
Documentation/cgroups.txt as well.
Group settings are checked against the following limits in order to keep the configuration
schedulable:
\Sum_{i} runtime_{i} / global_period <= global_runtime / global_period
in order to keep the configuration schedulable.
For now, this can be simplified to just the following (but see Future plans):
\Sum_{i} runtime_{i} <= global_runtime
3. Future plans
===============
There is work in progress to make the scheduling period for each group
("/sys/kernel/uids/<uid>/cpu_rt_period_us" or
"/cgroup/<cgroup>/cpu.rt_period_us" respectively) configurable as well.
The constraint on the period is that a subgroup must have a smaller or
equal period to its parent. But realistically its not very useful _yet_
as its prone to starvation without deadline scheduling.
Consider two sibling groups A and B; both have 50% bandwidth, but A's
period is twice the length of B's.
* group A: period=100000us, runtime=10000us
- this runs for 0.01s once every 0.1s
* group B: period= 50000us, runtime=10000us
- this runs for 0.01s twice every 0.1s (or once every 0.05 sec).
This means that currently a while (1) loop in A will run for the full period of
B and can starve B's tasks (assuming they are of lower priority) for a whole
period.
The next project will be SCHED_EDF (Earliest Deadline First scheduling) to bring
full deadline scheduling to the linux kernel. Deadline scheduling the above
groups and treating end of the period as a deadline will ensure that they both
get their allocated time.
Implementing SCHED_EDF might take a while to complete. Priority Inheritance is
the biggest challenge as the current linux PI infrastructure is geared towards
the limited static priority levels 0-139. With deadline scheduling you need to
do deadline inheritance (since priority is inversely proportional to the
deadline delta (deadline - now).
This means the whole PI machinery will have to be reworked - and that is one of
the most complex pieces of code we have.
Documentation/scsi/st.txt
浏览文件 @ 36d99df2
......@@ -2,7 +2,7 @@ This file contains brief information about the SCSI tape driver.
The driver is currently maintained by Kai Mäkisara (email
Kai.Makisara@kolumbus.fi)
Last modified: Mon Mar 7 21:14:44 2005 by kai.makisara
Last modified: Sun Feb 24 21:59:07 2008 by kai.makisara
BASICS
......@@ -133,6 +133,11 @@ the defaults set by the user. The value -1 means the default is not set. The
file 'dev' contains the device numbers corresponding to this device. The links
'device' and 'driver' point to the SCSI device and driver entries.
Each directory also contains the entry 'options' which shows the currently
enabled driver and mode options. The value in the file is a bit mask where the
bit definitions are the same as those used with MTSETDRVBUFFER in setting the
options.
A link named 'tape' is made from the SCSI device directory to the class
directory corresponding to the mode 0 auto-rewind device (e.g., st0).
......@@ -372,6 +377,11 @@ MTSETDRVBUFFER
MT_ST_SYSV sets the SYSV semantics (mode)
MT_ST_NOWAIT enables immediate mode (i.e., don't wait for
the command to finish) for some commands (e.g., rewind)
MT_ST_SILI enables setting the SILI bit in SCSI commands when
reading in variable block mode to enhance performance when
reading blocks shorter than the byte count; set this only
if you are sure that the drive supports SILI and the HBA
correctly returns transfer residuals
MT_ST_DEBUGGING debugging (global; debugging must be
compiled into the driver)
MT_ST_SETBOOLEANS
......
Documentation/x86/pat.txt 0 → 100644
浏览文件 @ 36d99df2
PAT (Page Attribute Table)
x86 Page Attribute Table (PAT) allows for setting the memory attribute at the
page level granularity. PAT is complementary to the MTRR settings which allows
for setting of memory types over physical address ranges. However, PAT is
more flexible than MTRR due to its capability to set attributes at page level
and also due to the fact that there are no hardware limitations on number of
such attribute settings allowed. Added flexibility comes with guidelines for
not having memory type aliasing for the same physical memory with multiple
virtual addresses.
PAT allows for different types of memory attributes. The most commonly used
ones that will be supported at this time are Write-back, Uncached,
Write-combined and Uncached Minus.
There are many different APIs in the kernel that allows setting of memory
attributes at the page level. In order to avoid aliasing, these interfaces
should be used thoughtfully. Below is a table of interfaces available,
their intended usage and their memory attribute relationships. Internally,
these APIs use a reserve_memtype()/free_memtype() interface on the physical
address range to avoid any aliasing.
-------------------------------------------------------------------
API | RAM | ACPI,... | Reserved/Holes |
-----------------------|----------|------------|------------------|
| | | |
ioremap | -- | UC | UC |
| | | |
ioremap_cache | -- | WB | WB |
| | | |
ioremap_nocache | -- | UC | UC |
| | | |
ioremap_wc | -- | -- | WC |
| | | |
set_memory_uc | UC | -- | -- |
set_memory_wb | | | |
| | | |
set_memory_wc | WC | -- | -- |
set_memory_wb | | | |
| | | |
pci sysfs resource | -- | -- | UC |
| | | |
pci sysfs resource_wc | -- | -- | WC |
is IORESOURCE_PREFETCH| | | |
| | | |
pci proc | -- | -- | UC |
!PCIIOC_WRITE_COMBINE | | | |
| | | |
pci proc | -- | -- | WC |
PCIIOC_WRITE_COMBINE | | | |
| | | |
/dev/mem | -- | UC | UC |
read-write | | | |
| | | |
/dev/mem | -- | UC | UC |
mmap SYNC flag | | | |
| | | |
/dev/mem | -- | WB/WC/UC | WB/WC/UC |
mmap !SYNC flag | |(from exist-| (from exist- |
and | | ing alias)| ing alias) |
any alias to this area| | | |
| | | |
/dev/mem | -- | WB | WB |
mmap !SYNC flag | | | |
no alias to this area | | | |
and | | | |
MTRR says WB | | | |
| | | |
/dev/mem | -- | -- | UC_MINUS |
mmap !SYNC flag | | | |
no alias to this area | | | |
and | | | |
MTRR says !WB | | | |
| | | |
-------------------------------------------------------------------
Notes:
-- in the above table mean "Not suggested usage for the API". Some of the --'s
are strictly enforced by the kernel. Some others are not really enforced
today, but may be enforced in future.
For ioremap and pci access through /sys or /proc - The actual type returned
can be more restrictive, in case of any existing aliasing for that address.
For example: If there is an existing uncached mapping, a new ioremap_wc can
return uncached mapping in place of write-combine requested.
set_memory_[uc|wc] and set_memory_wb should be used in pairs, where driver will
first make a region uc or wc and switch it back to wb after use.
Over time writes to /proc/mtrr will be deprecated in favor of using PAT based
interfaces. Users writing to /proc/mtrr are suggested to use above interfaces.
Drivers should use ioremap_[uc|wc] to access PCI BARs with [uc|wc] access
types.
Drivers should use set_memory_[uc|wc] to set access type for RAM ranges.
Documentation/x86_64/boot-options.txt
浏览文件 @ 36d99df2
......@@ -307,3 +307,8 @@ Debugging
stuck (default)
Miscellaneous
nogbpages
Do not use GB pages for kernel direct mappings.
gbpages
Use GB pages for kernel direct mappings.
MAINTAINERS
浏览文件 @ 36d99df2
......@@ -486,6 +486,12 @@ M: kernel@wantstofly.org
L: linux-arm-kernel@lists.arm.linux.org.uk (subscribers-only)
S: Maintained
ARM/GUMSTIX MACHINE SUPPORT
P: Steve Sakoman
M: sakoman@gmail.com
L: linux-arm-kernel@lists.arm.linux.org.uk (subscribers-only)
S: Maintained
ARM/HP JORNADA 7XX MACHINE SUPPORT
P: Kristoffer Ericson
M: kristoffer.ericson@gmail.com
......@@ -678,6 +684,11 @@ L: linux-wireless@vger.kernel.org
L: ath5k-devel@lists.ath5k.org
S: Maintained
ATI_REMOTE2 DRIVER
P: Ville Syrjala
M: syrjala@sci.fi
S: Maintained
ATL1 ETHERNET DRIVER
P: Jay Cliburn
M: jcliburn@gmail.com
......@@ -840,15 +851,6 @@ L: linux-wireless@vger.kernel.org
W: http://linuxwireless.org/en/users/Drivers/b43
S: Maintained
BCM43XX WIRELESS DRIVER (SOFTMAC BASED VERSION)
P: Larry Finger
M: Larry.Finger@lwfinger.net
P: Stefano Brivio
M: stefano.brivio@polimi.it
L: linux-wireless@vger.kernel.org
W: http://bcm43xx.berlios.de/
S: Obsolete
BEFS FILE SYSTEM
P: Sergey S. Kostyliov
M: rathamahata@php4.ru
......@@ -2319,6 +2321,12 @@ L: linux-kernel@vger.kernel.org
L: kexec@lists.infradead.org
S: Maintained
KGDB
P: Jason Wessel
M: jason.wessel@windriver.com
L: kgdb-bugreport@lists.sourceforge.net
S: Maintained
KPROBES
P: Ananth N Mavinakayanahalli
M: ananth@in.ibm.com
......@@ -2944,8 +2952,9 @@ P: Mark Fasheh
M: mfasheh@suse.com
P: Joel Becker
M: joel.becker@oracle.com
L: ocfs2-devel@oss.oracle.com
L: ocfs2-devel@oss.oracle.com (moderated for non-subscribers)
W: http://oss.oracle.com/projects/ocfs2/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git
S: Supported
OMNIKEY CARDMAN 4000 DRIVER
......@@ -3061,11 +3070,10 @@ L: linux-pci@atrey.karlin.mff.cuni.cz
S: Supported
PCI SUBSYSTEM
P: Greg Kroah-Hartman
M: gregkh@suse.de
P: Jesse Barnes
M: jbarnes@virtuousgeek.org
L: linux-kernel@vger.kernel.org
L: linux-pci@atrey.karlin.mff.cuni.cz
T: quilt kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
S: Supported
PCI HOTPLUG CORE
......@@ -3472,7 +3480,7 @@ P: Vlad Yasevich
M: vladislav.yasevich@hp.com
P: Sridhar Samudrala
M: sri@us.ibm.com
L: lksctp-developers@lists.sourceforge.net
L: linux-sctp@vger.kernel.org
W: http://lksctp.sourceforge.net
S: Supported
......@@ -3606,11 +3614,10 @@ M: mhoffman@lightlink.com
L: lm-sensors@lm-sensors.org
S: Maintained
SOFTMAC LAYER (IEEE 802.11)
P: Daniel Drake
M: dsd@gentoo.org
L: linux-wireless@vger.kernel.org
S: Obsolete
SMX UIO Interface
P: Ben Nizette
M: bn@niasdigital.com
S: Maintained
SOFTWARE RAID (Multiple Disks) SUPPORT
P: Ingo Molnar
......
Makefile
浏览文件 @ 36d99df2
......@@ -1538,7 +1538,7 @@ quiet_cmd_rmdirs = $(if $(wildcard $(rm-dirs)),CLEAN $(wildcard $(rm-dirs)))
quiet_cmd_rmfiles = $(if $(wildcard $(rm-files)),CLEAN $(wildcard $(rm-files)))
cmd_rmfiles = rm -f $(rm-files)
# Run depmod only is we have System.map and depmod is executable
# Run depmod only if we have System.map and depmod is executable
# and we build for the host arch
quiet_cmd_depmod = DEPMOD $(KERNELRELEASE)
cmd_depmod = \
......
arch/alpha/kernel/Makefile
浏览文件 @ 36d99df2
......@@ -7,7 +7,7 @@ EXTRA_AFLAGS := $(KBUILD_CFLAGS)
EXTRA_CFLAGS := -Werror -Wno-sign-compare
obj-y := entry.o traps.o process.o init_task.o osf_sys.o irq.o \
irq_alpha.o signal.o setup.o ptrace.o time.o semaphore.o \
irq_alpha.o signal.o setup.o ptrace.o time.o \
alpha_ksyms.o systbls.o err_common.o io.o
obj-$(CONFIG_VGA_HOSE) += console.o
......
arch/alpha/kernel/alpha_ksyms.c
浏览文件 @ 36d99df2
......@@ -77,15 +77,6 @@ EXPORT_SYMBOL(__do_clear_user);
EXPORT_SYMBOL(__strncpy_from_user);
EXPORT_SYMBOL(__strnlen_user);
/* Semaphore helper functions. */
EXPORT_SYMBOL(__down_failed);
EXPORT_SYMBOL(__down_failed_interruptible);
EXPORT_SYMBOL(__up_wakeup);
EXPORT_SYMBOL(down);
EXPORT_SYMBOL(down_interruptible);
EXPORT_SYMBOL(down_trylock);
EXPORT_SYMBOL(up);
/*
* SMP-specific symbols.
*/
......
arch/alpha/kernel/pci.c
浏览文件 @ 36d99df2
......@@ -372,28 +372,7 @@ EXPORT_SYMBOL(pcibios_bus_to_resource);
int
pcibios_enable_device(struct pci_dev *dev, int mask)
{
u16 cmd, oldcmd;
int i;
pci_read_config_word(dev, PCI_COMMAND, &cmd);
oldcmd = cmd;
for (i = 0; i < PCI_NUM_RESOURCES; i++) {
struct resource *res = &dev->resource[i];
if (res->flags & IORESOURCE_IO)
cmd |= PCI_COMMAND_IO;
else if (res->flags & IORESOURCE_MEM)
cmd |= PCI_COMMAND_MEMORY;
}
if (cmd != oldcmd) {
printk(KERN_DEBUG "PCI: Enabling device: (%s), cmd %x\n",
pci_name(dev), cmd);
/* Enable the appropriate bits in the PCI command register. */
pci_write_config_word(dev, PCI_COMMAND, cmd);
}
return 0;
return pci_enable_resources(dev, mask);
}
/*
......
arch/alpha/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
/*
* Alpha semaphore implementation.
*
* (C) Copyright 1996 Linus Torvalds
* (C) Copyright 1999, 2000 Richard Henderson
*/
#include <linux/errno.h>
#include <linux/sched.h>
#include <linux/init.h>
/*
* This is basically the PPC semaphore scheme ported to use
* the Alpha ll/sc sequences, so see the PPC code for
* credits.
*/
/*
* Atomically update sem->count.
* This does the equivalent of the following:
*
* old_count = sem->count;
* tmp = MAX(old_count, 0) + incr;
* sem->count = tmp;
* return old_count;
*/
static inline int __sem_update_count(struct semaphore *sem, int incr)
{
long old_count, tmp = 0;
__asm__ __volatile__(
"1: ldl_l %0,%2\n"
" cmovgt %0,%0,%1\n"
" addl %1,%3,%1\n"
" stl_c %1,%2\n"
" beq %1,2f\n"
" mb\n"
".subsection 2\n"
"2: br 1b\n"
".previous"
: "=&r" (old_count), "=&r" (tmp), "=m" (sem->count)
: "Ir" (incr), "1" (tmp), "m" (sem->count));
return old_count;
}
/*
* Perform the "down" function. Return zero for semaphore acquired,
* return negative for signalled out of the function.
*
* If called from down, the return is ignored and the wait loop is
* not interruptible. This means that a task waiting on a semaphore
* using "down()" cannot be killed until someone does an "up()" on
* the semaphore.
*
* If called from down_interruptible, the return value gets checked
* upon return. If the return value is negative then the task continues
* with the negative value in the return register (it can be tested by
* the caller).
*
* Either form may be used in conjunction with "up()".
*/
void __sched
__down_failed(struct semaphore *sem)
{
struct task_struct *tsk = current;
DECLARE_WAITQUEUE(wait, tsk);
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down failed(%p)\n",
tsk->comm, task_pid_nr(tsk), sem);
#endif
tsk->state = TASK_UNINTERRUPTIBLE;
wmb();
add_wait_queue_exclusive(&sem->wait, &wait);
/*
* Try to get the semaphore. If the count is > 0, then we've
* got the semaphore; we decrement count and exit the loop.
* If the count is 0 or negative, we set it to -1, indicating
* that we are asleep, and then sleep.
*/
while (__sem_update_count(sem, -1) <= 0) {
schedule();
set_task_state(tsk, TASK_UNINTERRUPTIBLE);
}
remove_wait_queue(&sem->wait, &wait);
tsk->state = TASK_RUNNING;
/*
* If there are any more sleepers, wake one of them up so
* that it can either get the semaphore, or set count to -1
* indicating that there are still processes sleeping.
*/
wake_up(&sem->wait);
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down acquired(%p)\n",
tsk->comm, task_pid_nr(tsk), sem);
#endif
}
int __sched
__down_failed_interruptible(struct semaphore *sem)
{
struct task_struct *tsk = current;
DECLARE_WAITQUEUE(wait, tsk);
long ret = 0;
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down failed(%p)\n",
tsk->comm, task_pid_nr(tsk), sem);
#endif
tsk->state = TASK_INTERRUPTIBLE;
wmb();
add_wait_queue_exclusive(&sem->wait, &wait);
while (__sem_update_count(sem, -1) <= 0) {
if (signal_pending(current)) {
/*
* A signal is pending - give up trying.
* Set sem->count to 0 if it is negative,
* since we are no longer sleeping.
*/
__sem_update_count(sem, 0);
ret = -EINTR;
break;
}
schedule();
set_task_state(tsk, TASK_INTERRUPTIBLE);
}
remove_wait_queue(&sem->wait, &wait);
tsk->state = TASK_RUNNING;
wake_up(&sem->wait);
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down %s(%p)\n",
current->comm, task_pid_nr(current),
(ret < 0 ? "interrupted" : "acquired"), sem);
#endif
return ret;
}
void
__up_wakeup(struct semaphore *sem)
{
/*
* Note that we incremented count in up() before we came here,
* but that was ineffective since the result was <= 0, and
* any negative value of count is equivalent to 0.
* This ends up setting count to 1, unless count is now > 0
* (i.e. because some other cpu has called up() in the meantime),
* in which case we just increment count.
*/
__sem_update_count(sem, 1);
wake_up(&sem->wait);
}
void __sched
down(struct semaphore *sem)
{
#ifdef WAITQUEUE_DEBUG
CHECK_MAGIC(sem->__magic);
#endif
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down(%p) <count=%d> from %p\n",
current->comm, task_pid_nr(current), sem,
atomic_read(&sem->count), __builtin_return_address(0));
#endif
__down(sem);
}
int __sched
down_interruptible(struct semaphore *sem)
{
#ifdef WAITQUEUE_DEBUG
CHECK_MAGIC(sem->__magic);
#endif
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down(%p) <count=%d> from %p\n",
current->comm, task_pid_nr(current), sem,
atomic_read(&sem->count), __builtin_return_address(0));
#endif
return __down_interruptible(sem);
}
int
down_trylock(struct semaphore *sem)
{
int ret;
#ifdef WAITQUEUE_DEBUG
CHECK_MAGIC(sem->__magic);
#endif
ret = __down_trylock(sem);
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): down_trylock %s from %p\n",
current->comm, task_pid_nr(current),
ret ? "failed" : "acquired",
__builtin_return_address(0));
#endif
return ret;
}
void
up(struct semaphore *sem)
{
#ifdef WAITQUEUE_DEBUG
CHECK_MAGIC(sem->__magic);
#endif
#ifdef CONFIG_DEBUG_SEMAPHORE
printk("%s(%d): up(%p) <count=%d> from %p\n",
current->comm, task_pid_nr(current), sem,
atomic_read(&sem->count), __builtin_return_address(0));
#endif
__up(sem);
}
arch/arm/Kconfig
浏览文件 @ 36d99df2
......@@ -255,6 +255,7 @@ config ARCH_EP93XX
select ARM_AMBA
select ARM_VIC
select GENERIC_GPIO
select HAVE_GPIO_LIB
help
This enables support for the Cirrus EP93xx series of CPUs.
......@@ -377,15 +378,17 @@ config ARCH_MXC
help
Support for Freescale MXC/iMX-based family of processors
config ARCH_ORION
config ARCH_ORION5X
bool "Marvell Orion"
depends on MMU
select PCI
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
help
Support for Marvell Orion System on Chip family.
Support for the following Marvell Orion 5x series SoCs:
Orion-1 (5181), Orion-NAS (5182), Orion-2 (5281.)
config ARCH_PNX4008
bool "Philips Nexperia PNX4008 Mobile"
......@@ -422,10 +425,15 @@ config ARCH_SA1100
bool "SA1100-based"
select ISA
select ARCH_DISCONTIGMEM_ENABLE
select ARCH_SPARSEMEM_ENABLE
select ARCH_SELECT_MEMORY_MODEL
select ARCH_MTD_XIP
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select TICK_ONESHOT
select HAVE_IDE
select HAVE_GPIO_LIB
help
Support for StrongARM 11x0 based boards.
......@@ -468,6 +476,7 @@ config ARCH_DAVINCI
config ARCH_OMAP
bool "TI OMAP"
select GENERIC_GPIO
select HAVE_GPIO_LIB
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
help
......@@ -516,7 +525,7 @@ source "arch/arm/mach-omap1/Kconfig"
source "arch/arm/mach-omap2/Kconfig"
source "arch/arm/mach-orion/Kconfig"
source "arch/arm/mach-orion5x/Kconfig"
source "arch/arm/plat-s3c24xx/Kconfig"
source "arch/arm/plat-s3c/Kconfig"
......@@ -563,6 +572,9 @@ config ARCH_ACORN
config PLAT_IOP
bool
config PLAT_ORION
bool
source arch/arm/mm/Kconfig
config IWMMXT
......@@ -650,7 +662,7 @@ source "kernel/time/Kconfig"
config SMP
bool "Symmetric Multi-Processing (EXPERIMENTAL)"
depends on EXPERIMENTAL && REALVIEW_EB_ARM11MP
depends on EXPERIMENTAL && (REALVIEW_EB_ARM11MP || MACH_REALVIEW_PB11MP)
help
This enables support for systems with more than one CPU. If you have
a system with only one CPU, like most personal computers, say N. If
......@@ -683,7 +695,7 @@ config HOTPLUG_CPU
config LOCAL_TIMERS
bool "Use local timer interrupts"
depends on SMP && REALVIEW_EB_ARM11MP
depends on SMP && (REALVIEW_EB_ARM11MP || MACH_REALVIEW_PB11MP)
default y
help
Enable support for local timers on SMP platforms, rather then the
......@@ -774,6 +786,12 @@ config ARCH_DISCONTIGMEM_ENABLE
or have huge holes in the physical address space for other reasons.
See <file:Documentation/vm/numa> for more.
config ARCH_SPARSEMEM_ENABLE
bool
config ARCH_SELECT_MEMORY_MODEL
bool
config NODES_SHIFT
int
default "4" if ARCH_LH7A40X
......@@ -1174,6 +1192,8 @@ source "drivers/dma/Kconfig"
source "drivers/dca/Kconfig"
source "drivers/uio/Kconfig"
endmenu
source "fs/Kconfig"
......
arch/arm/Makefile
浏览文件 @ 36d99df2
......@@ -134,12 +134,11 @@ endif
machine-$(CONFIG_ARCH_PNX4008) := pnx4008
machine-$(CONFIG_ARCH_NETX) := netx
machine-$(CONFIG_ARCH_NS9XXX) := ns9xxx
textofs-$(CONFIG_ARCH_NS9XXX) := 0x00108000
machine-$(CONFIG_ARCH_DAVINCI) := davinci
machine-$(CONFIG_ARCH_KS8695) := ks8695
incdir-$(CONFIG_ARCH_MXC) := mxc
machine-$(CONFIG_ARCH_MX3) := mx3
machine-$(CONFIG_ARCH_ORION) := orion
machine-$(CONFIG_ARCH_ORION5X) := orion5x
machine-$(CONFIG_ARCH_MSM7X00A) := msm
ifeq ($(CONFIG_ARCH_EBSA110),y)
......@@ -185,6 +184,7 @@ core-$(CONFIG_VFP) += arch/arm/vfp/
# If we have a common platform directory, then include it in the build.
core-$(CONFIG_PLAT_IOP) += arch/arm/plat-iop/
core-$(CONFIG_PLAT_ORION) += arch/arm/plat-orion/
core-$(CONFIG_ARCH_OMAP) += arch/arm/plat-omap/
core-$(CONFIG_PLAT_S3C24XX) += arch/arm/plat-s3c24xx/
core-$(CONFIG_ARCH_MXC) += arch/arm/plat-mxc/
......
arch/arm/boot/Makefile
浏览文件 @ 36d99df2
......@@ -61,9 +61,15 @@ endif
quiet_cmd_uimage = UIMAGE $@
cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
-C none -a $(ZRELADDR) -e $(ZRELADDR) \
-C none -a $(LOADADDR) -e $(LOADADDR) \
-n 'Linux-$(KERNELRELEASE)' -d $< $@
ifeq ($(CONFIG_ZBOOT_ROM),y)
$(obj)/uImage: LOADADDR=$(CONFIG_ZBOOT_ROM_TEXT)
else
$(obj)/uImage: LOADADDR=$(ZRELADDR)
endif
$(obj)/uImage: $(obj)/zImage FORCE
$(call if_changed,uimage)
@echo ' Image $@ is ready'
......
arch/arm/common/rtctime.c
浏览文件 @ 36d99df2
......@@ -22,7 +22,6 @@
#include <linux/mutex.h>
#include <asm/rtc.h>
#include <asm/semaphore.h>
static DECLARE_WAIT_QUEUE_HEAD(rtc_wait);
static struct fasync_struct *rtc_async_queue;
......
arch/arm/common/scoop.c
浏览文件 @ 36d99df2
......@@ -16,6 +16,7 @@
#include <linux/slab.h>
#include <linux/platform_device.h>
#include <asm/io.h>
#include <asm/gpio.h>
#include <asm/hardware/scoop.h>
/* PCMCIA to Scoop linkage
......@@ -30,10 +31,9 @@
struct scoop_pcmcia_config *platform_scoop_config;
EXPORT_SYMBOL(platform_scoop_config);
#define SCOOP_REG(d,adr) (*(volatile unsigned short*)(d +(adr)))
struct scoop_dev {
void *base;
void __iomem *base;
struct gpio_chip gpio;
spinlock_t scoop_lock;
unsigned short suspend_clr;
unsigned short suspend_set;
......@@ -44,13 +44,84 @@ void reset_scoop(struct device *dev)
{
struct scoop_dev *sdev = dev_get_drvdata(dev);
SCOOP_REG(sdev->base,SCOOP_MCR) = 0x0100; // 00
SCOOP_REG(sdev->base,SCOOP_CDR) = 0x0000; // 04
SCOOP_REG(sdev->base,SCOOP_CCR) = 0x0000; // 10
SCOOP_REG(sdev->base,SCOOP_IMR) = 0x0000; // 18
SCOOP_REG(sdev->base,SCOOP_IRM) = 0x00FF; // 14
SCOOP_REG(sdev->base,SCOOP_ISR) = 0x0000; // 1C
SCOOP_REG(sdev->base,SCOOP_IRM) = 0x0000;
iowrite16(0x0100, sdev->base + SCOOP_MCR); // 00
iowrite16(0x0000, sdev->base + SCOOP_CDR); // 04
iowrite16(0x0000, sdev->base + SCOOP_CCR); // 10
iowrite16(0x0000, sdev->base + SCOOP_IMR); // 18
iowrite16(0x00FF, sdev->base + SCOOP_IRM); // 14
iowrite16(0x0000, sdev->base + SCOOP_ISR); // 1C
iowrite16(0x0000, sdev->base + SCOOP_IRM);
}
static void __scoop_gpio_set(struct scoop_dev *sdev,
unsigned offset, int value)
{
unsigned short gpwr;
gpwr = ioread16(sdev->base + SCOOP_GPWR);
if (value)
gpwr |= 1 << (offset + 1);
else
gpwr &= ~(1 << (offset + 1));
iowrite16(gpwr, sdev->base + SCOOP_GPWR);
}
static void scoop_gpio_set(struct gpio_chip *chip, unsigned offset, int value)
{
struct scoop_dev *sdev = container_of(chip, struct scoop_dev, gpio);
unsigned long flags;
spin_lock_irqsave(&sdev->scoop_lock, flags);
__scoop_gpio_set(sdev, offset, value);
spin_unlock_irqrestore(&sdev->scoop_lock, flags);
}
static int scoop_gpio_get(struct gpio_chip *chip, unsigned offset)
{
struct scoop_dev *sdev = container_of(chip, struct scoop_dev, gpio);
/* XXX: I'm usure, but it seems so */
return ioread16(sdev->base + SCOOP_GPRR) & (1 << (offset + 1));
}
static int scoop_gpio_direction_input(struct gpio_chip *chip,
unsigned offset)
{
struct scoop_dev *sdev = container_of(chip, struct scoop_dev, gpio);
unsigned long flags;
unsigned short gpcr;
spin_lock_irqsave(&sdev->scoop_lock, flags);
gpcr = ioread16(sdev->base + SCOOP_GPCR);
gpcr &= ~(1 << (offset + 1));
iowrite16(gpcr, sdev->base + SCOOP_GPCR);
spin_unlock_irqrestore(&sdev->scoop_lock, flags);
return 0;
}
static int scoop_gpio_direction_output(struct gpio_chip *chip,
unsigned offset, int value)
{
struct scoop_dev *sdev = container_of(chip, struct scoop_dev, gpio);
unsigned long flags;
unsigned short gpcr;
spin_lock_irqsave(&sdev->scoop_lock, flags);
__scoop_gpio_set(sdev, offset, value);
gpcr = ioread16(sdev->base + SCOOP_GPCR);
gpcr |= 1 << (offset + 1);
iowrite16(gpcr, sdev->base + SCOOP_GPCR);
spin_unlock_irqrestore(&sdev->scoop_lock, flags);
return 0;
}
unsigned short set_scoop_gpio(struct device *dev, unsigned short bit)
......@@ -60,8 +131,8 @@ unsigned short set_scoop_gpio(struct device *dev, unsigned short bit)
struct scoop_dev *sdev = dev_get_drvdata(dev);
spin_lock_irqsave(&sdev->scoop_lock, flag);
gpio_bit = SCOOP_REG(sdev->base, SCOOP_GPWR) | bit;
SCOOP_REG(sdev->base, SCOOP_GPWR) = gpio_bit;
gpio_bit = ioread16(sdev->base + SCOOP_GPWR) | bit;
iowrite16(gpio_bit, sdev->base + SCOOP_GPWR);
spin_unlock_irqrestore(&sdev->scoop_lock, flag);
return gpio_bit;
......@@ -74,8 +145,8 @@ unsigned short reset_scoop_gpio(struct device *dev, unsigned short bit)
struct scoop_dev *sdev = dev_get_drvdata(dev);
spin_lock_irqsave(&sdev->scoop_lock, flag);
gpio_bit = SCOOP_REG(sdev->base, SCOOP_GPWR) & ~bit;
SCOOP_REG(sdev->base,SCOOP_GPWR) = gpio_bit;
gpio_bit = ioread16(sdev->base + SCOOP_GPWR) & ~bit;
iowrite16(gpio_bit, sdev->base + SCOOP_GPWR);
spin_unlock_irqrestore(&sdev->scoop_lock, flag);
return gpio_bit;
......@@ -87,13 +158,13 @@ EXPORT_SYMBOL(reset_scoop_gpio);
unsigned short read_scoop_reg(struct device *dev, unsigned short reg)
{
struct scoop_dev *sdev = dev_get_drvdata(dev);
return SCOOP_REG(sdev->base,reg);
return ioread16(sdev->base + reg);
}
void write_scoop_reg(struct device *dev, unsigned short reg, unsigned short data)
{
struct scoop_dev *sdev = dev_get_drvdata(dev);
SCOOP_REG(sdev->base,reg)=data;
iowrite16(data, sdev->base + reg);
}
EXPORT_SYMBOL(reset_scoop);
......@@ -104,9 +175,9 @@ static void check_scoop_reg(struct scoop_dev *sdev)
{
unsigned short mcr;
mcr = SCOOP_REG(sdev->base, SCOOP_MCR);
mcr = ioread16(sdev->base + SCOOP_MCR);
if ((mcr & 0x100) == 0)
SCOOP_REG(sdev->base, SCOOP_MCR) = 0x0101;
iowrite16(0x0101, sdev->base + SCOOP_MCR);
}
#ifdef CONFIG_PM
......@@ -115,8 +186,8 @@ static int scoop_suspend(struct platform_device *dev, pm_message_t state)
struct scoop_dev *sdev = platform_get_drvdata(dev);
check_scoop_reg(sdev);
sdev->scoop_gpwr = SCOOP_REG(sdev->base, SCOOP_GPWR);
SCOOP_REG(sdev->base, SCOOP_GPWR) = (sdev->scoop_gpwr & ~sdev->suspend_clr) | sdev->suspend_set;
sdev->scoop_gpwr = ioread16(sdev->base + SCOOP_GPWR);
iowrite16((sdev->scoop_gpwr & ~sdev->suspend_clr) | sdev->suspend_set, sdev->base + SCOOP_GPWR);
return 0;
}
......@@ -126,7 +197,7 @@ static int scoop_resume(struct platform_device *dev)
struct scoop_dev *sdev = platform_get_drvdata(dev);
check_scoop_reg(sdev);
SCOOP_REG(sdev->base,SCOOP_GPWR) = sdev->scoop_gpwr;
iowrite16(sdev->scoop_gpwr, sdev->base + SCOOP_GPWR);
return 0;
}
......@@ -135,11 +206,13 @@ static int scoop_resume(struct platform_device *dev)
#define scoop_resume NULL
#endif
int __init scoop_probe(struct platform_device *pdev)
static int __devinit scoop_probe(struct platform_device *pdev)
{
struct scoop_dev *devptr;
struct scoop_config *inf;
struct resource *mem = platform_get_resource(pdev, IORESOURCE_MEM, 0);
int ret;
int temp;
if (!mem)
return -EINVAL;
......@@ -154,40 +227,78 @@ int __init scoop_probe(struct platform_device *pdev)
devptr->base = ioremap(mem->start, mem->end - mem->start + 1);
if (!devptr->base) {
kfree(devptr);
return -ENOMEM;
ret = -ENOMEM;
goto err_ioremap;
}
platform_set_drvdata(pdev, devptr);
printk("Sharp Scoop Device found at 0x%08x -> 0x%08x\n",(unsigned int)mem->start,(unsigned int)devptr->base);
printk("Sharp Scoop Device found at 0x%08x -> 0x%8p\n",(unsigned int)mem->start, devptr->base);
SCOOP_REG(devptr->base, SCOOP_MCR) = 0x0140;
iowrite16(0x0140, devptr->base + SCOOP_MCR);
reset_scoop(&pdev->dev);
SCOOP_REG(devptr->base, SCOOP_CPR) = 0x0000;
SCOOP_REG(devptr->base, SCOOP_GPCR) = inf->io_dir & 0xffff;
SCOOP_REG(devptr->base, SCOOP_GPWR) = inf->io_out & 0xffff;
iowrite16(0x0000, devptr->base + SCOOP_CPR);
iowrite16(inf->io_dir & 0xffff, devptr->base + SCOOP_GPCR);
iowrite16(inf->io_out & 0xffff, devptr->base + SCOOP_GPWR);
devptr->suspend_clr = inf->suspend_clr;
devptr->suspend_set = inf->suspend_set;
devptr->gpio.base = -1;
if (inf->gpio_base != 0) {
devptr->gpio.label = pdev->dev.bus_id;
devptr->gpio.base = inf->gpio_base;
devptr->gpio.ngpio = 12; /* PA11 = 0, PA12 = 1, etc. up to PA22 = 11 */
devptr->gpio.set = scoop_gpio_set;
devptr->gpio.get = scoop_gpio_get;
devptr->gpio.direction_input = scoop_gpio_direction_input;
devptr->gpio.direction_output = scoop_gpio_direction_output;
ret = gpiochip_add(&devptr->gpio);
if (ret)
goto err_gpio;
}
return 0;
if (devptr->gpio.base != -1)
temp = gpiochip_remove(&devptr->gpio);
err_gpio:
platform_set_drvdata(pdev, NULL);
err_ioremap:
iounmap(devptr->base);
kfree(devptr);
return ret;
}
static int scoop_remove(struct platform_device *pdev)
static int __devexit scoop_remove(struct platform_device *pdev)
{
struct scoop_dev *sdev = platform_get_drvdata(pdev);
if (sdev) {
iounmap(sdev->base);
kfree(sdev);
platform_set_drvdata(pdev, NULL);
int ret;
if (!sdev)
return -EINVAL;
if (sdev->gpio.base != -1) {
ret = gpiochip_remove(&sdev->gpio);
if (ret) {
dev_err(&pdev->dev, "Can't remove gpio chip: %d\n", ret);
return ret;
}
}
platform_set_drvdata(pdev, NULL);
iounmap(sdev->base);
kfree(sdev);
return 0;
}
static struct platform_driver scoop_driver = {
.probe = scoop_probe,
.remove = scoop_remove,
.remove = __devexit_p(scoop_remove),
.suspend = scoop_suspend,
.resume = scoop_resume,
.driver = {
......@@ -195,7 +306,7 @@ static struct platform_driver scoop_driver = {
},
};
int __init scoop_init(void)
static int __init scoop_init(void)
{
return platform_driver_register(&scoop_driver);
}
......
arch/arm/configs/am200epdkit_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/at91rm9200dk_defconfig
浏览文件 @ 36d99df2
......@@ -620,14 +620,14 @@ CONFIG_I2C_CHARDEV=y
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
CONFIG_I2C_AT91=y
CONFIG_I2C_GPIO=y
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_PCA_ISA is not set
......
arch/arm/configs/at91rm9200ek_defconfig
浏览文件 @ 36d99df2
......@@ -594,14 +594,14 @@ CONFIG_I2C_CHARDEV=y
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
CONFIG_I2C_AT91=y
CONFIG_I2C_GPIO=y
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_PCA_ISA is not set
......
arch/arm/configs/ateb9200_defconfig
浏览文件 @ 36d99df2
......@@ -714,7 +714,7 @@ CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
CONFIG_I2C_AT91=m
CONFIG_I2C_GPIO=m
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_PCA_ISA is not set
......
arch/arm/configs/cam60_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/csb337_defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/csb637_defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/ecbat91_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/kafa_defconfig
浏览文件 @ 36d99df2
......@@ -587,14 +587,14 @@ CONFIG_I2C_CHARDEV=y
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
CONFIG_I2C_AT91=y
CONFIG_I2C_GPIO=y
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_PCA_ISA is not set
......
arch/arm/configs/magician_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/ns9xxx_defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/orion_defconfig → arch/arm/configs/orion5x_defconfig
浏览文件 @ 36d99df2
......@@ -140,7 +140,7 @@ CONFIG_CLASSIC_RCU=y
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_NS9XXX is not set
# CONFIG_ARCH_MXC is not set
CONFIG_ARCH_ORION=y
CONFIG_ARCH_ORION5X=y
# CONFIG_ARCH_PNX4008 is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
......
arch/arm/configs/picotux200_defconfig
浏览文件 @ 36d99df2
......@@ -727,14 +727,14 @@ CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
CONFIG_I2C_AT91=m
CONFIG_I2C_GPIO=m
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_STUB is not set
......
arch/arm/configs/sam9_l9260_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/tct_hammer_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/configs/yl9200_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 36d99df2
......@@ -7,7 +7,7 @@ AFLAGS_head.o := -DTEXT_OFFSET=$(TEXT_OFFSET)
# Object file lists.
obj-y := compat.o entry-armv.o entry-common.o irq.o \
process.o ptrace.o semaphore.o setup.o signal.o \
process.o ptrace.o setup.o signal.o \
sys_arm.o stacktrace.o time.o traps.o
obj-$(CONFIG_ISA_DMA_API) += dma.o
......@@ -22,6 +22,7 @@ obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o
obj-$(CONFIG_KPROBES) += kprobes.o kprobes-decode.o
obj-$(CONFIG_ATAGS_PROC) += atags.o
obj-$(CONFIG_OABI_COMPAT) += sys_oabi-compat.o
obj-$(CONFIG_ARM_THUMBEE) += thumbee.o
obj-$(CONFIG_CRUNCH) += crunch.o crunch-bits.o
AFLAGS_crunch-bits.o := -Wa,-mcpu=ep9312
......
arch/arm/kernel/asm-offsets.c
浏览文件 @ 36d99df2
......@@ -58,6 +58,9 @@ int main(void)
DEFINE(TI_TP_VALUE, offsetof(struct thread_info, tp_value));
DEFINE(TI_FPSTATE, offsetof(struct thread_info, fpstate));
DEFINE(TI_VFPSTATE, offsetof(struct thread_info, vfpstate));
#ifdef CONFIG_ARM_THUMBEE
DEFINE(TI_THUMBEE_STATE, offsetof(struct thread_info, thumbee_state));
#endif
#ifdef CONFIG_IWMMXT
DEFINE(TI_IWMMXT_STATE, offsetof(struct thread_info, fpstate.iwmmxt));
#endif
......@@ -108,5 +111,12 @@ int main(void)
DEFINE(PROCINFO_INITFUNC, offsetof(struct proc_info_list, __cpu_flush));
DEFINE(PROCINFO_MM_MMUFLAGS, offsetof(struct proc_info_list, __cpu_mm_mmu_flags));
DEFINE(PROCINFO_IO_MMUFLAGS, offsetof(struct proc_info_list, __cpu_io_mmu_flags));
BLANK();
#ifdef MULTI_DABORT
DEFINE(PROCESSOR_DABT_FUNC, offsetof(struct processor, _data_abort));
#endif
#ifdef MULTI_PABORT
DEFINE(PROCESSOR_PABT_FUNC, offsetof(struct processor, _prefetch_abort));
#endif
return 0;
}
arch/arm/kernel/calls.S
浏览文件 @ 36d99df2
......@@ -359,9 +359,11 @@
CALL(sys_kexec_load)
CALL(sys_utimensat)
CALL(sys_signalfd)
/* 350 */ CALL(sys_ni_syscall)
/* 350 */ CALL(sys_timerfd_create)
CALL(sys_eventfd)
CALL(sys_fallocate)
CALL(sys_timerfd_settime)
CALL(sys_timerfd_gettime)
#ifndef syscalls_counted
.equ syscalls_padding, ((NR_syscalls + 3) & ~3) - NR_syscalls
#define syscalls_counted
......
arch/arm/kernel/entry-armv.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/kernel/entry-common.S
浏览文件 @ 36d99df2
......@@ -352,6 +352,11 @@ sys_mmap2:
b do_mmap2
#endif
ENTRY(pabort_ifar)
mrc p15, 0, r0, cr6, cr0, 2
ENTRY(pabort_noifar)
mov pc, lr
#ifdef CONFIG_OABI_COMPAT
/*
......
arch/arm/kernel/head-common.S
浏览文件 @ 36d99df2
......@@ -75,8 +75,13 @@ __error_p:
#ifdef CONFIG_DEBUG_LL
adr r0, str_p1
bl printascii
mov r0, r9
bl printhex8
adr r0, str_p2
bl printascii
b __error
str_p1: .asciz "\nError: unrecognized/unsupported processor variant.\n"
str_p1: .asciz "\nError: unrecognized/unsupported processor variant (0x"
str_p2: .asciz ").\n"
.align
#endif
......
arch/arm/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/arm/kernel/thumbee.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-aaec2000/clock.c
浏览文件 @ 36d99df2
......@@ -18,8 +18,6 @@
#include <linux/clk.h>
#include <linux/mutex.h>
#include <asm/semaphore.h>
#include "clock.h"
static LIST_HEAD(clocks);
......
arch/arm/mach-at91/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ 36d99df2
......@@ -29,9 +29,12 @@ obj-$(CONFIG_MACH_KB9200) += board-kb9202.o
obj-$(CONFIG_MACH_ATEB9200) += board-eb9200.o
obj-$(CONFIG_MACH_KAFA) += board-kafa.o
obj-$(CONFIG_MACH_PICOTUX2XX) += board-picotux200.o
obj-$(CONFIG_MACH_ECBAT91) += board-ecbat91.o
# AT91SAM9260 board-specific support
obj-$(CONFIG_MACH_AT91SAM9260EK) += board-sam9260ek.o
obj-$(CONFIG_MACH_CAM60) += board-cam60.o
obj-$(CONFIG_MACH_SAM9_L9260) += board-sam9-l9260.o
# AT91SAM9261 board-specific support
obj-$(CONFIG_MACH_AT91SAM9261EK) += board-sam9261ek.o
......
arch/arm/mach-at91/at91cap9.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/at91sam9260.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/at91sam9261.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/at91sam9263.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/at91sam9rl.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-cam60.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-cap9adk.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-csb337.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-csb637.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-ecbat91.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-sam9-l9260.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/board-yl-9200.c 0 → 100755
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-clps711x/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ep93xx/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ep93xx/gpio.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-integrator/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-integrator/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-iop32x/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-iop32x/iq31244.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-iop32x/iq80321.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-iop33x/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-iop33x/iq80331.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-iop33x/iq80332.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ks8695/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ks8695/devices.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ks8695/leds.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/Makefile.boot
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/clock.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/clock.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/generic.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/generic.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/gpio-ns9360.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/gpio-ns9360.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/gpio.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/irq.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/plat-serial8250.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-ns9xxx/processor-ns9360.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap1/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap1/leds-osk.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap1/mux.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap1/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/board-2430sdp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/board-h4.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/clock.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/clock24xx.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/clock24xx.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/clock34xx.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/clock34xx.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/cm-regbits-24xx.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/cm-regbits-34xx.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/cm.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/control.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/memory.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/memory.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/pm-domain.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/arm/mach-omap2/pm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/prcm-common.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/prcm-regs.h 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/prm-regbits-24xx.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/prm-regbits-34xx.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/prm.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/sdrc.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/sleep.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/sram-fn.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-omap2/timer-gp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-orion/addr-map.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/arm/mach-orion5x/addr-map.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pnx4008/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pnx4008/gpio.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/cm-x270-pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/cm-x270.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/colibri.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/corgi_pm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/corgi_ssp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/devices.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/generic.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/generic.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/gpio.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/gumstix.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/idp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/irq.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/leds-trizeps4.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/littleton.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/mfp-pxa2xx.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/pcm027.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/pxa25x.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/pxa27x.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/pxa3xx.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/sharpsl_pm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/spitz.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/spitz_pm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/zylonite.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa300.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa320.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/core.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/core.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/platsmp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/realview_pb1176.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-realview/realview_pb11mp.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2410/mach-bast.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2410/mach-tct_hammer.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2410/mach-vr1000.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2412/s3c2412.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2440/mach-anubis.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-s3c2440/mach-osiris.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-sa1100/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-sa1100/generic.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-sa1100/generic.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-sa1100/gpio.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-sa1100/irq.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-sa1100/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mach-versatile/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm1020.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm1020e.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm1022.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm1026.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm6_7.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm720.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm920.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm922.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm925.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-arm926.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-feroceon.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-sa110.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-sa1100.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-v6.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-v7.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/mm/proc-xscale.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-iop/pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-mxc/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-mxc/irq.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-omap/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-omap/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-omap/common.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-omap/mux.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-omap/usb.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-orion/Makefile 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-orion/irq.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-orion/pcie.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-s3c24xx/clock.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/plat-s3c24xx/cpu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/kernel/entry-avr32b.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/kernel/process.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/avr32/kernel/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/mach-at32ap/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/mach-at32ap/at32ap700x.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/mach-at32ap/intc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/mach-at32ap/pm-at32ap700x.S 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/avr32/mach-at32ap/time-tc.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/avr32/mm/init.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/blackfin/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/blackfin/kernel/bfin_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/blackfin/kernel/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/cris/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/cris/kernel/crisksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/cris/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/frv/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/frv/kernel/frv_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/frv/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/frv/mb93090-mb00/pci-frv.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/frv/mb93090-mb00/pci-vdk.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/frv/mm/highmem.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/h8300/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/h8300/kernel/h8300_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/h8300/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/hp/sim/simeth.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/hp/sim/simscsi.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/ia32/elfcore32.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/asm-offsets.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/crash.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/efi.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/fsys.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/head.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/ia64_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/irq_ia64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/ivt.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/kprobes.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/mca.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/mca_asm.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/minstate.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/numa.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/patch.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/process.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/ptrace.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/salinfo.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/smp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/smpboot.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/kernel/unaligned.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/mm/contig.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/mm/discontig.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/mm/numa.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/mm/tlb.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/sn/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/sn/kernel/huberror.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/sn/kernel/sn2/sn_hwperf.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ia64/sn/pci/tioce_provider.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/m32r/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/m32r/kernel/m32r_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/m32r/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/m68k/atari/stram.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68k/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68k/kernel/m68k_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68k/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/m68k/lib/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68k/lib/semaphore.S 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/m68k/sun3/intersil.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68knommu/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68knommu/kernel/m68k_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68knommu/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/m68knommu/lib/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/m68knommu/lib/semaphore.S 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/mips/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/mips/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/mips/sgi-ip27/ip27-console.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/mn10300/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/mn10300/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/parisc/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/parisc/kernel/parisc_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/parisc/kernel/pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/parisc/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/parisc/kernel/sys_parisc32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/bamboo.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cpm-serial.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cuboot-pq2.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cuboot-rainier.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cuboot-sequoia.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cuboot-taishan.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cuboot-warp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/cuboot-yosemite.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/devtree.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/bamboo.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/canyonlands.dts 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/ebony.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/ep8248e.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/ep88xc.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/glacier.dts 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/haleakala.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/katmai.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/kilauea.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/ksi8560.dts 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/kuroboxHD.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/kuroboxHG.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/makalu.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/mpc8544ds.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/mpc8572ds.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/mpc866ads.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/mpc885ads.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/pq2fads.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/prpmc2800.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/rainier.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/sbc8641d.dts 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/sequoia.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/taishan.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/walnut.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/warp.dts
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/dts/yosemite.dts 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/ebony.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/libfdt-wrapper.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/mpc52xx-psc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/mpsc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/mv64x60.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/mv64x60_i2c.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/ns16550.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/ops.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/prpmc2800.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/ps3-head.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/ps3.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/serial.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/simpleboot.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/treeboot-walnut.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/virtex405-head.S 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/boot/wrapper
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/configs/44x/canyonlands_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/configs/85xx/ksi8560_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/configs/g5_defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/configs/ppc40x_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/configs/sbc8641d_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/btext.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/cpu_setup_44x.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/crash.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/crash_dump.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/entry_32.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/head_32.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/head_44x.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/head_booke.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/ibmebus.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/iommu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/isa-bridge.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/machine_kexec.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/paca.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/pci-common.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/ppc32.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/process.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/ptrace32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/rtas_flash.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/rtas_pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/signal_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/stacktrace.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/sys_ppc32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/syscalls.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/vdso.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/lib/rheap.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/lib/string.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fabs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fadd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fadds.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fcmpo.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fcmpu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fctiw.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fctiwz.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fdiv.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fdivs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmadd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmadds.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmr.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmsub.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmsubs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmul.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fmuls.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fnabs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fneg.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fnmadd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fnmadds.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fnmsub.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fnmsubs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fres.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/frsp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/frsqrte.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fsel.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fsqrt.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fsqrts.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fsub.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/fsubs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/lfd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/lfs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/mcrfs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/mffs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/mtfsb0.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/mtfsb1.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/mtfsf.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/mtfsfi.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/stfd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/stfiwx.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/math-emu/stfs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/40x_mmu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/44x_mmu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/fsl_booke_mmu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/init_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/init_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/mmu_decl.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/pgtable_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/ppc_mmu_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/mm/stab.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/40x/ep405.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/40x/makalu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/40x/virtex.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/40x/walnut.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/44x.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/bamboo.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/canyonlands.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/ebony.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/idle.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/katmai.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/44x/warp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/82xx/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/83xx/usb.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/85xx/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/85xx/ksi8560.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/86xx/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/86xx/sbc8641d.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/8xx/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/cell/ras.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/maple/pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/ps3/htab.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/ps3/mm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/ps3/setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/ps3/spu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/platforms/pseries/phyp_dump.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/cpm1.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/cpm2.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/cpm_common.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/dart_iommu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/fsl_lbc.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/mpic.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/mv64x60_dev.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/mv64x60_pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/mv64x60_pic.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/mv64x60_udbg.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/ppc4xx_pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/ppc4xx_pci.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/ppc4xx_soc.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/qe_lib/qe.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/qe_lib/qe_io.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/tsi108_dev.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/sysdev/tsi108_pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/8xx_io/commproc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/8xx_io/fec.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/kernel/head.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/kernel/pci.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/kernel/ppc_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/ppc/kernel/setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/mm/init.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/4xx/bamboo.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/4xx/ebony.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/4xx/luan.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/4xx/ocotea.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/4xx/taishan.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/4xx/yucca.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/chestnut.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/cpci690.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/ev64260.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/hdpu.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/lopec.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/mvme5100.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/powerpmc250.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/pplus.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/prep_setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/prpmc750.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/prpmc800.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/radstone_ppc7d.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/residual.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/sandpoint.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/sandpoint.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/sbc82xx.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/platforms/spruce.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/syslib/m8xx_setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/syslib/mpc52xx_setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/syslib/ocp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/ppc/syslib/ppc4xx_setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/aes_s390.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/crypt_s390.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/des_s390.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/sha.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/sha1_s390.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/sha256_s390.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/sha512_s390.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/crypto/sha_common.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/compat_linux.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/compat_signal.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/early.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/entry.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/entry64.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/ipl.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/kprobes.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/process.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/ptrace.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/s390_ext.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/s390_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/signal.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/sys_s390.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/topology.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/kernel/traps.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/lib/delay.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/lib/uaccess_pt.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/mm/extmem.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/mm/fault.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/Kconfig.debug
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/boards/se/7721/Makefile 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/boards/se/7721/irq.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/boards/se/7721/setup.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/boards/se/7722/setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/configs/se7721_defconfig 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/drivers/pci/pci-sh4.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/Makefile_32
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/Makefile_64
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cf-enabler.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cpu/sh2a/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cpu/sh2a/probe.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cpu/sh2a/setup-mxg.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cpu/sh4/probe.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cpu/sh4a/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/cpu/sh4a/setup-sh7723.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sh/kernel/setup.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/sh_ksyms_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/kernel/sh_ksyms_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/lib/clear_page.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/lib/copy_page.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/mm/cache-debugfs.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/mm/pmb.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sh/tools/mach-types
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/entry.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/errtbls.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/head.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/sclow.S 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/signal.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/sparc_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/sunos_asm.S 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/sunos_ioctl.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/sys_solaris.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/sys_sunos.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc/kernel/systbls.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc/kernel/time.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/defconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/binfmt_aout32.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/kernel/entry.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/kernel/signal.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/signal32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/sparc64_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/sunos_ioctl32.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/kernel/sys_sparc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/sys_sparc32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/sys_sunos32.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/kernel/systbls.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/systbls.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/kernel/ttable.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/sparc64/solaris/Makefile 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/conv.h 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/entry64.S 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/fs.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/ioctl.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/ipc.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/misc.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/signal.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/signal.h 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/socket.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/socksys.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/socksys.h 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/systbl.S 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/sparc64/solaris/timod.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/um/Kconfig.i386
浏览文件 @ 36d99df2
此差异已折叠。
arch/um/Kconfig.x86_64
浏览文件 @ 36d99df2
此差异已折叠。
arch/um/sys-i386/ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/um/sys-ppc/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/um/sys-x86_64/ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/v850/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/v850/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/v850/kernel/syscalls.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/v850/kernel/v850_ksyms.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/Kconfig
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/Kconfig.cpu
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/Kconfig.debug
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/a20.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/apm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/bitops.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/boot.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/cmdline.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/compressed/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/compressed/head_32.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/compressed/head_64.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/compressed/misc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/copy.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/cpucheck.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/edd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/header.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/install.sh
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/main.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/mca.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/memory.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/pm.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/pmjump.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/printf.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/string.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/tools/build.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/tty.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/version.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/video-bios.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/video-mode.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/video-vesa.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/video-vga.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/video.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/video.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/boot/voyager.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/crypto/aes-i586-asm_32.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/ia32/ia32_signal.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/ia32/ia32entry.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/ia32/sys_ia32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/boot.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/cstate.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/processor.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/Makefile 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/copy.S 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/video-bios.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/video-mode.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/video-vesa.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/video-vga.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/wakemain.c 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/wakeup.S 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/wakeup.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/realmode/wakeup.lds.S 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/sleep.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/sleep.h 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/sleep_32.c 已删除 100644 → 0
浏览文件 @ 076d8423
此差异已折叠。
arch/x86/kernel/acpi/wakeup_32.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/wakeup_64.S
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/acpi/wakeup_rm.S 0 → 100644
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/alternative.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/aperture_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/apic_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/apic_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/apm_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/asm-offsets_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/bugs_64.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/Makefile
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/amd.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/centaur.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/common.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/cpu.h
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/cyrix.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/feature_names.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/intel.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mcheck/mce_32.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mcheck/p5.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mcheck/p6.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/generic.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/if.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/main.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/state.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/nexgen.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/proc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/transmeta.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpu/umc.c
浏览文件 @ 36d99df2
此差异已折叠。
arch/x86/kernel/cpuid.c
浏览文件 @ 36d99df2
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或