Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
提交 e7fd5d4b 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge branch 'linus' into perfcounters/core 

Merge reason: This brach was on -rc1, refresh it to almost-rc4 to pick up
              the latest upstream fixes.
Signed-off-by: NIngo Molnar <mingo@elte.hu>
上级 1130b029 56a50add
展开全部 隐藏空白更改
内联 并排
Showing with 27362 addition and 13782 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.gitignore
浏览文件 @ e7fd5d4b
......@@ -49,6 +49,7 @@ include/linux/compile.h
include/linux/version.h
include/linux/utsrelease.h
include/linux/bounds.h
include/generated
# stgit generated dirs
patches-*
......
Documentation/ABI/testing/debugfs-pktcdvd
浏览文件 @ e7fd5d4b
What: /debug/pktcdvd/pktcdvd[0-7]
What: /sys/kernel/debug/pktcdvd/pktcdvd[0-7]
Date: Oct. 2006
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
......@@ -10,10 +10,10 @@ debugfs interface
The pktcdvd module (packet writing driver) creates
these files in debugfs:
/debug/pktcdvd/pktcdvd[0-7]/
/sys/kernel/debug/pktcdvd/pktcdvd[0-7]/
info (0444) Lots of driver statistics and infos.
Example:
-------
cat /debug/pktcdvd/pktcdvd0/info
cat /sys/kernel/debug/pktcdvd/pktcdvd0/info
Documentation/ABI/testing/sysfs-firmware-acpi
浏览文件 @ e7fd5d4b
......@@ -69,9 +69,13 @@ Description:
gpe1F: 0 invalid
gpe_all: 1192
sci: 1194
sci_not: 0
sci - The total number of times the ACPI SCI
has claimed an interrupt.
sci - The number of times the ACPI SCI
has been called and claimed an interrupt.
sci_not - The number of times the ACPI SCI
has been called and NOT claimed an interrupt.
gpe_all - count of SCI caused by GPEs.
......
Documentation/DocBook/Makefile
浏览文件 @ e7fd5d4b
......@@ -31,7 +31,7 @@ PS_METHOD = $(prefer-db2x)
###
# The targets that may be used.
PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs
PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs
BOOKS := $(addprefix $(obj)/,$(DOCBOOKS))
xmldocs: $(BOOKS)
......@@ -213,11 +213,12 @@ silent_gen_xml = :
dochelp:
@echo ' Linux kernel internal documentation in different formats:'
@echo ' htmldocs - HTML'
@echo ' installmandocs - install man pages generated by mandocs'
@echo ' mandocs - man pages'
@echo ' pdfdocs - PDF'
@echo ' psdocs - Postscript'
@echo ' xmldocs - XML DocBook'
@echo ' mandocs - man pages'
@echo ' installmandocs - install man pages generated by mandocs'
@echo ' cleandocs - clean all generated DocBook files'
###
# Temporary files left by various tools
......@@ -235,6 +236,10 @@ clean-files := $(DOCBOOKS) \
clean-dirs := $(patsubst %.xml,%,$(DOCBOOKS)) man
cleandocs:
$(Q)rm -f $(call objectify, $(clean-files))
$(Q)rm -rf $(call objectify, $(clean-dirs))
# Declare the contents of the .PHONY variable as phony. We keep that
# information in a variable se we can use it in if_changed and friends.
......
Documentation/DocBook/kernel-api.tmpl
浏览文件 @ e7fd5d4b
......@@ -190,16 +190,20 @@ X!Ekernel/module.c
!Edrivers/pci/pci.c
!Edrivers/pci/pci-driver.c
!Edrivers/pci/remove.c
!Edrivers/pci/pci-acpi.c
!Edrivers/pci/search.c
!Edrivers/pci/msi.c
!Edrivers/pci/bus.c
!Edrivers/pci/access.c
!Edrivers/pci/irq.c
!Edrivers/pci/htirq.c
<!-- FIXME: Removed for now since no structured comments in source
X!Edrivers/pci/hotplug.c
-->
!Edrivers/pci/probe.c
!Edrivers/pci/slot.c
!Edrivers/pci/rom.c
!Edrivers/pci/iov.c
!Idrivers/pci/pci-sysfs.c
</sect1>
<sect1><title>PCI Hotplug Support Library</title>
!Edrivers/pci/hotplug/pci_hotplug_core.c
......
Documentation/block/biodoc.txt
浏览文件 @ e7fd5d4b
......@@ -1040,23 +1040,21 @@ Front merges are handled by the binary trees in AS and deadline schedulers.
iii. Plugging the queue to batch requests in anticipation of opportunities for
merge/sort optimizations
This is just the same as in 2.4 so far, though per-device unplugging
support is anticipated for 2.5. Also with a priority-based i/o scheduler,
such decisions could be based on request priorities.
Plugging is an approach that the current i/o scheduling algorithm resorts to so
that it collects up enough requests in the queue to be able to take
advantage of the sorting/merging logic in the elevator. If the
queue is empty when a request comes in, then it plugs the request queue
(sort of like plugging the bottom of a vessel to get fluid to build up)
(sort of like plugging the bath tub of a vessel to get fluid to build up)
till it fills up with a few more requests, before starting to service
the requests. This provides an opportunity to merge/sort the requests before
passing them down to the device. There are various conditions when the queue is
unplugged (to open up the flow again), either through a scheduled task or
could be on demand. For example wait_on_buffer sets the unplugging going
(by running tq_disk) so the read gets satisfied soon. So in the read case,
the queue gets explicitly unplugged as part of waiting for completion,
in fact all queues get unplugged as a side-effect.
through sync_buffer() running blk_run_address_space(mapping). Or the caller
can do it explicity through blk_unplug(bdev). So in the read case,
the queue gets explicitly unplugged as part of waiting for completion on that
buffer. For page driven IO, the address space ->sync_page() takes care of
doing the blk_run_address_space().
Aside:
This is kind of controversial territory, as it's not clear if plugging is
......@@ -1067,11 +1065,6 @@ Aside:
multi-page bios being queued in one shot, we may not need to wait to merge
a big request from the broken up pieces coming by.
Per-queue granularity unplugging (still a Todo) may help reduce some of the
concerns with just a single tq_disk flush approach. Something like
blk_kick_queue() to unplug a specific queue (right away ?)
or optionally, all queues, is in the plan.
4.4 I/O contexts
I/O contexts provide a dynamically allocated per process data area. They may
be used in I/O schedulers, and in the block layer (could be used for IO statis,
......
Documentation/cgroups/cpuacct.txt
浏览文件 @ e7fd5d4b
......@@ -30,3 +30,21 @@ The above steps create a new group g1 and move the current shell
process (bash) into it. CPU time consumed by this bash and its children
can be obtained from g1/cpuacct.usage and the same is accumulated in
/cgroups/cpuacct.usage also.
cpuacct.stat file lists a few statistics which further divide the
CPU time obtained by the cgroup into user and system times. Currently
the following statistics are supported:
user: Time spent by tasks of the cgroup in user mode.
system: Time spent by tasks of the cgroup in kernel mode.
user and system are in USER_HZ unit.
cpuacct controller uses percpu_counter interface to collect user and
system times. This has two side effects:
- It is theoretically possible to see wrong values for user and system times.
This is because percpu_counter_read() on 32bit systems isn't safe
against concurrent writes.
- It is possible to see slightly outdated values for user and system times
due to the batch processing nature of percpu_counter.
Documentation/cgroups/memory.txt
浏览文件 @ e7fd5d4b
......@@ -6,15 +6,14 @@ used here with the memory controller that is used in hardware.
Salient features
a. Enable control of both RSS (mapped) and Page Cache (unmapped) pages
a. Enable control of Anonymous, Page Cache (mapped and unmapped) and
Swap Cache memory pages.
b. The infrastructure allows easy addition of other types of memory to control
c. Provides *zero overhead* for non memory controller users
d. Provides a double LRU: global memory pressure causes reclaim from the
global LRU; a cgroup on hitting a limit, reclaims from the per
cgroup LRU
NOTE: Swap Cache (unmapped) is not accounted now.
Benefits and Purpose of the memory controller
The memory controller isolates the memory behaviour of a group of tasks
......@@ -290,34 +289,44 @@ will be charged as a new owner of it.
moved to the parent. If you want to avoid that, force_empty will be useful.
5.2 stat file
memory.stat file includes following statistics (now)
cache - # of pages from page-cache and shmem.
rss - # of pages from anonymous memory.
pgpgin - # of event of charging
pgpgout - # of event of uncharging
active_anon - # of pages on active lru of anon, shmem.
inactive_anon - # of pages on active lru of anon, shmem
active_file - # of pages on active lru of file-cache
inactive_file - # of pages on inactive lru of file cache
unevictable - # of pages cannot be reclaimed.(mlocked etc)
Below is depend on CONFIG_DEBUG_VM.
inactive_ratio - VM internal parameter. (see mm/page_alloc.c)
recent_rotated_anon - VM internal parameter. (see mm/vmscan.c)
recent_rotated_file - VM internal parameter. (see mm/vmscan.c)
recent_scanned_anon - VM internal parameter. (see mm/vmscan.c)
recent_scanned_file - VM internal parameter. (see mm/vmscan.c)
Memo:
memory.stat file includes following statistics
cache - # of bytes of page cache memory.
rss - # of bytes of anonymous and swap cache memory.
pgpgin - # of pages paged in (equivalent to # of charging events).
pgpgout - # of pages paged out (equivalent to # of uncharging events).
active_anon - # of bytes of anonymous and swap cache memory on active
lru list.
inactive_anon - # of bytes of anonymous memory and swap cache memory on
inactive lru list.
active_file - # of bytes of file-backed memory on active lru list.
inactive_file - # of bytes of file-backed memory on inactive lru list.
unevictable - # of bytes of memory that cannot be reclaimed (mlocked etc).
The following additional stats are dependent on CONFIG_DEBUG_VM.
inactive_ratio - VM internal parameter. (see mm/page_alloc.c)
recent_rotated_anon - VM internal parameter. (see mm/vmscan.c)
recent_rotated_file - VM internal parameter. (see mm/vmscan.c)
recent_scanned_anon - VM internal parameter. (see mm/vmscan.c)
recent_scanned_file - VM internal parameter. (see mm/vmscan.c)
Memo:
recent_rotated means recent frequency of lru rotation.
recent_scanned means recent # of scans to lru.
showing for better debug please see the code for meanings.
Note:
Only anonymous and swap cache memory is listed as part of 'rss' stat.
This should not be confused with the true 'resident set size' or the
amount of physical memory used by the cgroup. Per-cgroup rss
accounting is not done yet.
5.3 swappiness
Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.
Following cgroup's swapiness can't be changed.
Following cgroups' swapiness can't be changed.
- root cgroup (uses /proc/sys/vm/swappiness).
- a cgroup which uses hierarchy and it has child cgroup.
- a cgroup which uses hierarchy and not the root of hierarchy.
......
Documentation/cgroups/resource_counter.txt
浏览文件 @ e7fd5d4b
......@@ -47,13 +47,18 @@ to work with it.
2. Basic accounting routines
a. void res_counter_init(struct res_counter *rc)
a. void res_counter_init(struct res_counter *rc,
struct res_counter *rc_parent)
Initializes the resource counter. As usual, should be the first
routine called for a new counter.
b. int res_counter_charge[_locked]
(struct res_counter *rc, unsigned long val)
The struct res_counter *parent can be used to define a hierarchical
child -> parent relationship directly in the res_counter structure,
NULL can be used to define no relationship.
c. int res_counter_charge(struct res_counter *rc, unsigned long val,
struct res_counter **limit_fail_at)
When a resource is about to be allocated it has to be accounted
with the appropriate resource counter (controller should determine
......@@ -67,15 +72,25 @@ to work with it.
* if the charging is performed first, then it should be uncharged
on error path (if the one is called).
c. void res_counter_uncharge[_locked]
If the charging fails and a hierarchical dependency exists, the
limit_fail_at parameter is set to the particular res_counter element
where the charging failed.
d. int res_counter_charge_locked
(struct res_counter *rc, unsigned long val)
The same as res_counter_charge(), but it must not acquire/release the
res_counter->lock internally (it must be called with res_counter->lock
held).
e. void res_counter_uncharge[_locked]
(struct res_counter *rc, unsigned long val)
When a resource is released (freed) it should be de-accounted
from the resource counter it was accounted to. This is called
"uncharging".
The _locked routines imply that the res_counter->lock is taken.
The _locked routines imply that the res_counter->lock is taken.
2.1 Other accounting routines
......
Documentation/driver-model/platform.txt
浏览文件 @ e7fd5d4b
......@@ -169,3 +169,62 @@ three different ways to find such a match:
be probed later if another device registers. (Which is OK, since
this interface is only for use with non-hotpluggable devices.)
Early Platform Devices and Drivers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The early platform interfaces provide platform data to platform device
drivers early on during the system boot. The code is built on top of the
early_param() command line parsing and can be executed very early on.
Example: "earlyprintk" class early serial console in 6 steps
1. Registering early platform device data
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The architecture code registers platform device data using the function
early_platform_add_devices(). In the case of early serial console this
should be hardware configuration for the serial port. Devices registered
at this point will later on be matched against early platform drivers.
2. Parsing kernel command line
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The architecture code calls parse_early_param() to parse the kernel
command line. This will execute all matching early_param() callbacks.
User specified early platform devices will be registered at this point.
For the early serial console case the user can specify port on the
kernel command line as "earlyprintk=serial.0" where "earlyprintk" is
the class string, "serial" is the name of the platfrom driver and
0 is the platform device id. If the id is -1 then the dot and the
id can be omitted.
3. Installing early platform drivers belonging to a certain class
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The architecture code may optionally force registration of all early
platform drivers belonging to a certain class using the function
early_platform_driver_register_all(). User specified devices from
step 2 have priority over these. This step is omitted by the serial
driver example since the early serial driver code should be disabled
unless the user has specified port on the kernel command line.
4. Early platform driver registration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compiled-in platform drivers making use of early_platform_init() are
automatically registered during step 2 or 3. The serial driver example
should use early_platform_init("earlyprintk", &platform_driver).
5. Probing of early platform drivers belonging to a certain class
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The architecture code calls early_platform_driver_probe() to match
registered early platform devices associated with a certain class with
registered early platform drivers. Matched devices will get probed().
This step can be executed at any point during the early boot. As soon
as possible may be good for the serial port case.
6. Inside the early platform driver probe()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The driver code needs to take special care during early boot, especially
when it comes to memory allocation and interrupt registration. The code
in the probe() function can use is_early_platform_device() to check if
it is called at early platform device or at the regular platform device
time. The early serial driver performs register_console() at this point.
For further information, see <linux/platform_device.h>.
Documentation/feature-removal-schedule.txt
浏览文件 @ e7fd5d4b
......@@ -428,3 +428,12 @@ Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to
After a reasonable transition period, we will remove the legacy
fakephp interface.
Who: Alex Chiang <achiang@hp.com>
---------------------------
What: i2c-voodoo3 driver
When: October 2009
Why: Superseded by tdfxfb. I2C/DDC support used to live in a separate
driver but this caused driver conflicts.
Who: Jean Delvare <khali@linux-fr.org>
Krzysztof Helt <krzysztof.h1@wp.pl>
Documentation/filesystems/caching/cachefiles.txt
浏览文件 @ e7fd5d4b
......@@ -407,7 +407,7 @@ A NOTE ON SECURITY
==================
CacheFiles makes use of the split security in the task_struct. It allocates
its own task_security structure, and redirects current->act_as to point to it
its own task_security structure, and redirects current->cred to point to it
when it acts on behalf of another process, in that process's context.
The reason it does this is that it calls vfs_mkdir() and suchlike rather than
......@@ -429,9 +429,9 @@ This means it may lose signals or ptrace events for example, and affects what
the process looks like in /proc.
So CacheFiles makes use of a logical split in the security between the
objective security (task->sec) and the subjective security (task->act_as). The
objective security holds the intrinsic security properties of a process and is
never overridden. This is what appears in /proc, and is what is used when a
objective security (task->real_cred) and the subjective security (task->cred).
The objective security holds the intrinsic security properties of a process and
is never overridden. This is what appears in /proc, and is what is used when a
process is the target of an operation by some other process (SIGKILL for
example).
......
Documentation/filesystems/pohmelfs/design_notes.txt
浏览文件 @ e7fd5d4b
......@@ -56,9 +56,10 @@ workloads and can fully utilize the bandwidth to the servers when doing bulk
data transfers.
POHMELFS clients operate with a working set of servers and are capable of balancing read-only
operations (like lookups or directory listings) between them.
operations (like lookups or directory listings) between them according to IO priorities.
Administrators can add or remove servers from the set at run-time via special commands (described
in Documentation/pohmelfs/info.txt file). Writes are replicated to all servers.
in Documentation/pohmelfs/info.txt file). Writes are replicated to all servers, which are connected
with write permission turned on. IO priority and permissions can be changed in run-time.
POHMELFS is capable of full data channel encryption and/or strong crypto hashing.
One can select any kernel supported cipher, encryption mode, hash type and operation mode
......
Documentation/filesystems/pohmelfs/info.txt
浏览文件 @ e7fd5d4b
POHMELFS usage information.
Mount options:
Mount options.
All but index, number of crypto threads and maximum IO size can changed via remount.
idx=%u
Each mountpoint is associated with a special index via this option.
Administrator can add or remove servers from the given index, so all mounts,
......@@ -52,16 +54,27 @@ mcache_timeout=%u
Usage examples.
Add (or remove if it already exists) server server1.net:1025 into the working set with index $idx
Add server server1.net:1025 into the working set with index $idx
with appropriate hash algorithm and key file and cipher algorithm, mode and key file:
$cfg -a server1.net -p 1025 -i $idx -K $hash_key -k $cipher_key
$cfg A add -a server1.net -p 1025 -i $idx -K $hash_key -k $cipher_key
Mount filesystem with given index $idx to /mnt mountpoint.
Client will connect to all servers specified in the working set via previous command:
mount -t pohmel -o idx=$idx q /mnt
One can add or remove servers from working set after mounting too.
Change permissions to read-only (-I 1 option, '-I 2' - write-only, 3 - rw):
$cfg A modify -a server1.net -p 1025 -i $idx -I 1
Change IO priority to 123 (node with the highest priority gets read requests).
$cfg A modify -a server1.net -p 1025 -i $idx -P 123
One can check currect status of all connections in the mountstats file:
# cat /proc/$PID/mountstats
...
device none mounted on /mnt with fstype pohmel
idx addr(:port) socket_type protocol active priority permissions
0 server1.net:1026 1 6 1 250 1
0 server2.net:1025 1 6 1 123 3
Server installation.
......
Documentation/filesystems/vfs.txt
浏览文件 @ e7fd5d4b
......@@ -277,8 +277,7 @@ or bottom half).
unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
again.
statfs: called when the VFS needs to get filesystem statistics. This
is called with the kernel lock held
statfs: called when the VFS needs to get filesystem statistics.
remount_fs: called when the filesystem is remounted. This is called
with the kernel lock held
......
Documentation/infiniband/ipoib.txt
浏览文件 @ e7fd5d4b
......@@ -24,6 +24,49 @@ Partitions and P_Keys
The P_Key for any interface is given by the "pkey" file, and the
main interface for a subinterface is in "parent."
Datagram vs Connected modes
The IPoIB driver supports two modes of operation: datagram and
connected. The mode is set and read through an interface's
/sys/class/net/<intf name>/mode file.
In datagram mode, the IB UD (Unreliable Datagram) transport is used
and so the interface MTU has is equal to the IB L2 MTU minus the
IPoIB encapsulation header (4 bytes). For example, in a typical IB
fabric with a 2K MTU, the IPoIB MTU will be 2048 - 4 = 2044 bytes.
In connected mode, the IB RC (Reliable Connected) transport is used.
Connected mode is to takes advantage of the connected nature of the
IB transport and allows an MTU up to the maximal IP packet size of
64K, which reduces the number of IP packets needed for handling
large UDP datagrams, TCP segments, etc and increases the performance
for large messages.
In connected mode, the interface's UD QP is still used for multicast
and communication with peers that don't support connected mode. In
this case, RX emulation of ICMP PMTU packets is used to cause the
networking stack to use the smaller UD MTU for these neighbours.
Stateless offloads
If the IB HW supports IPoIB stateless offloads, IPoIB advertises
TCP/IP checksum and/or Large Send (LSO) offloading capability to the
network stack.
Large Receive (LRO) offloading is also implemented and may be turned
on/off using ethtool calls. Currently LRO is supported only for
checksum offload capable devices.
Stateless offloads are supported only in datagram mode.
Interrupt moderation
If the underlying IB device supports CQ event moderation, one can
use ethtool to set interrupt mitigation parameters and thus reduce
the overhead incurred by handling interrupts. The main code path of
IPoIB doesn't use events for TX completion signaling so only RX
moderation is supported.
Debugging Information
By compiling the IPoIB driver with CONFIG_INFINIBAND_IPOIB_DEBUG set
......@@ -55,3 +98,5 @@ References
http://ietf.org/rfc/rfc4391.txt
IP over InfiniBand (IPoIB) Architecture (RFC 4392)
http://ietf.org/rfc/rfc4392.txt
IP over InfiniBand: Connected Mode (RFC 4755)
http://ietf.org/rfc/rfc4755.txt
Documentation/input/rotary-encoder.txt 0 → 100644
浏览文件 @ e7fd5d4b
rotary-encoder - a generic driver for GPIO connected devices
Daniel Mack <daniel@caiaq.de>, Feb 2009
0. Function
-----------
Rotary encoders are devices which are connected to the CPU or other
peripherals with two wires. The outputs are phase-shifted by 90 degrees
and by triggering on falling and rising edges, the turn direction can
be determined.
The phase diagram of these two outputs look like this:
_____ _____ _____
| | | | | |
Channel A ____| |_____| |_____| |____
: : : : : : : : : : : :
__ _____ _____ _____
| | | | | | |
Channel B |_____| |_____| |_____| |__
: : : : : : : : : : : :
Event a b c d a b c d a b c d
|<-------->|
one step
For more information, please see
http://en.wikipedia.org/wiki/Rotary_encoder
1. Events / state machine
-------------------------
a) Rising edge on channel A, channel B in low state
This state is used to recognize a clockwise turn
b) Rising edge on channel B, channel A in high state
When entering this state, the encoder is put into 'armed' state,
meaning that there it has seen half the way of a one-step transition.
c) Falling edge on channel A, channel B in high state
This state is used to recognize a counter-clockwise turn
d) Falling edge on channel B, channel A in low state
Parking position. If the encoder enters this state, a full transition
should have happend, unless it flipped back on half the way. The
'armed' state tells us about that.
2. Platform requirements
------------------------
As there is no hardware dependent call in this driver, the platform it is
used with must support gpiolib. Another requirement is that IRQs must be
able to fire on both edges.
3. Board integration
--------------------
To use this driver in your system, register a platform_device with the
name 'rotary-encoder' and associate the IRQs and some specific platform
data with it.
struct rotary_encoder_platform_data is declared in
include/linux/rotary-encoder.h and needs to be filled with the number of
steps the encoder has and can carry information about externally inverted
signals (because of used invertig buffer or other reasons).
Because GPIO to IRQ mapping is platform specific, this information must
be given in seperately to the driver. See the example below.
---------<snip>---------
/* board support file example */
#include <linux/input.h>
#include <linux/rotary_encoder.h>
#define GPIO_ROTARY_A 1
#define GPIO_ROTARY_B 2
static struct rotary_encoder_platform_data my_rotary_encoder_info = {
.steps = 24,
.axis = ABS_X,
.gpio_a = GPIO_ROTARY_A,
.gpio_b = GPIO_ROTARY_B,
.inverted_a = 0,
.inverted_b = 0,
};
static struct platform_device rotary_encoder_device = {
.name = "rotary-encoder",
.id = 0,
.dev = {
.platform_data = &my_rotary_encoder_info,
}
};
Documentation/kbuild/makefiles.txt
浏览文件 @ e7fd5d4b
......@@ -40,10 +40,16 @@ This document describes the Linux kernel Makefiles.
--- 6.7 Custom kbuild commands
--- 6.8 Preprocessing linker scripts
=== 7 Kbuild Variables
=== 8 Makefile language
=== 9 Credits
=== 10 TODO
=== 7 Kbuild syntax for exported headers
--- 7.1 header-y
--- 7.2 objhdr-y
--- 7.3 destination-y
--- 7.4 unifdef-y (deprecated)
=== 8 Kbuild Variables
=== 9 Makefile language
=== 10 Credits
=== 11 TODO
=== 1 Overview
......@@ -310,6 +316,16 @@ more details, with real examples.
#arch/m68k/fpsp040/Makefile
ldflags-y := -x
subdir-ccflags-y, subdir-asflags-y
The two flags listed above are similar to ccflags-y and as-falgs-y.
The difference is that the subdir- variants has effect for the kbuild
file where tey are present and all subdirectories.
Options specified using subdir-* are added to the commandline before
the options specified using the non-subdir variants.
Example:
subdir-ccflags-y := -Werror
CFLAGS_$@, AFLAGS_$@
CFLAGS_$@ and AFLAGS_$@ only apply to commands in current
......@@ -1143,8 +1159,69 @@ When kbuild executes, the following steps are followed (roughly):
The kbuild infrastructure for *lds file are used in several
architecture-specific files.
=== 7 Kbuild syntax for exported headers
The kernel include a set of headers that is exported to userspace.
Many headers can be exported as-is but other headers requires a
minimal pre-processing before they are ready for user-space.
The pre-processing does:
- drop kernel specific annotations
- drop include of compiler.h
- drop all sections that is kernel internat (guarded by ifdef __KERNEL__)
Each relevant directory contain a file name "Kbuild" which specify the
headers to be exported.
See subsequent chapter for the syntax of the Kbuild file.
--- 7.1 header-y
header-y specify header files to be exported.
Example:
#include/linux/Kbuild
header-y += usb/
header-y += aio_abi.h
The convention is to list one file per line and
preferably in alphabetic order.
header-y also specify which subdirectories to visit.
A subdirectory is identified by a trailing '/' which
can be seen in the example above for the usb subdirectory.
Subdirectories are visited before their parent directories.
--- 7.2 objhdr-y
objhdr-y specifies generated files to be exported.
Generated files are special as they need to be looked
up in another directory when doing 'make O=...' builds.
Example:
#include/linux/Kbuild
objhdr-y += version.h
--- 7.3 destination-y
When an architecture have a set of exported headers that needs to be
exported to a different directory destination-y is used.
destination-y specify the destination directory for all exported
headers in the file where it is present.
Example:
#arch/xtensa/platforms/s6105/include/platform/Kbuild
destination-y := include/linux
In the example above all exported headers in the Kbuild file
will be located in the directory "include/linux" when exported.
--- 7.4 unifdef-y (deprecated)
unifdef-y is deprecated. A direct replacement is header-y.
=== 7 Kbuild Variables
=== 8 Kbuild Variables
The top Makefile exports the following variables:
......@@ -1206,7 +1283,7 @@ The top Makefile exports the following variables:
INSTALL_MOD_STRIP will used as the option(s) to the strip command.
=== 8 Makefile language
=== 9 Makefile language
The kernel Makefiles are designed to be run with GNU Make. The Makefiles
use only the documented features of GNU Make, but they do use many
......@@ -1225,14 +1302,14 @@ time the left-hand side is used.
There are some cases where "=" is appropriate. Usually, though, ":="
is the right choice.
=== 9 Credits
=== 10 Credits
Original version made by Michael Elizabeth Chastain, <mailto:mec@shout.net>
Updates by Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Updates by Sam Ravnborg <sam@ravnborg.org>
Language QA by Jan Engelhardt <jengelh@gmx.de>
=== 10 TODO
=== 11 TODO
- Describe how kbuild supports shipped files with _shipped.
- Generating offset header files.
......
Documentation/kernel-parameters.txt
浏览文件 @ e7fd5d4b
......@@ -134,7 +134,7 @@ and is between 256 and 4096 characters. It is defined in the file
./include/asm/setup.h as COMMAND_LINE_SIZE.
acpi= [HW,ACPI,X86-64,i386]
acpi= [HW,ACPI,X86]
Advanced Configuration and Power Interface
Format: { force | off | ht | strict | noirq | rsdt }
force -- enable ACPI if default was off
......@@ -218,7 +218,7 @@ and is between 256 and 4096 characters. It is defined in the file
acpi_osi="!string2" # remove built-in string2
acpi_osi= # disable all strings
acpi_pm_good [X86-32,X86-64]
acpi_pm_good [X86]
Override the pmtimer bug detection: force the kernel
to assume that this machine's pmtimer latches its value
and always returns good values.
......@@ -231,6 +231,35 @@ and is between 256 and 4096 characters. It is defined in the file
power state again in power transition.
1 : disable the power state check
acpi_sci= [HW,ACPI] ACPI System Control Interrupt trigger mode
Format: { level | edge | high | low }
acpi_serialize [HW,ACPI] force serialization of AML methods
acpi_skip_timer_override [HW,ACPI]
Recognize and ignore IRQ0/pin2 Interrupt Override.
For broken nForce2 BIOS resulting in XT-PIC timer.
acpi_sleep= [HW,ACPI] Sleep options
Format: { s3_bios, s3_mode, s3_beep, s4_nohwsig,
old_ordering, s4_nonvs }
See Documentation/power/video.txt for information on
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, with respect to putting devices into
low power states, to be enforced (the ACPI 2.0 ordering
of _PTS is used by default).
s4_nonvs prevents the kernel from saving/restoring the
ACPI NVS memory during hibernation.
acpi_use_timer_override [HW,ACPI]
Use timer override. For some broken Nvidia NF5 boards
that require a timer override, but don't have HPET
acpi_enforce_resources= [ACPI]
{ strict | lax | no }
Check for resource conflicts between native drivers
......@@ -250,6 +279,9 @@ and is between 256 and 4096 characters. It is defined in the file
ad1848= [HW,OSS]
Format: <io>,<irq>,<dma>,<dma2>,<type>
add_efi_memmap [EFI; X86] Include EFI memory map in
kernel's map of available physical RAM.
advansys= [HW,SCSI]
See header of drivers/scsi/advansys.c.
......@@ -459,7 +491,7 @@ and is between 256 and 4096 characters. It is defined in the file
Also note the kernel might malfunction if you disable
some critical bits.
code_bytes [IA32/X86_64] How many bytes of object code to print
code_bytes [X86] How many bytes of object code to print
in an oops report.
Range: 0 - 8192
Default: 64
......@@ -592,7 +624,7 @@ and is between 256 and 4096 characters. It is defined in the file
MTRR settings. This parameter disables that behavior,
possibly causing your machine to run very slowly.
disable_timer_pin_1 [i386,x86-64]
disable_timer_pin_1 [X86]
Disable PIN 1 of APIC timer
Can be useful to work around chipset bugs.
......@@ -624,7 +656,7 @@ and is between 256 and 4096 characters. It is defined in the file
UART at the specified I/O port or MMIO address.
The options are the same as for ttyS, above.
earlyprintk= [X86-32,X86-64,SH,BLACKFIN]
earlyprintk= [X86,SH,BLACKFIN]
earlyprintk=vga
earlyprintk=serial[,ttySn[,baudrate]]
earlyprintk=dbgp
......@@ -659,7 +691,7 @@ and is between 256 and 4096 characters. It is defined in the file
See Documentation/block/as-iosched.txt and
Documentation/block/deadline-iosched.txt for details.
elfcorehdr= [IA64,PPC,SH,X86-32,X86_64]
elfcorehdr= [IA64,PPC,SH,X86]
Specifies physical address of start of kernel core
image elf header. Generally kexec loader will
pass this option to capture kernel.
......@@ -938,7 +970,7 @@ and is between 256 and 4096 characters. It is defined in the file
See comment before marvel_specify_io7 in
arch/alpha/kernel/core_marvel.c.
io_delay= [X86-32,X86-64] I/O delay method
io_delay= [X86] I/O delay method
0x80
Standard port 0x80 based delay
0xed
......@@ -1000,7 +1032,7 @@ and is between 256 and 4096 characters. It is defined in the file
keepinitrd [HW,ARM]
kernelcore=nn[KMG] [KNL,X86-32,IA-64,PPC,X86-64] This parameter
kernelcore=nn[KMG] [KNL,X86,IA-64,PPC] This parameter
specifies the amount of memory usable by the kernel
for non-movable allocations. The requested amount is
spread evenly throughout all nodes in the system. The
......@@ -1034,7 +1066,7 @@ and is between 256 and 4096 characters. It is defined in the file
Configure the RouterBoard 532 series on-chip
Ethernet adapter MAC address.
kstack=N [X86-32,X86-64] Print N words from the kernel stack
kstack=N [X86] Print N words from the kernel stack
in oops dumps.
l2cr= [PPC]
......@@ -1044,7 +1076,7 @@ and is between 256 and 4096 characters. It is defined in the file
lapic [X86-32,APIC] Enable the local APIC even if BIOS
disabled it.
lapic_timer_c2_ok [X86-32,x86-64,APIC] trust the local apic timer
lapic_timer_c2_ok [X86,APIC] trust the local apic timer
in C2 power state.
libata.dma= [LIBATA] DMA control
......@@ -1229,7 +1261,7 @@ and is between 256 and 4096 characters. It is defined in the file
[KNL,SH] Allow user to override the default size for
per-device physically contiguous DMA buffers.
memmap=exactmap [KNL,X86-32,X86_64] Enable setting of an exact
memmap=exactmap [KNL,X86] Enable setting of an exact
E820 memory map, as specified by the user.
Such memmap=exactmap lines can be constructed based on
BIOS output or other requirements. See the memmap=nn@ss
......@@ -1320,7 +1352,7 @@ and is between 256 and 4096 characters. It is defined in the file
mousedev.yres= [MOUSE] Vertical screen resolution, used for devices
reporting absolute coordinates, such as tablets
movablecore=nn[KMG] [KNL,X86-32,IA-64,PPC,X86-64] This parameter
movablecore=nn[KMG] [KNL,X86,IA-64,PPC] This parameter
is similar to kernelcore except it specifies the
amount of memory used for migratable allocations.
If both kernelcore and movablecore is specified,
......@@ -1422,7 +1454,7 @@ and is between 256 and 4096 characters. It is defined in the file
when a NMI is triggered.
Format: [state][,regs][,debounce][,die]
nmi_watchdog= [KNL,BUGS=X86-32,X86-64] Debugging features for SMP kernels
nmi_watchdog= [KNL,BUGS=X86] Debugging features for SMP kernels
Format: [panic,][num]
Valid num: 0,1,2
0 - turn nmi_watchdog off
......@@ -1475,11 +1507,11 @@ and is between 256 and 4096 characters. It is defined in the file
nodsp [SH] Disable hardware DSP at boot time.
noefi [X86-32,X86-64] Disable EFI runtime services support.
noefi [X86] Disable EFI runtime services support.
noexec [IA-64]
noexec [X86-32,X86-64]
noexec [X86]
On X86-32 available only on PAE configured kernels.
noexec=on: enable non-executable mappings (default)
noexec=off: disable non-executable mappings
......@@ -1525,7 +1557,7 @@ and is between 256 and 4096 characters. It is defined in the file
noirqdebug [X86-32] Disables the code which attempts to detect and
disable unhandled interrupt sources.
no_timer_check [X86-32,X86_64,APIC] Disables the code which tests for
no_timer_check [X86,APIC] Disables the code which tests for
broken timer IRQ sources.
noisapnp [ISAPNP] Disables ISA PnP code.
......@@ -1588,6 +1620,8 @@ and is between 256 and 4096 characters. It is defined in the file
nowb [ARM]
nox2apic [X86-64,APIC] Do not enable x2APIC mode.
nptcg= [IA64] Override max number of concurrent global TLB
purges which is reported from either PAL_VM_SUMMARY or
SAL PALO.
......@@ -1689,7 +1723,7 @@ and is between 256 and 4096 characters. It is defined in the file
disable the use of PCIE advanced error reporting.
nodomains [PCI] Disable support for multiple PCI
root domains (aka PCI segments, in ACPI-speak).
nommconf [X86-32,X86_64] Disable use of MMCONFIG for PCI
nommconf [X86] Disable use of MMCONFIG for PCI
Configuration
nomsi [MSI] If the PCI_MSI kernel config parameter is
enabled, this kernel boot option can be used to
......@@ -1838,6 +1872,12 @@ and is between 256 and 4096 characters. It is defined in the file
autoconfiguration.
Ranges are in pairs (memory base and size).
ports= [IP_VS_FTP] IPVS ftp helper module
Default is 21.
Up to 8 (IP_VS_APP_MAX_PORTS) ports
may be specified.
Format: <port>,<port>....
print-fatal-signals=
[KNL] debug: print fatal signals
print-fatal-signals=1: print segfault info to
......@@ -2380,7 +2420,7 @@ and is between 256 and 4096 characters. It is defined in the file
reported either.
unknown_nmi_panic
[X86-32,X86-64]
[X86]
Set unknown_nmi_panic=1 early on boot.
usbcore.autosuspend=
......@@ -2447,12 +2487,12 @@ and is between 256 and 4096 characters. It is defined in the file
medium is write-protected).
Example: quirks=0419:aaf5:rl,0421:0433:rc
vdso= [X86-32,SH,x86-64]
vdso= [X86,SH]
vdso=2: enable compat VDSO (default with COMPAT_VDSO)
vdso=1: enable VDSO (default)
vdso=0: disable VDSO mapping
vdso32= [X86-32,X86-64]
vdso32= [X86]
vdso32=2: enable compat VDSO (default with COMPAT_VDSO)
vdso32=1: enable 32-bit VDSO (default)
vdso32=0: disable 32-bit VDSO mapping
......
Documentation/laptops/thinkpad-acpi.txt
浏览文件 @ e7fd5d4b
ThinkPad ACPI Extras Driver
Version 0.22
November 23rd, 2008
Version 0.23
April 10th, 2009
Borislav Deianov <borislav@users.sf.net>
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
......
Documentation/lguest/lguest.txt
浏览文件 @ e7fd5d4b
......@@ -3,11 +3,11 @@
/, /` - or, A Young Coder's Illustrated Hypervisor
\\"--\\ http://lguest.ozlabs.org
Lguest is designed to be a minimal hypervisor for the Linux kernel, for
Linux developers and users to experiment with virtualization with the
minimum of complexity. Nonetheless, it should have sufficient
features to make it useful for specific tasks, and, of course, you are
encouraged to fork and enhance it (see drivers/lguest/README).
Lguest is designed to be a minimal 32-bit x86 hypervisor for the Linux kernel,
for Linux developers and users to experiment with virtualization with the
minimum of complexity. Nonetheless, it should have sufficient features to
make it useful for specific tasks, and, of course, you are encouraged to fork
and enhance it (see drivers/lguest/README).
Features:
......@@ -37,6 +37,7 @@ Running Lguest:
"Paravirtualized guest support" = Y
"Lguest guest support" = Y
"High Memory Support" = off/4GB
"PAE (Physical Address Extension) Support" = N
"Alignment value to which kernel should be aligned" = 0x100000
(CONFIG_PARAVIRT=y, CONFIG_LGUEST_GUEST=y, CONFIG_HIGHMEM64G=n and
CONFIG_PHYSICAL_ALIGN=0x100000)
......
Documentation/logo.svg 已删除 100644 → 0
浏览文件 @ 1130b029
因为 它太大了无法显示 source diff 。你可以改为 查看blob。
Documentation/logo.txt
浏览文件 @ e7fd5d4b
Tux is taking a three month sabbatical to work as a barber, so Tuz is
standing in. He's taken pains to ensure you'll hardly notice.
This is the full-colour version of the currently unofficial Linux logo
("currently unofficial" just means that there has been no paperwork and
that I have not really announced it yet). It was created by Larry Ewing,
and is freely usable as long as you acknowledge Larry as the original
artist.
Note that there are black-and-white versions of this available that
scale down to smaller sizes and are better for letterheads or whatever
you want to use it for: for the full range of logos take a look at
Larry's web-page:
http://www.isc.tamu.edu/~lewing/linux/
Image by Andrew McGown and Josh Bush. Image is licensed CC BY-SA.
Documentation/networking/bonding.txt
浏览文件 @ e7fd5d4b
......@@ -1242,7 +1242,7 @@ monitoring is enabled, and vice-versa.
To add ARP targets:
# echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
# echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
NOTE: up to 10 target addresses may be specified.
NOTE: up to 16 target addresses may be specified.
To remove an ARP target:
# echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
......
Documentation/powerpc/booting-without-of.txt
浏览文件 @ e7fd5d4b
......@@ -43,12 +43,11 @@ Table of Contents
2) Representing devices without a current OF specification
a) PHY nodes
b) Interrupt controllers
c) CFI or JEDEC memory-mapped NOR flash
d) 4xx/Axon EMAC ethernet nodes
e) Xilinx IP cores
f) USB EHCI controllers
g) MDIO on GPIOs
h) SPI busses
c) 4xx/Axon EMAC ethernet nodes
d) Xilinx IP cores
e) USB EHCI controllers
f) MDIO on GPIOs
g) SPI busses
VII - Marvell Discovery mv64[345]6x System Controller chips
1) The /system-controller node
......@@ -999,7 +998,7 @@ compatibility.
translation of SOC addresses for memory mapped SOC registers.
- bus-frequency: Contains the bus frequency for the SOC node.
Typically, the value of this field is filled in by the boot
loader.
loader.
Recommended properties:
......@@ -1287,71 +1286,7 @@ platforms are moved over to use the flattened-device-tree model.
device_type = "open-pic";
};
c) CFI or JEDEC memory-mapped NOR flash
Flash chips (Memory Technology Devices) are often used for solid state
file systems on embedded devices.
- compatible : should contain the specific model of flash chip(s)
used, if known, followed by either "cfi-flash" or "jedec-flash"
- reg : Address range of the flash chip
- bank-width : Width (in bytes) of the flash bank. Equal to the
device width times the number of interleaved chips.
- device-width : (optional) Width of a single flash chip. If
omitted, assumed to be equal to 'bank-width'.
- #address-cells, #size-cells : Must be present if the flash has
sub-nodes representing partitions (see below). In this case
both #address-cells and #size-cells must be equal to 1.
For JEDEC compatible devices, the following additional properties
are defined:
- vendor-id : Contains the flash chip's vendor id (1 byte).
- device-id : Contains the flash chip's device id (1 byte).
In addition to the information on the flash bank itself, the
device tree may optionally contain additional information
describing partitions of the flash address space. This can be
used on platforms which have strong conventions about which
portions of the flash are used for what purposes, but which don't
use an on-flash partition table such as RedBoot.
Each partition is represented as a sub-node of the flash device.
Each node's name represents the name of the corresponding
partition of the flash device.
Flash partitions
- reg : The partition's offset and size within the flash bank.
- label : (optional) The label / name for this flash partition.
If omitted, the label is taken from the node name (excluding
the unit address).
- read-only : (optional) This parameter, if present, is a hint to
Linux that this flash partition should only be mounted
read-only. This is usually used for flash partitions
containing early-boot firmware images or data which should not
be clobbered.
Example:
flash@ff000000 {
compatible = "amd,am29lv128ml", "cfi-flash";
reg = <ff000000 01000000>;
bank-width = <4>;
device-width = <1>;
#address-cells = <1>;
#size-cells = <1>;
fs@0 {
label = "fs";
reg = <0 f80000>;
};
firmware@f80000 {
label ="firmware";
reg = <f80000 80000>;
read-only;
};
};
d) 4xx/Axon EMAC ethernet nodes
c) 4xx/Axon EMAC ethernet nodes
The EMAC ethernet controller in IBM and AMCC 4xx chips, and also
the Axon bridge. To operate this needs to interact with a ths
......@@ -1499,7 +1434,7 @@ platforms are moved over to use the flattened-device-tree model.
available.
For Axon: 0x0000012a
e) Xilinx IP cores
d) Xilinx IP cores
The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range
......@@ -1761,7 +1696,7 @@ platforms are moved over to use the flattened-device-tree model.
listed above, nodes for these devices should include a phy-handle
property, and may include other common network device properties
like local-mac-address.
iv) Xilinx Uartlite
Xilinx uartlite devices are simple fixed speed serial ports.
......@@ -1793,7 +1728,7 @@ platforms are moved over to use the flattened-device-tree model.
- reg-offset : A value of 3 is required
- reg-shift : A value of 2 is required
f) USB EHCI controllers
e) USB EHCI controllers
Required properties:
- compatible : should be "usb-ehci".
......@@ -1819,7 +1754,7 @@ platforms are moved over to use the flattened-device-tree model.
big-endian;
};
g) MDIO on GPIOs
f) MDIO on GPIOs
Currently defined compatibles:
- virtual,gpio-mdio
......@@ -1839,7 +1774,7 @@ platforms are moved over to use the flattened-device-tree model.
&qe_pio_c 6>;
};
h) SPI (Serial Peripheral Interface) busses
g) SPI (Serial Peripheral Interface) busses
SPI busses can be described with a node for the SPI master device
and a set of child nodes for each SPI slave on the bus. For this
......
Documentation/powerpc/dts-bindings/fsl/i2c.txt
浏览文件 @ e7fd5d4b
......@@ -7,8 +7,10 @@ Required properties :
Recommended properties :
- compatible : Should be "fsl-i2c" for parts compatible with
Freescale I2C specifications.
- compatible : compatibility list with 2 entries, the first should
be "fsl,CHIP-i2c" where CHIP is the name of a compatible processor,
e.g. mpc8313, mpc8543, mpc8544, mpc5200 or mpc5200b. The second one
should be "fsl-i2c".
- 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
......@@ -16,17 +18,31 @@ Recommended properties :
controller you have.
- interrupt-parent : the phandle for the interrupt controller that
services interrupts for this device.
- dfsrr : boolean; if defined, indicates that this I2C device has
a digital filter sampling rate register
- fsl5200-clocking : boolean; if defined, indicated that this device
uses the FSL 5200 clocking mechanism.
Example :
i2c@3000 {
interrupt-parent = <40000>;
interrupts = <1b 3>;
reg = <3000 18>;
device_type = "i2c";
compatible = "fsl-i2c";
dfsrr;
- fsl,preserve-clocking : boolean; if defined, the clock settings
from the bootloader are preserved (not touched).
- clock-frequency : desired I2C bus clock frequency in Hz.
Examples :
i2c@3d00 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,mpc5200b-i2c","fsl,mpc5200-i2c","fsl-i2c";
cell-index = <0>;
reg = <0x3d00 0x40>;
interrupts = <2 15 0>;
interrupt-parent = <&mpc5200_pic>;
fsl,preserve-clocking;
};
i2c@3100 {
#address-cells = <1>;
#size-cells = <0>;
cell-index = <1>;
compatible = "fsl,mpc8544-i2c", "fsl-i2c";
reg = <0x3100 0x100>;
interrupts = <43 2>;
interrupt-parent = <&mpic>;
clock-frequency = <400000>;
};
Documentation/powerpc/dts-bindings/mtd-physmap.txt 0 → 100644
浏览文件 @ e7fd5d4b
CFI or JEDEC memory-mapped NOR flash
Flash chips (Memory Technology Devices) are often used for solid state
file systems on embedded devices.
- compatible : should contain the specific model of flash chip(s)
used, if known, followed by either "cfi-flash" or "jedec-flash"
- reg : Address range(s) of the flash chip(s)
It's possible to (optionally) define multiple "reg" tuples so that
non-identical NOR chips can be described in one flash node.
- bank-width : Width (in bytes) of the flash bank. Equal to the
device width times the number of interleaved chips.
- device-width : (optional) Width of a single flash chip. If
omitted, assumed to be equal to 'bank-width'.
- #address-cells, #size-cells : Must be present if the flash has
sub-nodes representing partitions (see below). In this case
both #address-cells and #size-cells must be equal to 1.
For JEDEC compatible devices, the following additional properties
are defined:
- vendor-id : Contains the flash chip's vendor id (1 byte).
- device-id : Contains the flash chip's device id (1 byte).
In addition to the information on the flash bank itself, the
device tree may optionally contain additional information
describing partitions of the flash address space. This can be
used on platforms which have strong conventions about which
portions of the flash are used for what purposes, but which don't
use an on-flash partition table such as RedBoot.
Each partition is represented as a sub-node of the flash device.
Each node's name represents the name of the corresponding
partition of the flash device.
Flash partitions
- reg : The partition's offset and size within the flash bank.
- label : (optional) The label / name for this flash partition.
If omitted, the label is taken from the node name (excluding
the unit address).
- read-only : (optional) This parameter, if present, is a hint to
Linux that this flash partition should only be mounted
read-only. This is usually used for flash partitions
containing early-boot firmware images or data which should not
be clobbered.
Example:
flash@ff000000 {
compatible = "amd,am29lv128ml", "cfi-flash";
reg = <ff000000 01000000>;
bank-width = <4>;
device-width = <1>;
#address-cells = <1>;
#size-cells = <1>;
fs@0 {
label = "fs";
reg = <0 f80000>;
};
firmware@f80000 {
label ="firmware";
reg = <f80000 80000>;
read-only;
};
};
Here an example with multiple "reg" tuples:
flash@f0000000,0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "intel,PC48F4400P0VB", "cfi-flash";
reg = <0 0x00000000 0x02000000
0 0x02000000 0x02000000>;
bank-width = <2>;
partition@0 {
label = "test-part1";
reg = <0 0x04000000>;
};
};
Documentation/sound/alsa/HD-Audio.txt
浏览文件 @ e7fd5d4b
......@@ -169,7 +169,7 @@ PCI SSID look-up.
What `model` option values are available depends on the codec chip.
Check your codec chip from the codec proc file (see "Codec Proc-File"
section below). It will show the vendor/product name of your codec
chip. Then, see Documentation/sound/alsa/HD-Audio-Modelstxt file,
chip. Then, see Documentation/sound/alsa/HD-Audio-Models.txt file,
the section of HD-audio driver. You can find a list of codecs
and `model` options belonging to each codec. For example, for Realtek
ALC262 codec chip, pass `model=ultra` for devices that are compatible
......@@ -177,7 +177,7 @@ with Samsung Q1 Ultra.
Thus, the first thing you can do for any brand-new, unsupported and
non-working HD-audio hardware is to check HD-audio codec and several
different `model` option values. If you have a luck, some of them
different `model` option values. If you have any luck, some of them
might suit with your device well.
Some codecs such as ALC880 have a special model option `model=test`.
......
Documentation/sparse.txt
浏览文件 @ e7fd5d4b
......@@ -42,6 +42,14 @@ sure that bitwise types don't get mixed up (little-endian vs big-endian
vs cpu-endian vs whatever), and there the constant "0" really _is_
special.
__bitwise__ - to be used for relatively compact stuff (gfp_t, etc.) that
is mostly warning-free and is supposed to stay that way. Warnings will
be generated without __CHECK_ENDIAN__.
__bitwise - noisy stuff; in particular, __le*/__be* are that. We really
don't want to drown in noise unless we'd explicitly asked for it.
Getting sparse
~~~~~~~~~~~~~~
......
Documentation/spi/spi-summary
浏览文件 @ e7fd5d4b
......@@ -511,10 +511,16 @@ SPI MASTER METHODS
This sets up the device clock rate, SPI mode, and word sizes.
Drivers may change the defaults provided by board_info, and then
call spi_setup(spi) to invoke this routine. It may sleep.
Unless each SPI slave has its own configuration registers, don't
change them right away ... otherwise drivers could corrupt I/O
that's in progress for other SPI devices.
** BUG ALERT: for some reason the first version of
** many spi_master drivers seems to get this wrong.
** When you code setup(), ASSUME that the controller
** is actively processing transfers for another device.
master->transfer(struct spi_device *spi, struct spi_message *message)
This must not sleep. Its responsibility is arrange that the
transfer happens and its complete() callback is issued. The two
......
Documentation/sysctl/net.txt
浏览文件 @ e7fd5d4b
......@@ -95,7 +95,7 @@ of struct cmsghdr structures with appended data.
There is only one file in this directory.
unix_dgram_qlen limits the max number of datagrams queued in Unix domain
socket's buffer. It will not take effect unless PF_UNIX flag is spicified.
socket's buffer. It will not take effect unless PF_UNIX flag is specified.
3. /proc/sys/net/ipv4 - IPV4 settings
......
Documentation/tomoyo.txt 0 → 100644
浏览文件 @ e7fd5d4b
--- What is TOMOYO? ---
TOMOYO is a name-based MAC extension (LSM module) for the Linux kernel.
LiveCD-based tutorials are available at
http://tomoyo.sourceforge.jp/en/1.6.x/1st-step/ubuntu8.04-live/
http://tomoyo.sourceforge.jp/en/1.6.x/1st-step/centos5-live/ .
Though these tutorials use non-LSM version of TOMOYO, they are useful for you
to know what TOMOYO is.
--- How to enable TOMOYO? ---
Build the kernel with CONFIG_SECURITY_TOMOYO=y and pass "security=tomoyo" on
kernel's command line.
Please see http://tomoyo.sourceforge.jp/en/2.2.x/ for details.
--- Where is documentation? ---
User <-> Kernel interface documentation is available at
http://tomoyo.sourceforge.jp/en/2.2.x/policy-reference.html .
Materials we prepared for seminars and symposiums are available at
http://sourceforge.jp/projects/tomoyo/docs/?category_id=532&language_id=1 .
Below lists are chosen from three aspects.
What is TOMOYO?
TOMOYO Linux Overview
http://sourceforge.jp/projects/tomoyo/docs/lca2009-takeda.pdf
TOMOYO Linux: pragmatic and manageable security for Linux
http://sourceforge.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf
TOMOYO Linux: A Practical Method to Understand and Protect Your Own Linux Box
http://sourceforge.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdf
What can TOMOYO do?
Deep inside TOMOYO Linux
http://sourceforge.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf
The role of "pathname based access control" in security.
http://sourceforge.jp/projects/tomoyo/docs/lfj2008-bof.pdf
History of TOMOYO?
Realities of Mainlining
http://sourceforge.jp/projects/tomoyo/docs/lfj2008.pdf
--- What is future plan? ---
We believe that inode based security and name based security are complementary
and both should be used together. But unfortunately, so far, we cannot enable
multiple LSM modules at the same time. We feel sorry that you have to give up
SELinux/SMACK/AppArmor etc. when you want to use TOMOYO.
We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
version of TOMOYO, available at http://tomoyo.sourceforge.jp/en/1.6.x/ .
LSM version of TOMOYO is a subset of non-LSM version of TOMOYO. We are planning
to port non-LSM version's functionalities to LSM versions.
Documentation/vm/00-INDEX
浏览文件 @ e7fd5d4b
00-INDEX
- this file.
active_mm.txt
- An explanation from Linus about tsk->active_mm vs tsk->mm.
balance
- various information on memory balancing.
hugetlbpage.txt
......
Documentation/vm/active_mm.txt 0 → 100644
浏览文件 @ e7fd5d4b
List: linux-kernel
Subject: Re: active_mm
From: Linus Torvalds <torvalds () transmeta ! com>
Date: 1999-07-30 21:36:24
Cc'd to linux-kernel, because I don't write explanations all that often,
and when I do I feel better about more people reading them.
On Fri, 30 Jul 1999, David Mosberger wrote:
>
> Is there a brief description someplace on how "mm" vs. "active_mm" in
> the task_struct are supposed to be used? (My apologies if this was
> discussed on the mailing lists---I just returned from vacation and
> wasn't able to follow linux-kernel for a while).
Basically, the new setup is:
- we have "real address spaces" and "anonymous address spaces". The
difference is that an anonymous address space doesn't care about the
user-level page tables at all, so when we do a context switch into an
anonymous address space we just leave the previous address space
active.
The obvious use for a "anonymous address space" is any thread that
doesn't need any user mappings - all kernel threads basically fall into
this category, but even "real" threads can temporarily say that for
some amount of time they are not going to be interested in user space,
and that the scheduler might as well try to avoid wasting time on
switching the VM state around. Currently only the old-style bdflush
sync does that.
- "tsk->mm" points to the "real address space". For an anonymous process,
tsk->mm will be NULL, for the logical reason that an anonymous process
really doesn't _have_ a real address space at all.
- however, we obviously need to keep track of which address space we
"stole" for such an anonymous user. For that, we have "tsk->active_mm",
which shows what the currently active address space is.
The rule is that for a process with a real address space (ie tsk->mm is
non-NULL) the active_mm obviously always has to be the same as the real
one.
For a anonymous process, tsk->mm == NULL, and tsk->active_mm is the
"borrowed" mm while the anonymous process is running. When the
anonymous process gets scheduled away, the borrowed address space is
returned and cleared.
To support all that, the "struct mm_struct" now has two counters: a
"mm_users" counter that is how many "real address space users" there are,
and a "mm_count" counter that is the number of "lazy" users (ie anonymous
users) plus one if there are any real users.
Usually there is at least one real user, but it could be that the real
user exited on another CPU while a lazy user was still active, so you do
actually get cases where you have a address space that is _only_ used by
lazy users. That is often a short-lived state, because once that thread
gets scheduled away in favour of a real thread, the "zombie" mm gets
released because "mm_users" becomes zero.
Also, a new rule is that _nobody_ ever has "init_mm" as a real MM any
more. "init_mm" should be considered just a "lazy context when no other
context is available", and in fact it is mainly used just at bootup when
no real VM has yet been created. So code that used to check
if (current->mm == &init_mm)
should generally just do
if (!current->mm)
instead (which makes more sense anyway - the test is basically one of "do
we have a user context", and is generally done by the page fault handler
and things like that).
Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,
because it slightly changes the interfaces to accomodate the alpha (who
would have thought it, but the alpha actually ends up having one of the
ugliest context switch codes - unlike the other architectures where the MM
and register state is separate, the alpha PALcode joins the two, and you
need to switch both together).
(From http://marc.info/?l=linux-kernel&m=93337278602211&w=2)
MAINTAINERS
浏览文件 @ e7fd5d4b
此差异已折叠。
Makefile
浏览文件 @ e7fd5d4b
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 30
EXTRAVERSION = -rc1
EXTRAVERSION = -rc3
NAME = Temporary Tasmanian Devil
# *DOCUMENTATION*
......@@ -169,7 +169,7 @@ SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
-e s/arm.*/arm/ -e s/sa110/arm/ \
-e s/s390x/s390/ -e s/parisc64/parisc/ \
-e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
-e s/sh.*/sh/ )
-e s/sh[234].*/sh/ )
# Cross compiling and selecting different set of gcc/bin-utils
# ---------------------------------------------------------------------------
......@@ -210,6 +210,11 @@ ifeq ($(ARCH),sparc64)
SRCARCH := sparc
endif
# Additional ARCH settings for sh
ifeq ($(ARCH),sh64)
SRCARCH := sh
endif
# Where to locate arch specific headers
hdr-arch := $(SRCARCH)
......@@ -567,7 +572,7 @@ KBUILD_CFLAGS += $(call cc-option,-Wdeclaration-after-statement,)
# disable pointer signed / unsigned warnings in gcc 4.0
KBUILD_CFLAGS += $(call cc-option,-Wno-pointer-sign,)
# disable invalid "can't wrap" optimzations for signed / pointers
# disable invalid "can't wrap" optimizations for signed / pointers
KBUILD_CFLAGS += $(call cc-option,-fwrapv)
# revert to pre-gcc-4.4 behaviour of .eh_frame
......@@ -597,6 +602,10 @@ LDFLAGS_BUILD_ID = $(patsubst -Wl$(comma)%,%,\
LDFLAGS_MODULE += $(LDFLAGS_BUILD_ID)
LDFLAGS_vmlinux += $(LDFLAGS_BUILD_ID)
ifeq ($(CONFIG_STRIP_ASM_SYMS),y)
LDFLAGS_vmlinux += -X
endif
# Default kernel image to build when no specific target is given.
# KBUILD_IMAGE may be overruled on the command line or
# set in the environment
......@@ -1191,7 +1200,7 @@ CLEAN_FILES += vmlinux System.map \
.tmp_kallsyms* .tmp_version .tmp_vmlinux* .tmp_System.map
# Directories & files removed with 'make mrproper'
MRPROPER_DIRS += include/config include2 usr/include
MRPROPER_DIRS += include/config include2 usr/include include/generated
MRPROPER_FILES += .config .config.old include/asm .version .old_version \
include/linux/autoconf.h include/linux/version.h \
include/linux/utsrelease.h \
......@@ -1587,5 +1596,5 @@ PHONY += FORCE
FORCE:
# Declare the contents of the .PHONY variable as phony. We keep that
# information in a variable se we can use it in if_changed and friends.
# information in a variable so we can use it in if_changed and friends.
.PHONY: $(PHONY)
arch/Kconfig
浏览文件 @ e7fd5d4b
......@@ -109,3 +109,6 @@ config HAVE_CLK
config HAVE_DMA_API_DEBUG
bool
config HAVE_DEFAULT_NO_SPIN_MUTEXES
bool
arch/alpha/include/asm/percpu.h
浏览文件 @ e7fd5d4b
......@@ -73,6 +73,6 @@ extern unsigned long __per_cpu_offset[NR_CPUS];
#endif /* SMP */
#define DECLARE_PER_CPU(type, name) extern __typeof__(type) per_cpu_var(name)
#include <asm-generic/percpu.h>
#endif /* __ALPHA_PERCPU_H */
arch/alpha/kernel/head.S
浏览文件 @ e7fd5d4b
......@@ -7,10 +7,11 @@
* the kernel global pointer and jump to the kernel entry-point.
*/
#include <linux/init.h>
#include <asm/system.h>
#include <asm/asm-offsets.h>
.section .text.head, "ax"
__HEAD
.globl swapper_pg_dir
.globl _stext
swapper_pg_dir=SWAPPER_PGD
......
arch/alpha/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
......@@ -16,7 +16,7 @@ SECTIONS
_text = .; /* Text and read-only data */
.text : {
*(.text.head)
HEAD_TEXT
TEXT_TEXT
SCHED_TEXT
LOCK_TEXT
......
arch/arm/common/vic.c
浏览文件 @ e7fd5d4b
......@@ -85,12 +85,11 @@ void __init vic_init(void __iomem *base, unsigned int irq_start,
writel(32, base + VIC_PL190_DEF_VECT_ADDR);
for (i = 0; i < 32; i++) {
unsigned int irq = irq_start + i;
set_irq_chip(irq, &vic_chip);
set_irq_chip_data(irq, base);
if (vic_sources & (1 << i)) {
unsigned int irq = irq_start + i;
set_irq_chip(irq, &vic_chip);
set_irq_chip_data(irq, base);
set_irq_handler(irq, handle_level_irq);
set_irq_flags(irq, IRQF_VALID | IRQF_PROBE);
}
......
arch/arm/configs/magician_defconfig
浏览文件 @ e7fd5d4b
......@@ -1183,7 +1183,11 @@ CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_SA1100=y
# CONFIG_RTC_DRV_PXA is not set
# CONFIG_DMADEVICES is not set
# CONFIG_REGULATOR is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
CONFIG_REGULATOR_BQ24022=y
# CONFIG_UIO is not set
# CONFIG_STAGING is not set
......
arch/arm/configs/s3c2410_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/include/asm/sizes.h
浏览文件 @ e7fd5d4b
......@@ -32,6 +32,7 @@
#define SZ_4K 0x00001000
#define SZ_8K 0x00002000
#define SZ_16K 0x00004000
#define SZ_32K 0x00008000
#define SZ_64K 0x00010000
#define SZ_128K 0x00020000
#define SZ_256K 0x00040000
......
arch/arm/include/asm/tlb.h
浏览文件 @ e7fd5d4b
......@@ -36,6 +36,8 @@
struct mmu_gather {
struct mm_struct *mm;
unsigned int fullmm;
unsigned long range_start;
unsigned long range_end;
};
DECLARE_PER_CPU(struct mmu_gather, mmu_gathers);
......@@ -63,7 +65,19 @@ tlb_finish_mmu(struct mmu_gather *tlb, unsigned long start, unsigned long end)
put_cpu_var(mmu_gathers);
}
#define tlb_remove_tlb_entry(tlb,ptep,address) do { } while (0)
/*
* Memorize the range for the TLB flush.
*/
static inline void
tlb_remove_tlb_entry(struct mmu_gather *tlb, pte_t *ptep, unsigned long addr)
{
if (!tlb->fullmm) {
if (addr < tlb->range_start)
tlb->range_start = addr;
if (addr + PAGE_SIZE > tlb->range_end)
tlb->range_end = addr + PAGE_SIZE;
}
}
/*
* In the case of tlb vma handling, we can optimise these away in the
......@@ -73,15 +87,18 @@ tlb_finish_mmu(struct mmu_gather *tlb, unsigned long start, unsigned long end)
static inline void
tlb_start_vma(struct mmu_gather *tlb, struct vm_area_struct *vma)
{
if (!tlb->fullmm)
if (!tlb->fullmm) {
flush_cache_range(vma, vma->vm_start, vma->vm_end);
tlb->range_start = TASK_SIZE;
tlb->range_end = 0;
}
}
static inline void
tlb_end_vma(struct mmu_gather *tlb, struct vm_area_struct *vma)
{
if (!tlb->fullmm)
flush_tlb_range(vma, vma->vm_start, vma->vm_end);
if (!tlb->fullmm && tlb->range_end > 0)
flush_tlb_range(vma, tlb->range_start, tlb->range_end);
}
#define tlb_remove_page(tlb,page) free_page_and_swap_cache(page)
......
arch/arm/include/asm/unistd.h
浏览文件 @ e7fd5d4b
......@@ -387,6 +387,8 @@
#define __NR_dup3 (__NR_SYSCALL_BASE+358)
#define __NR_pipe2 (__NR_SYSCALL_BASE+359)
#define __NR_inotify_init1 (__NR_SYSCALL_BASE+360)
#define __NR_preadv (__NR_SYSCALL_BASE+361)
#define __NR_pwritev (__NR_SYSCALL_BASE+362)
/*
* The following SWIs are ARM private.
......
arch/arm/kernel/calls.S
浏览文件 @ e7fd5d4b
......@@ -370,6 +370,8 @@
CALL(sys_dup3)
CALL(sys_pipe2)
/* 360 */ CALL(sys_inotify_init1)
CALL(sys_preadv)
CALL(sys_pwritev)
#ifndef syscalls_counted
.equ syscalls_padding, ((NR_syscalls + 3) & ~3) - NR_syscalls
#define syscalls_counted
......
arch/arm/kernel/sys_oabi-compat.c
浏览文件 @ e7fd5d4b
......@@ -83,6 +83,7 @@
#include <linux/net.h>
#include <linux/ipc.h>
#include <linux/uaccess.h>
#include <linux/slab.h>
struct oldabi_stat64 {
unsigned long long st_dev;
......@@ -176,21 +177,12 @@ asmlinkage long sys_oabi_fstatat64(int dfd,
int flag)
{
struct kstat stat;
int error = -EINVAL;
int error;
if ((flag & ~AT_SYMLINK_NOFOLLOW) != 0)
goto out;
if (flag & AT_SYMLINK_NOFOLLOW)
error = vfs_lstat_fd(dfd, filename, &stat);
else
error = vfs_stat_fd(dfd, filename, &stat);
if (!error)
error = cp_oldabi_stat64(&stat, statbuf);
out:
return error;
error = vfs_fstatat(dfd, filename, &stat, flag);
if (error)
return error;
return cp_oldabi_stat64(&stat, statbuf);
}
struct oabi_flock64 {
......
arch/arm/mach-at91/at91rm9200_time.c
浏览文件 @ e7fd5d4b
......@@ -85,7 +85,7 @@ static struct irqaction at91rm9200_timer_irq = {
.handler = at91rm9200_timer_interrupt
};
static cycle_t read_clk32k(void)
static cycle_t read_clk32k(struct clocksource *cs)
{
return read_CRTR();
}
......
arch/arm/mach-at91/at91sam926x_time.c
浏览文件 @ e7fd5d4b
......@@ -31,7 +31,7 @@ static u32 pit_cnt; /* access only w/system irq blocked */
* Clocksource: just a monotonic counter of MCK/16 cycles.
* We don't care whether or not PIT irqs are enabled.
*/
static cycle_t read_pit_clk(void)
static cycle_t read_pit_clk(struct clocksource *cs)
{
unsigned long flags;
u32 elapsed;
......
arch/arm/mach-at91/include/mach/board.h
浏览文件 @ e7fd5d4b
......@@ -87,7 +87,7 @@ extern void __init at91_add_device_eth(struct at91_eth_data *data);
/* USB Host */
struct at91_usbh_data {
u8 ports; /* number of ports on root hub */
u8 vbus_pin[]; /* port power-control pin */
u8 vbus_pin[2]; /* port power-control pin */
};
extern void __init at91_add_device_usbh(struct at91_usbh_data *data);
......
arch/arm/mach-davinci/time.c
浏览文件 @ e7fd5d4b
......@@ -238,7 +238,7 @@ static void __init timer_init(void)
/*
* clocksource
*/
static cycle_t read_cycles(void)
static cycle_t read_cycles(struct clocksource *cs)
{
struct timer_s *t = &timers[TID_CLOCKSOURCE];
......
arch/arm/mach-ep93xx/core.c
浏览文件 @ e7fd5d4b
......@@ -100,7 +100,7 @@ static unsigned int last_jiffy_time;
#define TIMER4_TICKS_PER_JIFFY ((CLOCK_TICK_RATE + (HZ/2)) / HZ)
static int ep93xx_timer_interrupt(int irq, void *dev_id)
static irqreturn_t ep93xx_timer_interrupt(int irq, void *dev_id)
{
__raw_writel(1, EP93XX_TIMER1_CLEAR);
while ((signed long)
......
arch/arm/mach-imx/include/mach/gpio.h
浏览文件 @ e7fd5d4b
#ifndef _IMX_GPIO_H
#include <linux/kernel.h>
#include <mach/hardware.h>
#include <mach/imx-regs.h>
#define IMX_GPIO_ALLOC_MODE_NORMAL 0
......
arch/arm/mach-imx/time.c
浏览文件 @ e7fd5d4b
......@@ -73,7 +73,7 @@ static void __init imx_timer_hardware_init(void)
IMX_TCTL(TIMER_BASE) = TCTL_FRR | TCTL_CLK_PCLK1 | TCTL_TEN;
}
cycle_t imx_get_cycles(void)
cycle_t imx_get_cycles(struct clocksource *cs)
{
return IMX_TCN(TIMER_BASE);
}
......
arch/arm/mach-ixp4xx/common.c
浏览文件 @ e7fd5d4b
......@@ -401,7 +401,7 @@ void __init ixp4xx_sys_init(void)
/*
* clocksource
*/
cycle_t ixp4xx_get_cycles(void)
cycle_t ixp4xx_get_cycles(struct clocksource *cs)
{
return *IXP4XX_OSTS;
}
......
arch/arm/mach-kirkwood/common.c
浏览文件 @ e7fd5d4b
......@@ -23,6 +23,7 @@
#include <asm/mach/map.h>
#include <asm/mach/time.h>
#include <mach/kirkwood.h>
#include <mach/bridge-regs.h>
#include <plat/cache-feroceon-l2.h>
#include <plat/ehci-orion.h>
#include <plat/mvsdio.h>
......
arch/arm/mach-kirkwood/include/mach/bridge-regs.h 0 → 100644
浏览文件 @ e7fd5d4b
/*
* arch/arm/mach-kirkwood/include/mach/bridge-regs.h
*
* Mbus-L to Mbus Bridge Registers
*
* This file is licensed under the terms of the GNU General Public
* License version 2. This program is licensed "as is" without any
* warranty of any kind, whether express or implied.
*/
#ifndef __ASM_ARCH_BRIDGE_REGS_H
#define __ASM_ARCH_BRIDGE_REGS_H
#include <mach/kirkwood.h>
#define CPU_CONTROL (BRIDGE_VIRT_BASE | 0x0104)
#define CPU_RESET 0x00000002
#define RSTOUTn_MASK (BRIDGE_VIRT_BASE | 0x0108)
#define SOFT_RESET_OUT_EN 0x00000004
#define SYSTEM_SOFT_RESET (BRIDGE_VIRT_BASE | 0x010c)
#define SOFT_RESET 0x00000001
#define BRIDGE_CAUSE (BRIDGE_VIRT_BASE | 0x0110)
#define BRIDGE_MASK (BRIDGE_VIRT_BASE | 0x0114)
#define BRIDGE_INT_TIMER0 0x0002
#define BRIDGE_INT_TIMER1 0x0004
#define BRIDGE_INT_TIMER1_CLR (~0x0004)
#define IRQ_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0200)
#define IRQ_CAUSE_LOW_OFF 0x0000
#define IRQ_MASK_LOW_OFF 0x0004
#define IRQ_CAUSE_HIGH_OFF 0x0010
#define IRQ_MASK_HIGH_OFF 0x0014
#define TIMER_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0300)
#define L2_CONFIG_REG (BRIDGE_VIRT_BASE | 0x0128)
#define L2_WRITETHROUGH 0x00000010
#endif
arch/arm/mach-kirkwood/include/mach/debug-macro.S
浏览文件 @ e7fd5d4b
......@@ -6,7 +6,7 @@
* published by the Free Software Foundation.
*/
#include <mach/kirkwood.h>
#include <mach/bridge-regs.h>
.macro addruart,rx
mrc p15, 0, \rx, c1, c0
......
arch/arm/mach-kirkwood/include/mach/entry-macro.S
浏览文件 @ e7fd5d4b
......@@ -8,7 +8,7 @@
* warranty of any kind, whether express or implied.
*/
#include <mach/kirkwood.h>
#include <mach/bridge-regs.h>
.macro disable_fiq
.endm
......
arch/arm/mach-kirkwood/include/mach/kirkwood.h
浏览文件 @ e7fd5d4b
......@@ -43,44 +43,6 @@
#define KIRKWOOD_PCIE_MEM_PHYS_BASE 0xe0000000
#define KIRKWOOD_PCIE_MEM_SIZE SZ_128M
/*
* MBUS bridge registers.
*/
#define BRIDGE_VIRT_BASE (KIRKWOOD_REGS_VIRT_BASE | 0x20000)
#define CPU_CONTROL (BRIDGE_VIRT_BASE | 0x0104)
#define CPU_RESET 0x00000002
#define RSTOUTn_MASK (BRIDGE_VIRT_BASE | 0x0108)
#define SOFT_RESET_OUT_EN 0x00000004
#define SYSTEM_SOFT_RESET (BRIDGE_VIRT_BASE | 0x010c)
#define SOFT_RESET 0x00000001
#define BRIDGE_CAUSE (BRIDGE_VIRT_BASE | 0x0110)
#define BRIDGE_MASK (BRIDGE_VIRT_BASE | 0x0114)
#define BRIDGE_INT_TIMER0 0x0002
#define BRIDGE_INT_TIMER1 0x0004
#define BRIDGE_INT_TIMER1_CLR (~0x0004)
#define IRQ_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0200)
#define IRQ_CAUSE_LOW_OFF 0x0000
#define IRQ_MASK_LOW_OFF 0x0004
#define IRQ_CAUSE_HIGH_OFF 0x0010
#define IRQ_MASK_HIGH_OFF 0x0014
#define TIMER_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0300)
#define L2_CONFIG_REG (BRIDGE_VIRT_BASE | 0x0128)
#define L2_WRITETHROUGH 0x00000010
/*
* Supported devices and revisions.
*/
#define MV88F6281_DEV_ID 0x6281
#define MV88F6281_REV_Z0 0
#define MV88F6281_REV_A0 2
#define MV88F6192_DEV_ID 0x6192
#define MV88F6192_REV_Z0 0
#define MV88F6192_REV_A0 2
#define MV88F6180_DEV_ID 0x6180
#define MV88F6180_REV_A0 2
/*
* Register Map
*/
......@@ -99,6 +61,8 @@
#define UART1_PHYS_BASE (DEV_BUS_PHYS_BASE | 0x2100)
#define UART1_VIRT_BASE (DEV_BUS_VIRT_BASE | 0x2100)
#define BRIDGE_VIRT_BASE (KIRKWOOD_REGS_VIRT_BASE | 0x20000)
#define PCIE_VIRT_BASE (KIRKWOOD_REGS_VIRT_BASE | 0x40000)
#define USB_PHYS_BASE (KIRKWOOD_REGS_PHYS_BASE | 0x50000)
......@@ -119,5 +83,18 @@
#define SDIO_PHYS_BASE (KIRKWOOD_REGS_PHYS_BASE | 0x90000)
/*
* Supported devices and revisions.
*/
#define MV88F6281_DEV_ID 0x6281
#define MV88F6281_REV_Z0 0
#define MV88F6281_REV_A0 2
#define MV88F6192_DEV_ID 0x6192
#define MV88F6192_REV_Z0 0
#define MV88F6192_REV_A0 2
#define MV88F6180_DEV_ID 0x6180
#define MV88F6180_REV_A0 2
#endif
arch/arm/mach-kirkwood/include/mach/system.h
浏览文件 @ e7fd5d4b
......@@ -9,8 +9,7 @@
#ifndef __ASM_ARCH_SYSTEM_H
#define __ASM_ARCH_SYSTEM_H
#include <mach/hardware.h>
#include <mach/kirkwood.h>
#include <mach/bridge-regs.h>
static inline void arch_idle(void)
{
......
arch/arm/mach-kirkwood/irq.c
浏览文件 @ e7fd5d4b
......@@ -12,6 +12,7 @@
#include <linux/init.h>
#include <linux/irq.h>
#include <linux/io.h>
#include <mach/bridge-regs.h>
#include <plat/irq.h>
#include <asm/gpio.h>
#include "common.h"
......
arch/arm/mach-loki/addr-map.c
浏览文件 @ e7fd5d4b
......@@ -38,6 +38,7 @@
/*
* CPU Address Decode Windows registers
*/
#define BRIDGE_REG(x) (BRIDGE_VIRT_BASE | (x))
#define CPU_WIN_CTRL(n) BRIDGE_REG(0x000 | ((n) << 4))
#define CPU_WIN_BASE(n) BRIDGE_REG(0x004 | ((n) << 4))
#define CPU_WIN_REMAP_LO(n) BRIDGE_REG(0x008 | ((n) << 4))
......
arch/arm/mach-loki/include/mach/bridge-regs.h 0 → 100644
浏览文件 @ e7fd5d4b
/*
* arch/arm/mach-loki/include/mach/bridge-regs.h
*
* This file is licensed under the terms of the GNU General Public
* License version 2. This program is licensed "as is" without any
* warranty of any kind, whether express or implied.
*/
#ifndef __ASM_ARCH_BRIDGE_REGS_H
#define __ASM_ARCH_BRIDGE_REGS_H
#include <mach/loki.h>
#define RSTOUTn_MASK (BRIDGE_VIRT_BASE | 0x0108)
#define SOFT_RESET_OUT_EN 0x00000004
#define SYSTEM_SOFT_RESET (BRIDGE_VIRT_BASE | 0x010c)
#define SOFT_RESET 0x00000001
#define BRIDGE_CAUSE (BRIDGE_VIRT_BASE | 0x0110)
#define BRIDGE_MASK (BRIDGE_VIRT_BASE | 0x0114)
#define BRIDGE_INT_TIMER0 0x0002
#define BRIDGE_INT_TIMER1 0x0004
#define BRIDGE_INT_TIMER1_CLR 0x0004
#define IRQ_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0200)
#define IRQ_CAUSE_OFF 0x0000
#define IRQ_MASK_OFF 0x0004
#define TIMER_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0300)
#endif
arch/arm/mach-loki/include/mach/entry-macro.S
浏览文件 @ e7fd5d4b
......@@ -8,7 +8,7 @@
* warranty of any kind, whether express or implied.
*/
#include <mach/loki.h>
#include <mach/bridge-regs.h>
.macro disable_fiq
.endm
......
arch/arm/mach-loki/include/mach/loki.h
浏览文件 @ e7fd5d4b
......@@ -58,20 +58,6 @@
#define UART1_VIRT_BASE (DEV_BUS_VIRT_BASE | 0x2100)
#define BRIDGE_VIRT_BASE (LOKI_REGS_VIRT_BASE | 0x20000)
#define BRIDGE_REG(x) (BRIDGE_VIRT_BASE | (x))
#define RSTOUTn_MASK (BRIDGE_VIRT_BASE | 0x0108)
#define SOFT_RESET_OUT_EN 0x00000004
#define SYSTEM_SOFT_RESET (BRIDGE_VIRT_BASE | 0x010c)
#define SOFT_RESET 0x00000001
#define BRIDGE_CAUSE (BRIDGE_VIRT_BASE | 0x0110)
#define BRIDGE_MASK (BRIDGE_VIRT_BASE | 0x0114)
#define BRIDGE_INT_TIMER0 0x0002
#define BRIDGE_INT_TIMER1 0x0004
#define BRIDGE_INT_TIMER1_CLR 0x0004
#define IRQ_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0200)
#define IRQ_CAUSE_OFF 0x0000
#define IRQ_MASK_OFF 0x0004
#define TIMER_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0300)
#define PCIE0_VIRT_BASE (LOKI_REGS_VIRT_BASE | 0x30000)
......
arch/arm/mach-loki/include/mach/system.h
浏览文件 @ e7fd5d4b
......@@ -9,8 +9,7 @@
#ifndef __ASM_ARCH_SYSTEM_H
#define __ASM_ARCH_SYSTEM_H
#include <mach/hardware.h>
#include <mach/loki.h>
#include <mach/bridge-regs.h>
static inline void arch_idle(void)
{
......
arch/arm/mach-loki/irq.c
浏览文件 @ e7fd5d4b
......@@ -12,6 +12,7 @@
#include <linux/init.h>
#include <linux/irq.h>
#include <linux/io.h>
#include <mach/bridge-regs.h>
#include <plat/irq.h>
#include "common.h"
......
arch/arm/mach-msm/timer.c
浏览文件 @ e7fd5d4b
......@@ -57,12 +57,12 @@ static irqreturn_t msm_timer_interrupt(int irq, void *dev_id)
return IRQ_HANDLED;
}
static cycle_t msm_gpt_read(void)
static cycle_t msm_gpt_read(struct clocksource *cs)
{
return readl(MSM_GPT_BASE + TIMER_COUNT_VAL);
}
static cycle_t msm_dgt_read(void)
static cycle_t msm_dgt_read(struct clocksource *cs)
{
return readl(MSM_DGT_BASE + TIMER_COUNT_VAL) >> MSM_DGT_SHIFT;
}
......
arch/arm/mach-mv78xx0/common.c
浏览文件 @ e7fd5d4b
......@@ -20,6 +20,7 @@
#include <asm/mach/map.h>
#include <asm/mach/time.h>
#include <mach/mv78xx0.h>
#include <mach/bridge-regs.h>
#include <plat/cache-feroceon-l2.h>
#include <plat/ehci-orion.h>
#include <plat/orion_nand.h>
......
arch/arm/mach-mv78xx0/include/mach/bridge-regs.h 0 → 100644
浏览文件 @ e7fd5d4b
/*
* arch/arm/mach-mv78xx0/include/mach/bridge-regs.h
*
* This file is licensed under the terms of the GNU General Public
* License version 2. This program is licensed "as is" without any
* warranty of any kind, whether express or implied.
*/
#ifndef __ASM_ARCH_BRIDGE_REGS_H
#define __ASM_ARCH_BRIDGE_REGS_H
#include <mach/mv78xx0.h>
#define CPU_CONTROL (BRIDGE_VIRT_BASE | 0x0104)
#define L2_WRITETHROUGH 0x00020000
#define RSTOUTn_MASK (BRIDGE_VIRT_BASE | 0x0108)
#define SOFT_RESET_OUT_EN 0x00000004
#define SYSTEM_SOFT_RESET (BRIDGE_VIRT_BASE | 0x010c)
#define SOFT_RESET 0x00000001
#define BRIDGE_CAUSE (BRIDGE_VIRT_BASE | 0x0110)
#define BRIDGE_MASK (BRIDGE_VIRT_BASE | 0x0114)
#define BRIDGE_INT_TIMER0 0x0002
#define BRIDGE_INT_TIMER1 0x0004
#define BRIDGE_INT_TIMER1_CLR (~0x0004)
#define IRQ_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0200)
#define IRQ_CAUSE_ERR_OFF 0x0000
#define IRQ_CAUSE_LOW_OFF 0x0004
#define IRQ_CAUSE_HIGH_OFF 0x0008
#define IRQ_MASK_ERR_OFF 0x000c
#define IRQ_MASK_LOW_OFF 0x0010
#define IRQ_MASK_HIGH_OFF 0x0014
#define TIMER_VIRT_BASE (BRIDGE_VIRT_BASE | 0x0300)
#endif
arch/arm/mach-mv78xx0/include/mach/entry-macro.S
浏览文件 @ e7fd5d4b
......@@ -8,7 +8,7 @@
* warranty of any kind, whether express or implied.
*/
#include <mach/mv78xx0.h>
#include <mach/bridge-regs.h>
.macro disable_fiq
.endm
......
arch/arm/mach-mv78xx0/include/mach/system.h
浏览文件 @ e7fd5d4b
......@@ -9,8 +9,7 @@
#ifndef __ASM_ARCH_SYSTEM_H
#define __ASM_ARCH_SYSTEM_H
#include <mach/hardware.h>
#include <mach/mv78xx0.h>
#include <mach/bridge-regs.h>
static inline void arch_idle(void)
{
......
arch/arm/mach-mv78xx0/irq.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-mx1/mx1ads.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-mx2/clock_imx21.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-mx3/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-mx3/mx31ads.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-mx3/pcm037.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-mx3/qong.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-netx/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-ns9xxx/time-ns9360.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-omap1/clock.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-omap1/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-omap2/timer-gp.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-omap2/usb-musb.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-orion5x/addr-map.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-orion5x/include/mach/bridge-regs.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-orion5x/irq.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-orion5x/mss2-setup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-orion5x/pci.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/cm-x2xx.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa300.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa320.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/colibri-pxa3xx.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/csb701.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/e740.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/e750.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/e800.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/generic.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/include/mach/palmte2.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/mioa701.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/palmld.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/palmt5.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/palmte2.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/palmtx.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-realview/core.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-s3c2412/mach-jive.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-s3c2440/mach-anubis.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-s3c2440/mach-osiris.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mach-versatile/core.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mm/proc-v6.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mm/proc-v7.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mm/tlb-v6.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/mm/tlb-v7.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-mxc/irq.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-mxc/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-omap/common.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-orion/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-s3c/gpio-config.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-s3c24xx/adc.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/arm/plat-s3c24xx/gpiolib.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/avr32/kernel/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/blackfin/kernel/time-ts.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/entry.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/head-mmu-fr451.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/head-uc-fr401.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/head-uc-fr451.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/head-uc-fr555.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/setup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/frv/mb93090-mb00/pci-vdk.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/include/asm/smp.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/include/asm/unistd.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/kernel/cyclone.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/kernel/pci-swiotlb.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/kernel/smp.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/kernel/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/kvm/kvm-ia64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/ia64/sn/kernel/sn2/timer.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m32r/kernel/head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m32r/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/amiga_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/apollo_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/atari_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/hp300_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/mac_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/multi_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/mvme147_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/mvme16x_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/q40_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/sun3_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/configs/sun3x_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/include/asm/unistd.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/kernel/entry.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/kernel/head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/kernel/sun3-head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/kernel/vmlinux-std.lds
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68k/kernel/vmlinux-sun3.lds
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68knommu/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68knommu/kernel/asm-offsets.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68knommu/kernel/dma.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/m68knommu/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/Kconfig 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/Kconfig.debug 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/boot/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/Kbuild 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/atomic.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/auxvec.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/bitops.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/bug.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/bugs.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/byteorder.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/cache.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/cacheflush.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/checksum.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/clinkage.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/cpuinfo.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/cputable.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/current.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/delay.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/device.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/div64.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/dma-mapping.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/dma.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/elf.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/entry.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/exceptions.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/flat.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/ftrace.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/gpio.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/hardirq.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/hw_irq.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/io.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/ioctls.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/ipcbuf.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/irq.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/irq_regs.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/irqflags.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/kdebug.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/kmap_types.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/linkage.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/lmb.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/mman.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/mmu.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/mmu_context.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/module.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/msgbuf.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/mutex.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/namei.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/of_device.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/of_platform.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/page.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/param.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/pci-bridge.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/pci.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/pgalloc.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/pgtable.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/posix_types.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/processor.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/prom.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/ptrace.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/pvr.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/registers.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/scatterlist.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/sections.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/segment.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/selfmod.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/sembuf.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/serial.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/setup.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/shmbuf.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/shmparam.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/sigcontext.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/siginfo.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/signal.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/socket.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/sockios.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/stat.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/string.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/swab.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/syscalls.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/system.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/termbits.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/termios.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/thread_info.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/timex.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/tlb.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/tlbflush.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/topology.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/types.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/uaccess.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/ucontext.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/unaligned.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/unistd.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/user.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/include/asm/vga.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/asm-offsets.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/cache.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/cpuinfo-pvr-full.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/cpuinfo-static.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/cpuinfo.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/mb.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/cpu/pvr.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/early_printk.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/entry-nommu.S 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/exceptions.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/head.S 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/heartbeat.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/hw_exception_handler.S 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/init_task.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/intc.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/irq.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/microblaze_ksyms.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/module.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/of_device.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/of_platform.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/process.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/prom.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/prom_parse.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/ptrace.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/selfmod.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/setup.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/signal.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/sys_microblaze.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/syscall_table.S 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/timer.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/traps.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/kernel/vmlinux.lds.S 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/checksum.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/fastcopy.S 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/memcpy.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/memmove.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/memset.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/lib/uaccess.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/mm/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/mm/init.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/platform/Kconfig.platform 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/platform/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/platform/generic/Kconfig.auto 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/platform/generic/Makefile 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/platform/generic/system.dts 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/microblaze/platform/platform.c 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/kernel/cevt-txx9.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/kernel/csrc-bcm1480.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/kernel/csrc-ioasic.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/kernel/csrc-r4k.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/kernel/csrc-sb1250.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/kernel/i8253.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/nxp/pnx8550/common/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/rb532/devices.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mips/sgi-ip27/ip27-timer.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/Makefile
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/cputime.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/emergency-restart.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/errno.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/fcntl.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/futex.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/ioctl.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/ipc.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/local.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/percpu.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/poll.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/resource.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/statfs.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/include/asm/xor.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/entry.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/gdb-io-serial.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/gdb-io-ttysm.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/gdb-stub.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/irq.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/setup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/traps.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/oprofile/Kconfig 已删除 100644 → 0
浏览文件 @ 1130b029
此差异已折叠。
arch/mn10300/unit-asb2303/leds.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/mn10300/unit-asb2305/leds.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/4xx.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/gef_ppc9a.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/lite5200b.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/tqm8540.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/tqm8541.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/tqm8548.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/tqm8555.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/boot/dts/tqm8560.dts
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/include/asm/elf.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/include/asm/futex.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/include/asm/parport.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/include/asm/ppc_asm.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/head_32.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/head_40x.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/head_44x.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/head_8xx.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/mm/tlb_nohash.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/mm/tlb_nohash_low.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/platforms/cell/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/platforms/ps3/setup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/powerpc/sysdev/fsl_rio.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/appldata/appldata_mem.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/cpuid.h 0 → 100644
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/cputime.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/kvm_host.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/lowcore.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/processor.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/ptrace.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/setup.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/thread_info.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/timer.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/timex.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/include/asm/unistd.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/asm-offsets.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/compat_wrapper.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/early.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/entry.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/entry64.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/ipl.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/nmi.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/syscalls.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/s390/kernel/vtime.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/boards/board-ap325rxa.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/boards/board-urquell.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/configs/sh7785lcr_defconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/drivers/pci/ops-sh7785lcr.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/drivers/pci/pci-sh7780.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/drivers/pci/pci.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/include/asm/dma-mapping.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/include/asm/ptrace.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/include/asm/scatterlist.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/include/asm/topology.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/include/asm/unistd_32.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/include/asm/unistd_64.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/cpu/sh5/entry.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/head_32.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/head_64.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/sys_sh.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/syscalls_32.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/syscalls_64.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/time_32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/timers/timer-tmu.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/vmlinux_32.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/kernel/vmlinux_64.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sh/mm/consistent.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/include/asm/atomic_32.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/include/asm/parport.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/include/asm/unistd.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/head_32.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/head_64.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/ldc.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/of_device_32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/of_device_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/pci_fire.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/pci_psycho.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/pci_sabre.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/pci_sun4v.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/power.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/smp_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/sys_sparc32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/systbls_32.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/systbls_64.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/time_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/sparc/mm/init_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/um/Kconfig.rest
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/um/kernel/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/Kconfig
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/Kconfig.cpu
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/Makefile
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/boot/video-vga.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/ia32/sys_ia32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/cpu_debug.h 100755 → 100644
浏览文件 @ e7fd5d4b
文件模式从 100755 更改为 100644
arch/x86/include/asm/cpufeature.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/desc.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/fixmap.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/hardirq.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/io.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/lguest_hcall.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/paravirt.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/pat.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/processor.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/sigcontext.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/tlbflush.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/topology.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/uv/uv_mmrs.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/xen/page.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/include/asm/xsave.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/apic/apic.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/apic/apic_flat_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/apic/io_apic.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/apic/nmi.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/apic/x2apic_uv_x.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/bios_uv.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/cpu/cpu_debug.c 100755 → 100644
浏览文件 @ e7fd5d4b
文件模式从 100755 更改为 100644
arch/x86/kernel/entry_64.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/ftrace.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/hpet.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/i8253.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/irq.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/kvmclock.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/microcode_core.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/mpparse.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/pci-swiotlb.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/ptrace.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/quirks.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/reboot.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/tlb_uv.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/tsc.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/uv_sysfs.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/uv_time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/vmiclock_32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kernel/xsave.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kvm/mmu.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/kvm/x86.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/lguest/boot.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/gup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/ioremap.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/numa_32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/numa_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/pageattr.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/pat.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/pgtable.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/mm/srat_64.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/pci/amd_bus.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/pci/common.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/pci/i386.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/pci/mmconfig-shared.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/xen/enlighten.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/xen/mmu.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/xen/mmu.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/xen/smp.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/xen/time.c
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/x86/xen/xen-ops.h
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/xtensa/kernel/head.S
浏览文件 @ e7fd5d4b
此差异已折叠。
arch/xtensa/kernel/vmlinux.lds.S
浏览文件 @ e7fd5d4b
此差异已折叠。
block/as-iosched.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk-barrier.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk-core.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk-merge.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk-settings.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk-sysfs.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk-timeout.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/blk.h
浏览文件 @ e7fd5d4b
此差异已折叠。
block/cfq-iosched.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/elevator.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/genhd.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/ioctl.c
浏览文件 @ e7fd5d4b
此差异已折叠。
block/scsi_ioctl.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/acpica/hwsleep.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/acpica/hwvalid.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/acpica/rscreate.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/button.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/ec.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/osl.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/proc.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/processor_idle.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/scan.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/sleep.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/sleep.h
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/system.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/thermal.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/video.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/acpi/wakeup.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/ahci.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/libata-core.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/libata-scsi.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/libata-sff.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/pata_hpt37x.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/pata_legacy.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/pata_ninja32.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/pata_via.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/sata_mv.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/ata/sata_via.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/atm/solos-pci.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/base/base.h
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/base/core.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/base/dd.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/base/platform.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/brd.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/cciss.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/hd.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/mg_disk.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/ub.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/umem.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/block/xsysace.c
浏览文件 @ e7fd5d4b
此差异已折叠。
drivers/char/agp/generic.c
浏览文件 @ e7fd5d4b
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或