Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 2dc94310 编写于 作者: R Russell King 提交者： Russell King
浏览文件
操作

Merge master.kernel.org:/pub/scm/linux/kernel/git/tmlind/linux-omap-upstream into devel

上级 c0601514 fb60cf4a
展开全部 隐藏空白更改
内联 并排
Showing with 126604 addition and 47192 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ 2dc94310
......@@ -2384,6 +2384,13 @@ N: Thomas Molina
E: tmolina@cablespeed.com
D: bug fixes, documentation, minor hackery
N: Paul Moore
E: paul.moore@hp.com
D: NetLabel author
S: Hewlett-Packard
S: 110 Spit Brook Road
S: Nashua, NH 03062
N: James Morris
E: jmorris@namei.org
W: http://namei.org/
......
Documentation/00-INDEX
浏览文件 @ 2dc94310
......@@ -184,6 +184,8 @@ mtrr.txt
- how to use PPro Memory Type Range Registers to increase performance.
nbd.txt
- info on a TCP implementation of a network block device.
netlabel/
- directory with information on the NetLabel subsystem.
networking/
- directory with info on various aspects of networking with Linux.
nfsroot.txt
......
Documentation/Changes
浏览文件 @ 2dc94310
......@@ -37,15 +37,14 @@ o e2fsprogs 1.29 # tune2fs
o jfsutils 1.1.3 # fsck.jfs -V
o reiserfsprogs 3.6.3 # reiserfsck -V 2>&1|grep reiserfsprogs
o xfsprogs 2.6.0 # xfs_db -V
o pcmciautils 004
o pcmcia-cs 3.1.21 # cardmgr -V
o pcmciautils 004 # pccardctl -V
o quota-tools 3.09 # quota -V
o PPP 2.4.0 # pppd --version
o isdn4k-utils 3.1pre1 # isdnctrl 2>&1|grep version
o nfs-utils 1.0.5 # showmount --version
o procps 3.2.0 # ps --version
o oprofile 0.9 # oprofiled --version
o udev 071 # udevinfo -V
o udev 081 # udevinfo -V
Kernel compilation
==================
......@@ -268,7 +267,7 @@ active clients.
To enable this new functionality, you need to:
mount -t nfsd nfsd /proc/fs/nfs
mount -t nfsd nfsd /proc/fs/nfsd
before running exportfs or mountd. It is recommended that all NFS
services be protected from the internet-at-large by a firewall where
......
Documentation/DocBook/libata.tmpl
浏览文件 @ 2dc94310
......@@ -868,18 +868,18 @@ and other resources, etc.
<chapter id="libataExt">
<title>libata Library</title>
!Edrivers/scsi/libata-core.c
!Edrivers/ata/libata-core.c
</chapter>
<chapter id="libataInt">
<title>libata Core Internals</title>
!Idrivers/scsi/libata-core.c
!Idrivers/ata/libata-core.c
</chapter>
<chapter id="libataScsiInt">
<title>libata SCSI translation/emulation</title>
!Edrivers/scsi/libata-scsi.c
!Idrivers/scsi/libata-scsi.c
!Edrivers/ata/libata-scsi.c
!Idrivers/ata/libata-scsi.c
</chapter>
<chapter id="ataExceptions">
......@@ -1600,12 +1600,12 @@ and other resources, etc.
<chapter id="PiixInt">
<title>ata_piix Internals</title>
!Idrivers/scsi/ata_piix.c
!Idrivers/ata/ata_piix.c
</chapter>
<chapter id="SILInt">
<title>sata_sil Internals</title>
!Idrivers/scsi/sata_sil.c
!Idrivers/ata/sata_sil.c
</chapter>
<chapter id="libataThanks">
......
Documentation/crypto/api-intro.txt
浏览文件 @ 2dc94310
......@@ -19,15 +19,14 @@ At the lowest level are algorithms, which register dynamically with the
API.
'Transforms' are user-instantiated objects, which maintain state, handle all
of the implementation logic (e.g. manipulating page vectors), provide an
abstraction to the underlying algorithms, and handle common logical
operations (e.g. cipher modes, HMAC for digests). However, at the user
of the implementation logic (e.g. manipulating page vectors) and provide an
abstraction to the underlying algorithms. However, at the user
level they are very simple.
Conceptually, the API layering looks like this:
[transform api] (user interface)
[transform ops] (per-type logic glue e.g. cipher.c, digest.c)
[transform ops] (per-type logic glue e.g. cipher.c, compress.c)
[algorithm api] (for registering algorithms)
The idea is to make the user interface and algorithm registration API
......@@ -44,22 +43,27 @@ under development.
Here's an example of how to use the API:
#include <linux/crypto.h>
#include <linux/err.h>
#include <linux/scatterlist.h>
struct scatterlist sg[2];
char result[128];
struct crypto_tfm *tfm;
struct crypto_hash *tfm;
struct hash_desc desc;
tfm = crypto_alloc_tfm("md5", 0);
if (tfm == NULL)
tfm = crypto_alloc_hash("md5", 0, CRYPTO_ALG_ASYNC);
if (IS_ERR(tfm))
fail();
/* ... set up the scatterlists ... */
desc.tfm = tfm;
desc.flags = 0;
crypto_digest_init(tfm);
crypto_digest_update(tfm, &sg, 2);
crypto_digest_final(tfm, result);
if (crypto_hash_digest(&desc, &sg, 2, result))
fail();
crypto_free_tfm(tfm);
crypto_free_hash(tfm);
Many real examples are available in the regression test module (tcrypt.c).
......@@ -126,7 +130,7 @@ might already be working on.
BUGS
Send bug reports to:
James Morris <jmorris@redhat.com>
Herbert Xu <herbert@gondor.apana.org.au>
Cc: David S. Miller <davem@redhat.com>
......@@ -134,13 +138,14 @@ FURTHER INFORMATION
For further patches and various updates, including the current TODO
list, see:
http://samba.org/~jamesm/crypto/
http://gondor.apana.org.au/~herbert/crypto/
AUTHORS
James Morris
David S. Miller
Herbert Xu
CREDITS
......@@ -238,8 +243,11 @@ Anubis algorithm contributors:
Tiger algorithm contributors:
Aaron Grothe
VIA PadLock contributors:
Michal Ludvig
Generic scatterwalk code by Adam J. Richter <adam@yggdrasil.com>
Please send any credits updates or corrections to:
James Morris <jmorris@redhat.com>
Herbert Xu <herbert@gondor.apana.org.au>
Documentation/dontdiff
浏览文件 @ 2dc94310
......@@ -135,6 +135,7 @@ tags
times.h*
tkparse
trix_boot.h
utsrelease.h*
version.h*
vmlinux
vmlinux-*
......
Documentation/kbuild/kconfig-language.txt
浏览文件 @ 2dc94310
......@@ -67,19 +67,19 @@ applicable everywhere (see syntax).
- default value: "default" <expr> ["if" <expr>]
A config option can have any number of default values. If multiple
default values are visible, only the first defined one is active.
Default values are not limited to the menu entry, where they are
defined, this means the default can be defined somewhere else or be
Default values are not limited to the menu entry where they are
defined. This means the default can be defined somewhere else or be
overridden by an earlier definition.
The default value is only assigned to the config symbol if no other
value was set by the user (via the input prompt above). If an input
prompt is visible the default value is presented to the user and can
be overridden by him.
Optionally dependencies only for this default value can be added with
Optionally, dependencies only for this default value can be added with
"if".
- dependencies: "depends on"/"requires" <expr>
This defines a dependency for this menu entry. If multiple
dependencies are defined they are connected with '&&'. Dependencies
dependencies are defined, they are connected with '&&'. Dependencies
are applied to all other options within this menu entry (which also
accept an "if" expression), so these two examples are equivalent:
......@@ -153,7 +153,7 @@ Nonconstant symbols are the most common ones and are defined with the
'config' statement. Nonconstant symbols consist entirely of alphanumeric
characters or underscores.
Constant symbols are only part of expressions. Constant symbols are
always surrounded by single or double quotes. Within the quote any
always surrounded by single or double quotes. Within the quote, any
other character is allowed and the quotes can be escaped using '\'.
Menu structure
......@@ -237,7 +237,7 @@ choices:
<choice block>
"endchoice"
This defines a choice group and accepts any of above attributes as
This defines a choice group and accepts any of the above attributes as
options. A choice can only be of type bool or tristate, while a boolean
choice only allows a single config entry to be selected, a tristate
choice also allows any number of config entries to be set to 'm'. This
......
Documentation/kbuild/makefiles.txt
浏览文件 @ 2dc94310
此差异已折叠。
Documentation/kbuild/modules.txt
浏览文件 @ 2dc94310
In this document you will find information about:
- how to build external modules
- how to make your module use kbuild infrastructure
- how to make your module use the kbuild infrastructure
- how kbuild will install a kernel
- how to install modules in a non-standard location
......@@ -24,7 +24,7 @@ In this document you will find information about:
--- 6.1 INSTALL_MOD_PATH
--- 6.2 INSTALL_MOD_DIR
=== 7. Module versioning & Module.symvers
--- 7.1 Symbols fron the kernel (vmlinux + modules)
--- 7.1 Symbols from the kernel (vmlinux + modules)
--- 7.2 Symbols and external modules
--- 7.3 Symbols from another external module
=== 8. Tips & Tricks
......@@ -36,13 +36,13 @@ In this document you will find information about:
kbuild includes functionality for building modules both
within the kernel source tree and outside the kernel source tree.
The latter is usually referred to as external modules and is used
both during development and for modules that are not planned to be
included in the kernel tree.
The latter is usually referred to as external or "out-of-tree"
modules and is used both during development and for modules that
are not planned to be included in the kernel tree.
What is covered within this file is mainly information to authors
of modules. The author of an external modules should supply
a makefile that hides most of the complexity so one only has to type
of modules. The author of an external module should supply
a makefile that hides most of the complexity, so one only has to type
'make' to build the module. A complete example will be present in
chapter 4, "Creating a kbuild file for an external module".
......@@ -63,14 +63,15 @@ when building an external module.
For the running kernel use:
make -C /lib/modules/`uname -r`/build M=`pwd`
For the above command to succeed the kernel must have been built with
modules enabled.
For the above command to succeed, the kernel must have been
built with modules enabled.
To install the modules that were just built:
make -C <path-to-kernel> M=`pwd` modules_install
More complex examples later, the above should get you going.
More complex examples will be shown later, the above should
be enough to get you started.
--- 2.2 Available targets
......@@ -89,13 +90,13 @@ when building an external module.
Same functionality as if no target was specified.
See description above.
make -C $KDIR M=$PWD modules_install
make -C $KDIR M=`pwd` modules_install
Install the external module(s).
Installation default is in /lib/modules/<kernel-version>/extra,
but may be prefixed with INSTALL_MOD_PATH - see separate
chapter.
make -C $KDIR M=$PWD clean
make -C $KDIR M=`pwd` clean
Remove all generated files for the module - the kernel
source directory is not modified.
......@@ -129,29 +130,28 @@ when building an external module.
To make sure the kernel contains the information required to
build external modules the target 'modules_prepare' must be used.
'module_prepare' solely exists as a simple way to prepare
a kernel for building external modules.
'module_prepare' exists solely as a simple way to prepare
a kernel source tree for building external modules.
Note: modules_prepare will not build Module.symvers even if
CONFIG_MODULEVERSIONING is set.
Therefore a full kernel build needs to be executed to make
module versioning work.
CONFIG_MODULEVERSIONING is set. Therefore a full kernel build
needs to be executed to make module versioning work.
--- 2.5 Building separate files for a module
It is possible to build single files which is part of a module.
This works equal for the kernel, a module and even for external
modules.
It is possible to build single files which are part of a module.
This works equally well for the kernel, a module and even for
external modules.
Examples (module foo.ko, consist of bar.o, baz.o):
make -C $KDIR M=`pwd` bar.lst
make -C $KDIR M=`pwd` bar.o
make -C $KDIR M=`pwd` foo.ko
make -C $KDIR M=`pwd` /
=== 3. Example commands
This example shows the actual commands to be executed when building
an external module for the currently running kernel.
In the example below the distribution is supposed to use the
In the example below, the distribution is supposed to use the
facility to locate output files for a kernel compile in a different
directory than the kernel source - but the examples will also work
when the source and the output files are mixed in the same directory.
......@@ -170,14 +170,14 @@ the following commands to build the module:
O=/lib/modules/`uname-r`/build \
M=`pwd`
Then to install the module use the following command:
Then, to install the module use the following command:
make -C /usr/src/`uname -r`/source \
O=/lib/modules/`uname-r`/build \
M=`pwd` \
modules_install
If one looks closely you will see that this is the same commands as
If you look closely you will see that this is the same command as
listed before - with the directories spelled out.
The above are rather long commands, and the following chapter
......@@ -230,7 +230,7 @@ following files:
endif
In example 1 the check for KERNELRELEASE is used to separate
In example 1, the check for KERNELRELEASE is used to separate
the two parts of the Makefile. kbuild will only see the two
assignments whereas make will see everything except the two
kbuild assignments.
......@@ -255,7 +255,7 @@ following files:
echo "X" > 8123_bin_shipped
In example 2 we are down to two fairly simple files and for simple
In example 2, we are down to two fairly simple files and for simple
files as used in this example the split is questionable. But some
external modules use Makefiles of several hundred lines and here it
really pays off to separate the kbuild part from the rest.
......@@ -282,9 +282,9 @@ following files:
endif
The trick here is to include the Kbuild file from Makefile so
if an older version of kbuild picks up the Makefile the Kbuild
file will be included.
The trick here is to include the Kbuild file from Makefile, so
if an older version of kbuild picks up the Makefile, the Kbuild
file will be included.
--- 4.2 Binary blobs included in a module
......@@ -301,18 +301,19 @@ following files:
obj-m := 8123.o
8123-y := 8123_if.o 8123_pci.o 8123_bin.o
In example 4 there is no distinction between the ordinary .c/.h files
In example 4, there is no distinction between the ordinary .c/.h files
and the binary file. But kbuild will pick up different rules to create
the .o file.
=== 5. Include files
Include files are a necessity when a .c file uses something from another .c
files (not strictly in the sense of .c but if good programming practice is
used). Any module that consist of more than one .c file will have a .h file
for one of the .c files.
- If the .h file only describes a module internal interface then the .h file
Include files are a necessity when a .c file uses something from other .c
files (not strictly in the sense of C, but if good programming practice is
used). Any module that consists of more than one .c file will have a .h file
for one of the .c files.
- If the .h file only describes a module internal interface, then the .h file
shall be placed in the same directory as the .c files.
- If the .h files describe an interface used by other parts of the kernel
located in different directories, the .h files shall be located in
......@@ -323,11 +324,11 @@ under include/ such as include/scsi. Another exception is arch-specific
.h files which are located under include/asm-$(ARCH)/*.
External modules have a tendency to locate include files in a separate include/
directory and therefore needs to deal with this in their kbuild file.
directory and therefore need to deal with this in their kbuild file.
--- 5.1 How to include files from the kernel include dir
When a module needs to include a file from include/linux/ then one
When a module needs to include a file from include/linux/, then one
just uses:
#include <linux/modules.h>
......@@ -348,7 +349,7 @@ directory and therefore needs to deal with this in their kbuild file.
The trick here is to use either EXTRA_CFLAGS (take effect for all .c
files) or CFLAGS_$F.o (take effect only for a single file).
In our example if we move 8123_if.h to a subdirectory named include/
In our example, if we move 8123_if.h to a subdirectory named include/
the resulting Kbuild file would look like:
--> filename: Kbuild
......@@ -362,19 +363,19 @@ directory and therefore needs to deal with this in their kbuild file.
--- 5.3 External modules using several directories
If an external module does not follow the usual kernel style but
decide to spread files over several directories then kbuild can
support this too.
If an external module does not follow the usual kernel style, but
decides to spread files over several directories, then kbuild can
handle this too.
Consider the following example:
|
+- src/complex_main.c
| +- hal/hardwareif.c
| +- hal/include/hardwareif.h
+- include/complex.h
To build a single module named complex.ko we then need the following
To build a single module named complex.ko, we then need the following
kbuild file:
Kbuild:
......@@ -387,12 +388,12 @@ directory and therefore needs to deal with this in their kbuild file.
kbuild knows how to handle .o files located in another directory -
although this is NOT reccommended practice. The syntax is to specify
although this is NOT recommended practice. The syntax is to specify
the directory relative to the directory where the Kbuild file is
located.
To find the .h files we have to explicitly tell kbuild where to look
for the .h files. When kbuild executes current directory is always
To find the .h files, we have to explicitly tell kbuild where to look
for the .h files. When kbuild executes, the current directory is always
the root of the kernel tree (argument to -C) and therefore we have to
tell kbuild how to find the .h files using absolute paths.
$(src) will specify the absolute path to the directory where the
......@@ -412,7 +413,7 @@ External modules are installed in the directory:
--- 6.1 INSTALL_MOD_PATH
Above are the default directories, but as always some level of
Above are the default directories, but as always, some level of
customization is possible. One can prefix the path using the variable
INSTALL_MOD_PATH:
......@@ -420,17 +421,17 @@ External modules are installed in the directory:
=> Install dir: /frodo/lib/modules/$(KERNELRELEASE)/kernel
INSTALL_MOD_PATH may be set as an ordinary shell variable or as in the
example above be specified on the command line when calling make.
example above, can be specified on the command line when calling make.
INSTALL_MOD_PATH has effect both when installing modules included in
the kernel as well as when installing external modules.
--- 6.2 INSTALL_MOD_DIR
When installing external modules they are default installed in a
When installing external modules they are by default installed to a
directory under /lib/modules/$(KERNELRELEASE)/extra, but one may wish
to locate modules for a specific functionality in a separate
directory. For this purpose one can use INSTALL_MOD_DIR to specify an
alternative name than 'extra'.
directory. For this purpose, one can use INSTALL_MOD_DIR to specify an
alternative name to 'extra'.
$ make INSTALL_MOD_DIR=gandalf -C KERNELDIR \
M=`pwd` modules_install
......@@ -444,16 +445,16 @@ Module versioning is enabled by the CONFIG_MODVERSIONS tag.
Module versioning is used as a simple ABI consistency check. The Module
versioning creates a CRC value of the full prototype for an exported symbol and
when a module is loaded/used then the CRC values contained in the kernel are
compared with similar values in the module. If they are not equal then the
compared with similar values in the module. If they are not equal, then the
kernel refuses to load the module.
Module.symvers contains a list of all exported symbols from a kernel build.
--- 7.1 Symbols fron the kernel (vmlinux + modules)
During a kernel build a file named Module.symvers will be generated.
During a kernel build, a file named Module.symvers will be generated.
Module.symvers contains all exported symbols from the kernel and
compiled modules. For each symbols the corresponding CRC value
compiled modules. For each symbols, the corresponding CRC value
is stored too.
The syntax of the Module.symvers file is:
......@@ -461,27 +462,27 @@ Module.symvers contains a list of all exported symbols from a kernel build.
Sample:
0x2d036834 scsi_remove_host drivers/scsi/scsi_mod
For a kernel build without CONFIG_MODVERSIONING enabled the crc
For a kernel build without CONFIG_MODVERSIONS enabled, the crc
would read: 0x00000000
Module.symvers serve two purposes.
1) It list all exported symbols both from vmlinux and all modules
2) It list CRC if CONFIG_MODVERSION is enabled
Module.symvers serves two purposes:
1) It lists all exported symbols both from vmlinux and all modules
2) It lists the CRC if CONFIG_MODVERSIONS is enabled
--- 7.2 Symbols and external modules
When building an external module the build system needs access to
When building an external module, the build system needs access to
the symbols from the kernel to check if all external symbols are
defined. This is done in the MODPOST step and to obtain all
symbols modpost reads Module.symvers from the kernel.
symbols, modpost reads Module.symvers from the kernel.
If a Module.symvers file is present in the directory where
the external module is being build this file will be read too.
During the MODPOST step a new Module.symvers file will be written
containing all exported symbols that was not defined in the kernel.
the external module is being built, this file will be read too.
During the MODPOST step, a new Module.symvers file will be written
containing all exported symbols that were not defined in the kernel.
--- 7.3 Symbols from another external module
Sometimes one external module uses exported symbols from another
Sometimes, an external module uses exported symbols from another
external module. Kbuild needs to have full knowledge on all symbols
to avoid spitting out warnings about undefined symbols.
Two solutions exist to let kbuild know all symbols of more than
......@@ -490,15 +491,15 @@ Module.symvers contains a list of all exported symbols from a kernel build.
impractical in certain situations.
Use a top-level Kbuild file
If you have two modules: 'foo', 'bar' and 'foo' needs symbols
from 'bar' then one can use a common top-level kbuild file so
both modules are compiled in same build.
If you have two modules: 'foo' and 'bar', and 'foo' needs
symbols from 'bar', then one can use a common top-level kbuild
file so both modules are compiled in same build.
Consider following directory layout:
./foo/ <= contains the foo module
./bar/ <= contains the bar module
The top-level Kbuild file would then look like:
#./Kbuild: (this file may also be named Makefile)
obj-y := foo/ bar/
......@@ -509,23 +510,23 @@ Module.symvers contains a list of all exported symbols from a kernel build.
knowledge on symbols from both modules.
Use an extra Module.symvers file
When an external module is build a Module.symvers file is
When an external module is built, a Module.symvers file is
generated containing all exported symbols which are not
defined in the kernel.
To get access to symbols from module 'bar' one can copy the
To get access to symbols from module 'bar', one can copy the
Module.symvers file from the compilation of the 'bar' module
to the directory where the 'foo' module is build.
During the module build kbuild will read the Module.symvers
to the directory where the 'foo' module is built.
During the module build, kbuild will read the Module.symvers
file in the directory of the external module and when the
build is finished a new Module.symvers file is created
build is finished, a new Module.symvers file is created
containing the sum of all symbols defined and not part of the
kernel.
=== 8. Tips & Tricks
--- 8.1 Testing for CONFIG_FOO_BAR
Modules often needs to check for certain CONFIG_ options to decide if
Modules often need to check for certain CONFIG_ options to decide if
a specific feature shall be included in the module. When kbuild is used
this is done by referencing the CONFIG_ variable directly.
......@@ -537,7 +538,7 @@ Module.symvers contains a list of all exported symbols from a kernel build.
External modules have traditionally used grep to check for specific
CONFIG_ settings directly in .config. This usage is broken.
As introduced before external modules shall use kbuild when building
and therefore can use the same methods as in-kernel modules when testing
for CONFIG_ definitions.
As introduced before, external modules shall use kbuild when building
and therefore can use the same methods as in-kernel modules when
testing for CONFIG_ definitions.
Documentation/netlabel/00-INDEX 0 → 100644
浏览文件 @ 2dc94310
00-INDEX
- this file.
cipso_ipv4.txt
- documentation on the IPv4 CIPSO protocol engine.
draft-ietf-cipso-ipsecurity-01.txt
- IETF draft of the CIPSO protocol, dated 16 July 1992.
introduction.txt
- NetLabel introduction, READ THIS FIRST.
lsm_interface.txt
- documentation on the NetLabel kernel security module API.
Documentation/netlabel/cipso_ipv4.txt 0 → 100644
浏览文件 @ 2dc94310
NetLabel CIPSO/IPv4 Protocol Engine
==============================================================================
Paul Moore, paul.moore@hp.com
May 17, 2006
* Overview
The NetLabel CIPSO/IPv4 protocol engine is based on the IETF Commercial IP
Security Option (CIPSO) draft from July 16, 1992. A copy of this draft can be
found in this directory, consult '00-INDEX' for the filename. While the IETF
draft never made it to an RFC standard it has become a de-facto standard for
labeled networking and is used in many trusted operating systems.
* Outbound Packet Processing
The CIPSO/IPv4 protocol engine applies the CIPSO IP option to packets by
adding the CIPSO label to the socket. This causes all packets leaving the
system through the socket to have the CIPSO IP option applied. The socket's
CIPSO label can be changed at any point in time, however, it is recommended
that it is set upon the socket's creation. The LSM can set the socket's CIPSO
label by using the NetLabel security module API; if the NetLabel "domain" is
configured to use CIPSO for packet labeling then a CIPSO IP option will be
generated and attached to the socket.
* Inbound Packet Processing
The CIPSO/IPv4 protocol engine validates every CIPSO IP option it finds at the
IP layer without any special handling required by the LSM. However, in order
to decode and translate the CIPSO label on the packet the LSM must use the
NetLabel security module API to extract the security attributes of the packet.
This is typically done at the socket layer using the 'socket_sock_rcv_skb()'
LSM hook.
* Label Translation
The CIPSO/IPv4 protocol engine contains a mechanism to translate CIPSO security
attributes such as sensitivity level and category to values which are
appropriate for the host. These mappings are defined as part of a CIPSO
Domain Of Interpretation (DOI) definition and are configured through the
NetLabel user space communication layer. Each DOI definition can have a
different security attribute mapping table.
* Label Translation Cache
The NetLabel system provides a framework for caching security attribute
mappings from the network labels to the corresponding LSM identifiers. The
CIPSO/IPv4 protocol engine supports this caching mechanism.
Documentation/netlabel/introduction.txt 0 → 100644
浏览文件 @ 2dc94310
NetLabel Introduction
==============================================================================
Paul Moore, paul.moore@hp.com
August 2, 2006
* Overview
NetLabel is a mechanism which can be used by kernel security modules to attach
security attributes to outgoing network packets generated from user space
applications and read security attributes from incoming network packets. It
is composed of three main components, the protocol engines, the communication
layer, and the kernel security module API.
* Protocol Engines
The protocol engines are responsible for both applying and retrieving the
network packet's security attributes. If any translation between the network
security attributes and those on the host are required then the protocol
engine will handle those tasks as well. Other kernel subsystems should
refrain from calling the protocol engines directly, instead they should use
the NetLabel kernel security module API described below.
Detailed information about each NetLabel protocol engine can be found in this
directory, consult '00-INDEX' for filenames.
* Communication Layer
The communication layer exists to allow NetLabel configuration and monitoring
from user space. The NetLabel communication layer uses a message based
protocol built on top of the Generic NETLINK transport mechanism. The exact
formatting of these NetLabel messages as well as the Generic NETLINK family
names can be found in the the 'net/netlabel/' directory as comments in the
header files as well as in 'include/net/netlabel.h'.
* Security Module API
The purpose of the NetLabel security module API is to provide a protocol
independent interface to the underlying NetLabel protocol engines. In addition
to protocol independence, the security module API is designed to be completely
LSM independent which should allow multiple LSMs to leverage the same code
base.
Detailed information about the NetLabel security module API can be found in the
'include/net/netlabel.h' header file as well as the 'lsm_interface.txt' file
found in this directory.
Documentation/netlabel/lsm_interface.txt 0 → 100644
浏览文件 @ 2dc94310
NetLabel Linux Security Module Interface
==============================================================================
Paul Moore, paul.moore@hp.com
May 17, 2006
* Overview
NetLabel is a mechanism which can set and retrieve security attributes from
network packets. It is intended to be used by LSM developers who want to make
use of a common code base for several different packet labeling protocols.
The NetLabel security module API is defined in 'include/net/netlabel.h' but a
brief overview is given below.
* NetLabel Security Attributes
Since NetLabel supports multiple different packet labeling protocols and LSMs
it uses the concept of security attributes to refer to the packet's security
labels. The NetLabel security attributes are defined by the
'netlbl_lsm_secattr' structure in the NetLabel header file. Internally the
NetLabel subsystem converts the security attributes to and from the correct
low-level packet label depending on the NetLabel build time and run time
configuration. It is up to the LSM developer to translate the NetLabel
security attributes into whatever security identifiers are in use for their
particular LSM.
* NetLabel LSM Protocol Operations
These are the functions which allow the LSM developer to manipulate the labels
on outgoing packets as well as read the labels on incoming packets. Functions
exist to operate both on sockets as well as the sk_buffs directly. These high
level functions are translated into low level protocol operations based on how
the administrator has configured the NetLabel subsystem.
* NetLabel Label Mapping Cache Operations
Depending on the exact configuration, translation between the network packet
label and the internal LSM security identifier can be time consuming. The
NetLabel label mapping cache is a caching mechanism which can be used to
sidestep much of this overhead once a mapping has been established. Once the
LSM has received a packet, used NetLabel to decode it's security attributes,
and translated the security attributes into a LSM internal identifier the LSM
can use the NetLabel caching functions to associate the LSM internal
identifier with the network packet's label. This means that in the future
when a incoming packet matches a cached value not only are the internal
NetLabel translation mechanisms bypassed but the LSM translation mechanisms are
bypassed as well which should result in a significant reduction in overhead.
Documentation/networking/LICENSE.qla3xxx 0 → 100644
浏览文件 @ 2dc94310
Copyright (c) 2003-2006 QLogic Corporation
QLogic Linux Networking HBA Driver
This program includes a device driver for Linux 2.6 that may be
distributed with QLogic hardware specific firmware binary file.
You may modify and redistribute the device driver code under the
GNU General Public License as published by the Free Software
Foundation (version 2 or a later version).
You may redistribute the hardware specific firmware binary file
under the following terms:
1. Redistribution of source code (only if applicable),
must retain the above copyright notice, this list of
conditions and the following disclaimer.
2. Redistribution in binary form must reproduce the above
copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
3. The name of QLogic Corporation may not be used to
endorse or promote products derived from this software
without specific prior written permission
REGARDLESS OF WHAT LICENSING MECHANISM IS USED OR APPLICABLE,
THIS PROGRAM IS PROVIDED BY QLOGIC CORPORATION "AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
USER ACKNOWLEDGES AND AGREES THAT USE OF THIS PROGRAM WILL NOT
CREATE OR GIVE GROUNDS FOR A LICENSE BY IMPLICATION, ESTOPPEL, OR
OTHERWISE IN ANY INTELLECTUAL PROPERTY RIGHTS (PATENT, COPYRIGHT,
TRADE SECRET, MASK WORK, OR OTHER PROPRIETARY RIGHT) EMBODIED IN
ANY OTHER QLOGIC HARDWARE OR SOFTWARE EITHER SOLELY OR IN
COMBINATION WITH THIS PROGRAM.
Documentation/networking/ip-sysctl.txt
浏览文件 @ 2dc94310
......@@ -375,6 +375,41 @@ tcp_slow_start_after_idle - BOOLEAN
be timed out after an idle period.
Default: 1
CIPSOv4 Variables:
cipso_cache_enable - BOOLEAN
If set, enable additions to and lookups from the CIPSO label mapping
cache. If unset, additions are ignored and lookups always result in a
miss. However, regardless of the setting the cache is still
invalidated when required when means you can safely toggle this on and
off and the cache will always be "safe".
Default: 1
cipso_cache_bucket_size - INTEGER
The CIPSO label cache consists of a fixed size hash table with each
hash bucket containing a number of cache entries. This variable limits
the number of entries in each hash bucket; the larger the value the
more CIPSO label mappings that can be cached. When the number of
entries in a given hash bucket reaches this limit adding new entries
causes the oldest entry in the bucket to be removed to make room.
Default: 10
cipso_rbm_optfmt - BOOLEAN
Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
the CIPSO draft specification (see Documentation/netlabel for details).
This means that when set the CIPSO tag will be padded with empty
categories in order to make the packet data 32-bit aligned.
Default: 0
cipso_rbm_structvalid - BOOLEAN
If set, do a very strict check of the CIPSO option when
ip_options_compile() is called. If unset, relax the checks done during
ip_options_compile(). Either way is "safe" as errors are caught else
where in the CIPSO processing code but setting this to 0 (False) should
result in less work (i.e. it should be faster) but could cause problems
with other implementations that require strict checking.
Default: 0
IP Variables:
ip_local_port_range - 2 INTEGERS
......@@ -730,6 +765,9 @@ conf/all/forwarding - BOOLEAN
This referred to as global forwarding.
proxy_ndp - BOOLEAN
Do proxy ndp.
conf/interface/*:
Change special settings per interface.
......
Documentation/networking/secid.txt 0 → 100644
浏览文件 @ 2dc94310
flowi structure:
The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
the label of the flow. This label of the flow is currently used in selecting
matching labeled xfrm(s).
If this is an outbound flow, the label is derived from the socket, if any, or
the incoming packet this flow is being generated as a response to (e.g. tcp
resets, timewait ack, etc.). It is also conceivable that the label could be
derived from other sources such as process context, device, etc., in special
cases, as may be appropriate.
If this is an inbound flow, the label is derived from the IPSec security
associations, if any, used by the packet.
Documentation/scsi/ChangeLog.arcmsr 0 → 100644
浏览文件 @ 2dc94310
**************************************************************************
** History
**
** REV# DATE NAME DESCRIPTION
** 1.00.00.00 3/31/2004 Erich Chen First release
** 1.10.00.04 7/28/2004 Erich Chen modify for ioctl
** 1.10.00.06 8/28/2004 Erich Chen modify for 2.6.x
** 1.10.00.08 9/28/2004 Erich Chen modify for x86_64
** 1.10.00.10 10/10/2004 Erich Chen bug fix for SMP & ioctl
** 1.20.00.00 11/29/2004 Erich Chen bug fix with arcmsr_bus_reset when PHY error
** 1.20.00.02 12/09/2004 Erich Chen bug fix with over 2T bytes RAID Volume
** 1.20.00.04 1/09/2005 Erich Chen fits for Debian linux kernel version 2.2.xx
** 1.20.00.05 2/20/2005 Erich Chen cleanly as look like a Linux driver at 2.6.x
** thanks for peoples kindness comment
** Kornel Wieliczek
** Christoph Hellwig
** Adrian Bunk
** Andrew Morton
** Christoph Hellwig
** James Bottomley
** Arjan van de Ven
** 1.20.00.06 3/12/2005 Erich Chen fix with arcmsr_pci_unmap_dma "unsigned long" cast,
** modify PCCB POOL allocated by "dma_alloc_coherent"
** (Kornel Wieliczek's comment)
** 1.20.00.07 3/23/2005 Erich Chen bug fix with arcmsr_scsi_host_template_init
** occur segmentation fault,
** if RAID adapter does not on PCI slot
** and modprobe/rmmod this driver twice.
** bug fix enormous stack usage (Adrian Bunk's comment)
** 1.20.00.08 6/23/2005 Erich Chen bug fix with abort command,
** in case of heavy loading when sata cable
** working on low quality connection
** 1.20.00.09 9/12/2005 Erich Chen bug fix with abort command handling, firmware version check
** and firmware update notify for hardware bug fix
** 1.20.00.10 9/23/2005 Erich Chen enhance sysfs function for change driver's max tag Q number.
** add DMA_64BIT_MASK for backward compatible with all 2.6.x
** add some useful message for abort command
** add ioctl code 'ARCMSR_IOCTL_FLUSH_ADAPTER_CACHE'
** customer can send this command for sync raid volume data
** 1.20.00.11 9/29/2005 Erich Chen by comment of Arjan van de Ven fix incorrect msleep redefine
** cast off sizeof(dma_addr_t) condition for 64bit pci_set_dma_mask
** 1.20.00.12 9/30/2005 Erich Chen bug fix with 64bit platform's ccbs using if over 4G system memory
** change 64bit pci_set_consistent_dma_mask into 32bit
** increcct adapter count if adapter initialize fail.
** miss edit at arcmsr_build_ccb....
** psge += sizeof(struct _SG64ENTRY *) =>
** psge += sizeof(struct _SG64ENTRY)
** 64 bits sg entry would be incorrectly calculated
** thanks Kornel Wieliczek give me kindly notify
** and detail description
** 1.20.00.13 11/15/2005 Erich Chen scheduling pending ccb with FIFO
** change the architecture of arcmsr command queue list
** for linux standard list
** enable usage of pci message signal interrupt
** follow Randy.Danlup kindness suggestion cleanup this code
**************************************************************************
\ No newline at end of file
Documentation/scsi/aacraid.txt
浏览文件 @ 2dc94310
......@@ -11,38 +11,43 @@ the original).
Supported Cards/Chipsets
-------------------------
PCI ID (pci.ids) OEM Product
9005:0285:9005:028a Adaptec 2020ZCR (Skyhawk)
9005:0285:9005:028e Adaptec 2020SA (Skyhawk)
9005:0285:9005:028b Adaptec 2025ZCR (Terminator)
9005:0285:9005:028f Adaptec 2025SA (Terminator)
9005:0285:9005:0286 Adaptec 2120S (Crusader)
9005:0286:9005:028d Adaptec 2130S (Lancer)
9005:0283:9005:0283 Adaptec Catapult (3210S with arc firmware)
9005:0284:9005:0284 Adaptec Tomcat (3410S with arc firmware)
9005:0285:9005:0285 Adaptec 2200S (Vulcan)
9005:0285:9005:0286 Adaptec 2120S (Crusader)
9005:0285:9005:0287 Adaptec 2200S (Vulcan-2m)
9005:0285:9005:0288 Adaptec 3230S (Harrier)
9005:0285:9005:0289 Adaptec 3240S (Tornado)
9005:0285:9005:028a Adaptec 2020ZCR (Skyhawk)
9005:0285:9005:028b Adaptec 2025ZCR (Terminator)
9005:0286:9005:028c Adaptec 2230S (Lancer)
9005:0286:9005:028c Adaptec 2230SLP (Lancer)
9005:0285:9005:0296 Adaptec 2240S (SabreExpress)
9005:0286:9005:028d Adaptec 2130S (Lancer)
9005:0285:9005:028e Adaptec 2020SA (Skyhawk)
9005:0285:9005:028f Adaptec 2025SA (Terminator)
9005:0285:9005:0290 Adaptec 2410SA (Jaguar)
9005:0285:9005:0293 Adaptec 21610SA (Corsair-16)
9005:0285:103c:3227 Adaptec 2610SA (Bearcat HP release)
9005:0285:9005:0293 Adaptec 21610SA (Corsair-16)
9005:0285:9005:0296 Adaptec 2240S (SabreExpress)
9005:0285:9005:0292 Adaptec 2810SA (Corsair-8)
9005:0285:9005:0294 Adaptec Prowler
9005:0286:9005:029d Adaptec 2420SA (Intruder HP release)
9005:0286:9005:029c Adaptec 2620SA (Intruder)
9005:0286:9005:029b Adaptec 2820SA (Intruder)
9005:0286:9005:02a7 Adaptec 2830SA (Skyray)
9005:0286:9005:02a8 Adaptec 2430SA (Skyray)
9005:0285:9005:0288 Adaptec 3230S (Harrier)
9005:0285:9005:0289 Adaptec 3240S (Tornado)
9005:0285:9005:0298 Adaptec 4000SAS (BlackBird)
9005:0285:9005:0297 Adaptec 4005SAS (AvonPark)
9005:0285:9005:0298 Adaptec 4000SAS (BlackBird)
9005:0285:9005:0299 Adaptec 4800SAS (Marauder-X)
9005:0285:9005:029a Adaptec 4805SAS (Marauder-E)
9005:0286:9005:029b Adaptec 2820SA (Intruder)
9005:0286:9005:029c Adaptec 2620SA (Intruder)
9005:0286:9005:029d Adaptec 2420SA (Intruder HP release)
9005:0286:9005:02a2 Adaptec 3800SAS (Hurricane44)
9005:0286:9005:02a7 Adaptec 3805SAS (Hurricane80)
9005:0286:9005:02a8 Adaptec 3400SAS (Hurricane40)
9005:0286:9005:02ac Adaptec 1800SAS (Typhoon44)
9005:0286:9005:02b3 Adaptec 2400SAS (Hurricane40lm)
9005:0285:9005:02b5 Adaptec ASR5800 (Voodoo44)
9005:0285:9005:02b6 Adaptec ASR5805 (Voodoo80)
9005:0285:9005:02b7 Adaptec ASR5808 (Voodoo08)
1011:0046:9005:0364 Adaptec 5400S (Mustang)
1011:0046:9005:0365 Adaptec 5400S (Mustang)
9005:0283:9005:0283 Adaptec Catapult (3210S with arc firmware)
9005:0284:9005:0284 Adaptec Tomcat (3410S with arc firmware)
9005:0287:9005:0800 Adaptec Themisto (Jupiter)
9005:0200:9005:0200 Adaptec Themisto (Jupiter)
9005:0286:9005:0800 Adaptec Callisto (Jupiter)
......@@ -64,18 +69,20 @@ Supported Cards/Chipsets
9005:0285:9005:0290 IBM ServeRAID 7t (Jaguar)
9005:0285:1014:02F2 IBM ServeRAID 8i (AvonPark)
9005:0285:1014:0312 IBM ServeRAID 8i (AvonParkLite)
9005:0286:1014:9580 IBM ServeRAID 8k/8k-l8 (Aurora)
9005:0286:1014:9540 IBM ServeRAID 8k/8k-l4 (AuroraLite)
9005:0286:9005:029f ICP ICP9014R0 (Lancer)
9005:0286:1014:9580 IBM ServeRAID 8k/8k-l8 (Aurora)
9005:0286:1014:034d IBM ServeRAID 8s (Hurricane)
9005:0286:9005:029e ICP ICP9024R0 (Lancer)
9005:0286:9005:029f ICP ICP9014R0 (Lancer)
9005:0286:9005:02a0 ICP ICP9047MA (Lancer)
9005:0286:9005:02a1 ICP ICP9087MA (Lancer)
9005:0286:9005:02a3 ICP ICP5445AU (Hurricane44)
9005:0286:9005:02a4 ICP ICP9085LI (Marauder-X)
9005:0286:9005:02a5 ICP ICP5085BR (Marauder-E)
9005:0286:9005:02a3 ICP ICP5445AU (Hurricane44)
9005:0286:9005:02a6 ICP ICP9067MA (Intruder-6)
9005:0286:9005:02a9 ICP ICP5087AU (Skyray)
9005:0286:9005:02aa ICP ICP5047AU (Skyray)
9005:0286:9005:02a9 ICP ICP5085AU (Hurricane80)
9005:0286:9005:02aa ICP ICP5045AU (Hurricane40)
9005:0286:9005:02b4 ICP ICP5045AL (Hurricane40lm)
People
-------------------------
......
Documentation/scsi/arcmsr_spec.txt 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
Documentation/scsi/libsas.txt 0 → 100644
浏览文件 @ 2dc94310
SAS Layer
---------
The SAS Layer is a management infrastructure which manages
SAS LLDDs. It sits between SCSI Core and SAS LLDDs. The
layout is as follows: while SCSI Core is concerned with
SAM/SPC issues, and a SAS LLDD+sequencer is concerned with
phy/OOB/link management, the SAS layer is concerned with:
* SAS Phy/Port/HA event management (LLDD generates,
SAS Layer processes),
* SAS Port management (creation/destruction),
* SAS Domain discovery and revalidation,
* SAS Domain device management,
* SCSI Host registration/unregistration,
* Device registration with SCSI Core (SAS) or libata
(SATA), and
* Expander management and exporting expander control
to user space.
A SAS LLDD is a PCI device driver. It is concerned with
phy/OOB management, and vendor specific tasks and generates
events to the SAS layer.
The SAS Layer does most SAS tasks as outlined in the SAS 1.1
spec.
The sas_ha_struct describes the SAS LLDD to the SAS layer.
Most of it is used by the SAS Layer but a few fields need to
be initialized by the LLDDs.
After initializing your hardware, from the probe() function
you call sas_register_ha(). It will register your LLDD with
the SCSI subsystem, creating a SCSI host and it will
register your SAS driver with the sysfs SAS tree it creates.
It will then return. Then you enable your phys to actually
start OOB (at which point your driver will start calling the
notify_* event callbacks).
Structure descriptions:
struct sas_phy --------------------
Normally this is statically embedded to your driver's
phy structure:
struct my_phy {
blah;
struct sas_phy sas_phy;
bleh;
};
And then all the phys are an array of my_phy in your HA
struct (shown below).
Then as you go along and initialize your phys you also
initialize the sas_phy struct, along with your own
phy structure.
In general, the phys are managed by the LLDD and the ports
are managed by the SAS layer. So the phys are initialized
and updated by the LLDD and the ports are initialized and
updated by the SAS layer.
There is a scheme where the LLDD can RW certain fields,
and the SAS layer can only read such ones, and vice versa.
The idea is to avoid unnecessary locking.
enabled -- must be set (0/1)
id -- must be set [0,MAX_PHYS)
class, proto, type, role, oob_mode, linkrate -- must be set
oob_mode -- you set this when OOB has finished and then notify
the SAS Layer.
sas_addr -- this normally points to an array holding the sas
address of the phy, possibly somewhere in your my_phy
struct.
attached_sas_addr -- set this when you (LLDD) receive an
IDENTIFY frame or a FIS frame, _before_ notifying the SAS
layer. The idea is that sometimes the LLDD may want to fake
or provide a different SAS address on that phy/port and this
allows it to do this. At best you should copy the sas
address from the IDENTIFY frame or maybe generate a SAS
address for SATA directly attached devices. The Discover
process may later change this.
frame_rcvd -- this is where you copy the IDENTIFY/FIS frame
when you get it; you lock, copy, set frame_rcvd_size and
unlock the lock, and then call the event. It is a pointer
since there's no way to know your hw frame size _exactly_,
so you define the actual array in your phy struct and let
this pointer point to it. You copy the frame from your
DMAable memory to that area holding the lock.
sas_prim -- this is where primitives go when they're
received. See sas.h. Grab the lock, set the primitive,
release the lock, notify.
port -- this points to the sas_port if the phy belongs
to a port -- the LLDD only reads this. It points to the
sas_port this phy is part of. Set by the SAS Layer.
ha -- may be set; the SAS layer sets it anyway.
lldd_phy -- you should set this to point to your phy so you
can find your way around faster when the SAS layer calls one
of your callbacks and passes you a phy. If the sas_phy is
embedded you can also use container_of -- whatever you
prefer.
struct sas_port --------------------
The LLDD doesn't set any fields of this struct -- it only
reads them. They should be self explanatory.
phy_mask is 32 bit, this should be enough for now, as I
haven't heard of a HA having more than 8 phys.
lldd_port -- I haven't found use for that -- maybe other
LLDD who wish to have internal port representation can make
use of this.
struct sas_ha_struct --------------------
It normally is statically declared in your own LLDD
structure describing your adapter:
struct my_sas_ha {
blah;
struct sas_ha_struct sas_ha;
struct my_phy phys[MAX_PHYS];
struct sas_port sas_ports[MAX_PHYS]; /* (1) */
bleh;
};
(1) If your LLDD doesn't have its own port representation.
What needs to be initialized (sample function given below).
pcidev
sas_addr -- since the SAS layer doesn't want to mess with
memory allocation, etc, this points to statically
allocated array somewhere (say in your host adapter
structure) and holds the SAS address of the host
adapter as given by you or the manufacturer, etc.
sas_port
sas_phy -- an array of pointers to structures. (see
note above on sas_addr).
These must be set. See more notes below.
num_phys -- the number of phys present in the sas_phy array,
and the number of ports present in the sas_port
array. There can be a maximum num_phys ports (one per
port) so we drop the num_ports, and only use
num_phys.
The event interface:
/* LLDD calls these to notify the class of an event. */
void (*notify_ha_event)(struct sas_ha_struct *, enum ha_event);
void (*notify_port_event)(struct sas_phy *, enum port_event);
void (*notify_phy_event)(struct sas_phy *, enum phy_event);
When sas_register_ha() returns, those are set and can be
called by the LLDD to notify the SAS layer of such events
the SAS layer.
The port notification:
/* The class calls these to notify the LLDD of an event. */
void (*lldd_port_formed)(struct sas_phy *);
void (*lldd_port_deformed)(struct sas_phy *);
If the LLDD wants notification when a port has been formed
or deformed it sets those to a function satisfying the type.
A SAS LLDD should also implement at least one of the Task
Management Functions (TMFs) described in SAM:
/* Task Management Functions. Must be called from process context. */
int (*lldd_abort_task)(struct sas_task *);
int (*lldd_abort_task_set)(struct domain_device *, u8 *lun);
int (*lldd_clear_aca)(struct domain_device *, u8 *lun);
int (*lldd_clear_task_set)(struct domain_device *, u8 *lun);
int (*lldd_I_T_nexus_reset)(struct domain_device *);
int (*lldd_lu_reset)(struct domain_device *, u8 *lun);
int (*lldd_query_task)(struct sas_task *);
For more information please read SAM from T10.org.
Port and Adapter management:
/* Port and Adapter management */
int (*lldd_clear_nexus_port)(struct sas_port *);
int (*lldd_clear_nexus_ha)(struct sas_ha_struct *);
A SAS LLDD should implement at least one of those.
Phy management:
/* Phy management */
int (*lldd_control_phy)(struct sas_phy *, enum phy_func);
lldd_ha -- set this to point to your HA struct. You can also
use container_of if you embedded it as shown above.
A sample initialization and registration function
can look like this (called last thing from probe())
*but* before you enable the phys to do OOB:
static int register_sas_ha(struct my_sas_ha *my_ha)
{
int i;
static struct sas_phy *sas_phys[MAX_PHYS];
static struct sas_port *sas_ports[MAX_PHYS];
my_ha->sas_ha.sas_addr = &my_ha->sas_addr[0];
for (i = 0; i < MAX_PHYS; i++) {
sas_phys[i] = &my_ha->phys[i].sas_phy;
sas_ports[i] = &my_ha->sas_ports[i];
}
my_ha->sas_ha.sas_phy = sas_phys;
my_ha->sas_ha.sas_port = sas_ports;
my_ha->sas_ha.num_phys = MAX_PHYS;
my_ha->sas_ha.lldd_port_formed = my_port_formed;
my_ha->sas_ha.lldd_dev_found = my_dev_found;
my_ha->sas_ha.lldd_dev_gone = my_dev_gone;
my_ha->sas_ha.lldd_max_execute_num = lldd_max_execute_num; (1)
my_ha->sas_ha.lldd_queue_size = ha_can_queue;
my_ha->sas_ha.lldd_execute_task = my_execute_task;
my_ha->sas_ha.lldd_abort_task = my_abort_task;
my_ha->sas_ha.lldd_abort_task_set = my_abort_task_set;
my_ha->sas_ha.lldd_clear_aca = my_clear_aca;
my_ha->sas_ha.lldd_clear_task_set = my_clear_task_set;
my_ha->sas_ha.lldd_I_T_nexus_reset= NULL; (2)
my_ha->sas_ha.lldd_lu_reset = my_lu_reset;
my_ha->sas_ha.lldd_query_task = my_query_task;
my_ha->sas_ha.lldd_clear_nexus_port = my_clear_nexus_port;
my_ha->sas_ha.lldd_clear_nexus_ha = my_clear_nexus_ha;
my_ha->sas_ha.lldd_control_phy = my_control_phy;
return sas_register_ha(&my_ha->sas_ha);
}
(1) This is normally a LLDD parameter, something of the
lines of a task collector. What it tells the SAS Layer is
whether the SAS layer should run in Direct Mode (default:
value 0 or 1) or Task Collector Mode (value greater than 1).
In Direct Mode, the SAS Layer calls Execute Task as soon as
it has a command to send to the SDS, _and_ this is a single
command, i.e. not linked.
Some hardware (e.g. aic94xx) has the capability to DMA more
than one task at a time (interrupt) from host memory. Task
Collector Mode is an optional feature for HAs which support
this in their hardware. (Again, it is completely optional
even if your hardware supports it.)
In Task Collector Mode, the SAS Layer would do _natural_
coalescing of tasks and at the appropriate moment it would
call your driver to DMA more than one task in a single HA
interrupt. DMBS may want to use this by insmod/modprobe
setting the lldd_max_execute_num to something greater than
1.
(2) SAS 1.1 does not define I_T Nexus Reset TMF.
Events
------
Events are _the only way_ a SAS LLDD notifies the SAS layer
of anything. There is no other method or way a LLDD to tell
the SAS layer of anything happening internally or in the SAS
domain.
Phy events:
PHYE_LOSS_OF_SIGNAL, (C)
PHYE_OOB_DONE,
PHYE_OOB_ERROR, (C)
PHYE_SPINUP_HOLD.
Port events, passed on a _phy_:
PORTE_BYTES_DMAED, (M)
PORTE_BROADCAST_RCVD, (E)
PORTE_LINK_RESET_ERR, (C)
PORTE_TIMER_EVENT, (C)
PORTE_HARD_RESET.
Host Adapter event:
HAE_RESET
A SAS LLDD should be able to generate
- at least one event from group C (choice),
- events marked M (mandatory) are mandatory (only one),
- events marked E (expander) if it wants the SAS layer
to handle domain revalidation (only one such).
- Unmarked events are optional.
Meaning:
HAE_RESET -- when your HA got internal error and was reset.
PORTE_BYTES_DMAED -- on receiving an IDENTIFY/FIS frame
PORTE_BROADCAST_RCVD -- on receiving a primitive
PORTE_LINK_RESET_ERR -- timer expired, loss of signal, loss
of DWS, etc. (*)
PORTE_TIMER_EVENT -- DWS reset timeout timer expired (*)
PORTE_HARD_RESET -- Hard Reset primitive received.
PHYE_LOSS_OF_SIGNAL -- the device is gone (*)
PHYE_OOB_DONE -- OOB went fine and oob_mode is valid
PHYE_OOB_ERROR -- Error while doing OOB, the device probably
got disconnected. (*)
PHYE_SPINUP_HOLD -- SATA is present, COMWAKE not sent.
(*) should set/clear the appropriate fields in the phy,
or alternatively call the inlined sas_phy_disconnected()
which is just a helper, from their tasklet.
The Execute Command SCSI RPC:
int (*lldd_execute_task)(struct sas_task *, int num,
unsigned long gfp_flags);
Used to queue a task to the SAS LLDD. @task is the tasks to
be executed. @num should be the number of tasks being
queued at this function call (they are linked listed via
task::list), @gfp_mask should be the gfp_mask defining the
context of the caller.
This function should implement the Execute Command SCSI RPC,
or if you're sending a SCSI Task as linked commands, you
should also use this function.
That is, when lldd_execute_task() is called, the command(s)
go out on the transport *immediately*. There is *no*
queuing of any sort and at any level in a SAS LLDD.
The use of task::list is two-fold, one for linked commands,
the other discussed below.
It is possible to queue up more than one task at a time, by
initializing the list element of struct sas_task, and
passing the number of tasks enlisted in this manner in num.
Returns: -SAS_QUEUE_FULL, -ENOMEM, nothing was queued;
0, the task(s) were queued.
If you want to pass num > 1, then either
A) you're the only caller of this function and keep track
of what you've queued to the LLDD, or
B) you know what you're doing and have a strategy of
retrying.
As opposed to queuing one task at a time (function call),
batch queuing of tasks, by having num > 1, greatly
simplifies LLDD code, sequencer code, and _hardware design_,
and has some performance advantages in certain situations
(DBMS).
The LLDD advertises if it can take more than one command at
a time at lldd_execute_task(), by setting the
lldd_max_execute_num parameter (controlled by "collector"
module parameter in aic94xx SAS LLDD).
You should leave this to the default 1, unless you know what
you're doing.
This is a function of the LLDD, to which the SAS layer can
cater to.
int lldd_queue_size
The host adapter's queue size. This is the maximum
number of commands the lldd can have pending to domain
devices on behalf of all upper layers submitting through
lldd_execute_task().
You really want to set this to something (much) larger than
1.
This _really_ has absolutely nothing to do with queuing.
There is no queuing in SAS LLDDs.
struct sas_task {
dev -- the device this task is destined to
list -- must be initialized (INIT_LIST_HEAD)
task_proto -- _one_ of enum sas_proto
scatter -- pointer to scatter gather list array
num_scatter -- number of elements in scatter
total_xfer_len -- total number of bytes expected to be transfered
data_dir -- PCI_DMA_...
task_done -- callback when the task has finished execution
};
When an external entity, entity other than the LLDD or the
SAS Layer, wants to work with a struct domain_device, it
_must_ call kobject_get() when getting a handle on the
device and kobject_put() when it is done with the device.
This does two things:
A) implements proper kfree() for the device;
B) increments/decrements the kref for all players:
domain_device
all domain_device's ... (if past an expander)
port
host adapter
pci device
and up the ladder, etc.
DISCOVERY
---------
The sysfs tree has the following purposes:
a) It shows you the physical layout of the SAS domain at
the current time, i.e. how the domain looks in the
physical world right now.
b) Shows some device parameters _at_discovery_time_.
This is a link to the tree(1) program, very useful in
viewing the SAS domain:
ftp://mama.indstate.edu/linux/tree/
I expect user space applications to actually create a
graphical interface of this.
That is, the sysfs domain tree doesn't show or keep state if
you e.g., change the meaning of the READY LED MEANING
setting, but it does show you the current connection status
of the domain device.
Keeping internal device state changes is responsibility of
upper layers (Command set drivers) and user space.
When a device or devices are unplugged from the domain, this
is reflected in the sysfs tree immediately, and the device(s)
removed from the system.
The structure domain_device describes any device in the SAS
domain. It is completely managed by the SAS layer. A task
points to a domain device, this is how the SAS LLDD knows
where to send the task(s) to. A SAS LLDD only reads the
contents of the domain_device structure, but it never creates
or destroys one.
Expander management from User Space
-----------------------------------
In each expander directory in sysfs, there is a file called
"smp_portal". It is a binary sysfs attribute file, which
implements an SMP portal (Note: this is *NOT* an SMP port),
to which user space applications can send SMP requests and
receive SMP responses.
Functionality is deceptively simple:
1. Build the SMP frame you want to send. The format and layout
is described in the SAS spec. Leave the CRC field equal 0.
open(2)
2. Open the expander's SMP portal sysfs file in RW mode.
write(2)
3. Write the frame you built in 1.
read(2)
4. Read the amount of data you expect to receive for the frame you built.
If you receive different amount of data you expected to receive,
then there was some kind of error.
close(2)
All this process is shown in detail in the function do_smp_func()
and its callers, in the file "expander_conf.c".
The kernel functionality is implemented in the file
"sas_expander.c".
The program "expander_conf.c" implements this. It takes one
argument, the sysfs file name of the SMP portal to the
expander, and gives expander information, including routing
tables.
The SMP portal gives you complete control of the expander,
so please be careful.
Documentation/sound/alsa/ALSA-Configuration.txt
浏览文件 @ 2dc94310
......@@ -758,6 +758,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
position_fix - Fix DMA pointer (0 = auto, 1 = none, 2 = POSBUF, 3 = FIFO size)
single_cmd - Use single immediate commands to communicate with
codecs (for debugging only)
disable_msi - Disable Message Signaled Interrupt (MSI)
This module supports one card and autoprobe.
......@@ -778,11 +779,16 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
6stack-digout 6-jack with a SPDIF out
w810 3-jack
z71v 3-jack (HP shared SPDIF)
asus 3-jack
asus 3-jack (ASUS Mobo)
asus-w1v ASUS W1V
asus-dig ASUS with SPDIF out
asus-dig2 ASUS with SPDIF out (using GPIO2)
uniwill 3-jack
F1734 2-jack
lg LG laptop (m1 express dual)
lg-lw LG LW20 laptop
lg-lw LG LW20/LW25 laptop
tcl TCL S700
clevo Clevo laptops (m520G, m665n)
test for testing/debugging purpose, almost all controls can be
adjusted. Appearing only when compiled with
$CONFIG_SND_DEBUG=y
......@@ -790,6 +796,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
ALC260
hp HP machines
hp-3013 HP machines (3013-variant)
fujitsu Fujitsu S7020
acer Acer TravelMate
basic fixed pin assignment (old default model)
......@@ -797,24 +804,32 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
ALC262
fujitsu Fujitsu Laptop
hp-bpc HP xw4400/6400/8400/9400 laptops
benq Benq ED8
basic fixed pin assignment w/o SPDIF
auto auto-config reading BIOS (default)
ALC882/885
3stack-dig 3-jack with SPDIF I/O
6stck-dig 6-jack digital with SPDIF I/O
arima Arima W820Di1
auto auto-config reading BIOS (default)
ALC883/888
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
6stack-dig-demo 6-stack digital for Intel demo board
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
auto auto-config reading BIOS (default)
ALC861/660
3stack 3-jack
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack with SPDIF I/O
3stack-660 3-jack (for ALC660)
uniwill-m31 Uniwill M31 laptop
auto auto-config reading BIOS (default)
CMI9880
......@@ -843,10 +858,21 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
3stack-dig ditto with SPDIF
laptop 3-jack with hp-jack automute
laptop-dig ditto with SPDIF
auto auto-confgi reading BIOS (default)
auto auto-config reading BIOS (default)
STAC9200/9205/9220/9221/9254
ref Reference board
3stack D945 3stack
5stack D945 5stack + SPDIF
STAC7661(?)
STAC9227/9228/9229/927x
ref Reference board
3stack D965 3stack
5stack D965 5stack + SPDIF
STAC9872
vaio Setup for VAIO FE550G/SZ110
vaio-ar Setup for VAIO AR
If the default configuration doesn't work and one of the above
matches with your device, report it together with the PCI
......@@ -1213,6 +1239,14 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module supports only 1 card. This module has no enable option.
Module snd-mts64
----------------
Module for Ego Systems (ESI) Miditerminal 4140
This module supports multiple devices.
Requires parport (CONFIG_PARPORT).
Module snd-nm256
----------------
......
Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl
浏览文件 @ 2dc94310
......@@ -1054,9 +1054,8 @@
<para>
For a device which allows hotplugging, you can use
<function>snd_card_free_in_thread</function>. This one will
postpone the destruction and wait in a kernel-thread until all
devices are closed.
<function>snd_card_free_when_closed</function>. This one will
postpone the destruction until all devices are closed.
</para>
</section>
......
Documentation/sparse.txt
浏览文件 @ 2dc94310
......@@ -69,10 +69,10 @@ recompiled, or use "make C=2" to run sparse on the files whether they need to
be recompiled or not. The latter is a fast way to check the whole tree if you
have already built it.
The optional make variable CF can be used to pass arguments to sparse. The
build system passes -Wbitwise to sparse automatically. To perform endianness
checks, you may define __CHECK_ENDIAN__:
The optional make variable CHECKFLAGS can be used to pass arguments to sparse.
The build system passes -Wbitwise to sparse automatically. To perform
endianness checks, you may define __CHECK_ENDIAN__:
make C=2 CF="-D__CHECK_ENDIAN__"
make C=2 CHECKFLAGS="-D__CHECK_ENDIAN__"
These checks are disabled by default as they generate a host of warnings.
Kbuild
浏览文件 @ 2dc94310
......@@ -28,7 +28,7 @@ define cmd_offsets
echo "/*"; \
echo " * DO NOT MODIFY."; \
echo " *"; \
echo " * This file was generated by $(srctree)/Kbuild"; \
echo " * This file was generated by Kbuild"; \
echo " *"; \
echo " */"; \
echo ""; \
......
MAINTAINERS
浏览文件 @ 2dc94310
......@@ -298,6 +298,14 @@ L: info-linux@geode.amd.com
W: http://www.amd.com/us-en/ConnectivitySolutions/TechnicalResources/0,,50_2334_2452_11363,00.html
S: Supported
AMSO1100 RNIC DRIVER
P: Tom Tucker
M: tom@opengridcomputing.com
P: Steve Wise
M: swise@opengridcomputing.com
L: openib-general@openib.org
S: Maintained
AOA (Apple Onboard Audio) ALSA DRIVER
P: Johannes Berg
M: johannes@sipsolutions.net
......@@ -449,9 +457,9 @@ L: linux-hams@vger.kernel.org
W: http://www.baycom.org/~tom/ham/ham.html
S: Maintained
BCM43XX WIRELESS DRIVER
P: Michael Buesch
M: mb@bu3sch.de
BCM43XX WIRELESS DRIVER (SOFTMAC BASED VERSION)
P: Larry Finger
M: Larry.Finger@lwfinger.net
P: Stefano Brivio
M: st3@riseup.net
W: http://bcm43xx.berlios.de/
......@@ -991,6 +999,14 @@ EFS FILESYSTEM
W: http://aeschi.ch.eu.org/efs/
S: Orphan
EHCA (IBM GX bus InfiniBand adapter) DRIVER:
P: Hoang-Nam Nguyen
M: hnguyen@de.ibm.com
P: Christoph Raisch
M: raisch@de.ibm.com
L: openib-general@openib.org
S: Supported
EMU10K1 SOUND DRIVER
P: James Courtier-Dutton
M: James@superbug.demon.co.uk
......@@ -1783,6 +1799,13 @@ W: http://www.penguinppc.org/
L: linuxppc-embedded@ozlabs.org
S: Maintained
LINUX FOR POWERPC PA SEMI PWRFICIENT
P: Olof Johansson
M: olof@lixom.net
W: http://www.pasemi.com/
L: linuxppc-dev@ozlabs.org
S: Supported
LLC (802.2)
P: Arnaldo Carvalho de Melo
M: acme@conectiva.com.br
......@@ -2366,6 +2389,12 @@ M: linux-driver@qlogic.com
L: linux-scsi@vger.kernel.org
S: Supported
QLOGIC QLA3XXX NETWORK DRIVER
P: Ron Mercer
M: linux-driver@qlogic.com
L: netdev@vger.kernel.org
S: Supported
QNX4 FILESYSTEM
P: Anders Larsen
M: al@alarsen.net
......@@ -2445,6 +2474,8 @@ S: Maintained
S390
P: Martin Schwidefsky
M: schwidefsky@de.ibm.com
P: Heiko Carstens
M: heiko.carstens@de.ibm.com
M: linux390@de.ibm.com
L: linux-390@vm.marist.edu
W: http://www.ibm.com/developerworks/linux/linux390/
......@@ -2459,8 +2490,8 @@ W: http://www.ibm.com/developerworks/linux/linux390/
S: Supported
S390 ZFCP DRIVER
P: Andreas Herrmann
M: aherrman@de.ibm.com
P: Swen Schillig
M: swen@vnet.ibm.com
M: linux390@de.ibm.com
L: linux-390@vm.marist.edu
W: http://www.ibm.com/developerworks/linux/linux390/
......@@ -2616,6 +2647,18 @@ P: Nicolas Pitre
M: nico@cam.org
S: Maintained
SOFTMAC LAYER (IEEE 802.11)
P: Johannes Berg
M: johannes@sipsolutions.net
P: Joe Jezak
M: josejx@gentoo.org
P: Daniel Drake
M: dsd@gentoo.org
W: http://softmac.sipsolutions.net/
L: softmac-dev@sipsolutions.net
L: netdev@vger.kernel.org
S: Maintained
SOFTWARE RAID (Multiple Disks) SUPPORT
P: Ingo Molnar
M: mingo@redhat.com
......@@ -2897,8 +2940,8 @@ W: http://www.auk.cx/tms380tr/
S: Maintained
TULIP NETWORK DRIVER
P: Jeff Garzik
M: jgarzik@pobox.com
P: Valerie Henson
M: val_henson@linux.intel.com
L: tulip-users@lists.sourceforge.net
W: http://sourceforge.net/projects/tulip/
S: Maintained
......@@ -3349,6 +3392,15 @@ W: http://www.qsl.net/dl1bke/
L: linux-hams@vger.kernel.org
S: Maintained
ZD1211RW WIRELESS DRIVER
P: Daniel Drake
M: dsd@gentoo.org
P: Ulrich Kunitz
M: kune@deine-taler.de
W: http://zd1211.ath.cx/wiki/DriverRewrite
L: zd1211-devs@lists.sourceforge.net (subscribers-only)
S: Maintained
ZF MACHZ WATCHDOG
P: Fernando Fuganti
M: fuganti@netbank.com.br
......
Makefile
浏览文件 @ 2dc94310
......@@ -41,9 +41,15 @@ ifndef KBUILD_VERBOSE
KBUILD_VERBOSE = 0
endif
# Call checker as part of compilation of C files
# Use 'make C=1' to enable checking (sparse, by default)
# Override with 'make C=1 CHECK=checker_executable CHECKFLAGS=....'
# Call a source code checker (by default, "sparse") as part of the
# C compilation.
#
# Use 'make C=1' to enable checking of only re-compiled files.
# Use 'make C=2' to enable checking of *all* source files, regardless
# of whether they are re-compiled or not.
#
# See the file "Documentation/sparse.txt" for more details, including
# where to get the "sparse" utility.
ifdef C
ifeq ("$(origin C)", "command line")
......@@ -639,12 +645,12 @@ define rule_vmlinux__
$(call cmd,vmlinux__)
$(Q)echo 'cmd_$@ := $(cmd_vmlinux__)' > $(@D)/.$(@F).cmd
$(Q)$(if $($(quiet)cmd_sysmap), \
echo ' $($(quiet)cmd_sysmap) System.map' &&) \
$(cmd_sysmap) $@ System.map; \
if [ $$? -ne 0 ]; then \
rm -f $@; \
/bin/false; \
$(Q)$(if $($(quiet)cmd_sysmap), \
echo ' $($(quiet)cmd_sysmap) System.map' &&) \
$(cmd_sysmap) $@ System.map; \
if [ $$? -ne 0 ]; then \
rm -f $@; \
/bin/false; \
fi;
$(verify_kallsyms)
endef
......@@ -677,12 +683,12 @@ endif
kallsyms.o := .tmp_kallsyms$(last_kallsyms).o
define verify_kallsyms
$(Q)$(if $($(quiet)cmd_sysmap), \
echo ' $($(quiet)cmd_sysmap) .tmp_System.map' &&) \
$(Q)$(if $($(quiet)cmd_sysmap), \
echo ' $($(quiet)cmd_sysmap) .tmp_System.map' &&) \
$(cmd_sysmap) .tmp_vmlinux$(last_kallsyms) .tmp_System.map
$(Q)cmp -s System.map .tmp_System.map || \
(echo Inconsistent kallsyms data; \
echo Try setting CONFIG_KALLSYMS_EXTRA_PASS; \
$(Q)cmp -s System.map .tmp_System.map || \
(echo Inconsistent kallsyms data; \
echo Try setting CONFIG_KALLSYMS_EXTRA_PASS; \
rm .tmp_kallsyms* ; /bin/false )
endef
......@@ -736,6 +742,7 @@ endif # ifdef CONFIG_KALLSYMS
# vmlinux image - including updated kernel symbols
vmlinux: $(vmlinux-lds) $(vmlinux-init) $(vmlinux-main) $(kallsyms.o) FORCE
$(call if_changed_rule,vmlinux__)
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost $@
$(Q)rm -f .old_version
# The actual objects are generated when descending,
......@@ -753,12 +760,34 @@ $(vmlinux-dirs): prepare scripts
$(Q)$(MAKE) $(build)=$@
# Build the kernel release string
# The KERNELRELEASE is stored in a file named include/config/kernel.release
# to be used when executing for example make install or make modules_install
#
# Take the contents of any files called localversion* and the config
# variable CONFIG_LOCALVERSION and append them to KERNELRELEASE.
# LOCALVERSION from the command line override all of this
# The KERNELRELEASE value built here is stored in the file
# include/config/kernel.release, and is used when executing several
# make targets, such as "make install" or "make modules_install."
#
# The eventual kernel release string consists of the following fields,
# shown in a hierarchical format to show how smaller parts are concatenated
# to form the larger and final value, with values coming from places like
# the Makefile, kernel config options, make command line options and/or
# SCM tag information.
#
# $(KERNELVERSION)
# $(VERSION) eg, 2
# $(PATCHLEVEL) eg, 6
# $(SUBLEVEL) eg, 18
# $(EXTRAVERSION) eg, -rc6
# $(localver-full)
# $(localver)
# localversion* (all localversion* files)
# $(CONFIG_LOCALVERSION) (from kernel config setting)
# $(localver-auto) (only if CONFIG_LOCALVERSION_AUTO is set)
# ./scripts/setlocalversion (SCM tag, if one exists)
# $(LOCALVERSION) (from make command line if provided)
#
# Note how the final $(localver-auto) string is included *only* if the
# kernel config option CONFIG_LOCALVERSION_AUTO is selected. Also, at the
# moment, only git is supported but other SCMs can edit the script
# scripts/setlocalversion and add the appropriate checks as needed.
nullstring :=
space := $(nullstring) # end of line
......@@ -892,15 +921,26 @@ depend dep:
INSTALL_HDR_PATH=$(objtree)/usr
export INSTALL_HDR_PATH
HDRARCHES=$(filter-out generic,$(patsubst $(srctree)/include/asm-%/Kbuild,%,$(wildcard $(srctree)/include/asm-*/Kbuild)))
PHONY += headers_install_all
headers_install_all: include/linux/version.h scripts_basic FORCE
$(Q)$(MAKE) $(build)=scripts scripts/unifdef
$(Q)for arch in $(HDRARCHES); do \
$(MAKE) ARCH=$$arch -f $(srctree)/scripts/Makefile.headersinst obj=include BIASMDIR=-bi-$$arch ;\
done
PHONY += headers_install
headers_install: include/linux/version.h
$(Q)unifdef -Ux /dev/null
$(Q)rm -rf $(INSTALL_HDR_PATH)/include
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.headersinst obj=include
headers_install: include/linux/version.h scripts_basic FORCE
@if [ ! -r include/asm-$(ARCH)/Kbuild ]; then \
echo '*** Error: Headers not exportable for this architecture ($(ARCH))'; \
exit 1 ; fi
$(Q)$(MAKE) $(build)=scripts scripts/unifdef
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.headersinst obj=include
PHONY += headers_check
headers_check: headers_install
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.headersinst obj=include HDRCHECK=1
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.headersinst obj=include HDRCHECK=1
# ---------------------------------------------------------------------------
# Modules
......@@ -916,7 +956,7 @@ all: modules
PHONY += modules
modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
@echo ' Building modules, stage 2.';
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.modpost
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
# Target to prepare building external modules
......@@ -942,7 +982,7 @@ _modinst_:
rm -f $(MODLIB)/build ; \
ln -s $(objtree) $(MODLIB)/build ; \
fi
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.modinst
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
# If System.map exists, run depmod. This deliberately does not have a
# dependency on System.map since that would run the dependency tree on
......@@ -1057,8 +1097,10 @@ boards := $(notdir $(boards))
help:
@echo 'Cleaning targets:'
@echo ' clean - remove most generated files but keep the config'
@echo ' clean - remove most generated files but keep the config and'
@echo ' enough build support to build external modules'
@echo ' mrproper - remove all generated files + config + various backup files'
@echo ' distclean - mrproper + remove editor backup and patch files'
@echo ''
@echo 'Configuration targets:'
@$(MAKE) -f $(srctree)/scripts/kconfig/Makefile help
......@@ -1076,13 +1118,17 @@ help:
@echo ' cscope - Generate cscope index'
@echo ' kernelrelease - Output the release version string'
@echo ' kernelversion - Output the version stored in Makefile'
@echo ' headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH'
@if [ -r include/asm-$(ARCH)/Kbuild ]; then \
echo ' headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH'; \
fi
@echo ' (default: $(INSTALL_HDR_PATH))'
@echo ''
@echo 'Static analysers'
@echo ' checkstack - Generate a list of stack hogs'
@echo ' namespacecheck - Name space analysis on compiled kernel'
@echo ' headers_check - Sanity check on exported headers'
@if [ -r include/asm-$(ARCH)/Kbuild ]; then \
echo ' headers_check - Sanity check on exported headers'; \
fi
@echo ''
@echo 'Kernel packaging:'
@$(MAKE) $(build)=$(package-dir) help
......@@ -1100,6 +1146,7 @@ help:
echo '')
@echo ' make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build'
@echo ' make V=2 [targets] 2 => give reason for rebuild of target'
@echo ' make O=dir [targets] Locate all output files in "dir", including .config'
@echo ' make C=1 [targets] Check all c source with $$CHECK (sparse by default)'
@echo ' make C=2 [targets] Force check of all c source with $$CHECK'
......@@ -1154,7 +1201,7 @@ $(module-dirs): crmodverdir $(objtree)/Module.symvers
modules: $(module-dirs)
@echo ' Building modules, stage 2.';
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.modpost
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
PHONY += modules_install
modules_install: _emodinst_ _emodinst_post
......@@ -1163,7 +1210,7 @@ install-dir := $(if $(INSTALL_MOD_DIR),$(INSTALL_MOD_DIR),extra)
PHONY += _emodinst_
_emodinst_:
$(Q)mkdir -p $(MODLIB)/$(install-dir)
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.modinst
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
# Run depmod only is we have System.map and depmod is executable
quiet_cmd_depmod = DEPMOD $(KERNELRELEASE)
......@@ -1264,6 +1311,31 @@ define all-defconfigs
$(call find-sources,'defconfig')
endef
define xtags
if $1 --version 2>&1 | grep -iq exuberant; then \
$(all-sources) | xargs $1 -a \
-I __initdata,__exitdata,__acquires,__releases \
-I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL \
--extra=+f --c-kinds=+px; \
$(all-kconfigs) | xargs $1 -a \
--langdef=kconfig \
--language-force=kconfig \
--regex-kconfig='/^[[:blank:]]*config[[:blank:]]+([[:alnum:]_]+)/\1/'; \
$(all-defconfigs) | xargs $1 -a \
--langdef=dotconfig \
--language-force=dotconfig \
--regex-dotconfig='/^#?[[:blank:]]*(CONFIG_[[:alnum:]_]+)/\1/'; \
elif $1 --version 2>&1 | grep -iq emacs; then \
$(all-sources) | xargs $1 -a; \
$(all-kconfigs) | xargs $1 -a \
--regex='/^[ \t]*config[ \t]+\([a-zA-Z0-9_]+\)/\1/'; \
$(all-defconfigs) | xargs $1 -a \
--regex='/^#?[ \t]?\(CONFIG_[a-zA-Z0-9_]+\)/\1/'; \
else \
$(all-sources) | xargs $1 -a; \
fi
endef
quiet_cmd_cscope-file = FILELST cscope.files
cmd_cscope-file = (echo \-k; echo \-q; $(all-sources)) > cscope.files
......@@ -1277,31 +1349,16 @@ cscope: FORCE
quiet_cmd_TAGS = MAKE $@
define cmd_TAGS
rm -f $@; \
ETAGSF=`etags --version | grep -i exuberant >/dev/null && \
echo "-I __initdata,__exitdata,__acquires,__releases \
-I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL \
--extra=+f --c-kinds=+px"`; \
$(all-sources) | xargs etags $$ETAGSF -a; \
if test "x$$ETAGSF" = x; then \
$(all-kconfigs) | xargs etags -a \
--regex='/^config[ \t]+\([a-zA-Z0-9_]+\)/\1/'; \
$(all-defconfigs) | xargs etags -a \
--regex='/^#?[ \t]?\(CONFIG_[a-zA-Z0-9_]+\)/\1/'; \
fi
$(call xtags,etags)
endef
TAGS: FORCE
$(call cmd,TAGS)
quiet_cmd_tags = MAKE $@
define cmd_tags
rm -f $@; \
CTAGSF=`ctags --version | grep -i exuberant >/dev/null && \
echo "-I __initdata,__exitdata,__acquires,__releases \
-I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL \
--extra=+f --c-kinds=+px"`; \
$(all-sources) | xargs ctags $$CTAGSF -a
$(call xtags,ctags)
endef
tags: FORCE
......@@ -1379,7 +1436,7 @@ endif
%.ko: prepare scripts FORCE
$(Q)$(MAKE) KBUILD_MODULES=$(if $(CONFIG_MODULES),1) \
$(build)=$(build-dir) $(@:.ko=.o)
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.modpost
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
# FIXME Should go into a make.lib or something
# ===========================================================================
......
arch/arm/mach-omap1/clock.c
浏览文件 @ 2dc94310
......@@ -20,6 +20,7 @@
#include <linux/clk.h>
#include <asm/io.h>
#include <asm/mach-types.h>
#include <asm/arch/cpu.h>
#include <asm/arch/usb.h>
......@@ -586,77 +587,53 @@ static int omap1_clk_set_rate(struct clk *clk, unsigned long rate)
*-------------------------------------------------------------------------*/
#ifdef CONFIG_OMAP_RESET_CLOCKS
/*
* Resets some clocks that may be left on from bootloader,
* but leaves serial clocks on. See also omap_late_clk_reset().
*/
static inline void omap1_early_clk_reset(void)
{
//omap_writel(0x3 << 29, MOD_CONF_CTRL_0);
}
static int __init omap1_late_clk_reset(void)
static void __init omap1_clk_disable_unused(struct clk *clk)
{
/* Turn off all unused clocks */
struct clk *p;
__u32 regval32;
/* USB_REQ_EN will be disabled later if necessary (usb_dc_ck) */
regval32 = omap_readw(SOFT_REQ_REG) & (1 << 4);
omap_writew(regval32, SOFT_REQ_REG);
omap_writew(0, SOFT_REQ_REG2);
list_for_each_entry(p, &clocks, node) {
if (p->usecount > 0 || (p->flags & ALWAYS_ENABLED) ||
p->enable_reg == 0)
continue;
/* Clocks in the DSP domain need api_ck. Just assume bootloader
* has not enabled any DSP clocks */
if ((u32)p->enable_reg == DSP_IDLECT2) {
printk(KERN_INFO "Skipping reset check for DSP domain "
"clock \"%s\"\n", p->name);
continue;
}
/* Clocks in the DSP domain need api_ck. Just assume bootloader
* has not enabled any DSP clocks */
if ((u32)clk->enable_reg == DSP_IDLECT2) {
printk(KERN_INFO "Skipping reset check for DSP domain "
"clock \"%s\"\n", clk->name);
return;
}
/* Is the clock already disabled? */
if (p->flags & ENABLE_REG_32BIT) {
if (p->flags & VIRTUAL_IO_ADDRESS)
regval32 = __raw_readl(p->enable_reg);
else
regval32 = omap_readl(p->enable_reg);
} else {
if (p->flags & VIRTUAL_IO_ADDRESS)
regval32 = __raw_readw(p->enable_reg);
/* Is the clock already disabled? */
if (clk->flags & ENABLE_REG_32BIT) {
if (clk->flags & VIRTUAL_IO_ADDRESS)
regval32 = __raw_readl(clk->enable_reg);
else
regval32 = omap_readw(p->enable_reg);
}
if ((regval32 & (1 << p->enable_bit)) == 0)
continue;
regval32 = omap_readl(clk->enable_reg);
} else {
if (clk->flags & VIRTUAL_IO_ADDRESS)
regval32 = __raw_readw(clk->enable_reg);
else
regval32 = omap_readw(clk->enable_reg);
}
/* FIXME: This clock seems to be necessary but no-one
* has asked for its activation. */
if (p == &tc2_ck // FIX: pm.c (SRAM), CCP, Camera
|| p == &ck_dpll1out.clk // FIX: SoSSI, SSR
|| p == &arm_gpio_ck // FIX: GPIO code for 1510
) {
printk(KERN_INFO "FIXME: Clock \"%s\" seems unused\n",
p->name);
continue;
}
if ((regval32 & (1 << clk->enable_bit)) == 0)
return;
printk(KERN_INFO "Disabling unused clock \"%s\"... ", p->name);
p->disable(p);
printk(" done\n");
/* FIXME: This clock seems to be necessary but no-one
* has asked for its activation. */
if (clk == &tc2_ck // FIX: pm.c (SRAM), CCP, Camera
|| clk == &ck_dpll1out.clk // FIX: SoSSI, SSR
|| clk == &arm_gpio_ck // FIX: GPIO code for 1510
) {
printk(KERN_INFO "FIXME: Clock \"%s\" seems unused\n",
clk->name);
return;
}
return 0;
printk(KERN_INFO "Disabling unused clock \"%s\"... ", clk->name);
clk->disable(clk);
printk(" done\n");
}
late_initcall(omap1_late_clk_reset);
#else
#define omap1_early_clk_reset() {}
#define omap1_clk_disable_unused NULL
#endif
static struct clk_functions omap1_clk_functions = {
......@@ -664,6 +641,7 @@ static struct clk_functions omap1_clk_functions = {
.clk_disable = omap1_clk_disable,
.clk_round_rate = omap1_clk_round_rate,
.clk_set_rate = omap1_clk_set_rate,
.clk_disable_unused = omap1_clk_disable_unused,
};
int __init omap1_clk_init(void)
......@@ -671,8 +649,13 @@ int __init omap1_clk_init(void)
struct clk ** clkp;
const struct omap_clock_config *info;
int crystal_type = 0; /* Default 12 MHz */
u32 reg;
/* USB_REQ_EN will be disabled later if necessary (usb_dc_ck) */
reg = omap_readw(SOFT_REQ_REG) & (1 << 4);
omap_writew(reg, SOFT_REQ_REG);
omap_writew(0, SOFT_REQ_REG2);
omap1_early_clk_reset();
clk_init(&omap1_clk_functions);
/* By default all idlect1 clocks are allowed to idle */
......@@ -772,6 +755,12 @@ int __init omap1_clk_init(void)
omap_writew(omap_readw(OMAP730_PCC_UPLD_CTRL) & ~0x1, OMAP730_PCC_UPLD_CTRL);
#endif
/* Amstrad Delta wants BCLK high when inactive */
if (machine_is_ams_delta())
omap_writel(omap_readl(ULPD_CLOCK_CTRL) |
(1 << SDW_MCLK_INV_BIT),
ULPD_CLOCK_CTRL);
/* Turn off DSP and ARM_TIMXO. Make sure ARM_INTHCK is not divided */
/* (on 730, bit 13 must not be cleared) */
if (cpu_is_omap730())
......
arch/arm/mach-omap1/clock.h
浏览文件 @ 2dc94310
......@@ -89,6 +89,7 @@ struct arm_idlect1_clk {
#define EN_DSPTIMCK 5
/* Various register defines for clock controls scattered around OMAP chip */
#define SDW_MCLK_INV_BIT 2 /* In ULPD_CLKC_CTRL */
#define USB_MCLK_EN_BIT 4 /* In ULPD_CLKC_CTRL */
#define USB_HOST_HHC_UHOST_EN 9 /* In MOD_CONF_CTRL_0 */
#define SWD_ULPD_PLL_CLK_REQ 1 /* In SWD_CLK_DIV_CTRL_SEL */
......@@ -741,6 +742,18 @@ static struct clk i2c_fck = {
.disable = &omap1_clk_disable_generic,
};
static struct clk i2c_ick = {
.name = "i2c_ick",
.id = 1,
.flags = CLOCK_IN_OMAP16XX |
VIRTUAL_CLOCK | CLOCK_NO_IDLE_PARENT |
ALWAYS_ENABLED,
.parent = &armper_ck.clk,
.recalc = &followparent_recalc,
.enable = &omap1_clk_enable_generic,
.disable = &omap1_clk_disable_generic,
};
static struct clk * onchip_clks[] = {
/* non-ULPD clocks */
&ck_ref,
......@@ -790,6 +803,7 @@ static struct clk * onchip_clks[] = {
/* Virtual clocks */
&virtual_ck_mpu,
&i2c_fck,
&i2c_ick,
};
#endif
arch/arm/mach-omap1/mux.c
浏览文件 @ 2dc94310
......@@ -199,6 +199,17 @@ MUX_CFG("N14_1610_UWIRE_CS0", 8, 9, 1, 1, 21, 0, 1, 1, 1)
MUX_CFG("P15_1610_UWIRE_CS3", 8, 12, 1, 1, 22, 0, 1, 1, 1)
MUX_CFG("N15_1610_UWIRE_CS1", 7, 18, 2, 1, 14, 0, NA, 0, 1)
/* OMAP-1610 SPI */
MUX_CFG("U19_1610_SPIF_SCK", 7, 21, 6, 1, 15, 0, 1, 1, 1)
MUX_CFG("U18_1610_SPIF_DIN", 8, 0, 6, 1, 18, 1, 1, 0, 1)
MUX_CFG("P20_1610_SPIF_DIN", 6, 27, 4, 1, 7, 1, 1, 0, 1)
MUX_CFG("W21_1610_SPIF_DOUT", 8, 3, 6, 1, 19, 0, 1, 0, 1)
MUX_CFG("R18_1610_SPIF_DOUT", 7, 9, 3, 1, 11, 0, 1, 0, 1)
MUX_CFG("N14_1610_SPIF_CS0", 8, 9, 6, 1, 21, 0, 1, 1, 1)
MUX_CFG("N15_1610_SPIF_CS1", 7, 18, 6, 1, 14, 0, 1, 1, 1)
MUX_CFG("T19_1610_SPIF_CS2", 7, 15, 4, 1, 13, 0, 1, 1, 1)
MUX_CFG("P15_1610_SPIF_CS3", 8, 12, 3, 1, 22, 0, 1, 1, 1)
/* OMAP-1610 Flash */
MUX_CFG("L3_1610_FLASH_CS2B_OE",10, 6, 1, NA, 0, 0, NA, 0, 1)
MUX_CFG("M8_1610_FLASH_CS2B_WE",10, 3, 1, NA, 0, 0, NA, 0, 1)
......
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ 2dc94310
......@@ -166,8 +166,8 @@ static struct omap_uart_config apollon_uart_config __initdata = {
static struct omap_mmc_config apollon_mmc_config __initdata = {
.mmc [0] = {
.enabled = 0,
.wire4 = 0,
.enabled = 1,
.wire4 = 1,
.wp_pin = -1,
.power_pin = -1,
.switch_pin = -1,
......@@ -257,6 +257,9 @@ static void __init omap_apollon_init(void)
/* REVISIT: where's the correct place */
omap_cfg_reg(W19_24XX_SYS_NIRQ);
/* Use Interal loop-back in MMC/SDIO Module Input Clock selection */
CONTROL_DEVCONF |= (1 << 24);
/*
* Make sure the serial ports are muxed on at this point.
* You have to mux them off in device drivers later on
......
arch/arm/mach-omap2/clock.c
浏览文件 @ 2dc94310
......@@ -32,10 +32,14 @@
#include "memory.h"
#include "clock.h"
#undef DEBUG
//#define DOWN_VARIABLE_DPLL 1 /* Experimental */
static struct prcm_config *curr_prcm_set;
static u32 curr_perf_level = PRCM_FULL_SPEED;
static struct clk *vclk;
static struct clk *sclk;
/*-------------------------------------------------------------------------
* Omap2 specific clock functions
......@@ -79,6 +83,14 @@ static void omap2_propagate_rate(struct clk * clk)
propagate_rate(clk);
}
static void omap2_set_osc_ck(int enable)
{
if (enable)
PRCM_CLKSRC_CTRL &= ~(0x3 << 3);
else
PRCM_CLKSRC_CTRL |= 0x3 << 3;
}
/* Enable an APLL if off */
static void omap2_clk_fixed_enable(struct clk *clk)
{
......@@ -101,12 +113,54 @@ static void omap2_clk_fixed_enable(struct clk *clk)
else if (clk == &apll54_ck)
cval = (1 << 6);
while (!CM_IDLEST_CKGEN & cval) { /* Wait for lock */
while (!(CM_IDLEST_CKGEN & cval)) { /* Wait for lock */
++i;
udelay(1);
if (i == 100000)
if (i == 100000) {
printk(KERN_ERR "Clock %s didn't lock\n", clk->name);
break;
}
}
}
static void omap2_clk_wait_ready(struct clk *clk)
{
unsigned long reg, other_reg, st_reg;
u32 bit;
int i;
reg = (unsigned long) clk->enable_reg;
if (reg == (unsigned long) &CM_FCLKEN1_CORE ||
reg == (unsigned long) &CM_FCLKEN2_CORE)
other_reg = (reg & ~0xf0) | 0x10;
else if (reg == (unsigned long) &CM_ICLKEN1_CORE ||
reg == (unsigned long) &CM_ICLKEN2_CORE)
other_reg = (reg & ~0xf0) | 0x00;
else
return;
/* No check for DSS or cam clocks */
if ((reg & 0x0f) == 0) {
if (clk->enable_bit <= 1 || clk->enable_bit == 31)
return;
}
/* Check if both functional and interface clocks
* are running. */
bit = 1 << clk->enable_bit;
if (!(__raw_readl(other_reg) & bit))
return;
st_reg = (other_reg & ~0xf0) | 0x20;
i = 0;
while (!(__raw_readl(st_reg) & bit)) {
i++;
if (i == 100000) {
printk(KERN_ERR "Timeout enabling clock %s\n", clk->name);
break;
}
}
if (i)
pr_debug("Clock %s stable after %d loops\n", clk->name, i);
}
/* Enables clock without considering parent dependencies or use count
......@@ -119,6 +173,11 @@ static int _omap2_clk_enable(struct clk * clk)
if (clk->flags & ALWAYS_ENABLED)
return 0;
if (unlikely(clk == &osc_ck)) {
omap2_set_osc_ck(1);
return 0;
}
if (unlikely(clk->enable_reg == 0)) {
printk(KERN_ERR "clock.c: Enable for %s without enable code\n",
clk->name);
......@@ -133,6 +192,9 @@ static int _omap2_clk_enable(struct clk * clk)
regval32 = __raw_readl(clk->enable_reg);
regval32 |= (1 << clk->enable_bit);
__raw_writel(regval32, clk->enable_reg);
wmb();
omap2_clk_wait_ready(clk);
return 0;
}
......@@ -155,6 +217,11 @@ static void _omap2_clk_disable(struct clk *clk)
{
u32 regval32;
if (unlikely(clk == &osc_ck)) {
omap2_set_osc_ck(0);
return;
}
if (clk->enable_reg == 0)
return;
......@@ -166,6 +233,7 @@ static void _omap2_clk_disable(struct clk *clk)
regval32 = __raw_readl(clk->enable_reg);
regval32 &= ~(1 << clk->enable_bit);
__raw_writel(regval32, clk->enable_reg);
wmb();
}
static int omap2_clk_enable(struct clk *clk)
......@@ -695,12 +763,14 @@ static int omap2_clk_set_rate(struct clk *clk, unsigned long rate)
reg_val = __raw_readl(reg);
reg_val &= ~(field_mask << div_off);
reg_val |= (field_val << div_off);
__raw_writel(reg_val, reg);
wmb();
clk->rate = clk->parent->rate / field_val;
if (clk->flags & DELAYED_APP)
if (clk->flags & DELAYED_APP) {
__raw_writel(0x1, (void __iomem *)&PRCM_CLKCFG_CTRL);
wmb();
}
ret = 0;
} else if (clk->set_rate != 0)
ret = clk->set_rate(clk, rate);
......@@ -836,10 +906,12 @@ static int omap2_clk_set_parent(struct clk *clk, struct clk *new_parent)
reg_val = __raw_readl(reg) & ~(field_mask << src_off);
reg_val |= (field_val << src_off);
__raw_writel(reg_val, reg);
wmb();
if (clk->flags & DELAYED_APP)
if (clk->flags & DELAYED_APP) {
__raw_writel(0x1, (void __iomem *)&PRCM_CLKCFG_CTRL);
wmb();
}
if (clk->usecount > 0)
_omap2_clk_enable(clk);
......@@ -953,12 +1025,29 @@ static int omap2_select_table_rate(struct clk * clk, unsigned long rate)
* Omap2 clock reset and init functions
*-------------------------------------------------------------------------*/
#ifdef CONFIG_OMAP_RESET_CLOCKS
static void __init omap2_clk_disable_unused(struct clk *clk)
{
u32 regval32;
regval32 = __raw_readl(clk->enable_reg);
if ((regval32 & (1 << clk->enable_bit)) == 0)
return;
printk(KERN_INFO "Disabling unused clock \"%s\"\n", clk->name);
_omap2_clk_disable(clk);
}
#else
#define omap2_clk_disable_unused NULL
#endif
static struct clk_functions omap2_clk_functions = {
.clk_enable = omap2_clk_enable,
.clk_disable = omap2_clk_disable,
.clk_round_rate = omap2_clk_round_rate,
.clk_set_rate = omap2_clk_set_rate,
.clk_set_parent = omap2_clk_set_parent,
.clk_disable_unused = omap2_clk_disable_unused,
};
static void __init omap2_get_crystal_rate(struct clk *osc, struct clk *sys)
......@@ -984,27 +1073,19 @@ static void __init omap2_get_crystal_rate(struct clk *osc, struct clk *sys)
sys->rate = sclk;
}
#ifdef CONFIG_OMAP_RESET_CLOCKS
static void __init omap2_disable_unused_clocks(void)
/*
* Set clocks for bypass mode for reboot to work.
*/
void omap2_clk_prepare_for_reboot(void)
{
struct clk *ck;
u32 regval32;
u32 rate;
list_for_each_entry(ck, &clocks, node) {
if (ck->usecount > 0 || (ck->flags & ALWAYS_ENABLED) ||
ck->enable_reg == 0)
continue;
regval32 = __raw_readl(ck->enable_reg);
if ((regval32 & (1 << ck->enable_bit)) == 0)
continue;
if (vclk == NULL || sclk == NULL)
return;
printk(KERN_INFO "Disabling unused clock \"%s\"\n", ck->name);
_omap2_clk_disable(ck);
}
rate = clk_get_rate(sclk);
clk_set_rate(vclk, rate);
}
late_initcall(omap2_disable_unused_clocks);
#endif
/*
* Switch the MPU rate if specified on cmdline.
......@@ -1077,8 +1158,27 @@ int __init omap2_clk_init(void)
*/
clk_enable(&sync_32k_ick);
clk_enable(&omapctrl_ick);
/* Force the APLLs active during bootup to avoid disabling and
* enabling them unnecessarily. */
clk_enable(&apll96_ck);
clk_enable(&apll54_ck);
if (cpu_is_omap2430())
clk_enable(&sdrc_ick);
/* Avoid sleeping sleeping during omap2_clk_prepare_for_reboot() */
vclk = clk_get(NULL, "virt_prcm_set");
sclk = clk_get(NULL, "sys_ck");
return 0;
}
static int __init omap2_disable_aplls(void)
{
clk_disable(&apll96_ck);
clk_disable(&apll54_ck);
return 0;
}
late_initcall(omap2_disable_aplls);
arch/arm/mach-omap2/clock.h
浏览文件 @ 2dc94310
......@@ -560,7 +560,7 @@ static struct clk osc_ck = { /* (*12, *13, 19.2, *26, 38.4)MHz */
.name = "osc_ck",
.rate = 26000000, /* fixed up in clock init */
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X |
RATE_FIXED | ALWAYS_ENABLED | RATE_PROPAGATES,
RATE_FIXED | RATE_PROPAGATES,
};
/* With out modem likely 12MHz, with modem likely 13MHz */
......@@ -1368,7 +1368,8 @@ static struct clk mcbsp5_fck = {
};
static struct clk mcspi1_ick = {
.name = "mcspi1_ick",
.name = "mcspi_ick",
.id = 1,
.parent = &l4_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
.enable_reg = (void __iomem *)&CM_ICLKEN1_CORE,
......@@ -1377,7 +1378,8 @@ static struct clk mcspi1_ick = {
};
static struct clk mcspi1_fck = {
.name = "mcspi1_fck",
.name = "mcspi_fck",
.id = 1,
.parent = &func_48m_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
.enable_reg = (void __iomem *)&CM_FCLKEN1_CORE,
......@@ -1386,7 +1388,8 @@ static struct clk mcspi1_fck = {
};
static struct clk mcspi2_ick = {
.name = "mcspi2_ick",
.name = "mcspi_ick",
.id = 2,
.parent = &l4_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
.enable_reg = (void __iomem *)&CM_ICLKEN1_CORE,
......@@ -1395,7 +1398,8 @@ static struct clk mcspi2_ick = {
};
static struct clk mcspi2_fck = {
.name = "mcspi2_fck",
.name = "mcspi_fck",
.id = 2,
.parent = &func_48m_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
.enable_reg = (void __iomem *)&CM_FCLKEN1_CORE,
......@@ -1404,7 +1408,8 @@ static struct clk mcspi2_fck = {
};
static struct clk mcspi3_ick = {
.name = "mcspi3_ick",
.name = "mcspi_ick",
.id = 3,
.parent = &l4_ck,
.flags = CLOCK_IN_OMAP243X,
.enable_reg = (void __iomem *)&CM_ICLKEN2_CORE,
......@@ -1413,7 +1418,8 @@ static struct clk mcspi3_ick = {
};
static struct clk mcspi3_fck = {
.name = "mcspi3_fck",
.name = "mcspi_fck",
.id = 3,
.parent = &func_48m_ck,
.flags = CLOCK_IN_OMAP243X,
.enable_reg = (void __iomem *)&CM_FCLKEN2_CORE,
......
arch/arm/mach-omap2/gpmc.c
浏览文件 @ 2dc94310
......@@ -13,6 +13,8 @@
#include <linux/init.h>
#include <linux/err.h>
#include <linux/clk.h>
#include <linux/ioport.h>
#include <linux/spinlock.h>
#include <asm/io.h>
#include <asm/arch/gpmc.h>
......@@ -41,6 +43,19 @@
#define GPMC_CS0 0x60
#define GPMC_CS_SIZE 0x30
#define GPMC_CS_NUM 8
#define GPMC_MEM_START 0x00000000
#define GPMC_MEM_END 0x3FFFFFFF
#define BOOT_ROM_SPACE 0x100000 /* 1MB */
#define GPMC_CHUNK_SHIFT 24 /* 16 MB */
#define GPMC_SECTION_SHIFT 28 /* 128 MB */
static struct resource gpmc_mem_root;
static struct resource gpmc_cs_mem[GPMC_CS_NUM];
static spinlock_t gpmc_mem_lock = SPIN_LOCK_UNLOCKED;
static unsigned gpmc_cs_map;
static void __iomem *gpmc_base =
(void __iomem *) IO_ADDRESS(GPMC_BASE);
static void __iomem *gpmc_cs_base =
......@@ -187,9 +202,168 @@ int gpmc_cs_set_timings(int cs, const struct gpmc_timings *t)
return 0;
}
unsigned long gpmc_cs_get_base_addr(int cs)
static void gpmc_cs_enable_mem(int cs, u32 base, u32 size)
{
u32 l;
u32 mask;
mask = (1 << GPMC_SECTION_SHIFT) - size;
l = gpmc_cs_read_reg(cs, GPMC_CS_CONFIG7);
l &= ~0x3f;
l = (base >> GPMC_CHUNK_SHIFT) & 0x3f;
l &= ~(0x0f << 8);
l |= ((mask >> GPMC_CHUNK_SHIFT) & 0x0f) << 8;
l |= 1 << 6; /* CSVALID */
gpmc_cs_write_reg(cs, GPMC_CS_CONFIG7, l);
}
static void gpmc_cs_disable_mem(int cs)
{
u32 l;
l = gpmc_cs_read_reg(cs, GPMC_CS_CONFIG7);
l &= ~(1 << 6); /* CSVALID */
gpmc_cs_write_reg(cs, GPMC_CS_CONFIG7, l);
}
static void gpmc_cs_get_memconf(int cs, u32 *base, u32 *size)
{
u32 l;
u32 mask;
l = gpmc_cs_read_reg(cs, GPMC_CS_CONFIG7);
*base = (l & 0x3f) << GPMC_CHUNK_SHIFT;
mask = (l >> 8) & 0x0f;
*size = (1 << GPMC_SECTION_SHIFT) - (mask << GPMC_CHUNK_SHIFT);
}
static int gpmc_cs_mem_enabled(int cs)
{
u32 l;
l = gpmc_cs_read_reg(cs, GPMC_CS_CONFIG7);
return l & (1 << 6);
}
static void gpmc_cs_set_reserved(int cs, int reserved)
{
return (gpmc_cs_read_reg(cs, GPMC_CS_CONFIG7) & 0x1f) << 24;
gpmc_cs_map &= ~(1 << cs);
gpmc_cs_map |= (reserved ? 1 : 0) << cs;
}
static int gpmc_cs_reserved(int cs)
{
return gpmc_cs_map & (1 << cs);
}
static unsigned long gpmc_mem_align(unsigned long size)
{
int order;
size = (size - 1) >> (GPMC_CHUNK_SHIFT - 1);
order = GPMC_CHUNK_SHIFT - 1;
do {
size >>= 1;
order++;
} while (size);
size = 1 << order;
return size;
}
static int gpmc_cs_insert_mem(int cs, unsigned long base, unsigned long size)
{
struct resource *res = &gpmc_cs_mem[cs];
int r;
size = gpmc_mem_align(size);
spin_lock(&gpmc_mem_lock);
res->start = base;
res->end = base + size - 1;
r = request_resource(&gpmc_mem_root, res);
spin_unlock(&gpmc_mem_lock);
return r;
}
int gpmc_cs_request(int cs, unsigned long size, unsigned long *base)
{
struct resource *res = &gpmc_cs_mem[cs];
int r = -1;
if (cs > GPMC_CS_NUM)
return -ENODEV;
size = gpmc_mem_align(size);
if (size > (1 << GPMC_SECTION_SHIFT))
return -ENOMEM;
spin_lock(&gpmc_mem_lock);
if (gpmc_cs_reserved(cs)) {
r = -EBUSY;
goto out;
}
if (gpmc_cs_mem_enabled(cs))
r = adjust_resource(res, res->start & ~(size - 1), size);
if (r < 0)
r = allocate_resource(&gpmc_mem_root, res, size, 0, ~0,
size, NULL, NULL);
if (r < 0)
goto out;
gpmc_cs_enable_mem(cs, res->start, res->end - res->start + 1);
*base = res->start;
gpmc_cs_set_reserved(cs, 1);
out:
spin_unlock(&gpmc_mem_lock);
return r;
}
void gpmc_cs_free(int cs)
{
spin_lock(&gpmc_mem_lock);
if (cs >= GPMC_CS_NUM || !gpmc_cs_reserved(cs)) {
printk(KERN_ERR "Trying to free non-reserved GPMC CS%d\n", cs);
BUG();
spin_unlock(&gpmc_mem_lock);
return;
}
gpmc_cs_disable_mem(cs);
release_resource(&gpmc_cs_mem[cs]);
gpmc_cs_set_reserved(cs, 0);
spin_unlock(&gpmc_mem_lock);
}
void __init gpmc_mem_init(void)
{
int cs;
unsigned long boot_rom_space = 0;
if (cpu_is_omap242x()) {
u32 l;
l = omap_readl(OMAP242X_CONTROL_STATUS);
/* In case of internal boot the 1st MB is redirected to the
* boot ROM memory space.
*/
if (l & (1 << 3))
boot_rom_space = BOOT_ROM_SPACE;
} else
/* We assume internal boot if the mode can't be
* determined.
*/
boot_rom_space = BOOT_ROM_SPACE;
gpmc_mem_root.start = GPMC_MEM_START + boot_rom_space;
gpmc_mem_root.end = GPMC_MEM_END;
/* Reserve all regions that has been set up by bootloader */
for (cs = 0; cs < GPMC_CS_NUM; cs++) {
u32 base, size;
if (!gpmc_cs_mem_enabled(cs))
continue;
gpmc_cs_get_memconf(cs, &base, &size);
if (gpmc_cs_insert_mem(cs, base, size) < 0)
BUG();
}
}
void __init gpmc_init(void)
......@@ -206,4 +380,6 @@ void __init gpmc_init(void)
l &= 0x03 << 3;
l |= (0x02 << 3) | (1 << 0);
gpmc_write_reg(GPMC_SYSCONFIG, l);
gpmc_mem_init();
}
arch/arm/mach-omap2/irq.c
浏览文件 @ 2dc94310
......@@ -41,18 +41,6 @@ static struct omap_irq_bank {
.nr_irqs = 96,
}, {
/* XXX: DSP INTC */
#if 0
/*
* Commented out for now until we fix the IVA clocking
*/
#ifdef CONFIG_ARCH_OMAP2420
}, {
/* IVA INTC (2420 only) */
.base_reg = OMAP24XX_IVA_INTC_BASE,
.nr_irqs = 16, /* Actually 32, but only 16 are used */
#endif
#endif
}
};
......
arch/arm/mach-omap2/mux.c
浏览文件 @ 2dc94310
......@@ -104,6 +104,20 @@ MUX_CFG_24XX("P20_24XX_TSC_IRQ", 0x108, 0, 0, 0, 1)
MUX_CFG_24XX("K15_24XX_UART3_TX", 0x118, 0, 0, 0, 1)
MUX_CFG_24XX("K14_24XX_UART3_RX", 0x119, 0, 0, 0, 1)
/* MMC/SDIO */
MUX_CFG_24XX("G19_24XX_MMC_CLKO", 0x0f3, 0, 0, 0, 1)
MUX_CFG_24XX("H18_24XX_MMC_CMD", 0x0f4, 0, 0, 0, 1)
MUX_CFG_24XX("F20_24XX_MMC_DAT0", 0x0f5, 0, 0, 0, 1)
MUX_CFG_24XX("H14_24XX_MMC_DAT1", 0x0f6, 0, 0, 0, 1)
MUX_CFG_24XX("E19_24XX_MMC_DAT2", 0x0f7, 0, 0, 0, 1)
MUX_CFG_24XX("D19_24XX_MMC_DAT3", 0x0f8, 0, 0, 0, 1)
MUX_CFG_24XX("F19_24XX_MMC_DAT_DIR0", 0x0f9, 0, 0, 0, 1)
MUX_CFG_24XX("E20_24XX_MMC_DAT_DIR1", 0x0fa, 0, 0, 0, 1)
MUX_CFG_24XX("F18_24XX_MMC_DAT_DIR2", 0x0fb, 0, 0, 0, 1)
MUX_CFG_24XX("E18_24XX_MMC_DAT_DIR3", 0x0fc, 0, 0, 0, 1)
MUX_CFG_24XX("G18_24XX_MMC_CMD_DIR", 0x0fd, 0, 0, 0, 1)
MUX_CFG_24XX("H15_24XX_MMC_CLKI", 0x0fe, 0, 0, 0, 1)
/* Keypad GPIO*/
MUX_CFG_24XX("T19_24XX_KBR0", 0x106, 3, 1, 1, 1)
MUX_CFG_24XX("R19_24XX_KBR1", 0x107, 3, 1, 1, 1)
......
arch/arm/mach-omap2/prcm.c
浏览文件 @ 2dc94310
......@@ -19,6 +19,8 @@
#include "prcm-regs.h"
extern void omap2_clk_prepare_for_reboot(void);
u32 omap_prcm_get_reset_sources(void)
{
return RM_RSTST_WKUP & 0x7f;
......@@ -28,12 +30,6 @@ EXPORT_SYMBOL(omap_prcm_get_reset_sources);
/* Resets clock rates and reboots the system. Only called from system.h */
void omap_prcm_arch_reset(char mode)
{
u32 rate;
struct clk *vclk, *sclk;
vclk = clk_get(NULL, "virt_prcm_set");
sclk = clk_get(NULL, "sys_ck");
rate = clk_get_rate(sclk);
clk_set_rate(vclk, rate); /* go to bypass for OMAP limitation */
omap2_clk_prepare_for_reboot();
RM_RSTCTRL_WKUP |= 2;
}
arch/arm/plat-omap/clock.c
浏览文件 @ 2dc94310
......@@ -100,6 +100,7 @@ void clk_disable(struct clk *clk)
return;
spin_lock_irqsave(&clockfw_lock, flags);
BUG_ON(clk->usecount == 0);
if (arch_clock->clk_disable)
arch_clock->clk_disable(clk);
spin_unlock_irqrestore(&clockfw_lock, flags);
......@@ -322,6 +323,31 @@ EXPORT_SYMBOL(clk_allow_idle);
/*-------------------------------------------------------------------------*/
#ifdef CONFIG_OMAP_RESET_CLOCKS
/*
* Disable any unused clocks left on by the bootloader
*/
static int __init clk_disable_unused(void)
{
struct clk *ck;
unsigned long flags;
list_for_each_entry(ck, &clocks, node) {
if (ck->usecount > 0 || (ck->flags & ALWAYS_ENABLED) ||
ck->enable_reg == 0)
continue;
spin_lock_irqsave(&clockfw_lock, flags);
if (arch_clock->clk_disable_unused)
arch_clock->clk_disable_unused(ck);
spin_unlock_irqrestore(&clockfw_lock, flags);
}
return 0;
}
late_initcall(clk_disable_unused);
#endif
int __init clk_init(struct clk_functions * custom_clocks)
{
if (!custom_clocks) {
......
arch/arm/plat-omap/devices.c
浏览文件 @ 2dc94310
......@@ -148,7 +148,7 @@ static inline void omap_init_kp(void) {}
#ifdef CONFIG_ARCH_OMAP24XX
#define OMAP_MMC1_BASE 0x4809c000
#define OMAP_MMC1_INT 83
#define OMAP_MMC1_INT INT_24XX_MMC_IRQ
#else
#define OMAP_MMC1_BASE 0xfffb7800
#define OMAP_MMC1_INT INT_MMC
......@@ -225,7 +225,14 @@ static void __init omap_init_mmc(void)
/* block 1 is always available and has just one pinout option */
mmc = &mmc_conf->mmc[0];
if (mmc->enabled) {
if (!cpu_is_omap24xx()) {
if (cpu_is_omap24xx()) {
omap_cfg_reg(H18_24XX_MMC_CMD);
omap_cfg_reg(H15_24XX_MMC_CLKI);
omap_cfg_reg(G19_24XX_MMC_CLKO);
omap_cfg_reg(F20_24XX_MMC_DAT0);
omap_cfg_reg(F19_24XX_MMC_DAT_DIR0);
omap_cfg_reg(G18_24XX_MMC_CMD_DIR);
} else {
omap_cfg_reg(MMC_CMD);
omap_cfg_reg(MMC_CLK);
omap_cfg_reg(MMC_DAT0);
......@@ -236,7 +243,14 @@ static void __init omap_init_mmc(void)
}
}
if (mmc->wire4) {
if (!cpu_is_omap24xx()) {
if (cpu_is_omap24xx()) {
omap_cfg_reg(H14_24XX_MMC_DAT1);
omap_cfg_reg(E19_24XX_MMC_DAT2);
omap_cfg_reg(D19_24XX_MMC_DAT3);
omap_cfg_reg(E20_24XX_MMC_DAT_DIR1);
omap_cfg_reg(F18_24XX_MMC_DAT_DIR2);
omap_cfg_reg(E18_24XX_MMC_DAT_DIR3);
} else {
omap_cfg_reg(MMC_DAT1);
/* NOTE: DAT2 can be on W10 (here) or M15 */
if (!mmc->nomux)
......
arch/arm/plat-omap/dma.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/arm/plat-omap/dmtimer.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/arm/plat-omap/mcbsp.c
浏览文件 @ 2dc94310
......@@ -75,8 +75,6 @@ static struct clk *mcbsp1_ick = 0;
static struct clk *mcbsp1_fck = 0;
static struct clk *mcbsp2_ick = 0;
static struct clk *mcbsp2_fck = 0;
static struct clk *sys_ck = 0;
static struct clk *sys_clkout = 0;
#endif
static void omap_mcbsp_dump_reg(u8 id)
......@@ -232,7 +230,6 @@ static void omap2_mcbsp2_mux_setup(void)
omap_cfg_reg(W15_24XX_MCBSP2_DR);
omap_cfg_reg(V15_24XX_MCBSP2_DX);
omap_cfg_reg(V14_24XX_GPIO117);
omap_cfg_reg(W14_24XX_SYS_CLKOUT);
}
#endif
......@@ -984,13 +981,7 @@ static int __init omap_mcbsp_init(void)
if (cpu_is_omap24xx()) {
mcbsp_info = mcbsp_24xx;
mcbsp_count = ARRAY_SIZE(mcbsp_24xx);
/* REVISIT: where's the right place? */
omap2_mcbsp2_mux_setup();
sys_ck = clk_get(0, "sys_ck");
sys_clkout = clk_get(0, "sys_clkout");
clk_set_parent(sys_clkout, sys_ck);
clk_enable(sys_clkout);
}
#endif
for (i = 0; i < OMAP_MAX_MCBSP_COUNT ; i++) {
......
arch/arm/plat-omap/pm.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ 2dc94310
......@@ -174,10 +174,7 @@ void __init omap_map_sram(void)
if (cpu_is_omap24xx()) {
omap_sram_io_desc[0].virtual = OMAP2_SRAM_VA;
if (is_sram_locked())
base = OMAP2_SRAM_PUB_PA;
else
base = OMAP2_SRAM_PA;
base = OMAP2_SRAM_PA;
base = ROUND_DOWN(base, PAGE_SIZE);
omap_sram_io_desc[0].pfn = __phys_to_pfn(base);
}
......
arch/arm/plat-omap/timer32k.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/frv/Makefile
浏览文件 @ 2dc94310
......@@ -108,11 +108,8 @@ Image: vmlinux
bootstrap:
$(Q)$(MAKEBOOT) bootstrap
archmrproper:
$(Q)$(MAKE) $(build)=arch/frv/boot mrproper
archclean:
$(Q)$(MAKE) $(build)=arch/frv/boot clean
$(Q)$(MAKE) $(clean)=arch/frv/boot
archdep: scripts/mkdep symlinks
$(Q)$(MAKE) $(build)=arch/frv/boot dep
arch/frv/boot/Makefile
浏览文件 @ 2dc94310
......@@ -8,6 +8,8 @@
# Copyright (C) 1995-2000 Russell King
#
targets := Image zImage bootpImage
SYSTEM =$(TOPDIR)/$(LINUX)
ZTEXTADDR = 0x02080000
......@@ -66,7 +68,6 @@ zinstall: $(CONFIGURE) zImage
# miscellany
#
mrproper clean:
$(RM) Image zImage bootpImage
# @$(MAKE) -C compressed clean
# @$(MAKE) -C bootp clean
......
arch/i386/crypto/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/i386/crypto/aes.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/i386/crypto/twofish-i586-asm.S 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/i386/crypto/twofish.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/flatdevtree.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/main.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/ops.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/prom.h 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
arch/powerpc/boot/stdio.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/stdio.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/boot/types.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/btext.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/crash_dump.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/dma_64.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/ibmebus.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/io.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/legacy_serial.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/misc.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/of_device.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/paca.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/pci_32.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/pci_64.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/pci_dn.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/rtas-proc.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/rtas_pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/sysfs.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/lib/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/lib/e2a.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
arch/powerpc/lib/locks.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/mm/slb.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/mm/tlb_64.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/83xx/pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/85xx/pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/86xx/pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/cell/setup.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/cell/smp.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/chrp/nvram.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/chrp/pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/chrp/setup.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/iseries/dt.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/maple/pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/pasemi/Makefile 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/pasemi/pasemi.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/pasemi/pci.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/pasemi/setup.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/pasemi/time.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/platforms/pseries/hvCall_inst.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/sysdev/i8259.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/sysdev/ipic.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/sysdev/mmio_nvram.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/sysdev/tsi108_pci.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/kernel/misc.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/kernel/ppc_ksyms.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/kernel/setup.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/platforms/85xx/sbc8560.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/platforms/85xx/sbc85xx.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/xmon/start.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/ppc/xmon/xmon.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/appldata/appldata.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/appldata/appldata_os.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/crypto/aes_s390.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/crypto/crypt_s390.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/crypto/des_s390.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/crypto/sha1_s390.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/crypto/sha256_s390.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/defconfig
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/hypfs/hypfs.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/hypfs/hypfs_diag.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/hypfs/hypfs_diag.h
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/hypfs/inode.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/entry.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/entry64.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/head.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/head31.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/head64.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/ipl.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/kprobes.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/reipl.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/reipl64.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/reipl_diag.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
arch/s390/kernel/s390_ksyms.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/signal.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/traps.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/kernel/vmlinux.lds.S
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/lib/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/lib/uaccess.S 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
arch/s390/lib/uaccess64.S 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
arch/s390/lib/uaccess_mvcos.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/lib/uaccess_std.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/mm/cmm.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/mm/fault.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/sh/kernel/process.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/sparc/kernel/ebus.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/sparc/kernel/ioport.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/sparc64/defconfig
浏览文件 @ 2dc94310
此差异已折叠。
arch/sparc64/kernel/time.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/x86_64/crypto/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
arch/x86_64/crypto/aes.c
浏览文件 @ 2dc94310
此差异已折叠。
arch/x86_64/crypto/twofish-x86_64-asm.S 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
arch/x86_64/crypto/twofish.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
block/ll_rw_blk.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
crypto/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
crypto/aes.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/algapi.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
crypto/anubis.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/api.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/arc4.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/blkcipher.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
crypto/blowfish.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/cast5.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/cast6.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/cbc.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
crypto/cipher.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/crc32c.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/crypto_null.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/cryptomgr.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
crypto/des.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/digest.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/ecb.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
crypto/hash.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
crypto/hmac.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/internal.h
浏览文件 @ 2dc94310
此差异已折叠。
crypto/khazad.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/michael_mic.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/proc.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/scatterwalk.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/scatterwalk.h
浏览文件 @ 2dc94310
此差异已折叠。
crypto/serpent.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/sha1.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/sha256.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/tcrypt.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/tcrypt.h
浏览文件 @ 2dc94310
此差异已折叠。
crypto/tea.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/twofish.c
浏览文件 @ 2dc94310
此差异已折叠。
crypto/twofish_common.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/Kconfig 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/Makefile 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/ata_generic.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_ali.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_amd.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_artop.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_atiixp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_cmd64x.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_cs5520.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_cs5530.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_cs5535.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_cypress.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_efar.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_hpt366.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_hpt37x.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_hpt3x2n.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_hpt3x3.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_isapnp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_it821x.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_jmicron.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_legacy.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_mpiix.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_netcell.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_ns87410.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_oldpiix.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_opti.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_optidma.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_pcmcia.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_pdc2027x.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_pdc202xx_old.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_qdi.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_radisys.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_rz1000.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_sc1200.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_serverworks.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_sil680.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_sis.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_sl82c105.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_triflex.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ata/pata_via.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/atm/he.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/base/hypervisor.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/block/DAC960.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/block/cciss_scsi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/block/cryptoloop.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/agp.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/backend.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/efficeon-agp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/frontend.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/generic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/intel-agp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/uninorth-agp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/agp/via-agp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/briq_panel.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/hvc_console.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/hvc_console.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/hvc_iseries.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/hvc_rtas.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/hvc_vio.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/hvsi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/istallion.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/tpm/tpm_atmel.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/viocons.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/char/viotape.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/cpufreq/cpufreq.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/cpufreq/cpufreq_ondemand.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/cpufreq/cpufreq_stats.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/crypto/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/crypto/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/crypto/padlock-aes.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/crypto/padlock-sha.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/crypto/padlock.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/i2c/busses/i2c-powermac.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/ide/ppc/pmac.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/addr.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/cache.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/cm.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/cma.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/device.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/iwcm.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/iwcm.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/mad.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/mad_priv.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/mad_rmpp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/sa_query.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/smi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/sysfs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/ucm.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/user_mad.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/core/verbs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/Kbuild 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/Kconfig 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_ae.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_ae.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_alloc.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_cm.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_cq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_intr.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_mm.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_mq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_mq.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_pd.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_provider.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_provider.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_qp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_rnic.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_status.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_user.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_vq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_vq.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/amso1100/c2_wr.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/Kconfig 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/Makefile 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_av.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_classes.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_classes_pSeries.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_cq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_eq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_hca.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_irq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_irq.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_iverbs.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_main.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_mcast.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_mrmw.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_mrmw.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_pd.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_qes.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_qp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_reqs.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_sqp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_tools.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ehca_uverbs.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hcp_if.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hcp_if.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hcp_phyp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hcp_phyp.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hipz_fns.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hipz_fns_core.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/hipz_hw.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ipz_pt_fn.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ehca/ipz_pt_fn.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ipath/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/hw/ipath/ipath_mmap.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/ulp/iser/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/infiniband/ulp/srp/ib_srp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/isdn/i4l/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/adbhid.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/macio_asic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/macio_sysfs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/smu.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/therm_adt746x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/therm_pm72.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/via-cuda.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/via-pmu-led.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/via-pmu.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/windfarm_pm81.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/macintosh/windfarm_pm91.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/md/dm-crypt.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/message/fusion/mptfc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/message/fusion/mptsas.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/chips/cfi_cmdset_0002.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/devices/pmc551.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/amd76xrom.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/arctic-mtd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/beech-mtd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/cstm_mips_ixx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/ebony.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/fortunet.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/ichxrom.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/iq80310.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
drivers/mtd/maps/ixp4xx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/l440gx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/lasat.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/nettel.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/ocotea.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/pcmciamtd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/physmap.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/redwood.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/sbc8240.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/scx200_docflash.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/maps/walnut.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/mtdcore.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/nand/au1550nd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/nand/edb7312.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/nand/ndfc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/nand/ppchameleonevb.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/mtd/ssfdc.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c501.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c501.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c503.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c503.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c505.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c505.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c507.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c509.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c515.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c523.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c523.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c527.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c527.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/3c59x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/7990.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/7990.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/8139cp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/8139too.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/82596.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/8390.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/8390.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/Space.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/a2065.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/a2065.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ac3200.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/acenic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/acenic.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/acenic_firmware.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/amd8111e.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/amd8111e.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/apne.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/arcnet/com20020-pci.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ariadne.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/arm/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/arm/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/arm/at91_ether.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/arm/ep93xx_eth.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/arm/etherh.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/at1700.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/atari_bionet.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/atari_pamsnet.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/atarilance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/atp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/au1000_eth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/au1000_eth.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/b44.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/bmac.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/bmac.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/bnx2.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/bnx2.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/bonding/bond_main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/bsd_comp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/cassini.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/cassini.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/chelsio/cxgb2.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/chelsio/sge.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/cris/eth_v10.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/cs89x0.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/cs89x0.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/de600.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/de620.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/declance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/defxx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/defxx.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/depca.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/depca.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dgrs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dgrs.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dgrs_asstruct.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dgrs_bcomm.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dgrs_ether.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dgrs_i82596.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dl2k.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dl2k.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/dummy.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e100.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000_ethtool.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000_hw.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000_hw.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000_main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000_osdep.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e1000/e1000_param.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/e2100.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/eepro.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/eepro100.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/eexpress.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/eexpress.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/Makefile 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_ethtool.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_hcall.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_hw.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_main.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_phyp.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_phyp.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_qmr.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ehea/ehea_qmr.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/epic100.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/eql.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/eth16i.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ewrk3.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ewrk3.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/fealnx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/fec.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/fec_8xx/fec_main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/forcedeth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/fs_enet/fs_enet-main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gianfar.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gianfar.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gianfar_ethtool.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gianfar_mii.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gianfar_mii.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gianfar_sysfs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gt64240eth.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/gt96100eth.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
drivers/net/gt96100eth.h 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
drivers/net/hamachi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/hp-plus.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/hp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/hp100.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/hp100.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/hplance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ibmveth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ibmveth.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ifb.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ioc3-eth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/irda/ali-ircc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/irda/irport.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/irda/mcs7780.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/irda/via-ircc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/irda/w83977af_ir.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/isa-skeleton.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/iseries_veth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ixgb/ixgb.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ixgb/ixgb_ethtool.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ixgb/ixgb_hw.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ixgb/ixgb_ids.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ixgb/ixgb_main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ixgb/ixgb_osdep.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/jazzsonic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/lance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/lasi_82596.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/lne390.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/loopback.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/lp486e.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/mac8390.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/mac89x0.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/mace.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/macmace.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/macsonic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/meth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/mii.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/mv643xx_eth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/myri10ge/myri10ge.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/myri10ge/myri10ge_mcp.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/myri_code.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/myri_sbus.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/natsemi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ne-h8300.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ne.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ne2.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ne2k-pci.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ne3210.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/netx-eth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ni5010.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ni52.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ni52.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ni65.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ni65.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ns83820.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/oaknet.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pci-skeleton.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/3c574_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/3c589_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/axnet_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/fmvj18x_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/ibmtr_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/nmclan_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/pcnet_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/smc91c92_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcmcia/xirc2ps_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pcnet32.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/phy/fixed.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/phy/smsc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/phy/vitesse.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/plip.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ppp_async.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ppp_deflate.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ppp_generic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ppp_mppe.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ppp_synctty.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/pppoe.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/qla3xxx.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/qla3xxx.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/r8169.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/rionet.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/rrunner.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/rrunner.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/s2io-regs.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/s2io.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/s2io.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/saa9730.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/saa9730.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sb1000.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sb1250-mac.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/seeq8005.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/seeq8005.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sgiseeq.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/shaper.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sis190.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sis900.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sis900.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sk98lin/skethtool.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sk98lin/skge.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sk_mca.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sk_mca.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/skfp/skfddi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/skge.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/skge.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sky2.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sky2.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/slhc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/slip.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/slip.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc-mca.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc-ultra.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc-ultra32.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc911x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc9194.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc9194.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/smc91x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sonic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sonic.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/spider_net.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/spider_net.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/spider_net_ethtool.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/starfire.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/stnic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sun3_82586.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sun3_82586.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sun3lance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sunbmac.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sundance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sungem.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sungem.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sungem_phy.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sungem_phy.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sunhme.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sunlance.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/sunqe.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tc35815.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tg3.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tlan.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tlan.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tokenring/3c359.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tokenring/lanstreamer.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/21142.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/de2104x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/de4x5.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/dmfe.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/eeprom.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/interrupt.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/media.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/pnic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/pnic2.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/timer.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/tulip.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/tulip_core.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/uli526x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/winbond-840.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/xircom_cb.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tulip/xircom_tulip_cb.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/tun.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/typhoon-firmware.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/typhoon.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/typhoon.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/ucc_geth.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/via-rhine.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/via-velocity.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/via-velocity.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/cycx_main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/dlci.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/dscc4.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/farsync.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/lmc/lmc_main.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/pc300_drv.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/pci200syn.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/sdla.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wan/wanxl.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/airo.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/atmel_pci.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/ipw2100.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/ipw2200.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/ipw2200.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/orinoco.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/orinoco.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/orinoco_pci.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/orinoco_plx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/orinoco_tmd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/ray_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/wavelan_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/wl3501_cs.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/wireless/zd1211rw/zd_rf_al7230b.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/yellowfin.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/net/znet.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/pci/hotplug/rpaphp_core.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/pci/quirks.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/block/dasd.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/block/dasd_devmap.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/block/dasd_eer.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/block/dasd_int.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/block/xpram.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/char/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/char/monwriter.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/char/vmcp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/char/vmcp.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/chsc.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/cio.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/css.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/device.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/device_fsm.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/device_ops.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/device_pgid.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/qdio.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/cio/qdio.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/ap_bus.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/ap_bus.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/z90common.h 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
drivers/s390/crypto/z90hardware.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
drivers/s390/crypto/z90main.c 已删除 100644 → 0
浏览文件 @ c0601514
此差异已折叠。
drivers/s390/crypto/zcrypt_api.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_api.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_cca_key.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_cex2a.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_cex2a.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_error.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_pcica.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_pcica.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_pcicc.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_pcicc.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_pcixcc.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/crypto/zcrypt_pcixcc.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/s390mach.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_aux.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_ccw.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_dbf.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_def.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_erp.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_ext.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_fsf.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/scsi/zfcp_scsi.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/s390/sysinfo.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/BusLogic.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/Kconfig
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/Makefile
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/a2091.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/a2091.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/a3000.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/a3000.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/aachba.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/aacraid.h
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/commctrl.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/comminit.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/commsup.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/dpcsup.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/linit.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/rkt.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/rx.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aacraid/sa.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/advansys.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aha152x.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic7xxx/aic79xx_osm.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic7xxx/aic7xxx_osm.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic7xxx_old.c
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/Kconfig 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/Makefile 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_dev.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_dump.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_dump.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_hwi.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_hwi.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_init.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_reg.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_reg.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_reg_def.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_sas.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_scb.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_sds.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_seq.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_seq.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_task.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/aic94xx/aic94xx_tmf.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/arcmsr/Makefile 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/arcmsr/arcmsr.h 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/arcmsr/arcmsr_attr.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
drivers/scsi/arcmsr/arcmsr_hba.c 0 → 100644
浏览文件 @ 2dc94310
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或