Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 cb28a1bb 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge branch 'linus' into core/generic-dma-coherent 

Conflicts:

	arch/x86/Kconfig
Signed-off-by: NIngo Molnar <mingo@elte.hu>
上级 b6d4f7e3 f934fb19
展开全部 隐藏空白更改
内联 并排
Showing with 54916 addition and 9792 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ cb28a1bb
......@@ -317,6 +317,14 @@ S: 2322 37th Ave SW
S: Seattle, Washington 98126-2010
S: USA
N: Muli Ben-Yehuda
E: mulix@mulix.org
E: muli@il.ibm.com
W: http://www.mulix.org
D: trident OSS sound driver, x86-64 dma-ops and Calgary IOMMU,
D: KVM and Xen bits and other misc. hackery.
S: Haifa, Israel
N: Johannes Berg
E: johannes@sipsolutions.net
W: http://johannes.sipsolutions.net/
......@@ -3344,8 +3352,7 @@ S: Spain
N: Linus Torvalds
E: torvalds@linux-foundation.org
D: Original kernel hacker
S: 12725 SW Millikan Way, Suite 400
S: Beaverton, Oregon 97005
S: Portland, Oregon 97005
S: USA
N: Marcelo Tosatti
......
Documentation/00-INDEX
浏览文件 @ cb28a1bb
......@@ -361,8 +361,6 @@ telephony/
- directory with info on telephony (e.g. voice over IP) support.
time_interpolators.txt
- info on time interpolators.
tipar.txt
- information about Parallel link cable for Texas Instruments handhelds.
tty.txt
- guide to the locking policies of the tty layer.
uml/
......
Documentation/ABI/testing/sysfs-dev 0 → 100644
浏览文件 @ cb28a1bb
What: /sys/dev
Date: April 2008
KernelVersion: 2.6.26
Contact: Dan Williams <dan.j.williams@intel.com>
Description: The /sys/dev tree provides a method to look up the sysfs
path for a device using the information returned from
stat(2). There are two directories, 'block' and 'char',
beneath /sys/dev containing symbolic links with names of
the form "<major>:<minor>". These links point to the
corresponding sysfs path for the given device.
Example:
$ readlink /sys/dev/block/8:32
../../block/sdc
Entries in /sys/dev/char and /sys/dev/block will be
dynamically created and destroyed as devices enter and
leave the system.
Users: mdadm <linux-raid@vger.kernel.org>
Documentation/ABI/testing/sysfs-devices-memory 0 → 100644
浏览文件 @ cb28a1bb
What: /sys/devices/system/memory
Date: June 2008
Contact: Badari Pulavarty <pbadari@us.ibm.com>
Description:
The /sys/devices/system/memory contains a snapshot of the
internal state of the kernel memory blocks. Files could be
added or removed dynamically to represent hot-add/remove
operations.
Users: hotplug memory add/remove tools
https://w3.opensource.ibm.com/projects/powerpc-utils/
What: /sys/devices/system/memory/memoryX/removable
Date: June 2008
Contact: Badari Pulavarty <pbadari@us.ibm.com>
Description:
The file /sys/devices/system/memory/memoryX/removable
indicates whether this memory block is removable or not.
This is useful for a user-level agent to determine
identify removable sections of the memory before attempting
potentially expensive hot-remove memory operation
Users: hotplug memory remove tools
https://w3.opensource.ibm.com/projects/powerpc-utils/
Documentation/ABI/testing/sysfs-kernel-mm 0 → 100644
浏览文件 @ cb28a1bb
What: /sys/kernel/mm
Date: July 2008
Contact: Nishanth Aravamudan <nacc@us.ibm.com>, VM maintainers
Description:
/sys/kernel/mm/ should contain any and all VM
related information in /sys/kernel/.
Documentation/ABI/testing/sysfs-kernel-mm-hugepages 0 → 100644
浏览文件 @ cb28a1bb
What: /sys/kernel/mm/hugepages/
Date: June 2008
Contact: Nishanth Aravamudan <nacc@us.ibm.com>, hugetlb maintainers
Description:
/sys/kernel/mm/hugepages/ contains a number of subdirectories
of the form hugepages-<size>kB, where <size> is the page size
of the hugepages supported by the kernel/CPU combination.
Under these directories are a number of files:
nr_hugepages
nr_overcommit_hugepages
free_hugepages
surplus_hugepages
resv_hugepages
See Documentation/vm/hugetlbpage.txt for details.
Documentation/CodingStyle
浏览文件 @ cb28a1bb
......@@ -474,25 +474,29 @@ make a good program).
So, you can either get rid of GNU emacs, or change it to use saner
values. To do the latter, you can stick the following in your .emacs file:
(defun linux-c-mode ()
"C mode with adjusted defaults for use with the Linux kernel."
(interactive)
(c-mode)
(c-set-style "K&R")
(setq tab-width 8)
(setq indent-tabs-mode t)
(setq c-basic-offset 8))
This will define the M-x linux-c-mode command. When hacking on a
module, if you put the string -*- linux-c -*- somewhere on the first
two lines, this mode will be automatically invoked. Also, you may want
to add
(setq auto-mode-alist (cons '("/usr/src/linux.*/.*\\.[ch]$" . linux-c-mode)
auto-mode-alist))
to your .emacs file if you want to have linux-c-mode switched on
automagically when you edit source files under /usr/src/linux.
(defun c-lineup-arglist-tabs-only (ignored)
"Line up argument lists by tabs, not spaces"
(let* ((anchor (c-langelem-pos c-syntactic-element))
(column (c-langelem-2nd-pos c-syntactic-element))
(offset (- (1+ column) anchor))
(steps (floor offset c-basic-offset)))
(* (max steps 1)
c-basic-offset)))
(add-hook 'c-mode-hook
(lambda ()
(let ((filename (buffer-file-name)))
;; Enable kernel mode for the appropriate files
(when (and filename
(string-match "~/src/linux-trees" filename))
(setq indent-tabs-mode t)
(c-set-style "linux")
(c-set-offset 'arglist-cont-nonempty
'(c-lineup-gcc-asm-reg
c-lineup-arglist-tabs-only))))))
This will make emacs go better with the kernel coding style for C
files below ~/src/linux-trees.
But even if you fail in getting emacs to do sane formatting, not
everything is lost: use "indent".
......
Documentation/DMA-API.txt
浏览文件 @ cb28a1bb
......@@ -298,10 +298,10 @@ recommended that you never use these unless you really know what the
cache width is.
int
dma_mapping_error(dma_addr_t dma_addr)
dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
int
pci_dma_mapping_error(dma_addr_t dma_addr)
pci_dma_mapping_error(struct pci_dev *hwdev, dma_addr_t dma_addr)
In some circumstances dma_map_single and dma_map_page will fail to create
a mapping. A driver can check for these errors by testing the returned
......
Documentation/DMA-attributes.txt
浏览文件 @ cb28a1bb
......@@ -22,3 +22,12 @@ ready and available in memory. The DMA of the "completion indication"
could race with data DMA. Mapping the memory used for completion
indications with DMA_ATTR_WRITE_BARRIER would prevent the race.
DMA_ATTR_WEAK_ORDERING
----------------------
DMA_ATTR_WEAK_ORDERING specifies that reads and writes to the mapping
may be weakly ordered, that is that reads and writes may pass each other.
Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
those that do not will simply ignore the attribute and exhibit default
behavior.
Documentation/DocBook/gadget.tmpl
浏览文件 @ cb28a1bb
......@@ -524,6 +524,44 @@ These utilities include endpoint autoconfiguration.
<!-- !Edrivers/usb/gadget/epautoconf.c -->
</sect1>
<sect1 id="composite"><title>Composite Device Framework</title>
<para>The core API is sufficient for writing drivers for composite
USB devices (with more than one function in a given configuration),
and also multi-configuration devices (also more than one function,
but not necessarily sharing a given configuration).
There is however an optional framework which makes it easier to
reuse and combine functions.
</para>
<para>Devices using this framework provide a <emphasis>struct
usb_composite_driver</emphasis>, which in turn provides one or
more <emphasis>struct usb_configuration</emphasis> instances.
Each such configuration includes at least one
<emphasis>struct usb_function</emphasis>, which packages a user
visible role such as "network link" or "mass storage device".
Management functions may also exist, such as "Device Firmware
Upgrade".
</para>
!Iinclude/linux/usb/composite.h
!Edrivers/usb/gadget/composite.c
</sect1>
<sect1 id="functions"><title>Composite Device Functions</title>
<para>At this writing, a few of the current gadget drivers have
been converted to this framework.
Near-term plans include converting all of them, except for "gadgetfs".
</para>
!Edrivers/usb/gadget/f_acm.c
!Edrivers/usb/gadget/f_serial.c
</sect1>
</chapter>
<chapter id="controllers"><title>Peripheral Controller Drivers</title>
......
Documentation/DocBook/kernel-locking.tmpl
浏览文件 @ cb28a1bb
......@@ -219,10 +219,10 @@
</para>
<sect1 id="lock-intro">
<title>Three Main Types of Kernel Locks: Spinlocks, Mutexes and Semaphores</title>
<title>Two Main Types of Kernel Locks: Spinlocks and Mutexes</title>
<para>
There are three main types of kernel locks. The fundamental type
There are two main types of kernel locks. The fundamental type
is the spinlock
(<filename class="headerfile">include/asm/spinlock.h</filename>),
which is a very simple single-holder lock: if you can't get the
......@@ -239,14 +239,6 @@
can't sleep (see <xref linkend="sleeping-things"/>), and so have to
use a spinlock instead.
</para>
<para>
The third type is a semaphore
(<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
task will be suspended and later on woken up - just like for mutexes.
</para>
<para>
Neither type of lock is recursive: see
<xref linkend="deadlock"/>.
......@@ -278,7 +270,7 @@
</para>
<para>
Semaphores still exist, because they are required for
Mutexes still exist, because they are required for
synchronization between <firstterm linkend="gloss-usercontext">user
contexts</firstterm>, as we will see below.
</para>
......@@ -289,18 +281,17 @@
<para>
If you have a data structure which is only ever accessed from
user context, then you can use a simple semaphore
(<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
<function>up()</function> to release it. There is also a
<function>down()</function>, which should be avoided, because it
user context, then you can use a simple mutex
(<filename>include/linux/mutex.h</filename>) to protect it. This
is the most trivial case: you initialize the mutex. Then you can
call <function>mutex_lock_interruptible()</function> to grab the mutex,
and <function>mutex_unlock()</function> to release it. There is also a
<function>mutex_lock()</function>, which should be avoided, because it
will not return if a signal is received.
</para>
<para>
Example: <filename>linux/net/core/netfilter.c</filename> allows
Example: <filename>net/netfilter/nf_sockopt.c</filename> allows
registration of new <function>setsockopt()</function> and
<function>getsockopt()</function> calls, with
<function>nf_register_sockopt()</function>. Registration and
......@@ -515,7 +506,7 @@
<listitem>
<para>
If you are in a process context (any syscall) and want to
lock other process out, use a semaphore. You can take a semaphore
lock other process out, use a mutex. You can take a mutex
and sleep (<function>copy_from_user*(</function> or
<function>kmalloc(x,GFP_KERNEL)</function>).
</para>
......@@ -662,7 +653,7 @@
<entry>SLBH</entry>
<entry>SLBH</entry>
<entry>SLBH</entry>
<entry>DI</entry>
<entry>MLI</entry>
<entry>None</entry>
</row>
......@@ -692,8 +683,8 @@
<entry>spin_lock_bh</entry>
</row>
<row>
<entry>DI</entry>
<entry>down_interruptible</entry>
<entry>MLI</entry>
<entry>mutex_lock_interruptible</entry>
</row>
</tbody>
......@@ -1310,7 +1301,7 @@ as Alan Cox says, <quote>Lock data, not code</quote>.
<para>
There is a coding bug where a piece of code tries to grab a
spinlock twice: it will spin forever, waiting for the lock to
be released (spinlocks, rwlocks and semaphores are not
be released (spinlocks, rwlocks and mutexes are not
recursive in Linux). This is trivial to diagnose: not a
stay-up-five-nights-talk-to-fluffy-code-bunnies kind of
problem.
......@@ -1335,7 +1326,7 @@ as Alan Cox says, <quote>Lock data, not code</quote>.
<para>
This complete lockup is easy to diagnose: on SMP boxes the
watchdog timer or compiling with <symbol>DEBUG_SPINLOCKS</symbol> set
watchdog timer or compiling with <symbol>DEBUG_SPINLOCK</symbol> set
(<filename>include/linux/spinlock.h</filename>) will show this up
immediately when it happens.
</para>
......@@ -1558,7 +1549,7 @@ the amount of locking which needs to be done.
<title>Read/Write Lock Variants</title>
<para>
Both spinlocks and semaphores have read/write variants:
Both spinlocks and mutexes have read/write variants:
<type>rwlock_t</type> and <structname>struct rw_semaphore</structname>.
These divide users into two classes: the readers and the writers. If
you are only reading the data, you can get a read lock, but to write to
......@@ -1681,7 +1672,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;linux/semaphore.h&gt;
#include &lt;linux/mutex.h&gt;
#include &lt;asm/errno.h&gt;
struct object
......@@ -1913,7 +1904,7 @@ machines due to caching.
</listitem>
<listitem>
<para>
<function> put_user()</function>
<function>put_user()</function>
</para>
</listitem>
</itemizedlist>
......@@ -1927,13 +1918,13 @@ machines due to caching.
<listitem>
<para>
<function>down_interruptible()</function> and
<function>down()</function>
<function>mutex_lock_interruptible()</function> and
<function>mutex_lock()</function>
</para>
<para>
There is a <function>down_trylock()</function> which can be
There is a <function>mutex_trylock()</function> which can be
used inside interrupt context, as it will not sleep.
<function>up()</function> will also never sleep.
<function>mutex_unlock()</function> will also never sleep.
</para>
</listitem>
</itemizedlist>
......@@ -2023,7 +2014,7 @@ machines due to caching.
<para>
Prior to 2.5, or when <symbol>CONFIG_PREEMPT</symbol> is
unset, processes in user context inside the kernel would not
preempt each other (ie. you had that CPU until you have it up,
preempt each other (ie. you had that CPU until you gave it up,
except for interrupts). With the addition of
<symbol>CONFIG_PREEMPT</symbol> in 2.5.4, this changed: when
in user context, higher priority tasks can "cut in": spinlocks
......
Documentation/DocBook/procfs-guide.tmpl
浏览文件 @ cb28a1bb
......@@ -29,12 +29,12 @@
<revhistory>
<revision>
<revnumber>1.0&nbsp;</revnumber>
<revnumber>1.0</revnumber>
<date>May 30, 2001</date>
<revremark>Initial revision posted to linux-kernel</revremark>
</revision>
<revision>
<revnumber>1.1&nbsp;</revnumber>
<revnumber>1.1</revnumber>
<date>June 3, 2001</date>
<revremark>Revised after comments from linux-kernel</revremark>
</revision>
......
Documentation/DocBook/uio-howto.tmpl
浏览文件 @ cb28a1bb
......@@ -21,6 +21,18 @@
</affiliation>
</author>
<copyright>
<year>2006-2008</year>
<holder>Hans-Jürgen Koch.</holder>
</copyright>
<legalnotice>
<para>
This documentation is Free Software licensed under the terms of the
GPL version 2.
</para>
</legalnotice>
<pubdate>2006-12-11</pubdate>
<abstract>
......@@ -29,6 +41,12 @@
</abstract>
<revhistory>
<revision>
<revnumber>0.5</revnumber>
<date>2008-05-22</date>
<authorinitials>hjk</authorinitials>
<revremark>Added description of write() function.</revremark>
</revision>
<revision>
<revnumber>0.4</revnumber>
<date>2007-11-26</date>
......@@ -57,20 +75,9 @@
</bookinfo>
<chapter id="aboutthisdoc">
<?dbhtml filename="about.html"?>
<?dbhtml filename="aboutthis.html"?>
<title>About this document</title>
<sect1 id="copyright">
<?dbhtml filename="copyright.html"?>
<title>Copyright and License</title>
<para>
Copyright (c) 2006 by Hans-Jürgen Koch.</para>
<para>
This documentation is Free Software licensed under the terms of the
GPL version 2.
</para>
</sect1>
<sect1 id="translations">
<?dbhtml filename="translations.html"?>
<title>Translations</title>
......@@ -189,6 +196,30 @@ interested in translating it, please email me
represents the total interrupt count. You can use this number
to figure out if you missed some interrupts.
</para>
<para>
For some hardware that has more than one interrupt source internally,
but not separate IRQ mask and status registers, there might be
situations where userspace cannot determine what the interrupt source
was if the kernel handler disables them by writing to the chip's IRQ
register. In such a case, the kernel has to disable the IRQ completely
to leave the chip's register untouched. Now the userspace part can
determine the cause of the interrupt, but it cannot re-enable
interrupts. Another cornercase is chips where re-enabling interrupts
is a read-modify-write operation to a combined IRQ status/acknowledge
register. This would be racy if a new interrupt occurred
simultaneously.
</para>
<para>
To address these problems, UIO also implements a write() function. It
is normally not used and can be ignored for hardware that has only a
single interrupt source or has separate IRQ mask and status registers.
If you need it, however, a write to <filename>/dev/uioX</filename>
will call the <function>irqcontrol()</function> function implemented
by the driver. You have to write a 32-bit value that is usually either
0 or 1 to disable or enable interrupts. If a driver does not implement
<function>irqcontrol()</function>, <function>write()</function> will
return with <varname>-ENOSYS</varname>.
</para>
<para>
To handle interrupts properly, your custom kernel module can
......@@ -362,6 +393,14 @@ device is actually used.
<function>open()</function>, you will probably also want a custom
<function>release()</function> function.
</para></listitem>
<listitem><para>
<varname>int (*irqcontrol)(struct uio_info *info, s32 irq_on)
</varname>: Optional. If you need to be able to enable or disable
interrupts from userspace by writing to <filename>/dev/uioX</filename>,
you can implement this function. The parameter <varname>irq_on</varname>
will be 0 to disable interrupts and 1 to enable them.
</para></listitem>
</itemizedlist>
<para>
......
Documentation/HOWTO
浏览文件 @ cb28a1bb
......@@ -358,7 +358,7 @@ Here is a list of some of the different kernel trees available:
- pcmcia, Dominik Brodowski <linux@dominikbrodowski.net>
git.kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git
- SCSI, James Bottomley <James.Bottomley@SteelEye.com>
- SCSI, James Bottomley <James.Bottomley@hansenpartnership.com>
git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
- x86, Ingo Molnar <mingo@elte.hu>
......
Documentation/Intel-IOMMU.txt
浏览文件 @ cb28a1bb
......@@ -48,7 +48,7 @@ IOVA generation is pretty generic. We used the same technique as vmalloc()
but these are not global address spaces, but separate for each domain.
Different DMA engines may support different number of domains.
We also allocate gaurd pages with each mapping, so we can attempt to catch
We also allocate guard pages with each mapping, so we can attempt to catch
any overflow that might happen.
......@@ -112,4 +112,4 @@ TBD
- For compatibility testing, could use unity map domain for all devices, just
provide a 1-1 for all useful memory under a single domain for all devices.
- API for paravirt ops for abstracting functionlity for VMM folks.
- API for paravirt ops for abstracting functionality for VMM folks.
Documentation/SubmittingPatches
浏览文件 @ cb28a1bb
......@@ -528,7 +528,33 @@ See more details on the proper patch format in the following
references.
16) Sending "git pull" requests (from Linus emails)
Please write the git repo address and branch name alone on the same line
so that I can't even by mistake pull from the wrong branch, and so
that a triple-click just selects the whole thing.
So the proper format is something along the lines of:
"Please pull from
git://jdelvare.pck.nerim.net/jdelvare-2.6 i2c-for-linus
to get these changes:"
so that I don't have to hunt-and-peck for the address and inevitably
get it wrong (actually, I've only gotten it wrong a few times, and
checking against the diffstat tells me when I get it wrong, but I'm
just a lot more comfortable when I don't have to "look for" the right
thing to pull, and double-check that I have the right branch-name).
Please use "git diff -M --stat --summary" to generate the diffstat:
the -M enables rename detection, and the summary enables a summary of
new/deleted or renamed files.
With rename detection, the statistics are rather different [...]
because git will notice that a fair number of the changes are renames.
-----------------------------------
SECTION 2 - HINTS, TIPS, AND TRICKS
......
Documentation/accounting/delay-accounting.txt
浏览文件 @ cb28a1bb
......@@ -11,6 +11,7 @@ the delays experienced by a task while
a) waiting for a CPU (while being runnable)
b) completion of synchronous block I/O initiated by the task
c) swapping in pages
d) memory reclaim
and makes these statistics available to userspace through
the taskstats interface.
......@@ -41,7 +42,7 @@ this structure. See
include/linux/taskstats.h
for a description of the fields pertaining to delay accounting.
It will generally be in the form of counters returning the cumulative
delay seen for cpu, sync block I/O, swapin etc.
delay seen for cpu, sync block I/O, swapin, memory reclaim etc.
Taking the difference of two successive readings of a given
counter (say cpu_delay_total) for a task will give the delay
......@@ -94,7 +95,9 @@ CPU count real total virtual total delay total
7876 92005750 100000000 24001500
IO count delay total
0 0
MEM count delay total
SWAP count delay total
0 0
RECLAIM count delay total
0 0
Get delays seen in executing a given simple command
......@@ -108,5 +111,7 @@ CPU count real total virtual total delay total
6 4000250 4000000 0
IO count delay total
0 0
MEM count delay total
SWAP count delay total
0 0
RECLAIM count delay total
0 0
Documentation/accounting/getdelays.c
浏览文件 @ cb28a1bb
......@@ -196,14 +196,18 @@ void print_delayacct(struct taskstats *t)
" %15llu%15llu%15llu%15llu\n"
"IO %15s%15s\n"
" %15llu%15llu\n"
"MEM %15s%15s\n"
"SWAP %15s%15s\n"
" %15llu%15llu\n"
"RECLAIM %12s%15s\n"
" %15llu%15llu\n",
"count", "real total", "virtual total", "delay total",
t->cpu_count, t->cpu_run_real_total, t->cpu_run_virtual_total,
t->cpu_delay_total,
"count", "delay total",
t->blkio_count, t->blkio_delay_total,
"count", "delay total", t->swapin_count, t->swapin_delay_total);
"count", "delay total", t->swapin_count, t->swapin_delay_total,
"count", "delay total",
t->freepages_count, t->freepages_delay_total);
}
void task_context_switch_counts(struct taskstats *t)
......
Documentation/accounting/taskstats-struct.txt
浏览文件 @ cb28a1bb
......@@ -6,7 +6,7 @@ This document contains an explanation of the struct taskstats fields.
There are three different groups of fields in the struct taskstats:
1) Common and basic accounting fields
If CONFIG_TASKSTATS is set, the taskstats inteface is enabled and
If CONFIG_TASKSTATS is set, the taskstats interface is enabled and
the common fields and basic accounting fields are collected for
delivery at do_exit() of a task.
2) Delay accounting fields
......@@ -26,6 +26,8 @@ There are three different groups of fields in the struct taskstats:
5) Time accounting for SMT machines
6) Extended delay accounting fields for memory reclaim
Future extension should add fields to the end of the taskstats struct, and
should not change the relative position of each field within the struct.
......@@ -170,4 +172,9 @@ struct taskstats {
__u64 ac_utimescaled; /* utime scaled on frequency etc */
__u64 ac_stimescaled; /* stime scaled on frequency etc */
__u64 cpu_scaled_run_real_total; /* scaled cpu_run_real_total */
6) Extended delay accounting fields for memory reclaim
/* Delay waiting for memory reclaim */
__u64 freepages_count;
__u64 freepages_delay_total;
}
Documentation/arm/Interrupts
浏览文件 @ cb28a1bb
......@@ -138,14 +138,8 @@ So, what's changed?
Set active the IRQ edge(s)/level. This replaces the
SA1111 INTPOL manipulation, and the set_GPIO_IRQ_edge()
function. Type should be one of the following:
#define IRQT_NOEDGE (0)
#define IRQT_RISING (__IRQT_RISEDGE)
#define IRQT_FALLING (__IRQT_FALEDGE)
#define IRQT_BOTHEDGE (__IRQT_RISEDGE|__IRQT_FALEDGE)
#define IRQT_LOW (__IRQT_LOWLVL)
#define IRQT_HIGH (__IRQT_HIGHLVL)
function. Type should be one of IRQ_TYPE_xxx defined in
<linux/irq.h>
3. set_GPIO_IRQ_edge() is obsolete, and should be replaced by set_irq_type.
......
Documentation/bt8xxgpio.txt 0 → 100644
浏览文件 @ cb28a1bb
===============================================================
== BT8XXGPIO driver ==
== ==
== A driver for a selfmade cheap BT8xx based PCI GPIO-card ==
== ==
== For advanced documentation, see ==
== http://www.bu3sch.de/btgpio.php ==
===============================================================
A generic digital 24-port PCI GPIO card can be built out of an ordinary
Brooktree bt848, bt849, bt878 or bt879 based analog TV tuner card. The
Brooktree chip is used in old analog Hauppauge WinTV PCI cards. You can easily
find them used for low prices on the net.
The bt8xx chip does have 24 digital GPIO ports.
These ports are accessible via 24 pins on the SMD chip package.
==============================================
== How to physically access the GPIO pins ==
==============================================
The are several ways to access these pins. One might unsolder the whole chip
and put it on a custom PCI board, or one might only unsolder each individual
GPIO pin and solder that to some tiny wire. As the chip package really is tiny
there are some advanced soldering skills needed in any case.
The physical pinouts are drawn in the following ASCII art.
The GPIO pins are marked with G00-G23
G G G G G G G G G G G G G G G G G G
0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
---------------------------------------------------------------------------
--| ^ ^ |--
--| pin 86 pin 67 |--
--| |--
--| pin 61 > |-- G18
--| |-- G19
--| |-- G20
--| |-- G21
--| |-- G22
--| pin 56 > |-- G23
--| |--
--| Brooktree 878/879 |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| |--
--| O |--
--| |--
---------------------------------------------------------------------------
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
^
This is pin 1
Documentation/controllers/memory.txt
浏览文件 @ cb28a1bb
......@@ -242,8 +242,7 @@ rmdir() if there are no tasks.
1. Add support for accounting huge pages (as a separate controller)
2. Make per-cgroup scanner reclaim not-shared pages first
3. Teach controller to account for shared-pages
4. Start reclamation when the limit is lowered
5. Start reclamation in the background when the limit is
4. Start reclamation in the background when the limit is
not yet hit but the usage is getting closer
Summary
......
Documentation/cpu-freq/governors.txt
浏览文件 @ cb28a1bb
......@@ -122,7 +122,7 @@ around '10000' or more.
show_sampling_rate_(min|max): the minimum and maximum sampling rates
available that you may set 'sampling_rate' to.
up_threshold: defines what the average CPU usaged between the samplings
up_threshold: defines what the average CPU usage between the samplings
of 'sampling_rate' needs to be for the kernel to make a decision on
whether it should increase the frequency. For example when it is set
to its default value of '80' it means that between the checking
......
Documentation/edac.txt
浏览文件 @ cb28a1bb
......@@ -222,74 +222,9 @@ both csrow2 and csrow3 are populated, this indicates a dual ranked
set of DIMMs for channels 0 and 1.
Within each of the 'mc','mcX' and 'csrowX' directories are several
Within each of the 'mcX' and 'csrowX' directories are several
EDAC control and attribute files.
============================================================================
DIRECTORY 'mc'
In directory 'mc' are EDAC system overall control and attribute files:
Panic on UE control file:
'edac_mc_panic_on_ue'
An uncorrectable error will cause a machine panic. This is usually
desirable. It is a bad idea to continue when an uncorrectable error
occurs - it is indeterminate what was uncorrected and the operating
system context might be so mangled that continuing will lead to further
corruption. If the kernel has MCE configured, then EDAC will never
notice the UE.
LOAD TIME: module/kernel parameter: panic_on_ue=[0|1]
RUN TIME: echo "1" >/sys/devices/system/edac/mc/edac_mc_panic_on_ue
Log UE control file:
'edac_mc_log_ue'
Generate kernel messages describing uncorrectable errors. These errors
are reported through the system message log system. UE statistics
will be accumulated even when UE logging is disabled.
LOAD TIME: module/kernel parameter: log_ue=[0|1]
RUN TIME: echo "1" >/sys/devices/system/edac/mc/edac_mc_log_ue
Log CE control file:
'edac_mc_log_ce'
Generate kernel messages describing correctable errors. These
errors are reported through the system message log system.
CE statistics will be accumulated even when CE logging is disabled.
LOAD TIME: module/kernel parameter: log_ce=[0|1]
RUN TIME: echo "1" >/sys/devices/system/edac/mc/edac_mc_log_ce
Polling period control file:
'edac_mc_poll_msec'
The time period, in milliseconds, for polling for error information.
Too small a value wastes resources. Too large a value might delay
necessary handling of errors and might loose valuable information for
locating the error. 1000 milliseconds (once each second) is the current
default. Systems which require all the bandwidth they can get, may
increase this.
LOAD TIME: module/kernel parameter: poll_msec=[0|1]
RUN TIME: echo "1000" >/sys/devices/system/edac/mc/edac_mc_poll_msec
============================================================================
'mcX' DIRECTORIES
......@@ -392,7 +327,7 @@ Sdram memory scrubbing rate:
'sdram_scrub_rate'
Read/Write attribute file that controls memory scrubbing. The scrubbing
rate is set by writing a minimum bandwith in bytes/sec to the attribute
rate is set by writing a minimum bandwidth in bytes/sec to the attribute
file. The rate will be translated to an internal value that gives at
least the specified rate.
......@@ -537,7 +472,6 @@ Channel 1 DIMM Label control file:
motherboard specific and determination of this information
must occur in userland at this time.
============================================================================
SYSTEM LOGGING
......@@ -570,7 +504,6 @@ error type, a notice of "no info" and then an optional,
driver-specific error message.
============================================================================
PCI Bus Parity Detection
......@@ -604,6 +537,74 @@ Enable/Disable PCI Parity checking control file:
echo "0" >/sys/devices/system/edac/pci/check_pci_parity
Parity Count:
'pci_parity_count'
This attribute file will display the number of parity errors that
have been detected.
============================================================================
MODULE PARAMETERS
Panic on UE control file:
'edac_mc_panic_on_ue'
An uncorrectable error will cause a machine panic. This is usually
desirable. It is a bad idea to continue when an uncorrectable error
occurs - it is indeterminate what was uncorrected and the operating
system context might be so mangled that continuing will lead to further
corruption. If the kernel has MCE configured, then EDAC will never
notice the UE.
LOAD TIME: module/kernel parameter: edac_mc_panic_on_ue=[0|1]
RUN TIME: echo "1" > /sys/module/edac_core/parameters/edac_mc_panic_on_ue
Log UE control file:
'edac_mc_log_ue'
Generate kernel messages describing uncorrectable errors. These errors
are reported through the system message log system. UE statistics
will be accumulated even when UE logging is disabled.
LOAD TIME: module/kernel parameter: edac_mc_log_ue=[0|1]
RUN TIME: echo "1" > /sys/module/edac_core/parameters/edac_mc_log_ue
Log CE control file:
'edac_mc_log_ce'
Generate kernel messages describing correctable errors. These
errors are reported through the system message log system.
CE statistics will be accumulated even when CE logging is disabled.
LOAD TIME: module/kernel parameter: edac_mc_log_ce=[0|1]
RUN TIME: echo "1" > /sys/module/edac_core/parameters/edac_mc_log_ce
Polling period control file:
'edac_mc_poll_msec'
The time period, in milliseconds, for polling for error information.
Too small a value wastes resources. Too large a value might delay
necessary handling of errors and might loose valuable information for
locating the error. 1000 milliseconds (once each second) is the current
default. Systems which require all the bandwidth they can get, may
increase this.
LOAD TIME: module/kernel parameter: edac_mc_poll_msec=[0|1]
RUN TIME: echo "1000" > /sys/module/edac_core/parameters/edac_mc_poll_msec
Panic on PCI PARITY Error:
......@@ -614,21 +615,13 @@ Panic on PCI PARITY Error:
error has been detected.
module/kernel parameter: panic_on_pci_parity=[0|1]
module/kernel parameter: edac_panic_on_pci_pe=[0|1]
Enable:
echo "1" >/sys/devices/system/edac/pci/panic_on_pci_parity
echo "1" > /sys/module/edac_core/parameters/edac_panic_on_pci_pe
Disable:
echo "0" >/sys/devices/system/edac/pci/panic_on_pci_parity
Parity Count:
'pci_parity_count'
This attribute file will display the number of parity errors that
have been detected.
echo "0" > /sys/module/edac_core/parameters/edac_panic_on_pci_pe
......
Documentation/fb/sh7760fb.txt 0 → 100644
浏览文件 @ cb28a1bb
SH7760/SH7763 integrated LCDC Framebuffer driver
================================================
0. Overwiew
-----------
The SH7760/SH7763 have an integrated LCD Display controller (LCDC) which
supports (in theory) resolutions ranging from 1x1 to 1024x1024,
with color depths ranging from 1 to 16 bits, on STN, DSTN and TFT Panels.
Caveats:
* Framebuffer memory must be a large chunk allocated at the top
of Area3 (HW requirement). Because of this requirement you should NOT
make the driver a module since at runtime it may become impossible to
get a large enough contiguous chunk of memory.
* The driver does not support changing resolution while loaded
(displays aren't hotpluggable anyway)
* Heavy flickering may be observed
a) if you're using 15/16bit color modes at >= 640x480 px resolutions,
b) during PCMCIA (or any other slow bus) activity.
* Rotation works only 90degress clockwise, and only if horizontal
resolution is <= 320 pixels.
files: drivers/video/sh7760fb.c
include/asm-sh/sh7760fb.h
Documentation/fb/sh7760fb.txt
1. Platform setup
-----------------
SH7760:
Video data is fetched via the DMABRG DMA engine, so you have to
configure the SH DMAC for DMABRG mode (write 0x94808080 to the
DMARSRA register somewhere at boot).
PFC registers PCCR and PCDR must be set to peripheral mode.
(write zeros to both).
The driver does NOT do the above for you since board setup is, well, job
of the board setup code.
2. Panel definitions
--------------------
The LCDC must explicitly be told about the type of LCD panel
attached. Data must be wrapped in a "struct sh7760fb_platdata" and
passed to the driver as platform_data.
Suggest you take a closer look at the SH7760 Manual, Section 30.
(http://documentation.renesas.com/eng/products/mpumcu/e602291_sh7760.pdf)
The following code illustrates what needs to be done to
get the framebuffer working on a 640x480 TFT:
====================== cut here ======================================
#include <linux/fb.h>
#include <asm/sh7760fb.h>
/*
* NEC NL6440bc26-01 640x480 TFT
* dotclock 25175 kHz
* Xres 640 Yres 480
* Htotal 800 Vtotal 525
* HsynStart 656 VsynStart 490
* HsynLenn 30 VsynLenn 2
*
* The linux framebuffer layer does not use the syncstart/synclen
* values but right/left/upper/lower margin values. The comments
* for the x_margin explain how to calculate those from given
* panel sync timings.
*/
static struct fb_videomode nl6448bc26 = {
.name = "NL6448BC26",
.refresh = 60,
.xres = 640,
.yres = 480,
.pixclock = 39683, /* in picoseconds! */
.hsync_len = 30,
.vsync_len = 2,
.left_margin = 114, /* HTOT - (HSYNSLEN + HSYNSTART) */
.right_margin = 16, /* HSYNSTART - XRES */
.upper_margin = 33, /* VTOT - (VSYNLEN + VSYNSTART) */
.lower_margin = 10, /* VSYNSTART - YRES */
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
.vmode = FB_VMODE_NONINTERLACED,
.flag = 0,
};
static struct sh7760fb_platdata sh7760fb_nl6448 = {
.def_mode = &nl6448bc26,
.ldmtr = LDMTR_TFT_COLOR_16, /* 16bit TFT panel */
.lddfr = LDDFR_8BPP, /* we want 8bit output */
.ldpmmr = 0x0070,
.ldpspr = 0x0500,
.ldaclnr = 0,
.ldickr = LDICKR_CLKSRC(LCDC_CLKSRC_EXTERNAL) |
LDICKR_CLKDIV(1),
.rotate = 0,
.novsync = 1,
.blank = NULL,
};
/* SH7760:
* 0xFE300800: 256 * 4byte xRGB palette ram
* 0xFE300C00: 42 bytes ctrl registers
*/
static struct resource sh7760_lcdc_res[] = {
[0] = {
.start = 0xFE300800,
.end = 0xFE300CFF,
.flags = IORESOURCE_MEM,
},
[1] = {
.start = 65,
.end = 65,
.flags = IORESOURCE_IRQ,
},
};
static struct platform_device sh7760_lcdc_dev = {
.dev = {
.platform_data = &sh7760fb_nl6448,
},
.name = "sh7760-lcdc",
.id = -1,
.resource = sh7760_lcdc_res,
.num_resources = ARRAY_SIZE(sh7760_lcdc_res),
};
====================== cut here ======================================
Documentation/fb/tridentfb.txt
浏览文件 @ cb28a1bb
......@@ -3,11 +3,25 @@ Tridentfb is a framebuffer driver for some Trident chip based cards.
The following list of chips is thought to be supported although not all are
tested:
those from the Image series with Cyber in their names - accelerated
those with Blade in their names (Blade3D,CyberBlade...) - accelerated
the newer CyberBladeXP family - nonaccelerated
Only PCI/AGP based cards are supported, none of the older Tridents.
those from the TGUI series 9440/96XX and with Cyber in their names
those from the Image series and with Cyber in their names
those with Blade in their names (Blade3D,CyberBlade...)
the newer CyberBladeXP family
All families are accelerated. Only PCI/AGP based cards are supported,
none of the older Tridents.
The driver supports 8, 16 and 32 bits per pixel depths.
The TGUI family requires a line length to be power of 2 if acceleration
is enabled. This means that range of possible resolutions and bpp is
limited comparing to the range if acceleration is disabled (see list
of parameters below).
Known bugs:
1. The driver randomly locks up on 3DImage975 chip with acceleration
enabled. The same happens in X11 (Xorg).
2. The ramdac speeds require some more fine tuning. It is possible to
switch resolution which the chip does not support at some depths for
older chips.
How to use it?
==============
......@@ -17,12 +31,11 @@ video=tridentfb
The parameters for tridentfb are concatenated with a ':' as in this example.
video=tridentfb:800x600,bpp=16,noaccel
video=tridentfb:800x600-16@75,noaccel
The second level parameters that tridentfb understands are:
noaccel - turns off acceleration (when it doesn't work for your card)
accel - force text acceleration (for boards which by default are noacceled)
fp - use flat panel related stuff
crt - assume monitor is present instead of fp
......@@ -31,21 +44,24 @@ center - for flat panels and resolutions smaller than native size center the
image, otherwise use
stretch
memsize - integer value in Kb, use if your card's memory size is misdetected.
memsize - integer value in KB, use if your card's memory size is misdetected.
look at the driver output to see what it says when initializing.
memdiff - integer value in Kb,should be nonzero if your card reports
more memory than it actually has.For instance mine is 192K less than
memdiff - integer value in KB, should be nonzero if your card reports
more memory than it actually has. For instance mine is 192K less than
detection says in all three BIOS selectable situations 2M, 4M, 8M.
Only use if your video memory is taken from main memory hence of
configurable size.Otherwise use memsize.
If in some modes which barely fit the memory you see garbage at the bottom
this might help by not letting change to that mode anymore.
configurable size. Otherwise use memsize.
If in some modes which barely fit the memory you see garbage
at the bottom this might help by not letting change to that mode
anymore.
nativex - the width in pixels of the flat panel.If you know it (usually 1024
800 or 1280) and it is not what the driver seems to detect use it.
bpp - bits per pixel (8,16 or 32)
mode - a mode name like 800x600 (as described in Documentation/fb/modedb.txt)
bpp - bits per pixel (8,16 or 32)
mode - a mode name like 800x600-8@75 as described in
Documentation/fb/modedb.txt
Using insane values for the above parameters will probably result in driver
misbehaviour so take care(for instance memsize=12345678 or memdiff=23784 or
......
Documentation/feature-removal-schedule.txt
浏览文件 @ cb28a1bb
......@@ -47,6 +47,30 @@ Who: Mauro Carvalho Chehab <mchehab@infradead.org>
---------------------------
What: old tuner-3036 i2c driver
When: 2.6.28
Why: This driver is for VERY old i2c-over-parallel port teletext receiver
boxes. Rather then spending effort on converting this driver to V4L2,
and since it is extremely unlikely that anyone still uses one of these
devices, it was decided to drop it.
Who: Hans Verkuil <hverkuil@xs4all.nl>
Mauro Carvalho Chehab <mchehab@infradead.org>
---------------------------
What: V4L2 dpc7146 driver
When: 2.6.28
Why: Old driver for the dpc7146 demonstration board that is no longer
relevant. The last time this was tested on actual hardware was
probably around 2002. Since this is a driver for a demonstration
board the decision was made to remove it rather than spending a
lot of effort continually updating this driver to stay in sync
with the latest internal V4L2 or I2C API.
Who: Hans Verkuil <hverkuil@xs4all.nl>
Mauro Carvalho Chehab <mchehab@infradead.org>
---------------------------
What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
When: November 2005
Files: drivers/pcmcia/: pcmcia_ioctl.c
......@@ -138,24 +162,6 @@ Who: Kay Sievers <kay.sievers@suse.de>
---------------------------
What: find_task_by_pid
When: 2.6.26
Why: With pid namespaces, calling this funciton will return the
wrong task when called from inside a namespace.
The best way to save a task pid and find a task by this
pid later, is to find this task's struct pid pointer (or get
it directly from the task) and call pid_task() later.
If someone really needs to get a task by its pid_t, then
he most likely needs the find_task_by_vpid() to get the
task from the same namespace as the current task is in, but
this may be not so in general.
Who: Pavel Emelyanov <xemul@openvz.org>
---------------------------
What: ACPI procfs interface
When: July 2008
Why: ACPI sysfs conversion should be finished by January 2008.
......@@ -300,11 +306,15 @@ 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>
What: SCTP_GET_PEER_ADDRS_NUM_OLD, SCTP_GET_PEER_ADDRS_OLD,
SCTP_GET_LOCAL_ADDRS_NUM_OLD, SCTP_GET_LOCAL_ADDRS_OLD
When: June 2009
Why: A newer version of the options have been introduced in 2005 that
removes the limitions of the old API. The sctp library has been
converted to use these new options at the same time. Any user
space app that directly uses the old options should convert to using
the new options.
Who: Vlad Yasevich <vladislav.yasevich@hp.com>
---------------------------
......@@ -314,3 +324,23 @@ Why: This option was introduced just to allow older lm-sensors userspace
to keep working over the upgrade to 2.6.26. At the scheduled time of
removal fixed lm-sensors (2.x or 3.x) should be readily available.
Who: Rene Herman <rene.herman@gmail.com>
---------------------------
What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS
(in net/core/net-sysfs.c)
When: After the only user (hal) has seen a release with the patches
for enough time, probably some time in 2010.
Why: Over 1K .text/.data size reduction, data is available in other
ways (ioctls)
Who: Johannes Berg <johannes@sipsolutions.net>
---------------------------
What: CONFIG_NF_CT_ACCT
When: 2.6.29
Why: Accounting can now be enabled/disabled without kernel recompilation.
Currently used only to set a default value for a feature that is also
controlled by a kernel/module/sysfs/sysctl parameter.
Who: Krzysztof Piotr Oledzki <ole@ans.pl>
Documentation/filesystems/Locking
浏览文件 @ cb28a1bb
......@@ -510,6 +510,7 @@ prototypes:
void (*close)(struct vm_area_struct*);
int (*fault)(struct vm_area_struct*, struct vm_fault *);
int (*page_mkwrite)(struct vm_area_struct *, struct page *);
int (*access)(struct vm_area_struct *, unsigned long, void*, int, int);
locking rules:
BKL mmap_sem PageLocked(page)
......@@ -517,6 +518,7 @@ open: no yes
close: no yes
fault: no yes
page_mkwrite: no yes no
access: no yes
->page_mkwrite() is called when a previously read-only page is
about to become writeable. The file system is responsible for
......@@ -525,6 +527,11 @@ taking to lock out truncate, the page range should be verified to be
within i_size. The page mapping should also be checked that it is not
NULL.
->access() is called when get_user_pages() fails in
acces_process_vm(), typically used to debug a process through
/proc/pid/mem or ptrace. This function is needed only for
VM_IO | VM_PFNMAP VMAs.
================================================================================
Dubious stuff
......
Documentation/filesystems/bfs.txt
浏览文件 @ cb28a1bb
......@@ -26,11 +26,11 @@ You can simplify mounting by just typing:
this will allocate the first available loopback device (and load loop.o
kernel module if necessary) automatically. If the loopback driver is not
loaded automatically, make sure that your kernel is compiled with kmod
support (CONFIG_KMOD) enabled. Beware that umount will not
deallocate /dev/loopN device if /etc/mtab file on your system is a
symbolic link to /proc/mounts. You will need to do it manually using
"-d" switch of losetup(8). Read losetup(8) manpage for more info.
loaded automatically, make sure that you have compiled the module and
that modprobe is functioning. Beware that umount will not deallocate
/dev/loopN device if /etc/mtab file on your system is a symbolic link to
/proc/mounts. You will need to do it manually using "-d" switch of
losetup(8). Read losetup(8) manpage for more info.
To create the BFS image under UnixWare you need to find out first which
slice contains it. The command prtvtoc(1M) is your friend:
......
Documentation/filesystems/configfs/configfs.txt
浏览文件 @ cb28a1bb
......@@ -233,12 +233,10 @@ accomplished via the group operations specified on the group's
config_item_type.
struct configfs_group_operations {
int (*make_item)(struct config_group *group,
const char *name,
struct config_item **new_item);
int (*make_group)(struct config_group *group,
const char *name,
struct config_group **new_group);
struct config_item *(*make_item)(struct config_group *group,
const char *name);
struct config_group *(*make_group)(struct config_group *group,
const char *name);
int (*commit_item)(struct config_item *item);
void (*disconnect_notify)(struct config_group *group,
struct config_item *item);
......
Documentation/filesystems/configfs/configfs_example.c
浏览文件 @ cb28a1bb
......@@ -273,13 +273,13 @@ static inline struct simple_children *to_simple_children(struct config_item *ite
return item ? container_of(to_config_group(item), struct simple_children, group) : NULL;
}
static int simple_children_make_item(struct config_group *group, const char *name, struct config_item **new_item)
static struct config_item *simple_children_make_item(struct config_group *group, const char *name)
{
struct simple_child *simple_child;
simple_child = kzalloc(sizeof(struct simple_child), GFP_KERNEL);
if (!simple_child)
return -ENOMEM;
return ERR_PTR(-ENOMEM);
config_item_init_type_name(&simple_child->item, name,
......@@ -287,8 +287,7 @@ static int simple_children_make_item(struct config_group *group, const char *nam
simple_child->storeme = 0;
*new_item = &simple_child->item;
return 0;
return &simple_child->item;
}
static struct configfs_attribute simple_children_attr_description = {
......@@ -360,21 +359,20 @@ static struct configfs_subsystem simple_children_subsys = {
* children of its own.
*/
static int group_children_make_group(struct config_group *group, const char *name, struct config_group **new_group)
static struct config_group *group_children_make_group(struct config_group *group, const char *name)
{
struct simple_children *simple_children;
simple_children = kzalloc(sizeof(struct simple_children),
GFP_KERNEL);
if (!simple_children)
return -ENOMEM;
return ERR_PTR(-ENOMEM);
config_group_init_type_name(&simple_children->group, name,
&simple_children_type);
*new_group = &simple_children->group;
return 0;
return &simple_children->group;
}
static struct configfs_attribute group_children_attr_description = {
......
Documentation/filesystems/nfs-rdma.txt
浏览文件 @ cb28a1bb
......@@ -5,7 +5,7 @@
################################################################################
Author: NetApp and Open Grid Computing
Date: April 15, 2008
Date: May 29, 2008
Table of Contents
~~~~~~~~~~~~~~~~~
......@@ -60,16 +60,18 @@ Installation
The procedures described in this document have been tested with
distributions from Red Hat's Fedora Project (http://fedora.redhat.com/).
- Install nfs-utils-1.1.1 or greater on the client
- Install nfs-utils-1.1.2 or greater on the client
An NFS/RDMA mount point can only be obtained by using the mount.nfs
command in nfs-utils-1.1.1 or greater. To see which version of mount.nfs
you are using, type:
An NFS/RDMA mount point can be obtained by using the mount.nfs command in
nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
version with support for NFS/RDMA mounts, but for various reasons we
recommend using nfs-utils-1.1.2 or greater). To see which version of
mount.nfs you are using, type:
> /sbin/mount.nfs -V
$ /sbin/mount.nfs -V
If the version is less than 1.1.1 or the command does not exist,
then you will need to install the latest version of nfs-utils.
If the version is less than 1.1.2 or the command does not exist,
you should install the latest version of nfs-utils.
Download the latest package from:
......@@ -77,22 +79,33 @@ Installation
Uncompress the package and follow the installation instructions.
If you will not be using GSS and NFSv4, the installation process
can be simplified by disabling these features when running configure:
If you will not need the idmapper and gssd executables (you do not need
these to create an NFS/RDMA enabled mount command), the installation
process can be simplified by disabling these features when running
configure:
> ./configure --disable-gss --disable-nfsv4
$ ./configure --disable-gss --disable-nfsv4
For more information on this see the package's README and INSTALL files.
To build nfs-utils you will need the tcp_wrappers package installed. For
more information on this see the package's README and INSTALL files.
After building the nfs-utils package, there will be a mount.nfs binary in
the utils/mount directory. This binary can be used to initiate NFS v2, v3,
or v4 mounts. To initiate a v4 mount, the binary must be called mount.nfs4.
The standard technique is to create a symlink called mount.nfs4 to mount.nfs.
or v4 mounts. To initiate a v4 mount, the binary must be called
mount.nfs4. The standard technique is to create a symlink called
mount.nfs4 to mount.nfs.
NOTE: mount.nfs and therefore nfs-utils-1.1.1 or greater is only needed
This mount.nfs binary should be installed at /sbin/mount.nfs as follows:
$ sudo cp utils/mount/mount.nfs /sbin/mount.nfs
In this location, mount.nfs will be invoked automatically for NFS mounts
by the system mount commmand.
NOTE: mount.nfs and therefore nfs-utils-1.1.2 or greater is only needed
on the NFS client machine. You do not need this specific version of
nfs-utils on the server. Furthermore, only the mount.nfs command from
nfs-utils-1.1.1 is needed on the client.
nfs-utils-1.1.2 is needed on the client.
- Install a Linux kernel with NFS/RDMA
......@@ -156,8 +169,8 @@ Check RDMA and NFS Setup
this time. For example, if you are using a Mellanox Tavor/Sinai/Arbel
card:
> modprobe ib_mthca
> modprobe ib_ipoib
$ modprobe ib_mthca
$ modprobe ib_ipoib
If you are using InfiniBand, make sure there is a Subnet Manager (SM)
running on the network. If your IB switch has an embedded SM, you can
......@@ -166,7 +179,7 @@ Check RDMA and NFS Setup
If an SM is running on your network, you should see the following:
> cat /sys/class/infiniband/driverX/ports/1/state
$ cat /sys/class/infiniband/driverX/ports/1/state
4: ACTIVE
where driverX is mthca0, ipath5, ehca3, etc.
......@@ -174,10 +187,10 @@ Check RDMA and NFS Setup
To further test the InfiniBand software stack, use IPoIB (this
assumes you have two IB hosts named host1 and host2):
host1> ifconfig ib0 a.b.c.x
host2> ifconfig ib0 a.b.c.y
host1> ping a.b.c.y
host2> ping a.b.c.x
host1$ ifconfig ib0 a.b.c.x
host2$ ifconfig ib0 a.b.c.y
host1$ ping a.b.c.y
host2$ ping a.b.c.x
For other device types, follow the appropriate procedures.
......@@ -202,11 +215,11 @@ NFS/RDMA Setup
/vol0 192.168.0.47(fsid=0,rw,async,insecure,no_root_squash)
/vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash)
The IP address(es) is(are) the client's IPoIB address for an InfiniBand HCA or the
cleint's iWARP address(es) for an RNIC.
The IP address(es) is(are) the client's IPoIB address for an InfiniBand
HCA or the cleint's iWARP address(es) for an RNIC.
NOTE: The "insecure" option must be used because the NFS/RDMA client does not
use a reserved port.
NOTE: The "insecure" option must be used because the NFS/RDMA client does
not use a reserved port.
Each time a machine boots:
......@@ -214,43 +227,45 @@ NFS/RDMA Setup
For InfiniBand using a Mellanox adapter:
> modprobe ib_mthca
> modprobe ib_ipoib
> ifconfig ib0 a.b.c.d
$ modprobe ib_mthca
$ modprobe ib_ipoib
$ ifconfig ib0 a.b.c.d
NOTE: use unique addresses for the client and server
- Start the NFS server
If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config),
load the RDMA transport module:
If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
kernel config), load the RDMA transport module:
> modprobe svcrdma
$ modprobe svcrdma
Regardless of how the server was built (module or built-in), start the server:
Regardless of how the server was built (module or built-in), start the
server:
> /etc/init.d/nfs start
$ /etc/init.d/nfs start
or
> service nfs start
$ service nfs start
Instruct the server to listen on the RDMA transport:
> echo rdma 2050 > /proc/fs/nfsd/portlist
$ echo rdma 2050 > /proc/fs/nfsd/portlist
- On the client system
If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config),
load the RDMA client module:
If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
kernel config), load the RDMA client module:
> modprobe xprtrdma.ko
$ modprobe xprtrdma.ko
Regardless of how the client was built (module or built-in), issue the mount.nfs command:
Regardless of how the client was built (module or built-in), use this
command to mount the NFS/RDMA server:
> /path/to/your/mount.nfs <IPoIB-server-name-or-address>:/<export> /mnt -i -o rdma,port=2050
$ mount -o rdma,port=2050 <IPoIB-server-name-or-address>:/<export> /mnt
To verify that the mount is using RDMA, run "cat /proc/mounts" and check the
"proto" field for the given mount.
To verify that the mount is using RDMA, run "cat /proc/mounts" and check
the "proto" field for the given mount.
Congratulations! You're using NFS/RDMA!
Documentation/filesystems/omfs.txt 0 → 100644
浏览文件 @ cb28a1bb
Optimized MPEG Filesystem (OMFS)
Overview
========
OMFS is a filesystem created by SonicBlue for use in the ReplayTV DVR
and Rio Karma MP3 player. The filesystem is extent-based, utilizing
block sizes from 2k to 8k, with hash-based directories. This
filesystem driver may be used to read and write disks from these
devices.
Note, it is not recommended that this FS be used in place of a general
filesystem for your own streaming media device. Native Linux filesystems
will likely perform better.
More information is available at:
http://linux-karma.sf.net/
Various utilities, including mkomfs and omfsck, are included with
omfsprogs, available at:
http://bobcopeland.com/karma/
Instructions are included in its README.
Options
=======
OMFS supports the following mount-time options:
uid=n - make all files owned by specified user
gid=n - make all files owned by specified group
umask=xxx - set permission umask to xxx
fmask=xxx - set umask to xxx for files
dmask=xxx - set umask to xxx for directories
Disk format
===========
OMFS discriminates between "sysblocks" and normal data blocks. The sysblock
group consists of super block information, file metadata, directory structures,
and extents. Each sysblock has a header containing CRCs of the entire
sysblock, and may be mirrored in successive blocks on the disk. A sysblock may
have a smaller size than a data block, but since they are both addressed by the
same 64-bit block number, any remaining space in the smaller sysblock is
unused.
Sysblock header information:
struct omfs_header {
__be64 h_self; /* FS block where this is located */
__be32 h_body_size; /* size of useful data after header */
__be16 h_crc; /* crc-ccitt of body_size bytes */
char h_fill1[2];
u8 h_version; /* version, always 1 */
char h_type; /* OMFS_INODE_X */
u8 h_magic; /* OMFS_IMAGIC */
u8 h_check_xor; /* XOR of header bytes before this */
__be32 h_fill2;
};
Files and directories are both represented by omfs_inode:
struct omfs_inode {
struct omfs_header i_head; /* header */
__be64 i_parent; /* parent containing this inode */
__be64 i_sibling; /* next inode in hash bucket */
__be64 i_ctime; /* ctime, in milliseconds */
char i_fill1[35];
char i_type; /* OMFS_[DIR,FILE] */
__be32 i_fill2;
char i_fill3[64];
char i_name[OMFS_NAMELEN]; /* filename */
__be64 i_size; /* size of file, in bytes */
};
Directories in OMFS are implemented as a large hash table. Filenames are
hashed then prepended into the bucket list beginning at OMFS_DIR_START.
Lookup requires hashing the filename, then seeking across i_sibling pointers
until a match is found on i_name. Empty buckets are represented by block
pointers with all-1s (~0).
A file is an omfs_inode structure followed by an extent table beginning at
OMFS_EXTENT_START:
struct omfs_extent_entry {
__be64 e_cluster; /* start location of a set of blocks */
__be64 e_blocks; /* number of blocks after e_cluster */
};
struct omfs_extent {
__be64 e_next; /* next extent table location */
__be32 e_extent_count; /* total # extents in this table */
__be32 e_fill;
struct omfs_extent_entry e_entry; /* start of extent entries */
};
Each extent holds the block offset followed by number of blocks allocated to
the extent. The final extent in each table is a terminator with e_cluster
being ~0 and e_blocks being ones'-complement of the total number of blocks
in the table.
If this table overflows, a continuation inode is written and pointed to by
e_next. These have a header but lack the rest of the inode structure.
Documentation/filesystems/proc.txt
浏览文件 @ cb28a1bb
......@@ -296,6 +296,7 @@ Table 1-4: Kernel info in /proc
uptime System uptime
version Kernel version
video bttv info of video resources (2.4)
vmallocinfo Show vmalloced areas
..............................................................................
You can, for example, check which interrupts are currently in use and what
......@@ -557,6 +558,49 @@ VmallocTotal: total size of vmalloc memory area
VmallocUsed: amount of vmalloc area which is used
VmallocChunk: largest contigious block of vmalloc area which is free
..............................................................................
vmallocinfo:
Provides information about vmalloced/vmaped areas. One line per area,
containing the virtual address range of the area, size in bytes,
caller information of the creator, and optional information depending
on the kind of area :
pages=nr number of pages
phys=addr if a physical address was specified
ioremap I/O mapping (ioremap() and friends)
vmalloc vmalloc() area
vmap vmap()ed pages
user VM_USERMAP area
vpages buffer for pages pointers was vmalloced (huge area)
N<node>=nr (Only on NUMA kernels)
Number of pages allocated on memory node <node>
> cat /proc/vmallocinfo
0xffffc20000000000-0xffffc20000201000 2101248 alloc_large_system_hash+0x204 ...
/0x2c0 pages=512 vmalloc N0=128 N1=128 N2=128 N3=128
0xffffc20000201000-0xffffc20000302000 1052672 alloc_large_system_hash+0x204 ...
/0x2c0 pages=256 vmalloc N0=64 N1=64 N2=64 N3=64
0xffffc20000302000-0xffffc20000304000 8192 acpi_tb_verify_table+0x21/0x4f...
phys=7fee8000 ioremap
0xffffc20000304000-0xffffc20000307000 12288 acpi_tb_verify_table+0x21/0x4f...
phys=7fee7000 ioremap
0xffffc2000031d000-0xffffc2000031f000 8192 init_vdso_vars+0x112/0x210
0xffffc2000031f000-0xffffc2000032b000 49152 cramfs_uncompress_init+0x2e ...
/0x80 pages=11 vmalloc N0=3 N1=3 N2=2 N3=3
0xffffc2000033a000-0xffffc2000033d000 12288 sys_swapon+0x640/0xac0 ...
pages=2 vmalloc N1=2
0xffffc20000347000-0xffffc2000034c000 20480 xt_alloc_table_info+0xfe ...
/0x130 [x_tables] pages=4 vmalloc N0=4
0xffffffffa0000000-0xffffffffa000f000 61440 sys_init_module+0xc27/0x1d00 ...
pages=14 vmalloc N2=14
0xffffffffa000f000-0xffffffffa0014000 20480 sys_init_module+0xc27/0x1d00 ...
pages=4 vmalloc N1=4
0xffffffffa0014000-0xffffffffa0017000 12288 sys_init_module+0xc27/0x1d00 ...
pages=2 vmalloc N1=2
0xffffffffa0017000-0xffffffffa0022000 45056 sys_init_module+0xc27/0x1d00 ...
pages=10 vmalloc N0=10
1.3 IDE devices in /proc/ide
----------------------------
......@@ -887,7 +931,7 @@ group_prealloc max_to_scan mb_groups mb_history min_to_scan order2_req
stats stream_req
mb_groups:
This file gives the details of mutiblock allocator buddy cache of free blocks
This file gives the details of multiblock allocator buddy cache of free blocks
mb_history:
Multiblock allocation history.
......@@ -1430,7 +1474,7 @@ used because pages_free(1355) is smaller than watermark + protection[2]
normal page requirement. If requirement is DMA zone(index=0), protection[0]
(=0) is used.
zone[i]'s protection[j] is calculated by following exprssion.
zone[i]'s protection[j] is calculated by following expression.
(i < j):
zone[i]->protection[j]
......
Documentation/filesystems/relay.txt
浏览文件 @ cb28a1bb
......@@ -294,6 +294,16 @@ user-defined data with a channel, and is immediately available
(including in create_buf_file()) via chan->private_data or
buf->chan->private_data.
Buffer-only channels
--------------------
These channels have no files associated and can be created with
relay_open(NULL, NULL, ...). Such channels are useful in scenarios such
as when doing early tracing in the kernel, before the VFS is up. In these
cases, one may open a buffer-only channel and then call
relay_late_setup_files() when the kernel is ready to handle files,
to expose the buffered data to the userspace.
Channel 'modes'
---------------
......
Documentation/filesystems/sysfs.txt
浏览文件 @ cb28a1bb
......@@ -248,6 +248,7 @@ The top level sysfs directory looks like:
block/
bus/
class/
dev/
devices/
firmware/
net/
......@@ -274,6 +275,11 @@ fs/ contains a directory for some filesystems. Currently each
filesystem wanting to export attributes must create its own hierarchy
below fs/ (see ./fuse.txt for an example).
dev/ contains two directories char/ and block/. Inside these two
directories there are symlinks named <major>:<minor>. These symlinks
point to the sysfs directory for the given device. /sys/dev provides a
quick way to lookup the sysfs interface for a device from the result of
a stat(2) operation.
More information can driver-model specific features can be found in
Documentation/driver-model/.
......
Documentation/filesystems/vfat.txt
浏览文件 @ cb28a1bb
......@@ -96,6 +96,14 @@ shortname=lower|win95|winnt|mixed
emulate the Windows 95 rule for create.
Default setting is `lower'.
tz=UTC -- Interpret timestamps as UTC rather than local time.
This option disables the conversion of timestamps
between local time (as used by Windows on FAT) and UTC
(which Linux uses internally). This is particuluarly
useful when mounting devices (like digital cameras)
that are set to UTC in order to avoid the pitfalls of
local time.
<bool>: 0,1,yes,no,true,false
TODO
......
Documentation/filesystems/vfs.txt
浏览文件 @ cb28a1bb
......@@ -143,7 +143,7 @@ struct file_system_type {
The get_sb() method has the following arguments:
struct file_system_type *fs_type: decribes the filesystem, partly initialized
struct file_system_type *fs_type: describes the filesystem, partly initialized
by the specific filesystem code
int flags: mount flags
......@@ -895,9 +895,9 @@ struct dentry_operations {
iput() yourself
d_dname: called when the pathname of a dentry should be generated.
Usefull for some pseudo filesystems (sockfs, pipefs, ...) to delay
Useful for some pseudo filesystems (sockfs, pipefs, ...) to delay
pathname generation. (Instead of doing it when dentry is created,
its done only when the path is needed.). Real filesystems probably
it's done only when the path is needed.). Real filesystems probably
dont want to use it, because their dentries are present in global
dcache hash, so their hash should be an invariant. As no lock is
held, d_dname() should not try to modify the dentry itself, unless
......
Documentation/gpio.txt
浏览文件 @ cb28a1bb
......@@ -347,15 +347,12 @@ necessarily be nonportable.
Dynamic definition of GPIOs is not currently standard; for example, as
a side effect of configuring an add-on board with some GPIO expanders.
These calls are purely for kernel space, but a userspace API could be built
on top of them.
GPIO implementor's framework (OPTIONAL)
=======================================
As noted earlier, there is an optional implementation framework making it
easier for platforms to support different kinds of GPIO controller using
the same programming interface.
the same programming interface. This framework is called "gpiolib".
As a debugging aid, if debugfs is available a /sys/kernel/debug/gpio file
will be found there. That will list all the controllers registered through
......@@ -392,11 +389,21 @@ either NULL or the label associated with that GPIO when it was requested.
Platform Support
----------------
To support this framework, a platform's Kconfig will "select HAVE_GPIO_LIB"
To support this framework, a platform's Kconfig will "select" either
ARCH_REQUIRE_GPIOLIB or ARCH_WANT_OPTIONAL_GPIOLIB
and arrange that its <asm/gpio.h> includes <asm-generic/gpio.h> and defines
three functions: gpio_get_value(), gpio_set_value(), and gpio_cansleep().
They may also want to provide a custom value for ARCH_NR_GPIOS.
ARCH_REQUIRE_GPIOLIB means that the gpio-lib code will always get compiled
into the kernel on that architecture.
ARCH_WANT_OPTIONAL_GPIOLIB means the gpio-lib code defaults to off and the user
can enable it and build it into the kernel optionally.
If neither of these options are selected, the platform does not support
GPIOs through GPIO-lib and the code cannot be enabled by the user.
Trivial implementations of those functions can directly use framework
code, which always dispatches through the gpio_chip:
......@@ -439,4 +446,120 @@ becomes available. That may mean the device should not be registered until
calls for that GPIO can work. One way to address such dependencies is for
such gpio_chip controllers to provide setup() and teardown() callbacks to
board specific code; those board specific callbacks would register devices
once all the necessary resources are available.
once all the necessary resources are available, and remove them later when
the GPIO controller device becomes unavailable.
Sysfs Interface for Userspace (OPTIONAL)
========================================
Platforms which use the "gpiolib" implementors framework may choose to
configure a sysfs user interface to GPIOs. This is different from the
debugfs interface, since it provides control over GPIO direction and
value instead of just showing a gpio state summary. Plus, it could be
present on production systems without debugging support.
Given approprate hardware documentation for the system, userspace could
know for example that GPIO #23 controls the write protect line used to
protect boot loader segments in flash memory. System upgrade procedures
may need to temporarily remove that protection, first importing a GPIO,
then changing its output state, then updating the code before re-enabling
the write protection. In normal use, GPIO #23 would never be touched,
and the kernel would have no need to know about it.
Again depending on appropriate hardware documentation, on some systems
userspace GPIO can be used to determine system configuration data that
standard kernels won't know about. And for some tasks, simple userspace
GPIO drivers could be all that the system really needs.
Note that standard kernel drivers exist for common "LEDs and Buttons"
GPIO tasks: "leds-gpio" and "gpio_keys", respectively. Use those
instead of talking directly to the GPIOs; they integrate with kernel
frameworks better than your userspace code could.
Paths in Sysfs
--------------
There are three kinds of entry in /sys/class/gpio:
- Control interfaces used to get userspace control over GPIOs;
- GPIOs themselves; and
- GPIO controllers ("gpio_chip" instances).
That's in addition to standard files including the "device" symlink.
The control interfaces are write-only:
/sys/class/gpio/
"export" ... Userspace may ask the kernel to export control of
a GPIO to userspace by writing its number to this file.
Example: "echo 19 > export" will create a "gpio19" node
for GPIO #19, if that's not requested by kernel code.
"unexport" ... Reverses the effect of exporting to userspace.
Example: "echo 19 > unexport" will remove a "gpio19"
node exported using the "export" file.
GPIO signals have paths like /sys/class/gpio/gpio42/ (for GPIO #42)
and have the following read/write attributes:
/sys/class/gpio/gpioN/
"direction" ... reads as either "in" or "out". This value may
normally be written. Writing as "out" defaults to
initializing the value as low. To ensure glitch free
operation, values "low" and "high" may be written to
configure the GPIO as an output with that initial value.
Note that this attribute *will not exist* if the kernel
doesn't support changing the direction of a GPIO, or
it was exported by kernel code that didn't explicitly
allow userspace to reconfigure this GPIO's direction.
"value" ... reads as either 0 (low) or 1 (high). If the GPIO
is configured as an output, this value may be written;
any nonzero value is treated as high.
GPIO controllers have paths like /sys/class/gpio/chipchip42/ (for the
controller implementing GPIOs starting at #42) and have the following
read-only attributes:
/sys/class/gpio/gpiochipN/
"base" ... same as N, the first GPIO managed by this chip
"label" ... provided for diagnostics (not always unique)
"ngpio" ... how many GPIOs this manges (N to N + ngpio - 1)
Board documentation should in most cases cover what GPIOs are used for
what purposes. However, those numbers are not always stable; GPIOs on
a daughtercard might be different depending on the base board being used,
or other cards in the stack. In such cases, you may need to use the
gpiochip nodes (possibly in conjunction with schematics) to determine
the correct GPIO number to use for a given signal.
Exporting from Kernel code
--------------------------
Kernel code can explicitly manage exports of GPIOs which have already been
requested using gpio_request():
/* export the GPIO to userspace */
int gpio_export(unsigned gpio, bool direction_may_change);
/* reverse gpio_export() */
void gpio_unexport();
After a kernel driver requests a GPIO, it may only be made available in
the sysfs interface by gpio_export(). The driver can control whether the
signal direction may change. This helps drivers prevent userspace code
from accidentally clobbering important system state.
This explicit exporting can help with debugging (by making some kinds
of experiments easier), or can provide an always-there interface that's
suitable for documenting as part of a board support package.
Documentation/i2c/upgrading-clients 0 → 100644
浏览文件 @ cb28a1bb
Upgrading I2C Drivers to the new 2.6 Driver Model
=================================================
Ben Dooks <ben-linux@fluff.org>
Introduction
------------
This guide outlines how to alter existing Linux 2.6 client drivers from
the old to the new new binding methods.
Example old-style driver
------------------------
struct example_state {
struct i2c_client client;
....
};
static struct i2c_driver example_driver;
static unsigned short ignore[] = { I2C_CLIENT_END };
static unsigned short normal_addr[] = { OUR_ADDR, I2C_CLIENT_END };
I2C_CLIENT_INSMOD;
static int example_attach(struct i2c_adapter *adap, int addr, int kind)
{
struct example_state *state;
struct device *dev = &adap->dev; /* to use for dev_ reports */
int ret;
state = kzalloc(sizeof(struct example_state), GFP_KERNEL);
if (state == NULL) {
dev_err(dev, "failed to create our state\n");
return -ENOMEM;
}
example->client.addr = addr;
example->client.flags = 0;
example->client.adapter = adap;
i2c_set_clientdata(&state->i2c_client, state);
strlcpy(client->i2c_client.name, "example", I2C_NAME_SIZE);
ret = i2c_attach_client(&state->i2c_client);
if (ret < 0) {
dev_err(dev, "failed to attach client\n");
kfree(state);
return ret;
}
dev = &state->i2c_client.dev;
/* rest of the initialisation goes here. */
dev_info(dev, "example client created\n");
return 0;
}
static int __devexit example_detach(struct i2c_client *client)
{
struct example_state *state = i2c_get_clientdata(client);
i2c_detach_client(client);
kfree(state);
return 0;
}
static int example_attach_adapter(struct i2c_adapter *adap)
{
return i2c_probe(adap, &addr_data, example_attach);
}
static struct i2c_driver example_driver = {
.driver = {
.owner = THIS_MODULE,
.name = "example",
},
.attach_adapter = example_attach_adapter,
.detach_client = __devexit_p(example_detach),
.suspend = example_suspend,
.resume = example_resume,
};
Updating the client
-------------------
The new style binding model will check against a list of supported
devices and their associated address supplied by the code registering
the busses. This means that the driver .attach_adapter and
.detach_adapter methods can be removed, along with the addr_data,
as follows:
- static struct i2c_driver example_driver;
- static unsigned short ignore[] = { I2C_CLIENT_END };
- static unsigned short normal_addr[] = { OUR_ADDR, I2C_CLIENT_END };
- I2C_CLIENT_INSMOD;
- static int example_attach_adapter(struct i2c_adapter *adap)
- {
- return i2c_probe(adap, &addr_data, example_attach);
- }
static struct i2c_driver example_driver = {
- .attach_adapter = example_attach_adapter,
- .detach_client = __devexit_p(example_detach),
}
Add the probe and remove methods to the i2c_driver, as so:
static struct i2c_driver example_driver = {
+ .probe = example_probe,
+ .remove = __devexit_p(example_remove),
}
Change the example_attach method to accept the new parameters
which include the i2c_client that it will be working with:
- static int example_attach(struct i2c_adapter *adap, int addr, int kind)
+ static int example_probe(struct i2c_client *client,
+ const struct i2c_device_id *id)
Change the name of example_attach to example_probe to align it with the
i2c_driver entry names. The rest of the probe routine will now need to be
changed as the i2c_client has already been setup for use.
The necessary client fields have already been setup before
the probe function is called, so the following client setup
can be removed:
- example->client.addr = addr;
- example->client.flags = 0;
- example->client.adapter = adap;
-
- strlcpy(client->i2c_client.name, "example", I2C_NAME_SIZE);
The i2c_set_clientdata is now:
- i2c_set_clientdata(&state->client, state);
+ i2c_set_clientdata(client, state);
The call to i2c_attach_client is no longer needed, if the probe
routine exits successfully, then the driver will be automatically
attached by the core. Change the probe routine as so:
- ret = i2c_attach_client(&state->i2c_client);
- if (ret < 0) {
- dev_err(dev, "failed to attach client\n");
- kfree(state);
- return ret;
- }
Remove the storage of 'struct i2c_client' from the 'struct example_state'
as we are provided with the i2c_client in our example_probe. Instead we
store a pointer to it for when it is needed.
struct example_state {
- struct i2c_client client;
+ struct i2c_client *client;
the new i2c client as so:
- struct device *dev = &adap->dev; /* to use for dev_ reports */
+ struct device *dev = &i2c_client->dev; /* to use for dev_ reports */
And remove the change after our client is attached, as the driver no
longer needs to register a new client structure with the core:
- dev = &state->i2c_client.dev;
In the probe routine, ensure that the new state has the client stored
in it:
static int example_probe(struct i2c_client *i2c_client,
const struct i2c_device_id *id)
{
struct example_state *state;
struct device *dev = &i2c_client->dev;
int ret;
state = kzalloc(sizeof(struct example_state), GFP_KERNEL);
if (state == NULL) {
dev_err(dev, "failed to create our state\n");
return -ENOMEM;
}
+ state->client = i2c_client;
Update the detach method, by changing the name to _remove and
to delete the i2c_detach_client call. It is possible that you
can also remove the ret variable as it is not not needed for
any of the core functions.
- static int __devexit example_detach(struct i2c_client *client)
+ static int __devexit example_remove(struct i2c_client *client)
{
struct example_state *state = i2c_get_clientdata(client);
- i2c_detach_client(client);
And finally ensure that we have the correct ID table for the i2c-core
and other utilities:
+ struct i2c_device_id example_idtable[] = {
+ { "example", 0 },
+ { }
+};
+
+MODULE_DEVICE_TABLE(i2c, example_idtable);
static struct i2c_driver example_driver = {
.driver = {
.owner = THIS_MODULE,
.name = "example",
},
+ .id_table = example_ids,
Our driver should now look like this:
struct example_state {
struct i2c_client *client;
....
};
static int example_probe(struct i2c_client *client,
const struct i2c_device_id *id)
{
struct example_state *state;
struct device *dev = &client->dev;
state = kzalloc(sizeof(struct example_state), GFP_KERNEL);
if (state == NULL) {
dev_err(dev, "failed to create our state\n");
return -ENOMEM;
}
state->client = client;
i2c_set_clientdata(client, state);
/* rest of the initialisation goes here. */
dev_info(dev, "example client created\n");
return 0;
}
static int __devexit example_remove(struct i2c_client *client)
{
struct example_state *state = i2c_get_clientdata(client);
kfree(state);
return 0;
}
static struct i2c_device_id example_idtable[] = {
{ "example", 0 },
{ }
};
MODULE_DEVICE_TABLE(i2c, example_idtable);
static struct i2c_driver example_driver = {
.driver = {
.owner = THIS_MODULE,
.name = "example",
},
.id_table = example_idtable,
.probe = example_probe,
.remove = __devexit_p(example_remove),
.suspend = example_suspend,
.resume = example_resume,
};
Documentation/ia64/kvm.txt
浏览文件 @ cb28a1bb
......@@ -50,9 +50,9 @@ Note: For step 2, please make sure that host page size == TARGET_PAGE_SIZE of qe
/usr/local/bin/qemu-system-ia64 -smp xx -m 512 -hda $your_image
(xx is the number of virtual processors for the guest, now the maximum value is 4)
5. Known possibile issue on some platforms with old Firmware.
5. Known possible issue on some platforms with old Firmware.
If meet strange host crashe issues, try to solve it through either of the following ways:
In the event of strange host crash issues, try to solve it through either of the following ways:
(1): Upgrade your Firmware to the latest one.
......@@ -65,8 +65,8 @@ index 0b53344..f02b0f7 100644
mov ar.pfs = loc1
mov rp = loc0
;;
- srlz.d // seralize restoration of psr.l
+ srlz.i // seralize restoration of psr.l
- srlz.d // serialize restoration of psr.l
+ srlz.i // serialize restoration of psr.l
+ ;;
br.ret.sptk.many b0
END(ia64_pal_call_static)
......
Documentation/ia64/paravirt_ops.txt 0 → 100644
浏览文件 @ cb28a1bb
Paravirt_ops on IA64
====================
21 May 2008, Isaku Yamahata <yamahata@valinux.co.jp>
Introduction
------------
The aim of this documentation is to help with maintainability and/or to
encourage people to use paravirt_ops/IA64.
paravirt_ops (pv_ops in short) is a way for virtualization support of
Linux kernel on x86. Several ways for virtualization support were
proposed, paravirt_ops is the winner.
On the other hand, now there are also several IA64 virtualization
technologies like kvm/IA64, xen/IA64 and many other academic IA64
hypervisors so that it is good to add generic virtualization
infrastructure on Linux/IA64.
What is paravirt_ops?
---------------------
It has been developed on x86 as virtualization support via API, not ABI.
It allows each hypervisor to override operations which are important for
hypervisors at API level. And it allows a single kernel binary to run on
all supported execution environments including native machine.
Essentially paravirt_ops is a set of function pointers which represent
operations corresponding to low level sensitive instructions and high
level functionalities in various area. But one significant difference
from usual function pointer table is that it allows optimization with
binary patch. It is because some of these operations are very
performance sensitive and indirect call overhead is not negligible.
With binary patch, indirect C function call can be transformed into
direct C function call or in-place execution to eliminate the overhead.
Thus, operations of paravirt_ops are classified into three categories.
- simple indirect call
These operations correspond to high level functionality so that the
overhead of indirect call isn't very important.
- indirect call which allows optimization with binary patch
Usually these operations correspond to low level instructions. They
are called frequently and performance critical. So the overhead is
very important.
- a set of macros for hand written assembly code
Hand written assembly codes (.S files) also need paravirtualization
because they include sensitive instructions or some of code paths in
them are very performance critical.
The relation to the IA64 machine vector
---------------------------------------
Linux/IA64 has the IA64 machine vector functionality which allows the
kernel to switch implementations (e.g. initialization, ipi, dma api...)
depending on executing platform.
We can replace some implementations very easily defining a new machine
vector. Thus another approach for virtualization support would be
enhancing the machine vector functionality.
But paravirt_ops approach was taken because
- virtualization support needs wider support than machine vector does.
e.g. low level instruction paravirtualization. It must be
initialized very early before platform detection.
- virtualization support needs more functionality like binary patch.
Probably the calling overhead might not be very large compared to the
emulation overhead of virtualization. However in the native case, the
overhead should be eliminated completely.
A single kernel binary should run on each environment including native,
and the overhead of paravirt_ops on native environment should be as
small as possible.
- for full virtualization technology, e.g. KVM/IA64 or
Xen/IA64 HVM domain, the result would be
(the emulated platform machine vector. probably dig) + (pv_ops).
This means that the virtualization support layer should be under
the machine vector layer.
Possibly it might be better to move some function pointers from
paravirt_ops to machine vector. In fact, Xen domU case utilizes both
pv_ops and machine vector.
IA64 paravirt_ops
-----------------
In this section, the concrete paravirt_ops will be discussed.
Because of the architecture difference between ia64 and x86, the
resulting set of functions is very different from x86 pv_ops.
- C function pointer tables
They are not very performance critical so that simple C indirect
function call is acceptable. The following structures are defined at
this moment. For details see linux/include/asm-ia64/paravirt.h
- struct pv_info
This structure describes the execution environment.
- struct pv_init_ops
This structure describes the various initialization hooks.
- struct pv_iosapic_ops
This structure describes hooks to iosapic operations.
- struct pv_irq_ops
This structure describes hooks to irq related operations
- struct pv_time_op
This structure describes hooks to steal time accounting.
- a set of indirect calls which need optimization
Currently this class of functions correspond to a subset of IA64
intrinsics. At this moment the optimization with binary patch isn't
implemented yet.
struct pv_cpu_op is defined. For details see
linux/include/asm-ia64/paravirt_privop.h
Mostly they correspond to ia64 intrinsics 1-to-1.
Caveat: Now they are defined as C indirect function pointers, but in
order to support binary patch optimization, they will be changed
using GCC extended inline assembly code.
- a set of macros for hand written assembly code (.S files)
For maintenance purpose, the taken approach for .S files is single
source code and compile multiple times with different macros definitions.
Each pv_ops instance must define those macros to compile.
The important thing here is that sensitive, but non-privileged
instructions must be paravirtualized and that some privileged
instructions also need paravirtualization for reasonable performance.
Developers who modify .S files must be aware of that. At this moment
an easy checker is implemented to detect paravirtualization breakage.
But it doesn't cover all the cases.
Sometimes this set of macros is called pv_cpu_asm_op. But there is no
corresponding structure in the source code.
Those macros mostly 1:1 correspond to a subset of privileged
instructions. See linux/include/asm-ia64/native/inst.h.
And some functions written in assembly also need to be overrided so
that each pv_ops instance have to define some macros. Again see
linux/include/asm-ia64/native/inst.h.
Those structures must be initialized very early before start_kernel.
Probably initialized in head.S using multi entry point or some other trick.
For native case implementation see linux/arch/ia64/kernel/paravirt.c.
Documentation/input/cs461x.txt
浏览文件 @ cb28a1bb
......@@ -31,7 +31,7 @@ The driver works with ALSA drivers simultaneously. For example, the xracer
uses joystick as input device and PCM device as sound output in one time.
There are no sound or input collisions detected. The source code have
comments about them; but I've found the joystick can be initialized
separately of ALSA modules. So, you canm use only one joystick driver
separately of ALSA modules. So, you can use only one joystick driver
without ALSA drivers. The ALSA drivers are not needed to compile or
run this driver.
......
Documentation/input/gameport-programming.txt
浏览文件 @ cb28a1bb
$Id: gameport-programming.txt,v 1.3 2001/04/24 13:51:37 vojtech Exp $
Programming gameport drivers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......
Documentation/input/input.txt
浏览文件 @ cb28a1bb
Linux Input drivers v1.0
(c) 1999-2001 Vojtech Pavlik <vojtech@ucw.cz>
Sponsored by SuSE
$Id: input.txt,v 1.8 2002/05/29 03:15:01 bradleym Exp $
----------------------------------------------------------------------------
0. Disclaimer
......
Documentation/input/joystick-api.txt
浏览文件 @ cb28a1bb
......@@ -5,8 +5,6 @@
7 Aug 1998
$Id: joystick-api.txt,v 1.2 2001/05/08 21:21:23 vojtech Exp $
1. Initialization
~~~~~~~~~~~~~~~~~
......
Documentation/input/joystick-parport.txt
浏览文件 @ cb28a1bb
......@@ -2,7 +2,6 @@
(c) 1998-2000 Vojtech Pavlik <vojtech@ucw.cz>
(c) 1998 Andree Borrmann <a.borrmann@tu-bs.de>
Sponsored by SuSE
$Id: joystick-parport.txt,v 1.6 2001/09/25 09:31:32 vojtech Exp $
----------------------------------------------------------------------------
0. Disclaimer
......
Documentation/input/joystick.txt
浏览文件 @ cb28a1bb
Linux Joystick driver v2.0.0
(c) 1996-2000 Vojtech Pavlik <vojtech@ucw.cz>
Sponsored by SuSE
$Id: joystick.txt,v 1.12 2002/03/03 12:13:07 jdeneux Exp $
----------------------------------------------------------------------------
0. Disclaimer
......
Documentation/ioctl/ioctl-decoding.txt
浏览文件 @ cb28a1bb
To decode a hex IOCTL code:
Most architecures use this generic format, but check
Most architectures use this generic format, but check
include/ARCH/ioctl.h for specifics, e.g. powerpc
uses 3 bits to encode read/write and 13 bits for size.
......@@ -18,7 +18,7 @@ uses 3 bits to encode read/write and 13 bits for size.
7-0 function #
So for example 0x82187201 is a read with arg length of 0x218,
So for example 0x82187201 is a read with arg length of 0x218,
character 'r' function 1. Grepping the source reveals this is:
#define VFAT_IOCTL_READDIR_BOTH _IOR('r', 1, struct dirent [2])
Documentation/iostats.txt
浏览文件 @ cb28a1bb
......@@ -143,7 +143,7 @@ disk and partition statistics are consistent again. Since we still don't
keep record of the partition-relative address, an operation is attributed to
the partition which contains the first sector of the request after the
eventual merges. As requests can be merged across partition, this could lead
to some (probably insignificant) innacuracy.
to some (probably insignificant) inaccuracy.
Additional notes
----------------
......
Documentation/isdn/README.mISDN 0 → 100644
浏览文件 @ cb28a1bb
mISDN is a new modular ISDN driver, in the long term it should replace
the old I4L driver architecture for passiv ISDN cards.
It was designed to allow a broad range of applications and interfaces
but only have the basic function in kernel, the interface to the user
space is based on sockets with a own address family AF_ISDN.
Documentation/kernel-parameters.txt
浏览文件 @ cb28a1bb
......@@ -87,7 +87,8 @@ parameter is applicable:
SH SuperH architecture is enabled.
SMP The kernel is an SMP kernel.
SPARC Sparc architecture is enabled.
SWSUSP Software suspend is enabled.
SWSUSP Software suspend (hibernation) is enabled.
SUSPEND System suspend states are enabled.
TS Appropriate touchscreen support is enabled.
USB USB support is enabled.
USBHID USB Human Interface Device support is enabled.
......@@ -147,10 +148,12 @@ and is between 256 and 4096 characters. It is defined in the file
default: 0
acpi_sleep= [HW,ACPI] Sleep options
Format: { s3_bios, s3_mode, s3_beep, old_ordering }
Format: { s3_bios, s3_mode, s3_beep, s4_nohwsig, old_ordering }
See Documentation/power/video.txt for s3_bios and s3_mode.
s3_beep is for debugging; it makes the PC's speaker beep
as soon as the kernel's real-mode entry point is called.
s4_nohwsig prevents ACPI hardware signature from being
used during resume from hibernation.
old_ordering causes the ACPI 1.0 ordering of the _PTS
control method, wrt putting devices into low power
states, to be enforced (the ACPI 2.0 ordering of _PTS is
......@@ -774,8 +777,22 @@ and is between 256 and 4096 characters. It is defined in the file
hisax= [HW,ISDN]
See Documentation/isdn/README.HiSax.
hugepages= [HW,X86-32,IA-64] Maximal number of HugeTLB pages.
hugepagesz= [HW,IA-64,PPC] The size of the HugeTLB pages.
hugepages= [HW,X86-32,IA-64] HugeTLB pages to allocate at boot.
hugepagesz= [HW,IA-64,PPC,X86-64] The size of the HugeTLB pages.
On x86-64 and powerpc, this option can be specified
multiple times interleaved with hugepages= to reserve
huge pages of different sizes. Valid pages sizes on
x86-64 are 2M (when the CPU supports "pse") and 1G
(when the CPU supports the "pdpe1gb" cpuinfo flag)
Note that 1GB pages can only be allocated at boot time
using hugepages= and not freed afterwards.
default_hugepagesz=
[same as hugepagesz=] The size of the default
HugeTLB page size. This is the size represented by
the legacy /proc/ hugepages APIs, used for SHM, and
default size when mounting hugetlbfs filesystems.
Defaults to the default architecture's huge page size
if not specified.
i8042.direct [HW] Put keyboard port into non-translated mode
i8042.dumbkbd [HW] Pretend that controller can only read data from
......@@ -1206,7 +1223,7 @@ and is between 256 and 4096 characters. It is defined in the file
or
memmap=0x10000$0x18690000
memtest= [KNL,X86_64] Enable memtest
memtest= [KNL,X86] Enable memtest
Format: <integer>
range: 0,4 : pattern number
default : 0 <disable>
......@@ -1225,6 +1242,14 @@ and is between 256 and 4096 characters. It is defined in the file
mga= [HW,DRM]
mminit_loglevel=
[KNL] When CONFIG_DEBUG_MEMORY_INIT is set, this
parameter allows control of the logging verbosity for
the additional memory initialisation checks. A value
of 0 disables mminit logging and a level of 4 will
log everything. Information is printed at KERN_DEBUG
so loglevel=8 may also need to be specified.
mousedev.tap_time=
[MOUSE] Maximum time between finger touching and
leaving touchpad surface for touch to be considered
......@@ -1279,6 +1304,13 @@ and is between 256 and 4096 characters. It is defined in the file
This usage is only documented in each driver source
file if at all.
nf_conntrack.acct=
[NETFILTER] Enable connection tracking flow accounting
0 to disable accounting
1 to enable accounting
Default value depends on CONFIG_NF_CT_ACCT that is
going to be removed in 2.6.29.
nfsaddrs= [NFS]
See Documentation/filesystems/nfsroot.txt.
......@@ -2027,6 +2059,9 @@ and is between 256 and 4096 characters. It is defined in the file
snd-ymfpci= [HW,ALSA]
softlockup_panic=
[KNL] Should the soft-lockup detector generate panics.
sonypi.*= [HW] Sony Programmable I/O Control Device driver
See Documentation/sonypi.txt
......@@ -2091,6 +2126,12 @@ and is between 256 and 4096 characters. It is defined in the file
tdfx= [HW,DRM]
test_suspend= [SUSPEND]
Specify "mem" (for Suspend-to-RAM) or "standby" (for
standby suspend) as the system sleep state to briefly
enter during system startup. The system is woken from
this state using a wakeup-capable RTC alarm.
thash_entries= [KNL,NET]
Set number of hash buckets for TCP connection
......@@ -2118,13 +2159,6 @@ and is between 256 and 4096 characters. It is defined in the file
<deci-seconds>: poll all this frequency
0: no polling (default)
tipar.timeout= [HW,PPT]
Set communications timeout in tenths of a second
(default 15).
tipar.delay= [HW,PPT]
Set inter-bit delay in microseconds (default 10).
tmscsim= [HW,SCSI]
See comment before function dc390_setup() in
drivers/scsi/tmscsim.c.
......@@ -2158,6 +2192,10 @@ and is between 256 and 4096 characters. It is defined in the file
Note that genuine overcurrent events won't be
reported either.
unknown_nmi_panic
[X86-32,X86-64]
Set unknown_nmi_panic=1 early on boot.
usbcore.autosuspend=
[USB] The autosuspend time delay (in seconds) used
for newly-detected USB devices (default 2). This
......
Documentation/keys.txt
浏览文件 @ cb28a1bb
......@@ -864,7 +864,7 @@ payload contents" for more information.
request_key_with_auxdata() respectively.
These two functions return with the key potentially still under
construction. To wait for contruction completion, the following should be
construction. To wait for construction completion, the following should be
called:
int wait_for_key_construction(struct key *key, bool intr);
......
Documentation/laptops/thinkpad-acpi.txt
浏览文件 @ cb28a1bb
ThinkPad ACPI Extras Driver
Version 0.20
April 09th, 2008
Version 0.21
May 29th, 2008
Borislav Deianov <borislav@users.sf.net>
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
......@@ -621,7 +621,8 @@ Bluetooth
---------
procfs: /proc/acpi/ibm/bluetooth
sysfs device attribute: bluetooth_enable
sysfs device attribute: bluetooth_enable (deprecated)
sysfs rfkill class: switch "tpacpi_bluetooth_sw"
This feature shows the presence and current state of a ThinkPad
Bluetooth device in the internal ThinkPad CDC slot.
......@@ -643,8 +644,12 @@ Sysfs notes:
0: disables Bluetooth / Bluetooth is disabled
1: enables Bluetooth / Bluetooth is enabled.
Note: this interface will be probably be superseded by the
generic rfkill class, so it is NOT to be considered stable yet.
Note: this interface has been superseded by the generic rfkill
class. It has been deprecated, and it will be removed in year
2010.
rfkill controller switch "tpacpi_bluetooth_sw": refer to
Documentation/rfkill.txt for details.
Video output control -- /proc/acpi/ibm/video
--------------------------------------------
......@@ -1374,7 +1379,8 @@ EXPERIMENTAL: WAN
-----------------
procfs: /proc/acpi/ibm/wan
sysfs device attribute: wwan_enable
sysfs device attribute: wwan_enable (deprecated)
sysfs rfkill class: switch "tpacpi_wwan_sw"
This feature is marked EXPERIMENTAL because the implementation
directly accesses hardware registers and may not work as expected. USE
......@@ -1404,8 +1410,12 @@ Sysfs notes:
0: disables WWAN card / WWAN card is disabled
1: enables WWAN card / WWAN card is enabled.
Note: this interface will be probably be superseded by the
generic rfkill class, so it is NOT to be considered stable yet.
Note: this interface has been superseded by the generic rfkill
class. It has been deprecated, and it will be removed in year
2010.
rfkill controller switch "tpacpi_wwan_sw": refer to
Documentation/rfkill.txt for details.
Multiple Commands, Module Parameters
------------------------------------
......
Documentation/leds-class.txt
浏览文件 @ cb28a1bb
......@@ -59,7 +59,7 @@ Hardware accelerated blink of LEDs
Some LEDs can be programmed to blink without any CPU interaction. To
support this feature, a LED driver can optionally implement the
blink_set() function (see <linux/leds.h>). If implemeted, triggers can
blink_set() function (see <linux/leds.h>). If implemented, triggers can
attempt to use it before falling back to software timers. The blink_set()
function should return 0 if the blink setting is supported, or -EINVAL
otherwise, which means that LED blinking will be handled by software.
......
Documentation/local_ops.txt
浏览文件 @ cb28a1bb
......@@ -36,7 +36,7 @@ It can be done by slightly modifying the standard atomic operations : only
their UP variant must be kept. It typically means removing LOCK prefix (on
i386 and x86_64) and any SMP sychronization barrier. If the architecture does
not have a different behavior between SMP and UP, including asm-generic/local.h
in your archtecture's local.h is sufficient.
in your architecture's local.h is sufficient.
The local_t type is defined as an opaque signed long by embedding an
atomic_long_t inside a structure. This is made so a cast from this type to a
......
Documentation/md.txt
浏览文件 @ cb28a1bb
......@@ -236,6 +236,11 @@ All md devices contain:
writing the word for the desired state, however some states
cannot be explicitly set, and some transitions are not allowed.
Select/poll works on this file. All changes except between
active_idle and active (which can be frequent and are not
very interesting) are notified. active->active_idle is
reported if the metadata is externally managed.
clear
No devices, no size, no level
Writing is equivalent to STOP_ARRAY ioctl
......@@ -292,6 +297,10 @@ Each directory contains:
writemostly - device will only be subject to read
requests if there are no other options.
This applies only to raid1 arrays.
blocked - device has failed, metadata is "external",
and the failure hasn't been acknowledged yet.
Writes that would write to this device if
it were not faulty are blocked.
spare - device is working, but not a full member.
This includes spares that are in the process
of being recovered to
......@@ -301,6 +310,12 @@ Each directory contains:
Writing "remove" removes the device from the array.
Writing "writemostly" sets the writemostly flag.
Writing "-writemostly" clears the writemostly flag.
Writing "blocked" sets the "blocked" flag.
Writing "-blocked" clear the "blocked" flag and allows writes
to complete.
This file responds to select/poll. Any change to 'faulty'
or 'blocked' causes an event.
errors
An approximate count of read errors that have been detected on
......@@ -332,7 +347,7 @@ Each directory contains:
for storage of data. This will normally be the same as the
component_size. This can be written while assembling an
array. If a value less than the current component_size is
written, component_size will be reduced to this value.
written, it will be rejected.
An active md device will also contain and entry for each active device
......@@ -381,6 +396,19 @@ also have
'check' and 'repair' will start the appropriate process
providing the current state is 'idle'.
This file responds to select/poll. Any important change in the value
triggers a poll event. Sometimes the value will briefly be
"recover" if a recovery seems to be needed, but cannot be
achieved. In that case, the transition to "recover" isn't
notified, but the transition away is.
degraded
This contains a count of the number of devices by which the
arrays is degraded. So an optimal array with show '0'. A
single failed/missing drive will show '1', etc.
This file responds to select/poll, any increase or decrease
in the count of missing devices will trigger an event.
mismatch_count
When performing 'check' and 'repair', and possibly when
performing 'resync', md will count the number of errors that are
......
Documentation/moxa-smartio
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/networking/bonding.txt
浏览文件 @ cb28a1bb
......@@ -289,35 +289,73 @@ downdelay
fail_over_mac
Specifies whether active-backup mode should set all slaves to
the same MAC address (the traditional behavior), or, when
enabled, change the bond's MAC address when changing the
active interface (i.e., fail over the MAC address itself).
Fail over MAC is useful for devices that cannot ever alter
their MAC address, or for devices that refuse incoming
broadcasts with their own source MAC (which interferes with
the ARP monitor).
The down side of fail over MAC is that every device on the
network must be updated via gratuitous ARP, vs. just updating
a switch or set of switches (which often takes place for any
traffic, not just ARP traffic, if the switch snoops incoming
traffic to update its tables) for the traditional method. If
the gratuitous ARP is lost, communication may be disrupted.
When fail over MAC is used in conjuction with the mii monitor,
devices which assert link up prior to being able to actually
transmit and receive are particularly susecptible to loss of
the gratuitous ARP, and an appropriate updelay setting may be
required.
A value of 0 disables fail over MAC, and is the default. A
value of 1 enables fail over MAC. This option is enabled
automatically if the first slave added cannot change its MAC
address. This option may be modified via sysfs only when no
slaves are present in the bond.
This option was added in bonding version 3.2.0.
the same MAC address at enslavement (the traditional
behavior), or, when enabled, perform special handling of the
bond's MAC address in accordance with the selected policy.
Possible values are:
none or 0
This setting disables fail_over_mac, and causes
bonding to set all slaves of an active-backup bond to
the same MAC address at enslavement time. This is the
default.
active or 1
The "active" fail_over_mac policy indicates that the
MAC address of the bond should always be the MAC
address of the currently active slave. The MAC
address of the slaves is not changed; instead, the MAC
address of the bond changes during a failover.
This policy is useful for devices that cannot ever
alter their MAC address, or for devices that refuse
incoming broadcasts with their own source MAC (which
interferes with the ARP monitor).
The down side of this policy is that every device on
the network must be updated via gratuitous ARP,
vs. just updating a switch or set of switches (which
often takes place for any traffic, not just ARP
traffic, if the switch snoops incoming traffic to
update its tables) for the traditional method. If the
gratuitous ARP is lost, communication may be
disrupted.
When this policy is used in conjuction with the mii
monitor, devices which assert link up prior to being
able to actually transmit and receive are particularly
susecptible to loss of the gratuitous ARP, and an
appropriate updelay setting may be required.
follow or 2
The "follow" fail_over_mac policy causes the MAC
address of the bond to be selected normally (normally
the MAC address of the first slave added to the bond).
However, the second and subsequent slaves are not set
to this MAC address while they are in a backup role; a
slave is programmed with the bond's MAC address at
failover time (and the formerly active slave receives
the newly active slave's MAC address).
This policy is useful for multiport devices that
either become confused or incur a performance penalty
when multiple ports are programmed with the same MAC
address.
The default policy is none, unless the first slave cannot
change its MAC address, in which case the active policy is
selected by default.
This option may be modified via sysfs only when no slaves are
present in the bond.
This option was added in bonding version 3.2.0. The "follow"
policy was added in bonding version 3.3.0.
lacp_rate
......@@ -338,7 +376,8 @@ max_bonds
Specifies the number of bonding devices to create for this
instance of the bonding driver. E.g., if max_bonds is 3, and
the bonding driver is not already loaded, then bond0, bond1
and bond2 will be created. The default value is 1.
and bond2 will be created. The default value is 1. Specifying
a value of 0 will load bonding, but will not create any devices.
miimon
......@@ -501,6 +540,17 @@ mode
swapped with the new curr_active_slave that was
chosen.
num_grat_arp
Specifies the number of gratuitous ARPs to be issued after a
failover event. One gratuitous ARP is issued immediately after
the failover, subsequent ARPs are sent at a rate of one per link
monitor interval (arp_interval or miimon, whichever is active).
The valid range is 0 - 255; the default value is 1. This option
affects only the active-backup mode. This option was added for
bonding version 3.3.0.
primary
A string (eth0, eth2, etc) specifying which slave is the
......@@ -581,7 +631,7 @@ xmit_hash_policy
in environments where a layer3 gateway device is
required to reach most destinations.
This algorithm is 802.3ad complient.
This algorithm is 802.3ad compliant.
layer3+4
......
Documentation/networking/can.txt
浏览文件 @ cb28a1bb
......@@ -186,7 +186,7 @@ solution for a couple of reasons:
The Linux network devices (by default) just can handle the
transmission and reception of media dependent frames. Due to the
arbritration on the CAN bus the transmission of a low prio CAN-ID
arbitration on the CAN bus the transmission of a low prio CAN-ID
may be delayed by the reception of a high prio CAN frame. To
reflect the correct* traffic on the node the loopback of the sent
data has to be performed right after a successful transmission. If
......@@ -481,7 +481,7 @@ solution for a couple of reasons:
- stats_timer: To calculate the Socket CAN core statistics
(e.g. current/maximum frames per second) this 1 second timer is
invoked at can.ko module start time by default. This timer can be
disabled by using stattimer=0 on the module comandline.
disabled by using stattimer=0 on the module commandline.
- debug: (removed since SocketCAN SVN r546)
......
Documentation/networking/dm9000.txt 0 → 100644
浏览文件 @ cb28a1bb
DM9000 Network driver
=====================
Copyright 2008 Simtec Electronics,
Ben Dooks <ben@simtec.co.uk> <ben-linux@fluff.org>
Introduction
------------
This file describes how to use the DM9000 platform-device based network driver
that is contained in the files drivers/net/dm9000.c and drivers/net/dm9000.h.
The driver supports three DM9000 variants, the DM9000E which is the first chip
supported as well as the newer DM9000A and DM9000B devices. It is currently
maintained and tested by Ben Dooks, who should be CC: to any patches for this
driver.
Defining the platform device
----------------------------
The minimum set of resources attached to the platform device are as follows:
1) The physical address of the address register
2) The physical address of the data register
3) The IRQ line the device's interrupt pin is connected to.
These resources should be specified in that order, as the ordering of the
two address regions is important (the driver expects these to be address
and then data).
An example from arch/arm/mach-s3c2410/mach-bast.c is:
static struct resource bast_dm9k_resource[] = {
[0] = {
.start = S3C2410_CS5 + BAST_PA_DM9000,
.end = S3C2410_CS5 + BAST_PA_DM9000 + 3,
.flags = IORESOURCE_MEM,
},
[1] = {
.start = S3C2410_CS5 + BAST_PA_DM9000 + 0x40,
.end = S3C2410_CS5 + BAST_PA_DM9000 + 0x40 + 0x3f,
.flags = IORESOURCE_MEM,
},
[2] = {
.start = IRQ_DM9000,
.end = IRQ_DM9000,
.flags = IORESOURCE_IRQ | IORESOURCE_IRQ_HIGHLEVEL,
}
};
static struct platform_device bast_device_dm9k = {
.name = "dm9000",
.id = 0,
.num_resources = ARRAY_SIZE(bast_dm9k_resource),
.resource = bast_dm9k_resource,
};
Note the setting of the IRQ trigger flag in bast_dm9k_resource[2].flags,
as this will generate a warning if it is not present. The trigger from
the flags field will be passed to request_irq() when registering the IRQ
handler to ensure that the IRQ is setup correctly.
This shows a typical platform device, without the optional configuration
platform data supplied. The next example uses the same resources, but adds
the optional platform data to pass extra configuration data:
static struct dm9000_plat_data bast_dm9k_platdata = {
.flags = DM9000_PLATF_16BITONLY,
};
static struct platform_device bast_device_dm9k = {
.name = "dm9000",
.id = 0,
.num_resources = ARRAY_SIZE(bast_dm9k_resource),
.resource = bast_dm9k_resource,
.dev = {
.platform_data = &bast_dm9k_platdata,
}
};
The platform data is defined in include/linux/dm9000.h and described below.
Platform data
-------------
Extra platform data for the DM9000 can describe the IO bus width to the
device, whether or not an external PHY is attached to the device and
the availability of an external configuration EEPROM.
The flags for the platform data .flags field are as follows:
DM9000_PLATF_8BITONLY
The IO should be done with 8bit operations.
DM9000_PLATF_16BITONLY
The IO should be done with 16bit operations.
DM9000_PLATF_32BITONLY
The IO should be done with 32bit operations.
DM9000_PLATF_EXT_PHY
The chip is connected to an external PHY.
DM9000_PLATF_NO_EEPROM
This can be used to signify that the board does not have an
EEPROM, or that the EEPROM should be hidden from the user.
DM9000_PLATF_SIMPLE_PHY
Switch to using the simpler PHY polling method which does not
try and read the MII PHY state regularly. This is only available
when using the internal PHY. See the section on link state polling
for more information.
The config symbol DM9000_FORCE_SIMPLE_PHY_POLL, Kconfig entry
"Force simple NSR based PHY polling" allows this flag to be
forced on at build time.
PHY Link state polling
----------------------
The driver keeps track of the link state and informs the network core
about link (carrier) availablilty. This is managed by several methods
depending on the version of the chip and on which PHY is being used.
For the internal PHY, the original (and currently default) method is
to read the MII state, either when the status changes if we have the
necessary interrupt support in the chip or every two seconds via a
periodic timer.
To reduce the overhead for the internal PHY, there is now the option
of using the DM9000_FORCE_SIMPLE_PHY_POLL config, or DM9000_PLATF_SIMPLE_PHY
platform data option to read the summary information without the
expensive MII accesses. This method is faster, but does not print
as much information.
When using an external PHY, the driver currently has to poll the MII
link status as there is no method for getting an interrupt on link change.
DM9000A / DM9000B
-----------------
These chips are functionally similar to the DM9000E and are supported easily
by the same driver. The features are:
1) Interrupt on internal PHY state change. This means that the periodic
polling of the PHY status may be disabled on these devices when using
the internal PHY.
2) TCP/UDP checksum offloading, which the driver does not currently support.
ethtool
-------
The driver supports the ethtool interface for access to the driver
state information, the PHY state and the EEPROM.
Documentation/networking/e1000.txt
浏览文件 @ cb28a1bb
......@@ -513,21 +513,11 @@ Additional Configurations
Intel(R) PRO/1000 PT Dual Port Server Connection
Intel(R) PRO/1000 PT Dual Port Server Adapter
Intel(R) PRO/1000 PF Dual Port Server Adapter
Intel(R) PRO/1000 PT Quad Port Server Adapter
Intel(R) PRO/1000 PT Quad Port Server Adapter
NAPI
----
NAPI (Rx polling mode) is supported in the e1000 driver. NAPI is enabled
or disabled based on the configuration of the kernel. To override
the default, use the following compile-time flags.
To enable NAPI, compile the driver module, passing in a configuration option:
make CFLAGS_EXTRA=-DE1000_NAPI install
To disable NAPI, compile the driver module, passing in a configuration option:
make CFLAGS_EXTRA=-DE1000_NO_NAPI install
NAPI (Rx polling mode) is enabled in the e1000 driver.
See www.cyberus.ca/~hadi/usenix-paper.tgz for more information on NAPI.
......
Documentation/networking/ip-sysctl.txt
浏览文件 @ cb28a1bb
......@@ -551,8 +551,9 @@ icmp_echo_ignore_broadcasts - BOOLEAN
icmp_ratelimit - INTEGER
Limit the maximal rates for sending ICMP packets whose type matches
icmp_ratemask (see below) to specific targets.
0 to disable any limiting, otherwise the maximal rate in jiffies(1)
Default: 100
0 to disable any limiting,
otherwise the minimal space between responses in milliseconds.
Default: 1000
icmp_ratemask - INTEGER
Mask made of ICMP types for which rates are being limited.
......@@ -1023,11 +1024,23 @@ max_addresses - INTEGER
autoconfigured addresses.
Default: 16
disable_ipv6 - BOOLEAN
Disable IPv6 operation.
Default: FALSE (enable IPv6 operation)
accept_dad - INTEGER
Whether to accept DAD (Duplicate Address Detection).
0: Disable DAD
1: Enable DAD (default)
2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
link-local address has been found.
icmp/*:
ratelimit - INTEGER
Limit the maximal rates for sending ICMPv6 packets.
0 to disable any limiting, otherwise the maximal rate in jiffies(1)
Default: 100
0 to disable any limiting,
otherwise the minimal space between responses in milliseconds.
Default: 1000
IPv6 Update by:
......
Documentation/networking/ixgb.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/networking/mac80211_hwsim/README 0 → 100644
浏览文件 @ cb28a1bb
mac80211_hwsim - software simulator of 802.11 radio(s) for mac80211
Copyright (c) 2008, Jouni Malinen <j@w1.fi>
This program 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.
Introduction
mac80211_hwsim is a Linux kernel module that can be used to simulate
arbitrary number of IEEE 802.11 radios for mac80211. It can be used to
test most of the mac80211 functionality and user space tools (e.g.,
hostapd and wpa_supplicant) in a way that matches very closely with
the normal case of using real WLAN hardware. From the mac80211 view
point, mac80211_hwsim is yet another hardware driver, i.e., no changes
to mac80211 are needed to use this testing tool.
The main goal for mac80211_hwsim is to make it easier for developers
to test their code and work with new features to mac80211, hostapd,
and wpa_supplicant. The simulated radios do not have the limitations
of real hardware, so it is easy to generate an arbitrary test setup
and always reproduce the same setup for future tests. In addition,
since all radio operation is simulated, any channel can be used in
tests regardless of regulatory rules.
mac80211_hwsim kernel module has a parameter 'radios' that can be used
to select how many radios are simulated (default 2). This allows
configuration of both very simply setups (e.g., just a single access
point and a station) or large scale tests (multiple access points with
hundreds of stations).
mac80211_hwsim works by tracking the current channel of each virtual
radio and copying all transmitted frames to all other radios that are
currently enabled and on the same channel as the transmitting
radio. Software encryption in mac80211 is used so that the frames are
actually encrypted over the virtual air interface to allow more
complete testing of encryption.
A global monitoring netdev, hwsim#, is created independent of
mac80211. This interface can be used to monitor all transmitted frames
regardless of channel.
Simple example
This example shows how to use mac80211_hwsim to simulate two radios:
one to act as an access point and the other as a station that
associates with the AP. hostapd and wpa_supplicant are used to take
care of WPA2-PSK authentication. In addition, hostapd is also
processing access point side of association.
Please note that the current Linux kernel does not enable AP mode, so a
simple patch is needed to enable AP mode selection:
http://johannes.sipsolutions.net/patches/kernel/all/LATEST/006-allow-ap-vlan-modes.patch
# Build mac80211_hwsim as part of kernel configuration
# Load the module
modprobe mac80211_hwsim
# Run hostapd (AP) for wlan0
hostapd hostapd.conf
# Run wpa_supplicant (station) for wlan1
wpa_supplicant -Dwext -iwlan1 -c wpa_supplicant.conf
Documentation/networking/mac80211_hwsim/hostapd.conf 0 → 100644
浏览文件 @ cb28a1bb
interface=wlan0
driver=nl80211
hw_mode=g
channel=1
ssid=mac80211 test
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_passphrase=12345678
Documentation/networking/mac80211_hwsim/wpa_supplicant.conf 0 → 100644
浏览文件 @ cb28a1bb
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="mac80211 test"
psk="12345678"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=CCMP
}
Documentation/networking/multiqueue.txt
浏览文件 @ cb28a1bb
......@@ -3,19 +3,11 @@
===========================================
Section 1: Base driver requirements for implementing multiqueue support
Section 2: Qdisc support for multiqueue devices
Section 3: Brief howto using PRIO or RR for multiqueue devices
Intro: Kernel support for multiqueue devices
---------------------------------------------------------
Kernel support for multiqueue devices is only an API that is presented to the
netdevice layer for base drivers to implement. This feature is part of the
core networking stack, and all network devices will be running on the
multiqueue-aware stack. If a base driver only has one queue, then these
changes are transparent to that driver.
Kernel support for multiqueue devices is always present.
Section 1: Base driver requirements for implementing multiqueue support
-----------------------------------------------------------------------
......@@ -32,84 +24,4 @@ netif_{start|stop|wake}_subqueue() functions to manage each queue while the
device is still operational. netdev->queue_lock is still used when the device
comes online or when it's completely shut down (unregister_netdev(), etc.).
Finally, the base driver should indicate that it is a multiqueue device. The
feature flag NETIF_F_MULTI_QUEUE should be added to the netdev->features
bitmap on device initialization. Below is an example from e1000:
#ifdef CONFIG_E1000_MQ
if ( (adapter->hw.mac.type == e1000_82571) ||
(adapter->hw.mac.type == e1000_82572) ||
(adapter->hw.mac.type == e1000_80003es2lan))
netdev->features |= NETIF_F_MULTI_QUEUE;
#endif
Section 2: Qdisc support for multiqueue devices
-----------------------------------------------
Currently two qdiscs support multiqueue devices. A new round-robin qdisc,
sch_rr, and sch_prio. The qdisc is responsible for classifying the skb's to
bands and queues, and will store the queue mapping into skb->queue_mapping.
Use this field in the base driver to determine which queue to send the skb
to.
sch_rr has been added for hardware that doesn't want scheduling policies from
software, so it's a straight round-robin qdisc. It uses the same syntax and
classification priomap that sch_prio uses, so it should be intuitive to
configure for people who've used sch_prio.
In order to utilitize the multiqueue features of the qdiscs, the network
device layer needs to enable multiple queue support. This can be done by
selecting NETDEVICES_MULTIQUEUE under Drivers.
The PRIO qdisc naturally plugs into a multiqueue device. If
NETDEVICES_MULTIQUEUE is selected, then on qdisc load, the number of
bands requested is compared to the number of queues on the hardware. If they
are equal, it sets a one-to-one mapping up between the queues and bands. If
they're not equal, it will not load the qdisc. This is the same behavior
for RR. Once the association is made, any skb that is classified will have
skb->queue_mapping set, which will allow the driver to properly queue skb's
to multiple queues.
Section 3: Brief howto using PRIO and RR for multiqueue devices
---------------------------------------------------------------
The userspace command 'tc,' part of the iproute2 package, is used to configure
qdiscs. To add the PRIO qdisc to your network device, assuming the device is
called eth0, run the following command:
# tc qdisc add dev eth0 root handle 1: prio bands 4 multiqueue
This will create 4 bands, 0 being highest priority, and associate those bands
to the queues on your NIC. Assuming eth0 has 4 Tx queues, the band mapping
would look like:
band 0 => queue 0
band 1 => queue 1
band 2 => queue 2
band 3 => queue 3
Traffic will begin flowing through each queue if your TOS values are assigning
traffic across the various bands. For example, ssh traffic will always try to
go out band 0 based on TOS -> Linux priority conversion (realtime traffic),
so it will be sent out queue 0. ICMP traffic (pings) fall into the "normal"
traffic classification, which is band 1. Therefore pings will be send out
queue 1 on the NIC.
Note the use of the multiqueue keyword. This is only in versions of iproute2
that support multiqueue networking devices; if this is omitted when loading
a qdisc onto a multiqueue device, the qdisc will load and operate the same
if it were loaded onto a single-queue device (i.e. - sends all traffic to
queue 0).
Another alternative to multiqueue band allocation can be done by using the
multiqueue option and specify 0 bands. If this is the case, the qdisc will
allocate the number of bands to equal the number of queues that the device
reports, and bring the qdisc online.
The behavior of tc filters remains the same, where it will override TOS priority
classification.
Author: Peter P. Waskiewicz Jr. <peter.p.waskiewicz.jr@intel.com>
Documentation/networking/packet_mmap.txt
浏览文件 @ cb28a1bb
......@@ -326,7 +326,7 @@ just one call to mmap is needed:
mmap(0, size, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0);
If tp_frame_size is a divisor of tp_block_size frames will be
contiguosly spaced by tp_frame_size bytes. If not, each
contiguously spaced by tp_frame_size bytes. If not, each
tp_block_size/tp_frame_size frames there will be a gap between
the frames. This is because a frame cannot be spawn across two
blocks.
......
Documentation/networking/s2io.txt
浏览文件 @ cb28a1bb
......@@ -52,13 +52,10 @@ d. MSI/MSI-X. Can be enabled on platforms which support this feature
(IA64, Xeon) resulting in noticeable performance improvement(upto 7%
on certain platforms).
e. NAPI. Compile-time option(CONFIG_S2IO_NAPI) for better Rx interrupt
moderation.
f. Statistics. Comprehensive MAC-level and software statistics displayed
e. Statistics. Comprehensive MAC-level and software statistics displayed
using "ethtool -S" option.
g. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
f. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
with multiple steering options.
4. Command line parameters
......
Documentation/networking/tc-actions-env-rules.txt
浏览文件 @ cb28a1bb
......@@ -4,26 +4,27 @@ The "enviromental" rules for authors of any new tc actions are:
1) If you stealeth or borroweth any packet thou shalt be branching
from the righteous path and thou shalt cloneth.
For example if your action queues a packet to be processed later
or intentionaly branches by redirecting a packet then you need to
For example if your action queues a packet to be processed later,
or intentionally branches by redirecting a packet, then you need to
clone the packet.
There are certain fields in the skb tc_verd that need to be reset so we
avoid loops etc. A few are generic enough so much so that skb_act_clone()
resets them for you. So invoke skb_act_clone() rather than skb_clone()
avoid loops, etc. A few are generic enough that skb_act_clone()
resets them for you, so invoke skb_act_clone() rather than skb_clone().
2) If you munge any packet thou shalt call pskb_expand_head in the case
someone else is referencing the skb. After that you "own" the skb.
You must also tell us if it is ok to munge the packet (TC_OK2MUNGE),
this way any action downstream can stomp on the packet.
3) dropping packets you dont own is a nono. You simply return
3) Dropping packets you don't own is a no-no. You simply return
TC_ACT_SHOT to the caller and they will drop it.
The "enviromental" rules for callers of actions (qdiscs etc) are:
*) thou art responsible for freeing anything returned as being
*) Thou art responsible for freeing anything returned as being
TC_ACT_SHOT/STOLEN/QUEUED. If none of TC_ACT_SHOT/STOLEN/QUEUED is
returned then all is great and you dont need to do anything.
returned, then all is great and you don't need to do anything.
Post on netdev if something is unclear.
Documentation/networking/udplite.txt
浏览文件 @ cb28a1bb
......@@ -148,7 +148,7 @@
getsockopt(sockfd, SOL_SOCKET, SO_NO_CHECK, &value, ...);
is meaningless (as in TCP). Packets with a zero checksum field are
illegal (cf. RFC 3828, sec. 3.1) will be silently discarded.
illegal (cf. RFC 3828, sec. 3.1) and will be silently discarded.
4) Fragmentation
......
Documentation/power/00-INDEX
浏览文件 @ cb28a1bb
00-INDEX
- This file
apm-acpi.txt
- basic info about the APM and ACPI support.
basic-pm-debugging.txt
- Debugging suspend and resume
devices.txt
......@@ -14,8 +16,6 @@ notifiers.txt
- Registering suspend notifiers in device drivers
pci.txt
- How the PCI Subsystem Does Power Management
pm.txt
- info on Linux power management support.
pm_qos_interface.txt
- info on Linux PM Quality of Service interface
power_supply_class.txt
......
Documentation/power/apm-acpi.txt 0 → 100644
浏览文件 @ cb28a1bb
APM or ACPI?
------------
If you have a relatively recent x86 mobile, desktop, or server system,
odds are it supports either Advanced Power Management (APM) or
Advanced Configuration and Power Interface (ACPI). ACPI is the newer
of the two technologies and puts power management in the hands of the
operating system, allowing for more intelligent power management than
is possible with BIOS controlled APM.
The best way to determine which, if either, your system supports is to
build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is
enabled by default). If a working ACPI implementation is found, the
ACPI driver will override and disable APM, otherwise the APM driver
will be used.
No, sorry, you cannot have both ACPI and APM enabled and running at
once. Some people with broken ACPI or broken APM implementations
would like to use both to get a full set of working features, but you
simply cannot mix and match the two. Only one power management
interface can be in control of the machine at once. Think about it..
User-space Daemons
------------------
Both APM and ACPI rely on user-space daemons, apmd and acpid
respectively, to be completely functional. Obtain both of these
daemons from your Linux distribution or from the Internet (see below)
and be sure that they are started sometime in the system boot process.
Go ahead and start both. If ACPI or APM is not available on your
system the associated daemon will exit gracefully.
apmd: http://worldvisions.ca/~apenwarr/apmd/
acpid: http://acpid.sf.net/
Documentation/power/pm.txt 已删除 100644 → 0
浏览文件 @ b6d4f7e3
Linux Power Management Support
This document briefly describes how to use power management with your
Linux system and how to add power management support to Linux drivers.
APM or ACPI?
------------
If you have a relatively recent x86 mobile, desktop, or server system,
odds are it supports either Advanced Power Management (APM) or
Advanced Configuration and Power Interface (ACPI). ACPI is the newer
of the two technologies and puts power management in the hands of the
operating system, allowing for more intelligent power management than
is possible with BIOS controlled APM.
The best way to determine which, if either, your system supports is to
build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is
enabled by default). If a working ACPI implementation is found, the
ACPI driver will override and disable APM, otherwise the APM driver
will be used.
No, sorry, you cannot have both ACPI and APM enabled and running at
once. Some people with broken ACPI or broken APM implementations
would like to use both to get a full set of working features, but you
simply cannot mix and match the two. Only one power management
interface can be in control of the machine at once. Think about it..
User-space Daemons
------------------
Both APM and ACPI rely on user-space daemons, apmd and acpid
respectively, to be completely functional. Obtain both of these
daemons from your Linux distribution or from the Internet (see below)
and be sure that they are started sometime in the system boot process.
Go ahead and start both. If ACPI or APM is not available on your
system the associated daemon will exit gracefully.
apmd: http://worldvisions.ca/~apenwarr/apmd/
acpid: http://acpid.sf.net/
Driver Interface -- OBSOLETE, DO NOT USE!
----------------*************************
Note: pm_register(), pm_access(), pm_dev_idle() and friends are
obsolete. Please do not use them. Instead you should properly hook
your driver into the driver model, and use its suspend()/resume()
callbacks to do this kind of stuff.
If you are writing a new driver or maintaining an old driver, it
should include power management support. Without power management
support, a single driver may prevent a system with power management
capabilities from ever being able to suspend (safely).
Overview:
1) Register each instance of a device with "pm_register"
2) Call "pm_access" before accessing the hardware.
(this will ensure that the hardware is awake and ready)
3) Your "pm_callback" is called before going into a
suspend state (ACPI D1-D3) or after resuming (ACPI D0)
from a suspend.
4) Call "pm_dev_idle" when the device is not being used
(optional but will improve device idle detection)
5) When unloaded, unregister the device with "pm_unregister"
/*
* Description: Register a device with the power-management subsystem
*
* Parameters:
* type - device type (PCI device, system device, ...)
* id - instance number or unique identifier
* cback - request handler callback (suspend, resume, ...)
*
* Returns: Registered PM device or NULL on error
*
* Examples:
* dev = pm_register(PM_SYS_DEV, PM_SYS_VGA, vga_callback);
*
* struct pci_dev *pci_dev = pci_find_dev(...);
* dev = pm_register(PM_PCI_DEV, PM_PCI_ID(pci_dev), callback);
*/
struct pm_dev *pm_register(pm_dev_t type, unsigned long id, pm_callback cback);
/*
* Description: Unregister a device with the power management subsystem
*
* Parameters:
* dev - PM device previously returned from pm_register
*/
void pm_unregister(struct pm_dev *dev);
/*
* Description: Unregister all devices with a matching callback function
*
* Parameters:
* cback - previously registered request callback
*
* Notes: Provided for easier porting from old APM interface
*/
void pm_unregister_all(pm_callback cback);
/*
* Power management request callback
*
* Parameters:
* dev - PM device previously returned from pm_register
* rqst - request type
* data - data, if any, associated with the request
*
* Returns: 0 if the request is successful
* EINVAL if the request is not supported
* EBUSY if the device is now busy and cannot handle the request
* ENOMEM if the device was unable to handle the request due to memory
*
* Details: The device request callback will be called before the
* device/system enters a suspend state (ACPI D1-D3) or
* or after the device/system resumes from suspend (ACPI D0).
* For PM_SUSPEND, the ACPI D-state being entered is passed
* as the "data" argument to the callback. The device
* driver should save (PM_SUSPEND) or restore (PM_RESUME)
* device context when the request callback is called.
*
* Once a driver returns 0 (success) from a suspend
* request, it should not process any further requests or
* access the device hardware until a call to "pm_access" is made.
*/
typedef int (*pm_callback)(struct pm_dev *dev, pm_request_t rqst, void *data);
Driver Details
--------------
This is just a quick Q&A as a stopgap until a real driver writers'
power management guide is available.
Q: When is a device suspended?
Devices can be suspended based on direct user request (eg. laptop lid
closes), system power policy (eg. sleep after 30 minutes of console
inactivity), or device power policy (eg. power down device after 5
minutes of inactivity)
Q: Must a driver honor a suspend request?
No, a driver can return -EBUSY from a suspend request and this
will stop the system from suspending. When a suspend request
fails, all suspended devices are resumed and the system continues
to run. Suspend can be retried at a later time.
Q: Can the driver block suspend/resume requests?
Yes, a driver can delay its return from a suspend or resume
request until the device is ready to handle requests. It
is advantageous to return as quickly as possible from a
request as suspend/resume are done serially.
Q: What context is a suspend/resume initiated from?
A suspend or resume is initiated from a kernel thread context.
It is safe to block, allocate memory, initiate requests
or anything else you can do within the kernel.
Q: Will requests continue to arrive after a suspend?
Possibly. It is the driver's responsibility to queue(*),
fail, or drop any requests that arrive after returning
success to a suspend request. It is important that the
driver not access its device until after it receives
a resume request as the device's bus may no longer
be active.
(*) If a driver queues requests for processing after
resume be aware that the device, network, etc.
might be in a different state than at suspend time.
It's probably better to drop requests unless
the driver is a storage device.
Q: Do I have to manage bus-specific power management registers
No. It is the responsibility of the bus driver to manage
PCI, USB, etc. power management registers. The bus driver
or the power management subsystem will also enable any
wake-on functionality that the device has.
Q: So, really, what do I need to do to support suspend/resume?
You need to save any device context that would
be lost if the device was powered off and then restore
it at resume time. When ACPI is active, there are
three levels of device suspend states; D1, D2, and D3.
(The suspend state is passed as the "data" argument
to the device callback.) With D3, the device is powered
off and loses all context, D1 and D2 are shallower power
states and require less device context to be saved. To
play it safe, just save everything at suspend and restore
everything at resume.
Q: Where do I store device context for suspend?
Anywhere in memory, kmalloc a buffer or store it
in the device descriptor. You are guaranteed that the
contents of memory will be restored and accessible
before resume, even when the system suspends to disk.
Q: What do I need to do for ACPI vs. APM vs. etc?
Drivers need not be aware of the specific power management
technology that is active. They just need to be aware
of when the overlying power management system requests
that they suspend or resume.
Q: What about device dependencies?
When a driver registers a device, the power management
subsystem uses the information provided to build a
tree of device dependencies (eg. USB device X is on
USB controller Y which is on PCI bus Z) When power
management wants to suspend a device, it first sends
a suspend request to its driver, then the bus driver,
and so on up to the system bus. Device resumes
proceed in the opposite direction.
Q: Who do I contact for additional information about
enabling power management for my specific driver/device?
ACPI Development mailing list: linux-acpi@vger.kernel.org
System Interface -- OBSOLETE, DO NOT USE!
----------------*************************
If you are providing new power management support to Linux (ie.
adding support for something like APM or ACPI), you should
communicate with drivers through the existing generic power
management interface.
/*
* Send a request to all devices
*
* Parameters:
* rqst - request type
* data - data, if any, associated with the request
*
* Returns: 0 if the request is successful
* See "pm_callback" return for errors
*
* Details: Walk list of registered devices and call pm_send
* for each until complete or an error is encountered.
* If an error is encountered for a suspend request,
* return all devices to the state they were in before
* the suspend request.
*/
int pm_send_all(pm_request_t rqst, void *data);
/*
* Find a matching device
*
* Parameters:
* type - device type (PCI device, system device, or 0 to match all devices)
* from - previous match or NULL to start from the beginning
*
* Returns: Matching device or NULL if none found
*/
struct pm_dev *pm_find(pm_dev_t type, struct pm_dev *from);
Documentation/powerpc/dts-bindings/fsl/cpm_qe/gpio.txt 0 → 100644
浏览文件 @ cb28a1bb
Every GPIO controller node must have #gpio-cells property defined,
this information will be used to translate gpio-specifiers.
On CPM1 devices, all ports are using slightly different register layouts.
Ports A, C and D are 16bit ports and Ports B and E are 32bit ports.
On CPM2 devices, all ports are 32bit ports and use a common register layout.
Required properties:
- compatible : "fsl,cpm1-pario-bank-a", "fsl,cpm1-pario-bank-b",
"fsl,cpm1-pario-bank-c", "fsl,cpm1-pario-bank-d",
"fsl,cpm1-pario-bank-e", "fsl,cpm2-pario-bank"
- #gpio-cells : Should be two. The first cell is the pin number and the
second cell is used to specify optional paramters (currently unused).
- gpio-controller : Marks the port as GPIO controller.
Example of three SOC GPIO banks defined as gpio-controller nodes:
CPM1_PIO_A: gpio-controller@950 {
#gpio-cells = <2>;
compatible = "fsl,cpm1-pario-bank-a";
reg = <0x950 0x10>;
gpio-controller;
};
CPM1_PIO_B: gpio-controller@ab8 {
#gpio-cells = <2>;
compatible = "fsl,cpm1-pario-bank-b";
reg = <0xab8 0x10>;
gpio-controller;
};
CPM1_PIO_E: gpio-controller@ac8 {
#gpio-cells = <2>;
compatible = "fsl,cpm1-pario-bank-e";
reg = <0xac8 0x18>;
gpio-controller;
};
Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe/usb.txt
浏览文件 @ cb28a1bb
* USB (Universal Serial Bus Controller)
Freescale QUICC Engine USB Controller
Required properties:
- compatible : could be "qe_udc" or "fhci-hcd".
- mode : the could be "host" or "slave".
- reg : Offset and length of the register set for the device
- interrupts : <a b> where a is the interrupt number and b is a
field that represents an encoding of the sense and level
information for the interrupt. This should be encoded based on
the information in section 2) depending on the type of interrupt
controller you have.
- interrupt-parent : the phandle for the interrupt controller that
services interrupts for this device.
- compatible : should be "fsl,<chip>-qe-usb", "fsl,mpc8323-qe-usb".
- reg : the first two cells should contain usb registers location and
length, the next two two cells should contain PRAM location and
length.
- interrupts : should contain USB interrupt.
- interrupt-parent : interrupt source phandle.
- fsl,fullspeed-clock : specifies the full speed USB clock source:
"none": clock source is disabled
"brg1" through "brg16": clock source is BRG1-BRG16, respectively
"clk1" through "clk24": clock source is CLK1-CLK24, respectively
- fsl,lowspeed-clock : specifies the low speed USB clock source:
"none": clock source is disabled
"brg1" through "brg16": clock source is BRG1-BRG16, respectively
"clk1" through "clk24": clock source is CLK1-CLK24, respectively
- hub-power-budget : USB power budget for the root hub, in mA.
- gpios : should specify GPIOs in this order: USBOE, USBTP, USBTN, USBRP,
USBRN, SPEED (optional), and POWER (optional).
Example(slave):
usb@6c0 {
compatible = "qe_udc";
reg = <6c0 40>;
interrupts = <8b 0>;
interrupt-parent = <700>;
mode = "slave";
};
Example:
usb@6c0 {
compatible = "fsl,mpc8360-qe-usb", "fsl,mpc8323-qe-usb";
reg = <0x6c0 0x40 0x8b00 0x100>;
interrupts = <11>;
interrupt-parent = <&qeic>;
fsl,fullspeed-clock = "clk21";
gpios = <&qe_pio_b 2 0 /* USBOE */
&qe_pio_b 3 0 /* USBTP */
&qe_pio_b 8 0 /* USBTN */
&qe_pio_b 9 0 /* USBRP */
&qe_pio_b 11 0 /* USBRN */
&qe_pio_e 20 0 /* SPEED */
&qe_pio_e 21 0 /* POWER */>;
};
Documentation/powerpc/dts-bindings/fsl/mcu-mpc8349emitx.txt 0 → 100644
浏览文件 @ cb28a1bb
Freescale MPC8349E-mITX-compatible Power Management Micro Controller Unit (MCU)
Required properties:
- compatible : "fsl,<mcu-chip>-<board>", "fsl,mcu-mpc8349emitx".
- reg : should specify I2C address (0x0a).
- #gpio-cells : should be 2.
- gpio-controller : should be present.
Example:
mcu@0a {
#gpio-cells = <2>;
compatible = "fsl,mc9s08qg8-mpc8349emitx",
"fsl,mcu-mpc8349emitx";
reg = <0x0a>;
gpio-controller;
};
Documentation/powerpc/dts-bindings/fsl/pmc.txt 0 → 100644
浏览文件 @ cb28a1bb
* Power Management Controller
Properties:
- compatible: "fsl,<chip>-pmc".
"fsl,mpc8349-pmc" should be listed for any chip whose PMC is
compatible. "fsl,mpc8313-pmc" should also be listed for any chip
whose PMC is compatible, and implies deep-sleep capability.
"fsl,mpc8548-pmc" should be listed for any chip whose PMC is
compatible. "fsl,mpc8536-pmc" should also be listed for any chip
whose PMC is compatible, and implies deep-sleep capability.
"fsl,mpc8641d-pmc" should be listed for any chip whose PMC is
compatible; all statements below that apply to "fsl,mpc8548-pmc" also
apply to "fsl,mpc8641d-pmc".
Compatibility does not include bit assigments in SCCR/PMCDR/DEVDISR; these
bit assigments are indicated via the sleep specifier in each device's
sleep property.
- reg: For devices compatible with "fsl,mpc8349-pmc", the first resource
is the PMC block, and the second resource is the Clock Configuration
block.
For devices compatible with "fsl,mpc8548-pmc", the first resource
is a 32-byte block beginning with DEVDISR.
- interrupts: For "fsl,mpc8349-pmc"-compatible devices, the first
resource is the PMC block interrupt.
- fsl,mpc8313-wakeup-timer: For "fsl,mpc8313-pmc"-compatible devices,
this is a phandle to an "fsl,gtm" node on which timer 4 can be used as
a wakeup source from deep sleep.
Sleep specifiers:
fsl,mpc8349-pmc: Sleep specifiers consist of one cell. For each bit
that is set in the cell, the corresponding bit in SCCR will be saved
and cleared on suspend, and restored on resume. This sleep controller
supports disabling and resuming devices at any time.
fsl,mpc8536-pmc: Sleep specifiers consist of three cells, the third of
which will be ORed into PMCDR upon suspend, and cleared from PMCDR
upon resume. The first two cells are as described for fsl,mpc8578-pmc.
This sleep controller only supports disabling devices during system
sleep, or permanently.
fsl,mpc8548-pmc: Sleep specifiers consist of one or two cells, the
first of which will be ORed into DEVDISR (and the second into
DEVDISR2, if present -- this cell should be zero or absent if the
hardware does not have DEVDISR2) upon a request for permanent device
disabling. This sleep controller does not support configuring devices
to disable during system sleep (unless supported by another compatible
match), or dynamically.
Example:
power@b00 {
compatible = "fsl,mpc8313-pmc", "fsl,mpc8349-pmc";
reg = <0xb00 0x100 0xa00 0x100>;
interrupts = <80 8>;
};
Documentation/powerpc/dts-bindings/fsl/tsec.txt
浏览文件 @ cb28a1bb
......@@ -24,46 +24,39 @@ Example:
* Gianfar-compatible ethernet nodes
Required properties:
Properties:
- device_type : Should be "network"
- model : Model of the device. Can be "TSEC", "eTSEC", or "FEC"
- compatible : Should be "gianfar"
- reg : Offset and length of the register set for the device
- mac-address : List of bytes representing the ethernet address of
- local-mac-address : List of bytes representing the ethernet address of
this controller
- interrupts : <a b> where a is the interrupt number and b is a
field that represents an encoding of the sense and level
information for the interrupt. This should be encoded based on
the information in section 2) depending on the type of interrupt
controller you have.
- interrupt-parent : the phandle for the interrupt controller that
services interrupts for this device.
- interrupts : For FEC devices, the first interrupt is the device's
interrupt. For TSEC and eTSEC devices, the first interrupt is
transmit, the second is receive, and the third is error.
- phy-handle : The phandle for the PHY connected to this ethernet
controller.
- fixed-link : <a b c d e> where a is emulated phy id - choose any,
but unique to the all specified fixed-links, b is duplex - 0 half,
1 full, c is link speed - d#10/d#100/d#1000, d is pause - 0 no
pause, 1 pause, e is asym_pause - 0 no asym_pause, 1 asym_pause.
Recommended properties:
- phy-connection-type : a string naming the controller/PHY interface type,
i.e., "mii" (default), "rmii", "gmii", "rgmii", "rgmii-id", "sgmii",
"tbi", or "rtbi". This property is only really needed if the connection
is of type "rgmii-id", as all other connection types are detected by
hardware.
- fsl,magic-packet : If present, indicates that the hardware supports
waking up via magic packet.
Example:
ethernet@24000 {
#size-cells = <0>;
device_type = "network";
model = "TSEC";
compatible = "gianfar";
reg = <24000 1000>;
mac-address = [ 00 E0 0C 00 73 00 ];
interrupts = <d 3 e 3 12 3>;
interrupt-parent = <40000>;
phy-handle = <2452000>
reg = <0x24000 0x1000>;
local-mac-address = [ 00 E0 0C 00 73 00 ];
interrupts = <29 2 30 2 34 2>;
interrupt-parent = <&mpic>;
phy-handle = <&phy0>
};
Documentation/powerpc/dts-bindings/fsl/upm-nand.txt 0 → 100644
浏览文件 @ cb28a1bb
Freescale Localbus UPM programmed to work with NAND flash
Required properties:
- compatible : "fsl,upm-nand".
- reg : should specify localbus chip select and size used for the chip.
- fsl,upm-addr-offset : UPM pattern offset for the address latch.
- fsl,upm-cmd-offset : UPM pattern offset for the command latch.
- gpios : may specify optional GPIO connected to the Ready-Not-Busy pin.
Example:
upm@1,0 {
compatible = "fsl,upm-nand";
reg = <1 0 1>;
fsl,upm-addr-offset = <16>;
fsl,upm-cmd-offset = <8>;
gpios = <&qe_pio_e 18 0>;
flash {
#address-cells = <1>;
#size-cells = <1>;
compatible = "...";
partition@0 {
...
};
};
};
Documentation/powerpc/dts-bindings/gpio/led.txt 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/powerpc/qe_firmware.txt
浏览文件 @ cb28a1bb
......@@ -217,7 +217,7 @@ Although it is not recommended, you can specify '0' in the soc.model
field to skip matching SOCs altogether.
The 'model' field is a 16-bit number that matches the actual SOC. The
'major' and 'minor' fields are the major and minor revision numbrs,
'major' and 'minor' fields are the major and minor revision numbers,
respectively, of the SOC.
For example, to match the 8323, revision 1.0:
......
Documentation/rfkill.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/s390/driver-model.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/scsi/ibmmca.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/scsi/lpfc.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/serial/driver
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/sh/clk.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/sparse.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/specialix.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/sysfs-rules.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/telephony/ixj.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/timers/highres.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/usb/authorization.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/usb/gadget_serial.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/usb/persist.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/usb/uhci.txt 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
Documentation/video4linux/cx18.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/video4linux/gspca.txt 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
Documentation/vm/hugetlbpage.txt
浏览文件 @ cb28a1bb
此差异已折叠。
Kbuild
浏览文件 @ cb28a1bb
此差异已折叠。
MAINTAINERS
浏览文件 @ cb28a1bb
此差异已折叠。
Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/alpha/boot/misc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/alpha/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/alpha/mm/numa.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/boot/compressed/misc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/common/dmabounce.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/common/locomo.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/common/sa1111.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/common/scoop.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/configs/ezx_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/ecard.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/kgdb.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/kprobes.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/module.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/time.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/board-cam60.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/board-cap9adk.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/board-dk.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/board-kb9202.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/board-yl-9200.c 100755 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-at91/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-imx/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-integrator/impd1.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-integrator/lm.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-iop32x/n2100.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp2000/core.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp23xx/core.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp23xx/roadrunner.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/avila-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/coyote-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/dsmg600-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/fsg-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/gtwx5715-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/ixdp425-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/ixdpg425-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/nas100d-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ixp4xx/wg302v2-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ks8695/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-netx/generic.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-ns9xxx/clock.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-omap1/board-palmz71.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-omap1/fpga.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-orion5x/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-orion5x/ts209-setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pnx4008/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/clock.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/clock.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/cm-x270-pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/cm-x270-pci.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/cm-x270.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/devices.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/e400_lcd.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/e740_lcd.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/e750_lcd.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/e800_lcd.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/eseries.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/eseries_udc.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/ezx.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/littleton.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/mfp-pxa2xx.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/palmtx.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/pcm027.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/pxa25x.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/pxa300.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/pxa320.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/pxa3xx.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/pxa930.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/reset.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/saar.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/sharpsl_pm.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/spitz.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/ssp.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/tavorevb.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/tosa-bt.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/zylonite.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa300.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa320.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-sa1100/cerf.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-sa1100/clock.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-sa1100/h3600.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-sa1100/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-sa1100/neponset.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mach-sa1100/pleb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mm/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mm/discontig.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mm/fault-armv.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-mxc/gpio.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-omap/fb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-omap/mailbox.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-s3c24xx/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-s3c24xx/dma.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/plat-s3c24xx/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/boards/atstk1000/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/kernel/cpu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/kernel/process.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/kernel/stacktrace.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/kernel/time.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/mach-at32ap/at32ap700x.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/mach-at32ap/hsmc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/mach-at32ap/pio.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/avr32/mm/ioremap.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/Kconfig.debug
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/configs/CM-BF527_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/bfin_dma_5xx.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/bfin_gpio.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/dualcore_test.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/blackfin/kernel/entry.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/kgdb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/module.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/process.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/ptrace.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/traps.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/kernel/vmlinux.lds.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-bf527/boards/cm_bf527.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-bf527/head.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-bf533/head.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-bf537/head.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-bf548/head.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-bf561/head.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-common/entry.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mach-common/pm.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mm/blackfin_sram.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mm/blackfin_sram.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/blackfin/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/arch-v10/boot/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/arch-v10/kernel/kgdb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/arch-v10/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/arch-v32/boot/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/arch-v32/kernel/kgdb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/arch-v32/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/kernel/profile.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/cris/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/frv/kernel/gdb-stub.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/frv/kernel/pm.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/frv/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/h8300/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/h8300/boot/compressed/misc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/h8300/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/h8300/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/hp/common/hwsw_iommu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/hp/sim/simserial.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/err_inject.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/head.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/iosapic.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/irq_ia64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/ivt.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/kprobes.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/minstate.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/module.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/nr-irqs.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/paravirt.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/paravirt_inst.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/paravirtentry.S 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/smpboot.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/sys_ia64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/time.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kernel/vmlinux.lds.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kvm/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/kvm/kvm-ia64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/mm/discontig.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/mm/hugetlbpage.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/ia64/sn/pci/pci_dma.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m32r/boot/compressed/misc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m32r/mm/discontig.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m32r/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/amiga/chipram.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/amiga/config.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/atari/debug.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/fpsp040/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/ifpsp060/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/kernel/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/kernel/vmlinux-std.lds
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/kernel/vmlinux-sun3.lds
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/lib/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/baboon.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/bootparse.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/m68k/mac/config.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/debug.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/oss.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/psc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mac/via.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/math-emu/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mm/motorola.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/mm/sun3mmu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/q40/config.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/config.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/dvma.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/idprom.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/mmu_emu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/prom/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/prom/console.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/prom/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/prom/misc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/prom/printf.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/sbus.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/m68k/sun3/sun3dvma.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68k/sun3/sun3ints.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/configs/m5208evb_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/configs/m5249evb_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/configs/m5275evb_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/configs/m5307c3_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/configs/m5407c3_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/kernel/time.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/kernel/traps.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/kernel/vmlinux.lds.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/m68knommu/platform/coldfire/dma_timer.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/au1000/common/power.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/cobalt/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/configs/rb532_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/module.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/process.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/rtlx.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/scall32-o32.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/scall64-64.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/scall64-n32.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/scall64-o32.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/stacktrace.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/kernel/syscall.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/math-emu/kernel_linkage.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/mm/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/mm/dma-default.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/mm/pgtable.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/mips/pci/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/pci/fixup-rc32434.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/pci/ops-rc32434.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/pci/pci-rc32434.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/pci/pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/Makefile 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/devices.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/gpio.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/irq.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/prom.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/serial.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/setup.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/rb532/time.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/sgi-ip22/ip22-platform.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/sgi-ip22/ip28-berr.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/sgi-ip27/ip27-klnuma.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/sgi-ip27/ip27-memory.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/sgi-ip32/ip32-platform.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/sibyte/common/sb_tbprof.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/irq_tx4927.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/irq_tx4938.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/mem_tx4927.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/mem_tx4938.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/mips/txx9/generic/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/setup_tx4927.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/generic/setup_tx4938.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/jmr3927/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/rbtx4927/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/rbtx4927/prom.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/rbtx4927/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/rbtx4938/prom.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mips/txx9/rbtx4938/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mn10300/boot/compressed/misc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mn10300/kernel/gdb-stub.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mn10300/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/mn10300/mm/pgtable.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/parisc/hpux/sys_hpux.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/parisc/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/configs/ppc6xx_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/configs/ps3_defconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/entry_32.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/idle.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/iommu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/kgdb.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/kprobes.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/legacy_serial.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/machine_kexec.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/pci-common.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/process.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/ptrace.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/rtas_flash.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/signal.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/stacktrace.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/suspend.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/sysfs.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kvm/44x_tlb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kvm/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kvm/emulate.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/kvm/powerpc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/lib/code-patching.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/lib/feature-fixups.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/lib/string.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/fault.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/hugetlbpage.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/init_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/pgtable_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/pgtable_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/mm/tlb_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/52xx/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/82xx/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/83xx/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/83xx/pci.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/powerpc/platforms/83xx/suspend-asm.S 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/83xx/suspend.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/83xx/usb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/85xx/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/86xx/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/cell/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/cell/cbe_powerbutton.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/cell/cpufreq_spudemand.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/cell/ras.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/chrp/pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/iseries/mf.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/ps3/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/platforms/pseries/cmm.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/axonram.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/dart_iommu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/fsl_pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/fsl_pci.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/ipic.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/qe_lib/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/qe_lib/qe.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/powerpc/sysdev/qe_lib/ucc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kernel/kprobes.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kernel/process.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kernel/topology.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kvm/gaccess.h
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kvm/intercept.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kvm/interrupt.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kvm/kvm-s390.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kvm/priv.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/kvm/sigp.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/mm/hugetlbpage.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/Kconfig.debug
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/dreamcast/rtc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/ap325rxa/Makefile 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/ap325rxa/setup.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/migor/Kconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/migor/lcd_qvga.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/rsk7203/Makefile 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/rsk7203/setup.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/sh7763rdp/Makefile 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/sh7763rdp/irq.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/sh7763rdp/setup.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/sh7785lcr/Makefile 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/renesas/sh7785lcr/setup.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/se/7343/irq.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/se/7343/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/se/770x/io.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/se/770x/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boards/se/7722/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/compressed/Makefile_32
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/compressed/Makefile_64
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/compressed/misc_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/compressed/misc_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/compressed/piggy.S 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/boot/compressed/vmlinux.scr 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/sh/configs/ap325rxa_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/configs/se7343_defconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/configs/se7712_defconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/configs/sh7763rdp_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/configs/sh7785lcr_defconfig 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/dma/dma-sysfs.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/pci/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/pci/fixups-sh7785lcr.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/pci/ops-dreamcast.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/pci/ops-sh7785lcr.c 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/pci/pci-auto.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/drivers/pci/pci.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/Makefile_32
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cf-enabler.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/clock.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/irq/intc.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh2/entry.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh2/ex.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh2a/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh2a/entry.S 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh2a/ex.S 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh3/ex.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh4/probe.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh4a/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/cpu/sh4a/clock-sh7343.c 已删除 100644 → 0
浏览文件 @ b6d4f7e3
此差异已折叠。
arch/sh/kernel/entry-common.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/machine_kexec.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/process_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/process_64.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/ptrace_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/setup.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/signal_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/stacktrace.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/sys_sh32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/syscalls_32.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/syscalls_64.S
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/time_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/timers/timer-tmu.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/kernel/traps_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/lib/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/cache-debugfs.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/cache-sh4.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/consistent.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/fault_32.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/hugetlbpage.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/init.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/numa.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/pg-sh4.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/pg-sh7705.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/mm/pmb.c
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sh/tools/mach-types
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/Makefile
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/Kbuild 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/agp.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/asi.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/atomic.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/auxio.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/auxio_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/auxio_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/bitops.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/btfixup.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/bugs.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/cacheflush.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/cacheflush_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/checksum.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/checksum_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/checksum_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/cpudata.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/cpudata_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/current.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/delay.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/display7seg.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/dma-mapping.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/dma-mapping_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/dma.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/dma_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/dma_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ebus.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ebus_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/elf.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/envctrl.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/fcntl.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/fhc.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/floppy.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/floppy_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/floppy_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/futex.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/hardirq.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/head.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/hugetlb.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/hypervisor.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ide.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/idprom.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/io.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/io_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/io_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ioctls.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/iommu.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ipcbuf.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ipcbuf_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ipcbuf_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/irq.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/irqflags.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/irqflags_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/irqflags_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/kdebug.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/kmap_types.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/machines.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mbus.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mc146818rtc.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mmu.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mmu_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mmu_context.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/module.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mostek.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/mostek_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/msgbuf.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/of_platform.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/of_platform_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/of_platform_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/openprom.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/openprom_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/oplib.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/oplib_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/oplib_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/page.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/page_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/page_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/parport.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pci.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pci_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pci_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/percpu.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pgalloc.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pgalloc_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pgtable.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pgtable_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pgtable_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/pil.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/posix_types.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/posix_types_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/posix_types_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/processor.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/processor_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/processor_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ptrace.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ptrace_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/ptrace_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/reg.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/reg_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/reg_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/resource.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sbus.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sbus_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sbus_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/scatterlist.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sections.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sembuf.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/setup.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sfp-machine.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sfp-machine_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sfp-machine_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/shmbuf.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/shmparam.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/sigcontext.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/siginfo.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/signal.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/signal_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/signal_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/smp.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/smp_32.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/smp_64.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/spinlock.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
arch/sparc/include/asm/spinlock_types.h 0 → 100644
浏览文件 @ cb28a1bb
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或