Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
提交 8a84fc15 编写于 作者: D David Woodhouse
浏览文件
操作

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

Manually resolve conflict in include/mtd/Kbuild
Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
上级 28b79ff9 82965add
展开全部 隐藏空白更改
内联 并排
Showing with 53705 addition and 23191 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ 8a84fc15
......@@ -1620,7 +1620,8 @@ D: fbdev hacking
N: Jesper Juhl
E: jesper.juhl@gmail.com
D: Various fixes, cleanups and minor features.
D: Various fixes, cleanups and minor features all over the tree.
D: Wrote initial version of the hdaps driver (since passed on to others).
S: Lemnosvej 1, 3.tv
S: 2300 Copenhagen S.
S: Denmark
......@@ -2384,6 +2385,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/
......@@ -2470,7 +2478,8 @@ S: Derbyshire DE4 3RL
S: United Kingdom
N: Ian S. Nelson
E: ian.nelson@echostar.com
E: nelsonis@earthlink.net
P: 1024D/00D3D983 3EFD 7B86 B888 D7E2 29B6 9E97 576F 1B97 00D3 D983
D: Minor mmap and ide hacks
S: 1370 Atlantis Ave.
S: Lafayette CO, 80026
......
Documentation/00-INDEX
浏览文件 @ 8a84fc15
......@@ -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/ABI/obsolete/devfs → Documentation/ABI/removed/devfs
浏览文件 @ 8a84fc15
What: devfs
Date: July 2005
Date: July 2005 (scheduled), finally removed in kernel v2.6.18
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
devfs has been unmaintained for a number of years, has unfixable
races, contains a naming policy within the kernel that is
against the LSB, and can be replaced by using udev.
The files fs/devfs/*, include/linux/devfs_fs*.h will be removed,
The files fs/devfs/*, include/linux/devfs_fs*.h were removed,
along with the the assorted devfs function calls throughout the
kernel tree.
Users:
Documentation/ABI/testing/sysfs-power 0 → 100644
浏览文件 @ 8a84fc15
What: /sys/power/
Date: August 2006
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/power directory will contain files that will
provide a unified interface to the power management
subsystem.
What: /sys/power/state
Date: August 2006
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/power/state file controls the system power state.
Reading from this file returns what states are supported,
which is hard-coded to 'standby' (Power-On Suspend), 'mem'
(Suspend-to-RAM), and 'disk' (Suspend-to-Disk).
Writing to this file one of these strings causes the system to
transition into that state. Please see the file
Documentation/power/states.txt for a description of each of
these states.
What: /sys/power/disk
Date: August 2006
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/power/disk file controls the operating mode of the
suspend-to-disk mechanism. Reading from this file returns
the name of the method by which the system will be put to
sleep on the next suspend. There are four methods supported:
'firmware' - means that the memory image will be saved to disk
by some firmware, in which case we also assume that the
firmware will handle the system suspend.
'platform' - the memory image will be saved by the kernel and
the system will be put to sleep by the platform driver (e.g.
ACPI or other PM registers).
'shutdown' - the memory image will be saved by the kernel and
the system will be powered off.
'reboot' - the memory image will be saved by the kernel and
the system will be rebooted.
The suspend-to-disk method may be chosen by writing to this
file one of the accepted strings:
'firmware'
'platform'
'shutdown'
'reboot'
It will only change to 'firmware' or 'platform' if the system
supports that.
What: /sys/power/image_size
Date: August 2006
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/power/image_size file controls the size of the image
created by the suspend-to-disk mechanism. It can be written a
string representing a non-negative integer that will be used
as an upper limit of the image size, in bytes. The kernel's
suspend-to-disk code will do its best to ensure the image size
will not exceed this number. However, if it turns out to be
impossible, the kernel will try to suspend anyway using the
smallest image possible. In particular, if "0" is written to
this file, the suspend image will be as small as possible.
Reading from this file will display the current image size
limit, which is set to 500 MB by default.
What: /sys/power/pm_trace
Date: August 2006
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/power/pm_trace file controls the code which saves the
last PM event point in the RTC across reboots, so that you can
debug a machine that just hangs during suspend (or more
commonly, during resume). Namely, the RTC is only used to save
the last PM event point if this file contains '1'. Initially
it contains '0' which may be changed to '1' by writing a
string representing a nonzero integer into it.
To use this debugging feature you should attempt to suspend
the machine, then reboot it and run
dmesg -s 1000000 | grep 'hash matches'
CAUTION: Using it will cause your machine's real-time (CMOS)
clock to be set to a random invalid time after a resume.
Documentation/Changes
浏览文件 @ 8a84fc15
......@@ -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/CodingStyle
浏览文件 @ 8a84fc15
......@@ -532,6 +532,40 @@ appears outweighs the potential value of the hint that tells gcc to do
something it would have done anyway.
Chapter 16: Function return values and names
Functions can return values of many different kinds, and one of the
most common is a value indicating whether the function succeeded or
failed. Such a value can be represented as an error-code integer
(-Exxx = failure, 0 = success) or a "succeeded" boolean (0 = failure,
non-zero = success).
Mixing up these two sorts of representations is a fertile source of
difficult-to-find bugs. If the C language included a strong distinction
between integers and booleans then the compiler would find these mistakes
for us... but it doesn't. To help prevent such bugs, always follow this
convention:
If the name of a function is an action or an imperative command,
the function should return an error-code integer. If the name
is a predicate, the function should return a "succeeded" boolean.
For example, "add work" is a command, and the add_work() function returns 0
for success or -EBUSY for failure. In the same way, "PCI device present" is
a predicate, and the pci_dev_present() function returns 1 if it succeeds in
finding a matching device or 0 if it doesn't.
All EXPORTed functions must respect this convention, and so should all
public functions. Private (static) functions need not, but it is
recommended that they do.
Functions whose return value is the actual result of a computation, rather
than an indication of whether the computation succeeded, are not subject to
this rule. Generally they indicate failure by returning some out-of-range
result. Typical examples would be functions that return pointers; they use
NULL or the ERR_PTR mechanism to report failure.
Appendix I: References
......
Documentation/DocBook/kernel-api.tmpl
浏览文件 @ 8a84fc15
......@@ -181,27 +181,6 @@ X!Ilib/string.c
</sect1>
</chapter>
<chapter id="proc">
<title>The proc filesystem</title>
<sect1><title>sysctl interface</title>
!Ekernel/sysctl.c
</sect1>
<sect1><title>proc filesystem interface</title>
!Ifs/proc/base.c
</sect1>
</chapter>
<chapter id="debugfs">
<title>The debugfs filesystem</title>
<sect1><title>debugfs interface</title>
!Efs/debugfs/inode.c
!Efs/debugfs/file.c
</sect1>
</chapter>
<chapter id="vfs">
<title>The Linux VFS</title>
<sect1><title>The Filesystem types</title>
......@@ -234,6 +213,50 @@ X!Ilib/string.c
</sect1>
</chapter>
<chapter id="proc">
<title>The proc filesystem</title>
<sect1><title>sysctl interface</title>
!Ekernel/sysctl.c
</sect1>
<sect1><title>proc filesystem interface</title>
!Ifs/proc/base.c
</sect1>
</chapter>
<chapter id="sysfs">
<title>The Filesystem for Exporting Kernel Objects</title>
!Efs/sysfs/file.c
!Efs/sysfs/symlink.c
!Efs/sysfs/bin.c
</chapter>
<chapter id="debugfs">
<title>The debugfs filesystem</title>
<sect1><title>debugfs interface</title>
!Efs/debugfs/inode.c
!Efs/debugfs/file.c
</sect1>
</chapter>
<chapter id="relayfs">
<title>relay interface support</title>
<para>
Relay interface support
is designed to provide an efficient mechanism for tools and
facilities to relay large amounts of data from kernel space to
user space.
</para>
<sect1><title>relay interface</title>
!Ekernel/relay.c
!Ikernel/relay.c
</sect1>
</chapter>
<chapter id="netcore">
<title>Linux Networking</title>
<sect1><title>Networking Base Types</title>
......@@ -349,13 +372,6 @@ X!Earch/i386/kernel/mca.c
</sect1>
</chapter>
<chapter id="sysfs">
<title>The Filesystem for Exporting Kernel Objects</title>
!Efs/sysfs/file.c
!Efs/sysfs/symlink.c
!Efs/sysfs/bin.c
</chapter>
<chapter id="security">
<title>Security Framework</title>
!Esecurity/security.c
......@@ -386,6 +402,7 @@ X!Iinclude/linux/device.h
-->
!Edrivers/base/driver.c
!Edrivers/base/core.c
!Edrivers/base/class.c
!Edrivers/base/firmware_class.c
!Edrivers/base/transport_class.c
!Edrivers/base/dmapool.c
......@@ -437,6 +454,11 @@ X!Edrivers/pnp/system.c
!Eblock/ll_rw_blk.c
</chapter>
<chapter id="chrdev">
<title>Char devices</title>
!Efs/char_dev.c
</chapter>
<chapter id="miscdev">
<title>Miscellaneous Devices</title>
!Edrivers/char/misc.c
......
Documentation/DocBook/libata.tmpl
浏览文件 @ 8a84fc15
......@@ -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/DocBook/usb.tmpl
浏览文件 @ 8a84fc15
......@@ -43,59 +43,52 @@
<para>A Universal Serial Bus (USB) is used to connect a host,
such as a PC or workstation, to a number of peripheral
devices. USB uses a tree structure, with the host at the
devices. USB uses a tree structure, with the host as the
root (the system's master), hubs as interior nodes, and
peripheral devices as leaves (and slaves).
peripherals as leaves (and slaves).
Modern PCs support several such trees of USB devices, usually
one USB 2.0 tree (480 Mbit/sec each) with
a few USB 1.1 trees (12 Mbit/sec each) that are used when you
connect a USB 1.1 device directly to the machine's "root hub".
</para>
<para>That master/slave asymmetry was designed in part for
ease of use. It is not physically possible to assemble
(legal) USB cables incorrectly: all upstream "to-the-host"
connectors are the rectangular type, matching the sockets on
root hubs, and the downstream type are the squarish type
(or they are built in to the peripheral).
Software doesn't need to deal with distributed autoconfiguration
since the pre-designated master node manages all that.
At the electrical level, bus protocol overhead is reduced by
eliminating arbitration and moving scheduling into host software.
<para>That master/slave asymmetry was designed-in for a number of
reasons, one being ease of use. It is not physically possible to
assemble (legal) USB cables incorrectly: all upstream "to the host"
connectors are the rectangular type (matching the sockets on
root hubs), and all downstream connectors are the squarish type
(or they are built into the peripheral).
Also, the host software doesn't need to deal with distributed
auto-configuration since the pre-designated master node manages all that.
And finally, at the electrical level, bus protocol overhead is reduced by
eliminating arbitration and moving scheduling into the host software.
</para>
<para>USB 1.0 was announced in January 1996, and was revised
<para>USB 1.0 was announced in January 1996 and was revised
as USB 1.1 (with improvements in hub specification and
support for interrupt-out transfers) in September 1998.
USB 2.0 was released in April 2000, including high speed
transfers and transaction translating hubs (used for USB 1.1
USB 2.0 was released in April 2000, adding high-speed
transfers and transaction-translating hubs (used for USB 1.1
and 1.0 backward compatibility).
</para>
<para>USB support was added to Linux early in the 2.2 kernel series
shortly before the 2.3 development forked off. Updates
from 2.3 were regularly folded back into 2.2 releases, bringing
new features such as <filename>/sbin/hotplug</filename> support,
more drivers, and more robustness.
The 2.5 kernel series continued such improvements, and also
worked on USB 2.0 support,
higher performance,
better consistency between host controller drivers,
API simplification (to make bugs less likely),
and providing internal "kerneldoc" documentation.
<para>Kernel developers added USB support to Linux early in the 2.2 kernel
series, shortly before 2.3 development forked. Updates from 2.3 were
regularly folded back into 2.2 releases, which improved reliability and
brought <filename>/sbin/hotplug</filename> support as well more drivers.
Such improvements were continued in the 2.5 kernel series, where they added
USB 2.0 support, improved performance, and made the host controller drivers
(HCDs) more consistent. They also simplified the API (to make bugs less
likely) and added internal "kerneldoc" documentation.
</para>
<para>Linux can run inside USB devices as well as on
the hosts that control the devices.
Because the Linux 2.x USB support evolved to support mass market
platforms such as Apple Macintosh or PC-compatible systems,
it didn't address design concerns for those types of USB systems.
So it can't be used inside mass-market PDAs, or other peripherals.
USB device drivers running inside those Linux peripherals
But USB device drivers running inside those peripherals
don't do the same things as the ones running inside hosts,
and so they've been given a different name:
they're called <emphasis>gadget drivers</emphasis>.
This document does not present gadget drivers.
so they've been given a different name:
<emphasis>gadget drivers</emphasis>.
This document does not cover gadget drivers.
</para>
</chapter>
......@@ -103,17 +96,14 @@
<chapter id="host">
<title>USB Host-Side API Model</title>
<para>Within the kernel,
host-side drivers for USB devices talk to the "usbcore" APIs.
There are two types of public "usbcore" APIs, targetted at two different
layers of USB driver. Those are
<emphasis>general purpose</emphasis> drivers, exposed through
driver frameworks such as block, character, or network devices;
and drivers that are <emphasis>part of the core</emphasis>,
which are involved in managing a USB bus.
Such core drivers include the <emphasis>hub</emphasis> driver,
which manages trees of USB devices, and several different kinds
of <emphasis>host controller driver (HCD)</emphasis>,
<para>Host-side drivers for USB devices talk to the "usbcore" APIs.
There are two. One is intended for
<emphasis>general-purpose</emphasis> drivers (exposed through
driver frameworks), and the other is for drivers that are
<emphasis>part of the core</emphasis>.
Such core drivers include the <emphasis>hub</emphasis> driver
(which manages trees of USB devices) and several different kinds
of <emphasis>host controller drivers</emphasis>,
which control individual busses.
</para>
......@@ -122,21 +112,21 @@
<itemizedlist>
<listitem><para>USB supports four kinds of data transfer
(control, bulk, interrupt, and isochronous). Two transfer
types use bandwidth as it's available (control and bulk),
while the other two types of transfer (interrupt and isochronous)
<listitem><para>USB supports four kinds of data transfers
(control, bulk, interrupt, and isochronous). Two of them (control
and bulk) use bandwidth as it's available,
while the other two (interrupt and isochronous)
are scheduled to provide guaranteed bandwidth.
</para></listitem>
<listitem><para>The device description model includes one or more
"configurations" per device, only one of which is active at a time.
Devices that are capable of high speed operation must also support
full speed configurations, along with a way to ask about the
"other speed" configurations that might be used.
Devices that are capable of high-speed operation must also support
full-speed configurations, along with a way to ask about the
"other speed" configurations which might be used.
</para></listitem>
<listitem><para>Configurations have one or more "interface", each
<listitem><para>Configurations have one or more "interfaces", each
of which may have "alternate settings". Interfaces may be
standardized by USB "Class" specifications, or may be specific to
a vendor or device.</para>
......@@ -162,7 +152,7 @@
</para></listitem>
<listitem><para>The Linux USB API supports synchronous calls for
control and bulk messaging.
control and bulk messages.
It also supports asynchnous calls for all kinds of data transfer,
using request structures called "URBs" (USB Request Blocks).
</para></listitem>
......@@ -463,14 +453,25 @@
file in your Linux kernel sources.
</para>
<para>Otherwise the main use for this file from programs
is to poll() it to get notifications of usb devices
as they're plugged or unplugged.
To see what changed, you'd need to read the file and
compare "before" and "after" contents, scan the filesystem,
or see its hotplug event.
<para>This file, in combination with the poll() system call, can
also be used to detect when devices are added or removed:
<programlisting>int fd;
struct pollfd pfd;
fd = open("/proc/bus/usb/devices", O_RDONLY);
pfd = { fd, POLLIN, 0 };
for (;;) {
/* The first time through, this call will return immediately. */
poll(&amp;pfd, 1, -1);
/* To see what's changed, compare the file's previous and current
contents or scan the filesystem. (Scanning is more precise.) */
}</programlisting>
Note that this behavior is intended to be used for informational
and debug purposes. It would be more appropriate to use programs
such as udev or HAL to initialize a device or start a user-mode
helper program, for instance.
</para>
</sect1>
<sect1>
......
Documentation/HOWTO
浏览文件 @ 8a84fc15
......@@ -358,7 +358,8 @@ Here is a list of some of the different kernel trees available:
quilt trees:
- USB, PCI, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de>
kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
- x86-64, partly i386, Andi Kleen <ak@suse.de>
ftp.firstfloor.org:/pub/ak/x86_64/quilt/
Bug Reporting
-------------
......@@ -374,6 +375,26 @@ of information is needed by the kernel developers to help track down the
problem.
Managing bug reports
--------------------
One of the best ways to put into practice your hacking skills is by fixing
bugs reported by other people. Not only you will help to make the kernel
more stable, you'll learn to fix real world problems and you will improve
your skills, and other developers will be aware of your presence. Fixing
bugs is one of the best ways to earn merit amongst the developers, because
not many people like wasting time fixing other people's bugs.
To work in the already reported bug reports, go to http://bugzilla.kernel.org.
If you want to be advised of the future bug reports, you can subscribe to the
bugme-new mailing list (only new bug reports are mailed here) or to the
bugme-janitor mailing list (every change in the bugzilla is mailed here)
http://lists.osdl.org/mailman/listinfo/bugme-new
http://lists.osdl.org/mailman/listinfo/bugme-janitors
Mailing lists
-------------
......
Documentation/IPMI.txt
浏览文件 @ 8a84fc15
......@@ -326,9 +326,12 @@ for events, they will all receive all events that come in.
For receiving commands, you have to individually register commands you
want to receive. Call ipmi_register_for_cmd() and supply the netfn
and command name for each command you want to receive. Only one user
may be registered for each netfn/cmd, but different users may register
for different commands.
and command name for each command you want to receive. You also
specify a bitmask of the channels you want to receive the command from
(or use IPMI_CHAN_ALL for all channels if you don't care). Only one
user may be registered for each netfn/cmd/channel, but different users
may register for different commands, or the same command if the
channel bitmasks do not overlap.
From userland, equivalent IOCTLs are provided to do these functions.
......
Documentation/SubmitChecklist
浏览文件 @ 8a84fc15
......@@ -61,3 +61,8 @@ kernel patches.
Documentation/kernel-parameters.txt.
18: All new module parameters are documented with MODULE_PARM_DESC()
19: All new userspace interfaces are documented in Documentation/ABI/.
See Documentation/ABI/README for more information.
20: Check that it all passes `make headers_check'.
Documentation/SubmittingDrivers
浏览文件 @ 8a84fc15
......@@ -59,11 +59,11 @@ Copyright: The copyright owner must agree to use of GPL.
are the same person/entity. If not, the name of
the person/entity authorizing use of GPL should be
listed in case it's necessary to verify the will of
the copright owner.
the copyright owner.
Interfaces: If your driver uses existing interfaces and behaves like
other drivers in the same class it will be much more likely
to be accepted than if it invents gratuitous new ones.
to be accepted than if it invents gratuitous new ones.
If you need to implement a common API over Linux and NT
drivers do it in userspace.
......@@ -88,7 +88,7 @@ Clarity: It helps if anyone can see how to fix the driver. It helps
it will go in the bitbucket.
Control: In general if there is active maintainance of a driver by
the author then patches will be redirected to them unless
the author then patches will be redirected to them unless
they are totally obvious and without need of checking.
If you want to be the contact and update point for the
driver it is a good idea to state this in the comments,
......@@ -100,7 +100,7 @@ What Criteria Do Not Determine Acceptance
Vendor: Being the hardware vendor and maintaining the driver is
often a good thing. If there is a stable working driver from
other people already in the tree don't expect 'we are the
vendor' to get your driver chosen. Ideally work with the
vendor' to get your driver chosen. Ideally work with the
existing driver author to build a single perfect driver.
Author: It doesn't matter if a large Linux company wrote the driver,
......@@ -116,17 +116,13 @@ Linux kernel master tree:
ftp.??.kernel.org:/pub/linux/kernel/...
?? == your country code, such as "us", "uk", "fr", etc.
Linux kernel mailing list:
Linux kernel mailing list:
linux-kernel@vger.kernel.org
[mail majordomo@vger.kernel.org to subscribe]
Linux Device Drivers, Third Edition (covers 2.6.10):
http://lwn.net/Kernel/LDD3/ (free version)
Kernel traffic:
Weekly summary of kernel list activity (much easier to read)
http://www.kerneltraffic.org/kernel-traffic/
LWN.net:
Weekly summary of kernel development activity - http://lwn.net/
2.6 API changes:
......@@ -145,11 +141,8 @@ KernelNewbies:
Linux USB project:
http://www.linux-usb.org/
How to NOT write kernel driver by arjanv@redhat.com
http://people.redhat.com/arjanv/olspaper.pdf
How to NOT write kernel driver by Arjan van de Ven:
http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf
Kernel Janitor:
http://janitor.kernelnewbies.org/
--
Last updated on 17 Nov 2005.
Documentation/SubmittingPatches
浏览文件 @ 8a84fc15
......@@ -173,15 +173,15 @@ For small patches you may want to CC the Trivial Patch Monkey
trivial@kernel.org managed by Adrian Bunk; which collects "trivial"
patches. Trivial patches must qualify for one of the following rules:
Spelling fixes in documentation
Spelling fixes which could break grep(1).
Spelling fixes which could break grep(1)
Warning fixes (cluttering with useless warnings is bad)
Compilation fixes (only if they are actually correct)
Runtime fixes (only if they actually fix things)
Removing use of deprecated functions/macros (eg. check_region).
Removing use of deprecated functions/macros (eg. check_region)
Contact detail and documentation fixes
Non-portable code replaced by portable code (even in arch-specific,
since people copy, as long as it's trivial)
Any fix by the author/maintainer of the file. (ie. patch monkey
Any fix by the author/maintainer of the file (ie. patch monkey
in re-transmission mode)
URL: <http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/>
......@@ -209,6 +209,19 @@ Exception: If your mailer is mangling patches then someone may ask
you to re-send them using MIME.
WARNING: Some mailers like Mozilla send your messages with
---- message header ----
Content-Type: text/plain; charset=us-ascii; format=flowed
---- message header ----
The problem is that "format=flowed" makes some of the mailers
on receiving side to replace TABs with spaces and do similar
changes. Thus the patches from you can look corrupted.
To fix this just make your mozilla defaults/pref/mailnews.js file to look like:
pref("mailnews.send_plaintext_flowed", false); // RFC 2646=======
pref("mailnews.display.disable_format_flowed_support", true);
7) E-mail size.
......@@ -245,13 +258,13 @@ updated change.
It is quite common for Linus to "drop" your patch without comment.
That's the nature of the system. If he drops your patch, it could be
due to
* Your patch did not apply cleanly to the latest kernel version
* Your patch did not apply cleanly to the latest kernel version.
* Your patch was not sufficiently discussed on linux-kernel.
* A style issue (see section 2),
* An e-mail formatting issue (re-read this section)
* A technical problem with your change
* He gets tons of e-mail, and yours got lost in the shuffle
* You are being annoying (See Figure 1)
* A style issue (see section 2).
* An e-mail formatting issue (re-read this section).
* A technical problem with your change.
* He gets tons of e-mail, and yours got lost in the shuffle.
* You are being annoying.
When in doubt, solicit comments on linux-kernel mailing list.
......@@ -476,10 +489,10 @@ SECTION 3 - REFERENCES
Andrew Morton, "The perfect patch" (tpp).
<http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
Jeff Garzik, "Linux kernel patch submission format."
Jeff Garzik, "Linux kernel patch submission format".
<http://linux.yyz.us/patch-format.html>
Greg Kroah-Hartman "How to piss off a kernel subsystem maintainer".
Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".
<http://www.kroah.com/log/2005/03/31/>
<http://www.kroah.com/log/2005/07/08/>
<http://www.kroah.com/log/2005/10/19/>
......@@ -488,9 +501,9 @@ Greg Kroah-Hartman "How to piss off a kernel subsystem maintainer".
NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
<http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>
Kernel Documentation/CodingStyle
Kernel Documentation/CodingStyle:
<http://sosdg.org/~coywolf/lxr/source/Documentation/CodingStyle>
Linus Torvald's mail on the canonical patch format:
Linus Torvalds's mail on the canonical patch format:
<http://lkml.org/lkml/2005/4/7/183>
--
Documentation/accounting/getdelays.c
浏览文件 @ 8a84fc15
......@@ -285,7 +285,7 @@ int main(int argc, char *argv[])
if (maskset) {
rc = send_cmd(nl_sd, id, mypid, TASKSTATS_CMD_GET,
TASKSTATS_CMD_ATTR_REGISTER_CPUMASK,
&cpumask, sizeof(cpumask));
&cpumask, strlen(cpumask) + 1);
PRINTF("Sent register cpumask, retval %d\n", rc);
if (rc < 0) {
printf("error sending register cpumask\n");
......@@ -315,7 +315,8 @@ int main(int argc, char *argv[])
}
if (msg.n.nlmsg_type == NLMSG_ERROR ||
!NLMSG_OK((&msg.n), rep_len)) {
printf("fatal reply error, errno %d\n", errno);
struct nlmsgerr *err = NLMSG_DATA(&msg);
printf("fatal reply error, errno %d\n", err->error);
goto done;
}
......@@ -383,7 +384,7 @@ int main(int argc, char *argv[])
if (maskset) {
rc = send_cmd(nl_sd, id, mypid, TASKSTATS_CMD_GET,
TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK,
&cpumask, sizeof(cpumask));
&cpumask, strlen(cpumask) + 1);
printf("Sent deregister mask, retval %d\n", rc);
if (rc < 0)
err(rc, "error sending deregister cpumask\n");
......
Documentation/accounting/taskstats-struct.txt 0 → 100644
浏览文件 @ 8a84fc15
The struct taskstats
--------------------
This document contains an explanation of the struct taskstats fields.
There are three different groups of fields in the struct taskstats:
1) Common and basic accounting fields
If CONFIG_TASKSTATS is set, the taskstats inteface is enabled and
the common fields and basic accounting fields are collected for
delivery at do_exit() of a task.
2) Delay accounting fields
These fields are placed between
/* Delay accounting fields start */
and
/* Delay accounting fields end */
Their values are collected if CONFIG_TASK_DELAY_ACCT is set.
3) Extended accounting fields
These fields are placed between
/* Extended accounting fields start */
and
/* Extended accounting fields end */
Their values are collected if CONFIG_TASK_XACCT is set.
Future extension should add fields to the end of the taskstats struct, and
should not change the relative position of each field within the struct.
struct taskstats {
1) Common and basic accounting fields:
/* The version number of this struct. This field is always set to
* TAKSTATS_VERSION, which is defined in <linux/taskstats.h>.
* Each time the struct is changed, the value should be incremented.
*/
__u16 version;
/* The exit code of a task. */
__u32 ac_exitcode; /* Exit status */
/* The accounting flags of a task as defined in <linux/acct.h>
* Defined values are AFORK, ASU, ACOMPAT, ACORE, and AXSIG.
*/
__u8 ac_flag; /* Record flags */
/* The value of task_nice() of a task. */
__u8 ac_nice; /* task_nice */
/* The name of the command that started this task. */
char ac_comm[TS_COMM_LEN]; /* Command name */
/* The scheduling discipline as set in task->policy field. */
__u8 ac_sched; /* Scheduling discipline */
__u8 ac_pad[3];
__u32 ac_uid; /* User ID */
__u32 ac_gid; /* Group ID */
__u32 ac_pid; /* Process ID */
__u32 ac_ppid; /* Parent process ID */
/* The time when a task begins, in [secs] since 1970. */
__u32 ac_btime; /* Begin time [sec since 1970] */
/* The elapsed time of a task, in [usec]. */
__u64 ac_etime; /* Elapsed time [usec] */
/* The user CPU time of a task, in [usec]. */
__u64 ac_utime; /* User CPU time [usec] */
/* The system CPU time of a task, in [usec]. */
__u64 ac_stime; /* System CPU time [usec] */
/* The minor page fault count of a task, as set in task->min_flt. */
__u64 ac_minflt; /* Minor Page Fault Count */
/* The major page fault count of a task, as set in task->maj_flt. */
__u64 ac_majflt; /* Major Page Fault Count */
2) Delay accounting fields:
/* Delay accounting fields start
*
* All values, until the comment "Delay accounting fields end" are
* available only if delay accounting is enabled, even though the last
* few fields are not delays
*
* xxx_count is the number of delay values recorded
* xxx_delay_total is the corresponding cumulative delay in nanoseconds
*
* xxx_delay_total wraps around to zero on overflow
* xxx_count incremented regardless of overflow
*/
/* Delay waiting for cpu, while runnable
* count, delay_total NOT updated atomically
*/
__u64 cpu_count;
__u64 cpu_delay_total;
/* Following four fields atomically updated using task->delays->lock */
/* Delay waiting for synchronous block I/O to complete
* does not account for delays in I/O submission
*/
__u64 blkio_count;
__u64 blkio_delay_total;
/* Delay waiting for page fault I/O (swap in only) */
__u64 swapin_count;
__u64 swapin_delay_total;
/* cpu "wall-clock" running time
* On some architectures, value will adjust for cpu time stolen
* from the kernel in involuntary waits due to virtualization.
* Value is cumulative, in nanoseconds, without a corresponding count
* and wraps around to zero silently on overflow
*/
__u64 cpu_run_real_total;
/* cpu "virtual" running time
* Uses time intervals seen by the kernel i.e. no adjustment
* for kernel's involuntary waits due to virtualization.
* Value is cumulative, in nanoseconds, without a corresponding count
* and wraps around to zero silently on overflow
*/
__u64 cpu_run_virtual_total;
/* Delay accounting fields end */
/* version 1 ends here */
3) Extended accounting fields
/* Extended accounting fields start */
/* Accumulated RSS usage in duration of a task, in MBytes-usecs.
* The current rss usage is added to this counter every time
* a tick is charged to a task's system time. So, at the end we
* will have memory usage multiplied by system time. Thus an
* average usage per system time unit can be calculated.
*/
__u64 coremem; /* accumulated RSS usage in MB-usec */
/* Accumulated virtual memory usage in duration of a task.
* Same as acct_rss_mem1 above except that we keep track of VM usage.
*/
__u64 virtmem; /* accumulated VM usage in MB-usec */
/* High watermark of RSS usage in duration of a task, in KBytes. */
__u64 hiwater_rss; /* High-watermark of RSS usage */
/* High watermark of VM usage in duration of a task, in KBytes. */
__u64 hiwater_vm; /* High-water virtual memory usage */
/* The following four fields are I/O statistics of a task. */
__u64 read_char; /* bytes read */
__u64 write_char; /* bytes written */
__u64 read_syscalls; /* read syscalls */
__u64 write_syscalls; /* write syscalls */
/* Extended accounting fields end */
}
Documentation/cpusets.txt
浏览文件 @ 8a84fc15
......@@ -217,11 +217,11 @@ exclusive cpuset. Also, the use of a Linux virtual file system (vfs)
to represent the cpuset hierarchy provides for a familiar permission
and name space for cpusets, with a minimum of additional kernel code.
The cpus file in the root (top_cpuset) cpuset is read-only.
It automatically tracks the value of cpu_online_map, using a CPU
hotplug notifier. If and when memory nodes can be hotplugged,
we expect to make the mems file in the root cpuset read-only
as well, and have it track the value of node_online_map.
The cpus and mems files in the root (top_cpuset) cpuset are
read-only. The cpus file automatically tracks the value of
cpu_online_map using a CPU hotplug notifier, and the mems file
automatically tracks the value of node_online_map using the
cpuset_track_online_nodes() hook.
1.4 What are exclusive cpusets ?
......
Documentation/crypto/api-intro.txt
浏览文件 @ 8a84fc15
......@@ -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/devices.txt
浏览文件 @ 8a84fc15
......@@ -2543,6 +2543,9 @@ Your cooperation is appreciated.
64 = /dev/usb/rio500 Diamond Rio 500
65 = /dev/usb/usblcd USBLCD Interface (info@usblcd.de)
66 = /dev/usb/cpad0 Synaptics cPad (mouse/LCD)
67 = /dev/usb/adutux0 1st Ontrak ADU device
...
76 = /dev/usb/adutux10 10th Ontrak ADU device
96 = /dev/usb/hiddev0 1st USB HID device
...
111 = /dev/usb/hiddev15 16th USB HID device
......
Documentation/dontdiff
浏览文件 @ 8a84fc15
......@@ -135,6 +135,7 @@ tags
times.h*
tkparse
trix_boot.h
utsrelease.h*
version.h*
vmlinux
vmlinux-*
......
Documentation/fb/intelfb.txt
浏览文件 @ 8a84fc15
Intel 830M/845G/852GM/855GM/865G/915G Framebuffer driver
Intel 830M/845G/852GM/855GM/865G/915G/945G Framebuffer driver
================================================================
A. Introduction
This is a framebuffer driver for various Intel 810/815 compatible
This is a framebuffer driver for various Intel 8xx/9xx compatible
graphics devices. These would include:
Intel 830M
Intel 810E845G
Intel 845G
Intel 852GM
Intel 855GM
Intel 865G
Intel 915G
Intel 915GM
Intel 945G
Intel 945GM
B. List of available options
......@@ -78,7 +81,7 @@ C. Kernel booting
Separate each option/option-pair by commas (,) and the option from its value
with an equals sign (=) as in the following:
video=i810fb:option1,option2=value2
video=intelfb:option1,option2=value2
Sample Usage
------------
......
Documentation/feature-removal-schedule.txt
浏览文件 @ 8a84fc15
......@@ -6,6 +6,21 @@ be removed from this file.
---------------------------
What: /sys/devices/.../power/state
dev->power.power_state
dpm_runtime_{suspend,resume)()
When: July 2007
Why: Broken design for runtime control over driver power states, confusing
driver-internal runtime power management with: mechanisms to support
system-wide sleep state transitions; event codes that distinguish
different phases of swsusp "sleep" transitions; and userspace policy
inputs. This framework was never widely used, and most attempts to
use it were broken. Drivers should instead be exposing domain-specific
interfaces either to kernel or to userspace.
Who: Pavel Machek <pavel@suse.cz>
---------------------------
What: RAW driver (CONFIG_RAW_DRIVER)
When: December 2005
Why: declared obsolete since kernel 2.6.3
......@@ -31,17 +46,8 @@ Who: Jody McIntyre <scjody@modernduck.com>
---------------------------
What: sbp2: module parameter "force_inquiry_hack"
When: July 2006
Why: Superceded by parameter "workarounds". Both parameters are meant to be
used ad-hoc and for single devices only, i.e. not in modprobe.conf,
therefore the impact of this feature replacement should be low.
Who: Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
When: July 2006
When: December 2006
Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6
series. The old API have lots of drawbacks and don't provide enough
means to work with all video and audio standards. The newer API is
......@@ -55,6 +61,18 @@ Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
---------------------------
What: sys_sysctl
When: January 2007
Why: The same information is available through /proc/sys and that is the
interface user space prefers to use. And there do not appear to be
any existing user in user space of sys_sysctl. The additional
maintenance overhead of keeping a set of binary names gets
in the way of doing a good job of maintaining this interface.
Who: Eric Biederman <ebiederm@xmission.com>
---------------------------
What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
When: November 2005
Files: drivers/pcmcia/: pcmcia_ioctl.c
......@@ -202,14 +220,6 @@ Who: Nick Piggin <npiggin@suse.de>
---------------------------
What: Support for the MIPS EV96100 evaluation board
When: September 2006
Why: Does no longer build since at least November 15, 2003, apparently
no userbase left.
Who: Ralf Baechle <ralf@linux-mips.org>
---------------------------
What: Support for the Momentum / PMC-Sierra Jaguar ATX evaluation board
When: September 2006
Why: Does no longer build since quite some time, and was never popular,
......@@ -294,3 +304,24 @@ Why: The frame diverter is included in most distribution kernels, but is
It is not clear if anyone is still using it.
Who: Stephen Hemminger <shemminger@osdl.org>
---------------------------
What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
When: Oktober 2008
Why: The stacking of class devices makes these values misleading and
inconsistent.
Class devices should not carry any of these properties, and bus
devices have SUBSYTEM and DRIVER as a replacement.
Who: Kay Sievers <kay.sievers@suse.de>
---------------------------
What: i2c-isa
When: December 2006
Why: i2c-isa is a non-sense and doesn't fit in the device driver
model. Drivers relying on it are better implemented as platform
drivers.
Who: Jean Delvare <khali@linux-fr.org>
---------------------------
Documentation/filesystems/Locking
浏览文件 @ 8a84fc15
......@@ -356,10 +356,9 @@ The last two are called only from check_disk_change().
prototypes:
loff_t (*llseek) (struct file *, loff_t, int);
ssize_t (*read) (struct file *, char __user *, size_t, loff_t *);
ssize_t (*aio_read) (struct kiocb *, char __user *, size_t, loff_t);
ssize_t (*write) (struct file *, const char __user *, size_t, loff_t *);
ssize_t (*aio_write) (struct kiocb *, const char __user *, size_t,
loff_t);
ssize_t (*aio_read) (struct kiocb *, const struct iovec *, unsigned long, loff_t);
ssize_t (*aio_write) (struct kiocb *, const struct iovec *, unsigned long, loff_t);
int (*readdir) (struct file *, void *, filldir_t);
unsigned int (*poll) (struct file *, struct poll_table_struct *);
int (*ioctl) (struct inode *, struct file *, unsigned int,
......
Documentation/filesystems/proc.txt
浏览文件 @ 8a84fc15
......@@ -39,6 +39,8 @@ Table of Contents
2.9 Appletalk
2.10 IPX
2.11 /proc/sys/fs/mqueue - POSIX message queues filesystem
2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score
2.13 /proc/<pid>/oom_score - Display current oom-killer score
------------------------------------------------------------------------------
Preface
......@@ -1124,11 +1126,15 @@ debugging information is displayed on console.
NMI switch that most IA32 servers have fires unknown NMI up, for example.
If a system hangs up, try pressing the NMI switch.
[NOTE]
This function and oprofile share a NMI callback. Therefore this function
cannot be enabled when oprofile is activated.
And NMI watchdog will be disabled when the value in this file is set to
non-zero.
nmi_watchdog
------------
Enables/Disables the NMI watchdog on x86 systems. When the value is non-zero
the NMI watchdog is enabled and will continuously test all online cpus to
determine whether or not they are still functioning properly.
Because the NMI watchdog shares registers with oprofile, by disabling the NMI
watchdog, oprofile may have more registers to utilize.
2.4 /proc/sys/vm - The virtual memory subsystem
......@@ -1958,6 +1964,22 @@ a queue must be less or equal then msg_max.
maximum message size value (it is every message queue's attribute set during
its creation).
2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score
------------------------------------------------------
This file can be used to adjust the score used to select which processes
should be killed in an out-of-memory situation. Giving it a high score will
increase the likelihood of this process being killed by the oom-killer. Valid
values are in the range -16 to +15, plus the special value -17, which disables
oom-killing altogether for this process.
2.13 /proc/<pid>/oom_score - Display current oom-killer score
-------------------------------------------------------------
------------------------------------------------------------------------------
This file can be used to check the current score used by the oom-killer is for
any given <pid>. Use it together with /proc/<pid>/oom_adj to tune which
process should be killed in an out-of-memory situation.
------------------------------------------------------------------------------
Summary
......
Documentation/filesystems/vfs.txt
浏览文件 @ 8a84fc15
......@@ -699,9 +699,9 @@ This describes how the VFS can manipulate an open file. As of kernel
struct file_operations {
loff_t (*llseek) (struct file *, loff_t, int);
ssize_t (*read) (struct file *, char __user *, size_t, loff_t *);
ssize_t (*aio_read) (struct kiocb *, char __user *, size_t, loff_t);
ssize_t (*write) (struct file *, const char __user *, size_t, loff_t *);
ssize_t (*aio_write) (struct kiocb *, const char __user *, size_t, loff_t);
ssize_t (*aio_read) (struct kiocb *, const struct iovec *, unsigned long, loff_t);
ssize_t (*aio_write) (struct kiocb *, const struct iovec *, unsigned long, loff_t);
int (*readdir) (struct file *, void *, filldir_t);
unsigned int (*poll) (struct file *, struct poll_table_struct *);
int (*ioctl) (struct inode *, struct file *, unsigned int, unsigned long);
......
Documentation/hwmon/it87
浏览文件 @ 8a84fc15
......@@ -13,12 +13,25 @@ Supported chips:
from Super I/O config space (8 I/O ports)
Datasheet: Publicly available at the ITE website
http://www.ite.com.tw/
* IT8716F
Prefix: 'it8716'
Addresses scanned: from Super I/O config space (8 I/O ports)
Datasheet: Publicly available at the ITE website
http://www.ite.com.tw/product_info/file/pc/IT8716F_V0.3.ZIP
* IT8718F
Prefix: 'it8718'
Addresses scanned: from Super I/O config space (8 I/O ports)
Datasheet: Publicly available at the ITE website
http://www.ite.com.tw/product_info/file/pc/IT8718F_V0.2.zip
http://www.ite.com.tw/product_info/file/pc/IT8718F_V0%203_(for%20C%20version).zip
* SiS950 [clone of IT8705F]
Prefix: 'it87'
Addresses scanned: from Super I/O config space (8 I/O ports)
Datasheet: No longer be available
Author: Christophe Gauthron <chrisg@0-in.com>
Authors:
Christophe Gauthron <chrisg@0-in.com>
Jean Delvare <khali@linux-fr.org>
Module Parameters
......@@ -43,26 +56,46 @@ Module Parameters
Description
-----------
This driver implements support for the IT8705F, IT8712F and SiS950 chips.
This driver also supports IT8712F, which adds SMBus access, and a VID
input, used to report the Vcore voltage of the Pentium processor.
The IT8712F additionally features VID inputs.
This driver implements support for the IT8705F, IT8712F, IT8716F,
IT8718F and SiS950 chips.
These chips are 'Super I/O chips', supporting floppy disks, infrared ports,
joysticks and other miscellaneous stuff. For hardware monitoring, they
include an 'environment controller' with 3 temperature sensors, 3 fan
rotation speed sensors, 8 voltage sensors, and associated alarms.
The IT8712F and IT8716F additionally feature VID inputs, used to report
the Vcore voltage of the processor. The early IT8712F have 5 VID pins,
the IT8716F and late IT8712F have 6. They are shared with other functions
though, so the functionality may not be available on a given system.
The driver dumbly assume it is there.
The IT8718F also features VID inputs (up to 8 pins) but the value is
stored in the Super-I/O configuration space. Due to technical limitations,
this value can currently only be read once at initialization time, so
the driver won't notice and report changes in the VID value. The two
upper VID bits share their pins with voltage inputs (in5 and in6) so you
can't have both on a given board.
The IT8716F, IT8718F and later IT8712F revisions have support for
2 additional fans. They are not yet supported by the driver.
The IT8716F and IT8718F, and late IT8712F and IT8705F also have optional
16-bit tachometer counters for fans 1 to 3. This is better (no more fan
clock divider mess) but not compatible with the older chips and
revisions. For now, the driver only uses the 16-bit mode on the
IT8716F and IT8718F.
Temperatures are measured in degrees Celsius. An alarm is triggered once
when the Overtemperature Shutdown limit is crossed.
Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
triggered if the rotation speed has dropped below a programmable limit. Fan
readings can be divided by a programmable divider (1, 2, 4 or 8) to give the
readings more range or accuracy. Not all RPM values can accurately be
represented, so some rounding is done. With a divider of 2, the lowest
representable value is around 2600 RPM.
triggered if the rotation speed has dropped below a programmable limit. When
16-bit tachometer counters aren't used, fan readings can be divided by
a programmable divider (1, 2, 4 or 8) to give the readings more range or
accuracy. With a divider of 2, the lowest representable value is around
2600 RPM. Not all RPM values can accurately be represented, so some rounding
is done.
Voltage sensors (also known as IN sensors) report their values in volts. An
alarm is triggered if the voltage has crossed a programmable minimum or
......@@ -71,9 +104,9 @@ zero'; this is important for negative voltage measurements. All voltage
inputs can measure voltages between 0 and 4.08 volts, with a resolution of
0.016 volt. The battery voltage in8 does not have limit registers.
The VID lines (IT8712F only) encode the core voltage value: the voltage
level your processor should work with. This is hardcoded by the mainboard
and/or processor itself. It is a value in volts.
The VID lines (IT8712F/IT8716F/IT8718F) encode the core voltage value:
the voltage level your processor should work with. This is hardcoded by
the mainboard and/or processor itself. It is a value in volts.
If an alarm triggers, it will remain triggered until the hardware register
is read at least once. This means that the cause for the alarm may already
......
Documentation/hwmon/k8temp 0 → 100644
浏览文件 @ 8a84fc15
Kernel driver k8temp
====================
Supported chips:
* AMD K8 CPU
Prefix: 'k8temp'
Addresses scanned: PCI space
Datasheet: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/32559.pdf
Author: Rudolf Marek
Contact: Rudolf Marek <r.marek@sh.cvut.cz>
Description
-----------
This driver permits reading temperature sensor(s) embedded inside AMD K8 CPUs.
Official documentation says that it works from revision F of K8 core, but
in fact it seems to be implemented for all revisions of K8 except the first
two revisions (SH-B0 and SH-B3).
There can be up to four temperature sensors inside single CPU. The driver
will auto-detect the sensors and will display only temperatures from
implemented sensors.
Mapping of /sys files is as follows:
temp1_input - temperature of Core 0 and "place" 0
temp2_input - temperature of Core 0 and "place" 1
temp3_input - temperature of Core 1 and "place" 0
temp4_input - temperature of Core 1 and "place" 1
Temperatures are measured in degrees Celsius and measurement resolution is
1 degree C. It is expected that future CPU will have better resolution. The
temperature is updated once a second. Valid temperatures are from -49 to
206 degrees C.
Temperature known as TCaseMax was specified for processors up to revision E.
This temperature is defined as temperature between heat-spreader and CPU
case, so the internal CPU temperature supplied by this driver can be higher.
There is no easy way how to measure the temperature which will correlate
with TCaseMax temperature.
For newer revisions of CPU (rev F, socket AM2) there is a mathematically
computed temperature called TControl, which must be lower than TControlMax.
The relationship is following:
temp1_input - TjOffset*2 < TControlMax,
TjOffset is not yet exported by the driver, TControlMax is usually
70 degrees C. The rule of the thumb -> CPU temperature should not cross
60 degrees C too much.
Documentation/hwmon/vt1211 0 → 100644
浏览文件 @ 8a84fc15
Kernel driver vt1211
====================
Supported chips:
* VIA VT1211
Prefix: 'vt1211'
Addresses scanned: none, address read from Super-I/O config space
Datasheet: Provided by VIA upon request and under NDA
Authors: Juerg Haefliger <juergh@gmail.com>
This driver is based on the driver for kernel 2.4 by Mark D. Studebaker and
its port to kernel 2.6 by Lars Ekman.
Thanks to Joseph Chan and Fiona Gatt from VIA for providing documentation and
technical support.
Module Parameters
-----------------
* uch_config: int Override the BIOS default universal channel (UCH)
configuration for channels 1-5.
Legal values are in the range of 0-31. Bit 0 maps to
UCH1, bit 1 maps to UCH2 and so on. Setting a bit to 1
enables the thermal input of that particular UCH and
setting a bit to 0 enables the voltage input.
* int_mode: int Override the BIOS default temperature interrupt mode.
The only possible value is 0 which forces interrupt
mode 0. In this mode, any pending interrupt is cleared
when the status register is read but is regenerated as
long as the temperature stays above the hysteresis
limit.
Be aware that overriding BIOS defaults might cause some unwanted side effects!
Description
-----------
The VIA VT1211 Super-I/O chip includes complete hardware monitoring
capabilities. It monitors 2 dedicated temperature sensor inputs (temp1 and
temp2), 1 dedicated voltage (in5) and 2 fans. Additionally, the chip
implements 5 universal input channels (UCH1-5) that can be individually
programmed to either monitor a voltage or a temperature.
This chip also provides manual and automatic control of fan speeds (according
to the datasheet). The driver only supports automatic control since the manual
mode doesn't seem to work as advertised in the datasheet. In fact I couldn't
get manual mode to work at all! Be aware that automatic mode hasn't been
tested very well (due to the fact that my EPIA M10000 doesn't have the fans
connected to the PWM outputs of the VT1211 :-().
The following table shows the relationship between the vt1211 inputs and the
sysfs nodes.
Sensor Voltage Mode Temp Mode Default Use (from the datasheet)
------ ------------ --------- --------------------------------
Reading 1 temp1 Intel thermal diode
Reading 3 temp2 Internal thermal diode
UCH1/Reading2 in0 temp3 NTC type thermistor
UCH2 in1 temp4 +2.5V
UCH3 in2 temp5 VccP (processor core)
UCH4 in3 temp6 +5V
UCH5 in4 temp7 +12V
+3.3V in5 Internal VCC (+3.3V)
Voltage Monitoring
------------------
Voltages are sampled by an 8-bit ADC with a LSB of ~10mV. The supported input
range is thus from 0 to 2.60V. Voltage values outside of this range need
external scaling resistors. This external scaling needs to be compensated for
via compute lines in sensors.conf, like:
compute inx @*(1+R1/R2), @/(1+R1/R2)
The board level scaling resistors according to VIA's recommendation are as
follows. And this is of course totally dependent on the actual board
implementation :-) You will have to find documentation for your own
motherboard and edit sensors.conf accordingly.
Expected
Voltage R1 R2 Divider Raw Value
-----------------------------------------------
+2.5V 2K 10K 1.2 2083 mV
VccP --- --- 1.0 1400 mV (1)
+5V 14K 10K 2.4 2083 mV
+12V 47K 10K 5.7 2105 mV
+3.3V (int) 2K 3.4K 1.588 3300 mV (2)
+3.3V (ext) 6.8K 10K 1.68 1964 mV
(1) Depending on the CPU (1.4V is for a VIA C3 Nehemiah).
(2) R1 and R2 for 3.3V (int) are internal to the VT1211 chip and the driver
performs the scaling and returns the properly scaled voltage value.
Each measured voltage has an associated low and high limit which triggers an
alarm when crossed.
Temperature Monitoring
----------------------
Temperatures are reported in millidegree Celsius. Each measured temperature
has a high limit which triggers an alarm if crossed. There is an associated
hysteresis value with each temperature below which the temperature has to drop
before the alarm is cleared (this is only true for interrupt mode 0). The
interrupt mode can be forced to 0 in case the BIOS doesn't do it
automatically. See the 'Module Parameters' section for details.
All temperature channels except temp2 are external. Temp2 is the VT1211
internal thermal diode and the driver does all the scaling for temp2 and
returns the temperature in millidegree Celsius. For the external channels
temp1 and temp3-temp7, scaling depends on the board implementation and needs
to be performed in userspace via sensors.conf.
Temp1 is an Intel-type thermal diode which requires the following formula to
convert between sysfs readings and real temperatures:
compute temp1 (@-Offset)/Gain, (@*Gain)+Offset
According to the VIA VT1211 BIOS porting guide, the following gain and offset
values should be used:
Diode Type Offset Gain
---------- ------ ----
Intel CPU 88.638 0.9528
65.000 0.9686 *)
VIA C3 Ezra 83.869 0.9528
VIA C3 Ezra-T 73.869 0.9528
*) This is the formula from the lm_sensors 2.10.0 sensors.conf file. I don't
know where it comes from or how it was derived, it's just listed here for
completeness.
Temp3-temp7 support NTC thermistors. For these channels, the driver returns
the voltages as seen at the individual pins of UCH1-UCH5. The voltage at the
pin (Vpin) is formed by a voltage divider made of the thermistor (Rth) and a
scaling resistor (Rs):
Vpin = 2200 * Rth / (Rs + Rth) (2200 is the ADC max limit of 2200 mV)
The equation for the thermistor is as follows (google it if you want to know
more about it):
Rth = Ro * exp(B * (1 / T - 1 / To)) (To is 298.15K (25C) and Ro is the
nominal resistance at 25C)
Mingling the above two equations and assuming Rs = Ro and B = 3435 yields the
following formula for sensors.conf:
compute tempx 1 / (1 / 298.15 - (` (2200 / @ - 1)) / 3435) - 273.15,
2200 / (1 + (^ (3435 / 298.15 - 3435 / (273.15 + @))))
Fan Speed Control
-----------------
The VT1211 provides 2 programmable PWM outputs to control the speeds of 2
fans. Writing a 2 to any of the two pwm[1-2]_enable sysfs nodes will put the
PWM controller in automatic mode. There is only a single controller that
controls both PWM outputs but each PWM output can be individually enabled and
disabled.
Each PWM has 4 associated distinct output duty-cycles: full, high, low and
off. Full and off are internally hard-wired to 255 (100%) and 0 (0%),
respectively. High and low can be programmed via
pwm[1-2]_auto_point[2-3]_pwm. Each PWM output can be associated with a
different thermal input but - and here's the weird part - only one set of
thermal thresholds exist that controls both PWMs output duty-cycles. The
thermal thresholds are accessible via pwm[1-2]_auto_point[1-4]_temp. Note
that even though there are 2 sets of 4 auto points each, they map to the same
registers in the VT1211 and programming one set is sufficient (actually only
the first set pwm1_auto_point[1-4]_temp is writable, the second set is
read-only).
PWM Auto Point PWM Output Duty-Cycle
------------------------------------------------
pwm[1-2]_auto_point4_pwm full speed duty-cycle (hard-wired to 255)
pwm[1-2]_auto_point3_pwm high speed duty-cycle
pwm[1-2]_auto_point2_pwm low speed duty-cycle
pwm[1-2]_auto_point1_pwm off duty-cycle (hard-wired to 0)
Temp Auto Point Thermal Threshold
---------------------------------------------
pwm[1-2]_auto_point4_temp full speed temp
pwm[1-2]_auto_point3_temp high speed temp
pwm[1-2]_auto_point2_temp low speed temp
pwm[1-2]_auto_point1_temp off temp
Long story short, the controller implements the following algorithm to set the
PWM output duty-cycle based on the input temperature:
Thermal Threshold Output Duty-Cycle
(Rising Temp) (Falling Temp)
----------------------------------------------------------
full speed duty-cycle full speed duty-cycle
full speed temp
high speed duty-cycle full speed duty-cycle
high speed temp
low speed duty-cycle high speed duty-cycle
low speed temp
off duty-cycle low speed duty-cycle
off temp
Documentation/hwmon/w83627ehf 0 → 100644
浏览文件 @ 8a84fc15
Kernel driver w83627ehf
=======================
Supported chips:
* Winbond W83627EHF/EHG (ISA access ONLY)
Prefix: 'w83627ehf'
Addresses scanned: ISA address retrieved from Super I/O registers
Datasheet: http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/W83627EHF_%20W83627EHGb.pdf
Authors:
Jean Delvare <khali@linux-fr.org>
Yuan Mu (Winbond)
Rudolf Marek <r.marek@sh.cvut.cz>
Description
-----------
This driver implements support for the Winbond W83627EHF and W83627EHG
super I/O chips. We will refer to them collectively as Winbond chips.
The chips implement three temperature sensors, five fan rotation
speed sensors, ten analog voltage sensors, alarms with beep warnings (control
unimplemented), and some automatic fan regulation strategies (plus manual
fan control mode).
Temperatures are measured in degrees Celsius and measurement resolution is 1
degC for temp1 and 0.5 degC for temp2 and temp3. An alarm is triggered when
the temperature gets higher than high limit; it stays on until the temperature
falls below the Hysteresis value.
Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
triggered if the rotation speed has dropped below a programmable limit. Fan
readings can be divided by a programmable divider (1, 2, 4, 8, 16, 32, 64 or
128) to give the readings more range or accuracy. The driver sets the most
suitable fan divisor itself. Some fans might not be present because they
share pins with other functions.
Voltage sensors (also known as IN sensors) report their values in millivolts.
An alarm is triggered if the voltage has crossed a programmable minimum
or maximum limit.
The driver supports automatic fan control mode known as Thermal Cruise.
In this mode, the chip attempts to keep the measured temperature in a
predefined temperature range. If the temperature goes out of range, fan
is driven slower/faster to reach the predefined range again.
The mode works for fan1-fan4. Mapping of temperatures to pwm outputs is as
follows:
temp1 -> pwm1
temp2 -> pwm2
temp3 -> pwm3
prog -> pwm4 (the programmable setting is not supported by the driver)
/sys files
----------
pwm[1-4] - this file stores PWM duty cycle or DC value (fan speed) in range:
0 (stop) to 255 (full)
pwm[1-4]_enable - this file controls mode of fan/temperature control:
* 1 Manual Mode, write to pwm file any value 0-255 (full speed)
* 2 Thermal Cruise
Thermal Cruise mode
-------------------
If the temperature is in the range defined by:
pwm[1-4]_target - set target temperature, unit millidegree Celcius
(range 0 - 127000)
pwm[1-4]_tolerance - tolerance, unit millidegree Celcius (range 0 - 15000)
there are no changes to fan speed. Once the temperature leaves the interval,
fan speed increases (temp is higher) or decreases if lower than desired.
There are defined steps and times, but not exported by the driver yet.
pwm[1-4]_min_output - minimum fan speed (range 1 - 255), when the temperature
is below defined range.
pwm[1-4]_stop_time - how many milliseconds [ms] must elapse to switch
corresponding fan off. (when the temperature was below
defined range).
Note: last two functions are influenced by other control bits, not yet exported
by the driver, so a change might not have any effect.
Documentation/hwmon/w83791d
浏览文件 @ 8a84fc15
......@@ -5,7 +5,7 @@ Supported chips:
* Winbond W83791D
Prefix: 'w83791d'
Addresses scanned: I2C 0x2c - 0x2f
Datasheet: http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/W83791Da.pdf
Datasheet: http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/W83791D_W83791Gb.pdf
Author: Charles Spirakis <bezaur@gmail.com>
......@@ -20,6 +20,9 @@ Credits:
Chunhao Huang <DZShen@Winbond.com.tw>,
Rudolf Marek <r.marek@sh.cvut.cz>
Additional contributors:
Sven Anders <anders@anduras.de>
Module Parameters
-----------------
......@@ -46,7 +49,8 @@ Module Parameters
Description
-----------
This driver implements support for the Winbond W83791D chip.
This driver implements support for the Winbond W83791D chip. The W83791G
chip appears to be the same as the W83791D but is lead free.
Detection of the chip can sometimes be foiled because it can be in an
internal state that allows no clean access (Bank with ID register is not
......@@ -71,34 +75,36 @@ Voltage sensors (also known as IN sensors) report their values in millivolts.
An alarm is triggered if the voltage has crossed a programmable minimum
or maximum limit.
Alarms are provided as output from a "realtime status register". The
following bits are defined:
bit - alarm on:
0 - Vcore
1 - VINR0
2 - +3.3VIN
3 - 5VDD
4 - temp1
5 - temp2
6 - fan1
7 - fan2
8 - +12VIN
9 - -12VIN
10 - -5VIN
11 - fan3
12 - chassis
13 - temp3
14 - VINR1
15 - reserved
16 - tart1
17 - tart2
18 - tart3
19 - VSB
20 - VBAT
21 - fan4
22 - fan5
23 - reserved
The bit ordering for the alarm "realtime status register" and the
"beep enable registers" are different.
in0 (VCORE) : alarms: 0x000001 beep_enable: 0x000001
in1 (VINR0) : alarms: 0x000002 beep_enable: 0x002000 <== mismatch
in2 (+3.3VIN): alarms: 0x000004 beep_enable: 0x000004
in3 (5VDD) : alarms: 0x000008 beep_enable: 0x000008
in4 (+12VIN) : alarms: 0x000100 beep_enable: 0x000100
in5 (-12VIN) : alarms: 0x000200 beep_enable: 0x000200
in6 (-5VIN) : alarms: 0x000400 beep_enable: 0x000400
in7 (VSB) : alarms: 0x080000 beep_enable: 0x010000 <== mismatch
in8 (VBAT) : alarms: 0x100000 beep_enable: 0x020000 <== mismatch
in9 (VINR1) : alarms: 0x004000 beep_enable: 0x004000
temp1 : alarms: 0x000010 beep_enable: 0x000010
temp2 : alarms: 0x000020 beep_enable: 0x000020
temp3 : alarms: 0x002000 beep_enable: 0x000002 <== mismatch
fan1 : alarms: 0x000040 beep_enable: 0x000040
fan2 : alarms: 0x000080 beep_enable: 0x000080
fan3 : alarms: 0x000800 beep_enable: 0x000800
fan4 : alarms: 0x200000 beep_enable: 0x200000
fan5 : alarms: 0x400000 beep_enable: 0x400000
tart1 : alarms: 0x010000 beep_enable: 0x040000 <== mismatch
tart2 : alarms: 0x020000 beep_enable: 0x080000 <== mismatch
tart3 : alarms: 0x040000 beep_enable: 0x100000 <== mismatch
case_open : alarms: 0x001000 beep_enable: 0x001000
user_enable : alarms: -------- beep_enable: 0x800000
*** NOTE: It is the responsibility of user-space code to handle the fact
that the beep enable and alarm bits are in different positions when using that
feature of the chip.
When an alarm goes off, you can be warned by a beeping signal through your
computer speaker. It is possible to enable all beeping globally, or only
......@@ -109,5 +115,6 @@ often will do no harm, but will return 'old' values.
W83791D TODO:
---------------
Provide a patch for per-file alarms as discussed on the mailing list
Provide a patch for per-file alarms and beep enables as defined in the hwmon
documentation (Documentation/hwmon/sysfs-interface)
Provide a patch for smart-fan control (still need appropriate motherboard/fans)
Documentation/i2c/busses/i2c-viapro
浏览文件 @ 8a84fc15
......@@ -7,9 +7,12 @@ Supported adapters:
* VIA Technologies, Inc. VT82C686A/B
Datasheet: Sometimes available at the VIA website
* VIA Technologies, Inc. VT8231, VT8233, VT8233A, VT8235, VT8237R
* VIA Technologies, Inc. VT8231, VT8233, VT8233A
Datasheet: available on request from VIA
* VIA Technologies, Inc. VT8235, VT8237R, VT8237A, VT8251
Datasheet: available on request and under NDA from VIA
Authors:
Kysti Mlkki <kmalkki@cc.hut.fi>,
Mark D. Studebaker <mdsxyz123@yahoo.com>,
......@@ -39,6 +42,8 @@ Your lspci -n listing must show one of these :
device 1106:8235 (VT8231 function 4)
device 1106:3177 (VT8235)
device 1106:3227 (VT8237R)
device 1106:3337 (VT8237A)
device 1106:3287 (VT8251)
If none of these show up, you should look in the BIOS for settings like
enable ACPI / SMBus or even USB.
......
Documentation/i2c/i2c-stub
浏览文件 @ 8a84fc15
......@@ -6,9 +6,12 @@ This module is a very simple fake I2C/SMBus driver. It implements four
types of SMBus commands: write quick, (r/w) byte, (r/w) byte data, and
(r/w) word data.
You need to provide a chip address as a module parameter when loading
this driver, which will then only react to SMBus commands to this address.
No hardware is needed nor associated with this module. It will accept write
quick commands to all addresses; it will respond to the other commands (also
to all addresses) by reading from or writing to an array in memory. It will
quick commands to one address; it will respond to the other commands (also
to one address) by reading from or writing to an array in memory. It will
also spam the kernel logs for every command it handles.
A pointer register with auto-increment is implemented for all byte
......@@ -21,6 +24,11 @@ The typical use-case is like this:
3. load the target sensors chip driver module
4. observe its behavior in the kernel log
PARAMETERS:
int chip_addr:
The SMBus address to emulate a chip at.
CAVEATS:
There are independent arrays for byte/data and word/data commands. Depending
......@@ -33,6 +41,9 @@ If the hardware for your driver has banked registers (e.g. Winbond sensors
chips) this module will not work well - although it could be extended to
support that pretty easily.
Only one chip address is supported - although this module could be
extended to support more.
If you spam it hard enough, printk can be lossy. This module really wants
something like relayfs.
Documentation/kbuild/kconfig-language.txt
浏览文件 @ 8a84fc15
......@@ -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
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/kbuild/modules.txt
浏览文件 @ 8a84fc15
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/kernel-parameters.txt
浏览文件 @ 8a84fc15
......@@ -110,6 +110,13 @@ be entered as an environment variable, whereas its absence indicates that
it will appear as a kernel argument readable via /proc/cmdline by programs
running once the system is up.
The number of kernel parameters is not limited, but the length of the
complete command line (parameters including spaces etc.) is limited to
a fixed number of characters. This limit depends on the architecture
and is between 256 and 4096 characters. It is defined in the file
./include/asm/setup.h as COMMAND_LINE_SIZE.
53c7xx= [HW,SCSI] Amiga SCSI controllers
See header of drivers/scsi/53c7xx.c.
See also Documentation/scsi/ncr53c7xx.txt.
......@@ -573,8 +580,6 @@ running once the system is up.
gscd= [HW,CD]
Format: <io>
gt96100eth= [NET] MIPS GT96100 Advanced Communication Controller
gus= [HW,OSS]
Format: <io>,<irq>,<dma>,<dma16>
......@@ -1240,7 +1245,11 @@ running once the system is up.
bootloader. This is currently used on
IXP2000 systems where the bus has to be
configured a certain way for adjunct CPUs.
noearly [X86] Don't do any early type 1 scanning.
This might help on some broken boards which
machine check when some devices' config space
is read. But various workarounds are disabled
and some IOMMU drivers will not work.
pcmv= [HW,PCMCIA] BadgePAD 4
pd. [PARIDE]
......@@ -1322,7 +1331,7 @@ running once the system is up.
pt. [PARIDE]
See Documentation/paride.txt.
quiet= [KNL] Disable log messages
quiet [KNL] Disable most log messages
r128= [HW,DRM]
......@@ -1363,6 +1372,14 @@ running once the system is up.
reserve= [KNL,BUGS] Force the kernel to ignore some iomem area
reservetop= [IA-32]
Format: nn[KMG]
Reserves a hole at the top of the kernel virtual
address space.
reset_devices [KNL] Force drivers to reset the underlying device
during initialization.
resume= [SWSUSP]
Specify the partition device for software suspend
......
Documentation/lockdep-design.txt
浏览文件 @ 8a84fc15
......@@ -36,6 +36,28 @@ The validator tracks lock-class usage history into 5 separate state bits:
- 'ever used' [ == !unused ]
When locking rules are violated, these 4 state bits are presented in the
locking error messages, inside curlies. A contrived example:
modprobe/2287 is trying to acquire lock:
(&sio_locks[i].lock){--..}, at: [<c02867fd>] mutex_lock+0x21/0x24
but task is already holding lock:
(&sio_locks[i].lock){--..}, at: [<c02867fd>] mutex_lock+0x21/0x24
The bit position indicates hardirq, softirq, hardirq-read,
softirq-read respectively, and the character displayed in each
indicates:
'.' acquired while irqs enabled
'+' acquired in irq context
'-' acquired in process context with irqs disabled
'?' read-acquired both with irqs enabled and in irq context
Unused mutexes cannot be part of the cause of an error.
Single-lock state rules:
------------------------
......
Documentation/netlabel/00-INDEX 0 → 100644
浏览文件 @ 8a84fc15
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
浏览文件 @ 8a84fc15
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
浏览文件 @ 8a84fc15
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
浏览文件 @ 8a84fc15
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
浏览文件 @ 8a84fc15
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/bonding.txt
浏览文件 @ 8a84fc15
......@@ -192,6 +192,17 @@ or, for backwards compatibility, the option value. E.g.,
arp_interval
Specifies the ARP link monitoring frequency in milliseconds.
The ARP monitor works by periodically checking the slave
devices to determine whether they have sent or received
traffic recently (the precise criteria depends upon the
bonding mode, and the state of the slave). Regular traffic is
generated via ARP probes issued for the addresses specified by
the arp_ip_target option.
This behavior can be modified by the arp_validate option,
below.
If ARP monitoring is used in an etherchannel compatible mode
(modes 0 and 2), the switch should be configured in a mode
that evenly distributes packets across all links. If the
......@@ -213,6 +224,54 @@ arp_ip_target
maximum number of targets that can be specified is 16. The
default value is no IP addresses.
arp_validate
Specifies whether or not ARP probes and replies should be
validated in the active-backup mode. This causes the ARP
monitor to examine the incoming ARP requests and replies, and
only consider a slave to be up if it is receiving the
appropriate ARP traffic.
Possible values are:
none or 0
No validation is performed. This is the default.
active or 1
Validation is performed only for the active slave.
backup or 2
Validation is performed only for backup slaves.
all or 3
Validation is performed for all slaves.
For the active slave, the validation checks ARP replies to
confirm that they were generated by an arp_ip_target. Since
backup slaves do not typically receive these replies, the
validation performed for backup slaves is on the ARP request
sent out via the active slave. It is possible that some
switch or network configurations may result in situations
wherein the backup slaves do not receive the ARP requests; in
such a situation, validation of backup slaves must be
disabled.
This option is useful in network configurations in which
multiple bonding hosts are concurrently issuing ARPs to one or
more targets beyond a common switch. Should the link between
the switch and target fail (but not the switch itself), the
probe traffic generated by the multiple bonding instances will
fool the standard ARP monitor into considering the links as
still up. Use of the arp_validate option can resolve this, as
the ARP monitor will only consider ARP requests and replies
associated with its own instance of bonding.
This option was added in bonding version 3.1.0.
downdelay
Specifies the time, in milliseconds, to wait before disabling
......
Documentation/networking/dccp.txt
浏览文件 @ 8a84fc15
DCCP protocol
============
Last updated: 10 November 2005
Contents
========
......@@ -42,8 +41,11 @@ Socket options
DCCP_SOCKOPT_PACKET_SIZE is used for CCID3 to set default packet size for
calculations.
DCCP_SOCKOPT_SERVICE sets the service. This is compulsory as per the
specification. If you don't set it you will get EPROTO.
DCCP_SOCKOPT_SERVICE sets the service. The specification mandates use of
service codes (RFC 4340, sec. 8.1.2); if this socket option is not set,
the socket will fall back to 0 (which means that no meaningful service code
is present). Connecting sockets set at most one service option; for
listening sockets, multiple service codes can be specified.
Notes
=====
......
Documentation/networking/ip-sysctl.txt
浏览文件 @ 8a84fc15
......@@ -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/pktgen.txt
浏览文件 @ 8a84fc15
......@@ -100,6 +100,7 @@ Examples:
are: IPSRC_RND #IP Source is random (between min/max),
IPDST_RND, UDPSRC_RND,
UDPDST_RND, MACSRC_RND, MACDST_RND
MPLS_RND, VID_RND, SVID_RND
pgset "udp_src_min 9" set UDP source port min, If < udp_src_max, then
cycle through the port range.
......@@ -125,6 +126,21 @@ Examples:
pgset "mpls 0" turn off mpls (or any invalid argument works too!)
pgset "vlan_id 77" set VLAN ID 0-4095
pgset "vlan_p 3" set priority bit 0-7 (default 0)
pgset "vlan_cfi 0" set canonical format identifier 0-1 (default 0)
pgset "svlan_id 22" set SVLAN ID 0-4095
pgset "svlan_p 3" set priority bit 0-7 (default 0)
pgset "svlan_cfi 0" set canonical format identifier 0-1 (default 0)
pgset "vlan_id 9999" > 4095 remove vlan and svlan tags
pgset "svlan 9999" > 4095 remove svlan tag
pgset "tos XX" set former IPv4 TOS field (e.g. "tos 28" for AF11 no ECN, default 00)
pgset "traffic_class XX" set former IPv6 TRAFFIC CLASS (e.g. "traffic_class B8" for EF no ECN, default 00)
pgset stop aborts injection. Also, ^C aborts generator.
......
Documentation/networking/secid.txt 0 → 100644
浏览文件 @ 8a84fc15
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/nommu-mmap.txt
浏览文件 @ 8a84fc15
......@@ -116,6 +116,9 @@ FURTHER NOTES ON NO-MMU MMAP
(*) A list of all the mappings on the system is visible through /proc/maps in
no-MMU mode.
(*) A list of all the mappings in use by a process is visible through
/proc/<pid>/maps in no-MMU mode.
(*) Supplying MAP_FIXED or a requesting a particular mapping address will
result in an error.
......@@ -125,6 +128,49 @@ FURTHER NOTES ON NO-MMU MMAP
error will result if they don't. This is most likely to be encountered
with character device files, pipes, fifos and sockets.
==========================
INTERPROCESS SHARED MEMORY
==========================
Both SYSV IPC SHM shared memory and POSIX shared memory is supported in NOMMU
mode. The former through the usual mechanism, the latter through files created
on ramfs or tmpfs mounts.
=======
FUTEXES
=======
Futexes are supported in NOMMU mode if the arch supports them. An error will
be given if an address passed to the futex system call lies outside the
mappings made by a process or if the mapping in which the address lies does not
support futexes (such as an I/O chardev mapping).
=============
NO-MMU MREMAP
=============
The mremap() function is partially supported. It may change the size of a
mapping, and may move it[*] if MREMAP_MAYMOVE is specified and if the new size
of the mapping exceeds the size of the slab object currently occupied by the
memory to which the mapping refers, or if a smaller slab object could be used.
MREMAP_FIXED is not supported, though it is ignored if there's no change of
address and the object does not need to be moved.
Shared mappings may not be moved. Shareable mappings may not be moved either,
even if they are not currently shared.
The mremap() function must be given an exact match for base address and size of
a previously mapped object. It may not be used to create holes in existing
mappings, move parts of existing mappings or resize parts of mappings. It must
act on a complete mapping.
[*] Not currently supported.
============================================
PROVIDING SHAREABLE CHARACTER DEVICE SUPPORT
============================================
......
Documentation/pcieaer-howto.txt 0 → 100644
浏览文件 @ 8a84fc15
The PCI Express Advanced Error Reporting Driver Guide HOWTO
T. Long Nguyen <tom.l.nguyen@intel.com>
Yanmin Zhang <yanmin.zhang@intel.com>
07/29/2006
1. Overview
1.1 About this guide
This guide describes the basics of the PCI Express Advanced Error
Reporting (AER) driver and provides information on how to use it, as
well as how to enable the drivers of endpoint devices to conform with
PCI Express AER driver.
1.2 Copyright © Intel Corporation 2006.
1.3 What is the PCI Express AER Driver?
PCI Express error signaling can occur on the PCI Express link itself
or on behalf of transactions initiated on the link. PCI Express
defines two error reporting paradigms: the baseline capability and
the Advanced Error Reporting capability. The baseline capability is
required of all PCI Express components providing a minimum defined
set of error reporting requirements. Advanced Error Reporting
capability is implemented with a PCI Express advanced error reporting
extended capability structure providing more robust error reporting.
The PCI Express AER driver provides the infrastructure to support PCI
Express Advanced Error Reporting capability. The PCI Express AER
driver provides three basic functions:
- Gathers the comprehensive error information if errors occurred.
- Reports error to the users.
- Performs error recovery actions.
AER driver only attaches root ports which support PCI-Express AER
capability.
2. User Guide
2.1 Include the PCI Express AER Root Driver into the Linux Kernel
The PCI Express AER Root driver is a Root Port service driver attached
to the PCI Express Port Bus driver. If a user wants to use it, the driver
has to be compiled. Option CONFIG_PCIEAER supports this capability. It
depends on CONFIG_PCIEPORTBUS, so pls. set CONFIG_PCIEPORTBUS=y and
CONFIG_PCIEAER = y.
2.2 Load PCI Express AER Root Driver
There is a case where a system has AER support in BIOS. Enabling the AER
Root driver and having AER support in BIOS may result unpredictable
behavior. To avoid this conflict, a successful load of the AER Root driver
requires ACPI _OSC support in the BIOS to allow the AER Root driver to
request for native control of AER. See the PCI FW 3.0 Specification for
details regarding OSC usage. Currently, lots of firmwares don't provide
_OSC support while they use PCI Express. To support such firmwares,
forceload, a parameter of type bool, could enable AER to continue to
be initiated although firmwares have no _OSC support. To enable the
walkaround, pls. add aerdriver.forceload=y to kernel boot parameter line
when booting kernel. Note that forceload=n by default.
2.3 AER error output
When a PCI-E AER error is captured, an error message will be outputed to
console. If it's a correctable error, it is outputed as a warning.
Otherwise, it is printed as an error. So users could choose different
log level to filter out correctable error messages.
Below shows an example.
+------ PCI-Express Device Error -----+
Error Severity : Uncorrected (Fatal)
PCIE Bus Error type : Transaction Layer
Unsupported Request : First
Requester ID : 0500
VendorID=8086h, DeviceID=0329h, Bus=05h, Device=00h, Function=00h
TLB Header:
04000001 00200a03 05010000 00050100
In the example, 'Requester ID' means the ID of the device who sends
the error message to root port. Pls. refer to pci express specs for
other fields.
3. Developer Guide
To enable AER aware support requires a software driver to configure
the AER capability structure within its device and to provide callbacks.
To support AER better, developers need understand how AER does work
firstly.
PCI Express errors are classified into two types: correctable errors
and uncorrectable errors. This classification is based on the impacts
of those errors, which may result in degraded performance or function
failure.
Correctable errors pose no impacts on the functionality of the
interface. The PCI Express protocol can recover without any software
intervention or any loss of data. These errors are detected and
corrected by hardware. Unlike correctable errors, uncorrectable
errors impact functionality of the interface. Uncorrectable errors
can cause a particular transaction or a particular PCI Express link
to be unreliable. Depending on those error conditions, uncorrectable
errors are further classified into non-fatal errors and fatal errors.
Non-fatal errors cause the particular transaction to be unreliable,
but the PCI Express link itself is fully functional. Fatal errors, on
the other hand, cause the link to be unreliable.
When AER is enabled, a PCI Express device will automatically send an
error message to the PCIE root port above it when the device captures
an error. The Root Port, upon receiving an error reporting message,
internally processes and logs the error message in its PCI Express
capability structure. Error information being logged includes storing
the error reporting agent's requestor ID into the Error Source
Identification Registers and setting the error bits of the Root Error
Status Register accordingly. If AER error reporting is enabled in Root
Error Command Register, the Root Port generates an interrupt if an
error is detected.
Note that the errors as described above are related to the PCI Express
hierarchy and links. These errors do not include any device specific
errors because device specific errors will still get sent directly to
the device driver.
3.1 Configure the AER capability structure
AER aware drivers of PCI Express component need change the device
control registers to enable AER. They also could change AER registers,
including mask and severity registers. Helper function
pci_enable_pcie_error_reporting could be used to enable AER. See
section 3.3.
3.2. Provide callbacks
3.2.1 callback reset_link to reset pci express link
This callback is used to reset the pci express physical link when a
fatal error happens. The root port aer service driver provides a
default reset_link function, but different upstream ports might
have different specifications to reset pci express link, so all
upstream ports should provide their own reset_link functions.
In struct pcie_port_service_driver, a new pointer, reset_link, is
added.
pci_ers_result_t (*reset_link) (struct pci_dev *dev);
Section 3.2.2.2 provides more detailed info on when to call
reset_link.
3.2.2 PCI error-recovery callbacks
The PCI Express AER Root driver uses error callbacks to coordinate
with downstream device drivers associated with a hierarchy in question
when performing error recovery actions.
Data struct pci_driver has a pointer, err_handler, to point to
pci_error_handlers who consists of a couple of callback function
pointers. AER driver follows the rules defined in
pci-error-recovery.txt except pci express specific parts (e.g.
reset_link). Pls. refer to pci-error-recovery.txt for detailed
definitions of the callbacks.
Below sections specify when to call the error callback functions.
3.2.2.1 Correctable errors
Correctable errors pose no impacts on the functionality of
the interface. The PCI Express protocol can recover without any
software intervention or any loss of data. These errors do not
require any recovery actions. The AER driver clears the device's
correctable error status register accordingly and logs these errors.
3.2.2.2 Non-correctable (non-fatal and fatal) errors
If an error message indicates a non-fatal error, performing link reset
at upstream is not required. The AER driver calls error_detected(dev,
pci_channel_io_normal) to all drivers associated within a hierarchy in
question. for example,
EndPoint<==>DownstreamPort B<==>UpstreamPort A<==>RootPort.
If Upstream port A captures an AER error, the hierarchy consists of
Downstream port B and EndPoint.
A driver may return PCI_ERS_RESULT_CAN_RECOVER,
PCI_ERS_RESULT_DISCONNECT, or PCI_ERS_RESULT_NEED_RESET, depending on
whether it can recover or the AER driver calls mmio_enabled as next.
If an error message indicates a fatal error, kernel will broadcast
error_detected(dev, pci_channel_io_frozen) to all drivers within
a hierarchy in question. Then, performing link reset at upstream is
necessary. As different kinds of devices might use different approaches
to reset link, AER port service driver is required to provide the
function to reset link. Firstly, kernel looks for if the upstream
component has an aer driver. If it has, kernel uses the reset_link
callback of the aer driver. If the upstream component has no aer driver
and the port is downstream port, we will use the aer driver of the
root port who reports the AER error. As for upstream ports,
they should provide their own aer service drivers with reset_link
function. If error_detected returns PCI_ERS_RESULT_CAN_RECOVER and
reset_link returns PCI_ERS_RESULT_RECOVERED, the error handling goes
to mmio_enabled.
3.3 helper functions
3.3.1 int pci_find_aer_capability(struct pci_dev *dev);
pci_find_aer_capability locates the PCI Express AER capability
in the device configuration space. If the device doesn't support
PCI-Express AER, the function returns 0.
3.3.2 int pci_enable_pcie_error_reporting(struct pci_dev *dev);
pci_enable_pcie_error_reporting enables the device to send error
messages to root port when an error is detected. Note that devices
don't enable the error reporting by default, so device drivers need
call this function to enable it.
3.3.3 int pci_disable_pcie_error_reporting(struct pci_dev *dev);
pci_disable_pcie_error_reporting disables the device to send error
messages to root port when an error is detected.
3.3.4 int pci_cleanup_aer_uncorrect_error_status(struct pci_dev *dev);
pci_cleanup_aer_uncorrect_error_status cleanups the uncorrectable
error status register.
3.4 Frequent Asked Questions
Q: What happens if a PCI Express device driver does not provide an
error recovery handler (pci_driver->err_handler is equal to NULL)?
A: The devices attached with the driver won't be recovered. If the
error is fatal, kernel will print out warning messages. Please refer
to section 3 for more information.
Q: What happens if an upstream port service driver does not provide
callback reset_link?
A: Fatal error recovery will fail if the errors are reported by the
upstream ports who are attached by the service driver.
Q: How does this infrastructure deal with driver that is not PCI
Express aware?
A: This infrastructure calls the error callback functions of the
driver when an error happens. But if the driver is not aware of
PCI Express, the device might not report its own errors to root
port.
Q: What modifications will that driver need to make it compatible
with the PCI Express AER Root driver?
A: It could call the helper functions to enable AER in devices and
cleanup uncorrectable status register. Pls. refer to section 3.3.
Documentation/power/devices.txt
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/power/interface.txt
浏览文件 @ 8a84fc15
......@@ -52,3 +52,18 @@ suspend image will be as small as possible.
Reading from this file will display the current image size limit, which
is set to 500 MB by default.
/sys/power/pm_trace controls the code which saves the last PM event point in
the RTC across reboots, so that you can debug a machine that just hangs
during suspend (or more commonly, during resume). Namely, the RTC is only
used to save the last PM event point if this file contains '1'. Initially it
contains '0' which may be changed to '1' by writing a string representing a
nonzero integer into it.
To use this debugging feature you should attempt to suspend the machine, then
reboot it and run
dmesg -s 1000000 | grep 'hash matches'
CAUTION: Using it will cause your machine's real-time (CMOS) clock to be
set to a random invalid time after a resume.
Documentation/rt-mutex-design.txt
浏览文件 @ 8a84fc15
......@@ -333,11 +333,11 @@ cmpxchg is basically the following function performed atomically:
unsigned long _cmpxchg(unsigned long *A, unsigned long *B, unsigned long *C)
{
unsigned long T = *A;
if (*A == *B) {
*A = *C;
}
return T;
unsigned long T = *A;
if (*A == *B) {
*A = *C;
}
return T;
}
#define cmpxchg(a,b,c) _cmpxchg(&a,&b,&c)
......@@ -582,7 +582,7 @@ contention).
try_to_take_rt_mutex is used every time the task tries to grab a mutex in the
slow path. The first thing that is done here is an atomic setting of
the "Has Waiters" flag of the mutex's owner field. Yes, this could really
be false, because if the the mutex has no owner, there are no waiters and
be false, because if the mutex has no owner, there are no waiters and
the current task also won't have any waiters. But we don't have the lock
yet, so we assume we are going to be a waiter. The reason for this is to
play nice for those architectures that do have CMPXCHG. By setting this flag
......@@ -735,7 +735,7 @@ do have CMPXCHG, that check is done in the fast path, but it is still needed
in the slow path too. If a waiter of a mutex woke up because of a signal
or timeout between the time the owner failed the fast path CMPXCHG check and
the grabbing of the wait_lock, the mutex may not have any waiters, thus the
owner still needs to make this check. If there are no waiters than the mutex
owner still needs to make this check. If there are no waiters then the mutex
owner field is set to NULL, the wait_lock is released and nothing more is
needed.
......
Documentation/scsi/ChangeLog.arcmsr 0 → 100644
浏览文件 @ 8a84fc15
**************************************************************************
** 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
浏览文件 @ 8a84fc15
......@@ -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
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/scsi/libsas.txt 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/seclvl.txt 已删除 100644 → 0
浏览文件 @ 28b79ff9
BSD Secure Levels Linux Security Module
Michael A. Halcrow <mike@halcrow.us>
Introduction
Under the BSD Secure Levels security model, sets of policies are
associated with levels. Levels range from -1 to 2, with -1 being the
weakest and 2 being the strongest. These security policies are
enforced at the kernel level, so not even the superuser is able to
disable or circumvent them. This hardens the machine against attackers
who gain root access to the system.
Levels and Policies
Level -1 (Permanently Insecure):
- Cannot increase the secure level
Level 0 (Insecure):
- Cannot ptrace the init process
Level 1 (Default):
- /dev/mem and /dev/kmem are read-only
- IMMUTABLE and APPEND extended attributes, if set, may not be unset
- Cannot load or unload kernel modules
- Cannot write directly to a mounted block device
- Cannot perform raw I/O operations
- Cannot perform network administrative tasks
- Cannot setuid any file
Level 2 (Secure):
- Cannot decrement the system time
- Cannot write to any block device, whether mounted or not
- Cannot unmount any mounted filesystems
Compilation
To compile the BSD Secure Levels LSM, seclvl.ko, enable the
SECURITY_SECLVL configuration option. This is found under Security
options -> BSD Secure Levels in the kernel configuration menu.
Basic Usage
Once the machine is in a running state, with all the necessary modules
loaded and all the filesystems mounted, you can load the seclvl.ko
module:
# insmod seclvl.ko
The module defaults to secure level 1, except when compiled directly
into the kernel, in which case it defaults to secure level 0. To raise
the secure level to 2, the administrator writes ``2'' to the
seclvl/seclvl file under the sysfs mount point (assumed to be /sys in
these examples):
# echo -n "2" > /sys/seclvl/seclvl
Alternatively, you can initialize the module at secure level 2 with
the initlvl module parameter:
# insmod seclvl.ko initlvl=2
At this point, it is impossible to remove the module or reduce the
secure level. If the administrator wishes to have the option of doing
so, he must provide a module parameter, sha1_passwd, that specifies
the SHA1 hash of the password that can be used to reduce the secure
level to 0.
To generate this SHA1 hash, the administrator can use OpenSSL:
# echo -n "boogabooga" | openssl sha1
abeda4e0f33defa51741217592bf595efb8d289c
In order to use password-instigated secure level reduction, the SHA1
crypto module must be loaded or compiled into the kernel:
# insmod sha1.ko
The administrator can then insmod the seclvl module, including the
SHA1 hash of the password:
# insmod seclvl.ko
sha1_passwd=abeda4e0f33defa51741217592bf595efb8d289c
To reduce the secure level, write the password to seclvl/passwd under
your sysfs mount point:
# echo -n "boogabooga" > /sys/seclvl/passwd
The September 2004 edition of Sys Admin Magazine has an article about
the BSD Secure Levels LSM. I encourage you to refer to that article
for a more in-depth treatment of this security module:
http://www.samag.com/documents/s=9304/sam0409a/0409a.htm
Documentation/sh/new-machine.txt
浏览文件 @ 8a84fc15
......@@ -41,11 +41,6 @@ Board-specific code:
|
.. more boards here ...
It should also be noted that each board is required to have some certain
headers. At the time of this writing, io.h is the only thing that needs
to be provided for each board, and can generally just reference generic
functions (with the exception of isa_port2addr).
Next, for companion chips:
.
`-- arch
......@@ -104,12 +99,13 @@ and then populate that with sub-directories for each member of the family.
Both the Solution Engine and the hp6xx boards are an example of this.
After you have setup your new arch/sh/boards/ directory, remember that you
also must add a directory in include/asm-sh for headers localized to this
board. In order to interoperate seamlessly with the build system, it's best
to have this directory the same as the arch/sh/boards/ directory name,
though if your board is again part of a family, the build system has ways
of dealing with this, and you can feel free to name the directory after
the family member itself.
should also add a directory in include/asm-sh for headers localized to this
board (if there are going to be more than one). In order to interoperate
seamlessly with the build system, it's best to have this directory the same
as the arch/sh/boards/ directory name, though if your board is again part of
a family, the build system has ways of dealing with this (via incdir-y
overloading), and you can feel free to name the directory after the family
member itself.
There are a few things that each board is required to have, both in the
arch/sh/boards and the include/asm-sh/ heirarchy. In order to better
......@@ -122,6 +118,7 @@ might look something like:
* arch/sh/boards/vapor/setup.c - Setup code for imaginary board
*/
#include <linux/init.h>
#include <asm/rtc.h> /* for board_time_init() */
const char *get_system_type(void)
{
......@@ -152,79 +149,57 @@ int __init platform_setup(void)
}
Our new imaginary board will also have to tie into the machvec in order for it
to be of any use. Currently the machvec is slowly on its way out, but is still
required for the time being. As such, let us take a look at what needs to be
done for the machvec assignment.
to be of any use.
machvec functions fall into a number of categories:
- I/O functions to IO memory (inb etc) and PCI/main memory (readb etc).
- I/O remapping functions (ioremap etc)
- some initialisation functions
- a 'heartbeat' function
- some miscellaneous flags
The tree can be built in two ways:
- as a fully generic build. All drivers are linked in, and all functions
go through the machvec
- as a machine specific build. In this case only the required drivers
will be linked in, and some macros may be redefined to not go through
the machvec where performance is important (in particular IO functions).
There are three ways in which IO can be performed:
- none at all. This is really only useful for the 'unknown' machine type,
which us designed to run on a machine about which we know nothing, and
so all all IO instructions do nothing.
- fully custom. In this case all IO functions go to a machine specific
set of functions which can do what they like
- a generic set of functions. These will cope with most situations,
and rely on a single function, mv_port2addr, which is called through the
machine vector, and converts an IO address into a memory address, which
can be read from/written to directly.
Thus adding a new machine involves the following steps (I will assume I am
adding a machine called vapor):
- add a new file include/asm-sh/vapor/io.h which contains prototypes for
- I/O mapping functions (ioport_map, ioport_unmap, etc).
- a 'heartbeat' function.
- PCI and IRQ initialization routines.
- Consistent allocators (for boards that need special allocators,
particularly for allocating out of some board-specific SRAM for DMA
handles).
There are machvec functions added and removed over time, so always be sure to
consult include/asm-sh/machvec.h for the current state of the machvec.
The kernel will automatically wrap in generic routines for undefined function
pointers in the machvec at boot time, as machvec functions are referenced
unconditionally throughout most of the tree. Some boards have incredibly
sparse machvecs (such as the dreamcast and sh03), whereas others must define
virtually everything (rts7751r2d).
Adding a new machine is relatively trivial (using vapor as an example):
If the board-specific definitions are quite minimalistic, as is the case for
the vast majority of boards, simply having a single board-specific header is
sufficient.
- add a new file include/asm-sh/vapor.h which contains prototypes for
any machine specific IO functions prefixed with the machine name, for
example vapor_inb. These will be needed when filling out the machine
vector.
This is the minimum that is required, however there are ample
opportunities to optimise this. In particular, by making the prototypes
inline function definitions, it is possible to inline the function when
building machine specific versions. Note that the machine vector
functions will still be needed, so that a module built for a generic
setup can be loaded.
- add a new file arch/sh/boards/vapor/mach.c. This contains the definition
of the machine vector. When building the machine specific version, this
will be the real machine vector (via an alias), while in the generic
version is used to initialise the machine vector, and then freed, by
making it initdata. This should be defined as:
struct sh_machine_vector mv_vapor __initmv = {
.mv_name = "vapor",
}
ALIAS_MV(vapor)
- finally add a file arch/sh/boards/vapor/io.c, which contains
definitions of the machine specific io functions.
A note about initialisation functions. Three initialisation functions are
provided in the machine vector:
- mv_arch_init - called very early on from setup_arch
- mv_init_irq - called from init_IRQ, after the generic SH interrupt
initialisation
- mv_init_pci - currently not used
Any other remaining functions which need to be called at start up can be
added to the list using the __initcalls macro (or module_init if the code
can be built as a module). Many generic drivers probe to see if the device
they are targeting is present, however this may not always be appropriate,
so a flag can be added to the machine vector which will be set on those
machines which have the hardware in question, reducing the probe to a
single conditional.
Note that these prototypes are generated automatically by setting
__IO_PREFIX to something sensible. A typical example would be:
#define __IO_PREFIX vapor
#include <asm/io_generic.h>
somewhere in the board-specific header. Any boards being ported that still
have a legacy io.h should remove it entirely and switch to the new model.
- Add machine vector definitions to the board's setup.c. At a bare minimum,
this must be defined as something like:
struct sh_machine_vector mv_vapor __initmv = {
.mv_name = "vapor",
};
ALIAS_MV(vapor)
- finally add a file arch/sh/boards/vapor/io.c, which contains definitions of
the machine specific io functions (if there are enough to warrant it).
3. Hooking into the Build System
================================
......@@ -303,4 +278,3 @@ which will in turn copy the defconfig for this board, run it through
oldconfig (prompting you for any new options since the time of creation),
and start you on your way to having a functional kernel for your new
board.
Documentation/sh/register-banks.txt 0 → 100644
浏览文件 @ 8a84fc15
Notes on register bank usage in the kernel
==========================================
Introduction
------------
The SH-3 and SH-4 CPU families traditionally include a single partial register
bank (selected by SR.RB, only r0 ... r7 are banked), whereas other families
may have more full-featured banking or simply no such capabilities at all.
SR.RB banking
-------------
In the case of this type of banking, banked registers are mapped directly to
r0 ... r7 if SR.RB is set to the bank we are interested in, otherwise ldc/stc
can still be used to reference the banked registers (as r0_bank ... r7_bank)
when in the context of another bank. The developer must keep the SR.RB value
in mind when writing code that utilizes these banked registers, for obvious
reasons. Userspace is also not able to poke at the bank1 values, so these can
be used rather effectively as scratch registers by the kernel.
Presently the kernel uses several of these registers.
- r0_bank, r1_bank (referenced as k0 and k1, used for scratch
registers when doing exception handling).
- r2_bank (used to track the EXPEVT/INTEVT code)
- Used by do_IRQ() and friends for doing irq mapping based off
of the interrupt exception vector jump table offset
- r6_bank (global interrupt mask)
- The SR.IMASK interrupt handler makes use of this to set the
interrupt priority level (used by local_irq_enable())
- r7_bank (current)
Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl
浏览文件 @ 8a84fc15
......@@ -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
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/usb/error-codes.txt
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/usb/usb-serial.txt
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/video4linux/cx2341x/README.hm12 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/video4linux/cx2341x/README.vbi 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
Documentation/x86_64/kernel-stacks 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
Kbuild
浏览文件 @ 8a84fc15
此差异已折叠。
MAINTAINERS
浏览文件 @ 8a84fc15
此差异已折叠。
Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/alpha/kernel/proto.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/alpha/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/alpha/mm/Makefile
浏览文件 @ 8a84fc15
......@@ -4,6 +4,6 @@
EXTRA_CFLAGS := -Werror
obj-y := init.o fault.o extable.o remap.o
obj-y := init.o fault.o extable.o
obj-$(CONFIG_DISCONTIGMEM) += numa.o
arch/alpha/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/alpha/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/alpha/mm/remap.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/Kconfig-nommu
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/boot/compressed/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/boot/compressed/head.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/boot/compressed/misc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/common/icst307.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/common/icst525.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/common/locomo.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/common/sharpsl_pm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/configs/ep93xx_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/configs/s3c2410_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/apm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/debug.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/ecard.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/head-nommu.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/module.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/board-dk.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/board-ek.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/clock.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/clock.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/devices.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/generic.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/gpio.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-at91rm9200/pm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-ep93xx/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-ep93xx/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-ep93xx/edb9312.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-footbridge/dc21285.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop32x/Kconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop32x/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop32x/glantank.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop32x/iq31244.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop32x/iq80321.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop32x/n2100.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/Kconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/Makefile.boot 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/iq80331.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/iq80332.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/irq.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop33x/uart.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-iop3xx/Kconfig 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/common.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iop321-setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iop321-time.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iop331-irq.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iop331-pci.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iop331-setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iop331-time.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq31244-mm.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq31244-pci.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq80321-mm.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq80321-pci.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq80331-mm.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq80331-pci.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq80332-mm.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-iop3xx/iq80332-pci.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/board-fsample.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/board-h2.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/clock.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/clock.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap1/mux.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/board-h4.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/clock.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/bast-irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/cpu.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/devs.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/dma.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/dma.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/gpio.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/mach-amlm5900.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/mach-anubis.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/mach-vstms.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/pm-simtec.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/pm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/pm.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410-dma.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410-irq.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410-pm.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410-sleep.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412-dma.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412-irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412-pm.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2440-dma.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2440-dsc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c2440-irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/s3c244x-irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/sleep.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-s3c2410/usb-simtec.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-sa1100/collie.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mach-versatile/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/abort-lv4t.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/abort-nommu.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/alignment.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/cache-v4.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/context.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/copypage-v4mc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/copypage-v6.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/copypage-xscale.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/fault.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/flush.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/ioremap.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/mm-armv.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/mm/mm.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/mmap.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/nommu.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/pgd.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/proc-arm740.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/proc-arm7tdmi.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/proc-arm940.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/proc-arm946.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/proc-arm9tdmi.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/mm/proc-xscale.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/oprofile/op_model_xscale.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-iop/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-iop/gpio.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-iop/i2c.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-iop/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-iop/time.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/clock.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/devices.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/dmtimer.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/mcbsp.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/pm.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/timer32k.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/plat-omap/usb.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/vfp/vfp.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/vfp/vfpdouble.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/vfp/vfpinstr.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/vfp/vfpmodule.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm/vfp/vfpsingle.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm26/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/arm26/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/Kconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/Kconfig.debug 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boards/atstk1000/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boards/atstk1000/atstk1002.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boards/atstk1000/flash.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boards/atstk1000/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boards/atstk1000/spi.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boot/images/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boot/u-boot/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boot/u-boot/empty.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/boot/u-boot/head.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/asm-offsets.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/avr32_ksyms.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/cpu.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/entry-avr32b.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/head.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/init_task.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/irq.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/kprobes.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/module.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/process.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/ptrace.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/semaphore.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/signal.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/switch_to.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/sys_avr32.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/syscall-stubs.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/syscall_table.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/time.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/traps.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/kernel/vmlinux.lds.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/__avr32_asr64.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/__avr32_lsl64.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/__avr32_lsr64.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/clear_user.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/copy_user.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/csum_partial.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/csum_partial_copy_generic.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/delay.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/findbit.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/io-readsl.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/io-readsw.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/io-writesl.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/io-writesw.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/libgcc.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/longlong.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/memcpy.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/memset.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/strncpy_from_user.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/lib/strnlen_user.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/at32ap.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/at32ap7000.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/clock.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/clock.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/extint.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/hsmc.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/hsmc.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/intc.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/intc.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/pio.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/pio.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/sm.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mach-at32ap/sm.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/cache.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/clear_page.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/copy_page.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/dma-coherent.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/fault.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/init.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/ioremap.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/avr32/mm/tlb.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/cris/arch-v10/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/cris/arch-v32/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/cris/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/cris/mm/ioremap.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/boot/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/irq-mb93091.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/irq-mb93093.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/irq-mb93493.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/irq-routing.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/frv/kernel/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/mb93090-mb00/pci-irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/frv/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/h8300/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/h8300/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/boot/edd.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/boot/setup.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/boot/video.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/crypto/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/crypto/aes.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/crypto/twofish-i586-asm.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/crypto/twofish.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/acpi/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/acpi/boot.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/acpi/earlyquirk.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/apic.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/apm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/amd.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/centaur.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/common.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/cpu.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/cyrix.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/intel.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/mcheck/p4.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/mcheck/therm_throt.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/mtrr/generic.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/nexgen.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/proc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/rise.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/transmeta.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/cpu/umc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/crash.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/efi.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/efi_stub.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/entry.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/head.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/i8237.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/i8259.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/io_apic.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/machine_kexec.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/mca.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/microcode.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/mpparse.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/nmi.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/process.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/ptrace.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/reboot.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/relocate_kernel.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/semaphore.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/i386/kernel/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/smp.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/smpboot.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/srat.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/stacktrace.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/i386/kernel/syscall_table.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/time_hpet.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/topology.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/traps.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/tsc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/kernel/vmlinux.lds.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/lib/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/lib/delay.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/lib/semaphore.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/lib/usercopy.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mach-generic/bigsmp.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mach-generic/es7000.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mach-generic/probe.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mach-generic/summit.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/boot_ioremap.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/discontig.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/extable.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/highmem.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/ioremap.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/mm/pgtable.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/oprofile/nmi_int.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/oprofile/nmi_timer_int.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/oprofile/op_model_p4.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/oprofile/op_model_ppro.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/oprofile/op_x86_model.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/common.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/direct.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/early.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/mmconfig.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/pci/pci.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/i386/power/swsusp.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/hp/sim/simeth.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/esi.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/esi_stub.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/ia64_ksyms.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/kprobes.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/mca.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/mca_asm.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/mca_drv.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/mca_drv.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/numa.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/salinfo.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/smpboot.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/topology.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/uncached.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/kernel/vmlinux.lds.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/mm/contig.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/mm/discontig.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/mm/numa.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/sn/kernel/bte.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/sn/kernel/sn2/sn_hwperf.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/sn/pci/pcibr/pcibr_ate.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ia64/sn/pci/pcibr/pcibr_dma.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m32r/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m32r/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m32r/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m32r/mm/ioremap.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m68k/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m68k/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m68k/sun3/sun3ints.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m68knommu/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/m68knommu/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/au1000/common/dbdma.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/au1000/common/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/au1000/db1x00/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/au1000/db1x00/mirage_ts.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/configs/atlas_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/bigsur_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/cobalt_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/db1000_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/db1100_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/db1200_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/db1500_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/db1550_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ddb5477_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/e55_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/emma2rh_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ev64120_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/excite_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ip22_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ip27_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ip32_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/it8172_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ivr_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/jmr3927_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/malta_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/mipssim_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/mpc30x_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/ocelot_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/pb1100_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/pb1500_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/pb1550_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/qemu_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/rm200_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/sead_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/tb0226_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/tb0229_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/tb0287_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/workpad_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/configs/wrppmc_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/galileo-boards/ev96100/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/galileo-boards/ev96100/init.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/galileo-boards/ev96100/puts.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/galileo-boards/ev96100/reset.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/galileo-boards/ev96100/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/galileo-boards/ev96100/time.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/gt64120/common/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/cpu-probe.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/irixsig.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/process.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/scall32-o32.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/scall64-64.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/scall64-n32.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/scall64-o32.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/signal.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/signal32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/signal_n32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/smp-mt.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/smtc-asm.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/syscall.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/traps.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/kernel/vpe.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/c-r3k.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/c-r4k.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/c-sb1.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/c-tx39.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/cache.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/mm/tlb-r4k.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/pci/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/pci/fixup-atlas.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/pci/fixup-ev96100.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/pci/ops-au1000.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/pci/ops-gt96100.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/pci/pci-ev96100.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/mips/pci/pci-ip27.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/sgi-ip27/ip27-memory.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/sgi-ip27/ip27-timer.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/sibyte/bcm1480/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/mips/sibyte/sb1250/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/parisc/kernel/firmware.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/parisc/kernel/module.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/parisc/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/parisc/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/flatdevtree.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/main.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/ops.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/prom.h 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/powerpc/boot/stdio.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/stdio.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/boot/types.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/btext.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/crash_dump.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/dma_64.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/ibmebus.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/io.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/legacy_serial.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/misc.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/of_device.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/paca.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/pci_32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/pci_64.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/pci_dn.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/rtas-proc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/rtas_pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/swsusp_32.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/sys_ppc32.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/sysfs.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/lib/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/lib/e2a.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/powerpc/lib/locks.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/mm/slb.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/mm/tlb_64.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/83xx/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/85xx/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/86xx/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/cell/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/cell/smp.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/chrp/nvram.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/chrp/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/chrp/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/iseries/dt.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/maple/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/pasemi/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/pasemi/pasemi.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/pasemi/pci.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/pasemi/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/platforms/pseries/hvCall_inst.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/i8259.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/ipic.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/mmio_nvram.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/mpic.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/sysdev/tsi108_pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/kernel/misc.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/kernel/ppc_ksyms.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/kernel/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/kernel/traps.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/platforms/85xx/sbc8560.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/platforms/85xx/sbc85xx.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/xmon/start.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/ppc/xmon/xmon.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/appldata/appldata.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/appldata/appldata_mem.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/appldata/appldata_os.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/crypto/aes_s390.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/crypto/crypt_s390.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/crypto/des_s390.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/crypto/sha1_s390.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/crypto/sha256_s390.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/hypfs/hypfs.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/hypfs/hypfs_diag.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/hypfs/hypfs_diag.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/hypfs/inode.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/compat_wrapper.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/cpcmd.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/entry.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/entry64.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/head.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/head31.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/head64.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/ipl.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/kprobes.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/process.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/reipl.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/reipl64.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/reipl_diag.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/s390/kernel/relocate_kernel.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/s390_ksyms.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/semaphore.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/signal.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/stacktrace.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/traps.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/kernel/vmlinux.lds.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/lib/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/lib/delay.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/lib/div64.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/lib/spinlock.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/lib/uaccess.S 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/s390/lib/uaccess64.S 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/s390/lib/uaccess_mvcos.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/lib/uaccess_std.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/math-emu/math.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/math-emu/sfp-util.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/mm/cmm.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/mm/extmem.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/mm/fault.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/Kconfig.debug
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/adx/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/adx/irq.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/adx/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/bigsur/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/bigsur/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/cat68701/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/cat68701/irq.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/cat68701/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/cqreek/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/cqreek/irq.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/cqreek/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/dmida/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/dmida/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/dreamcast/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/dreamcast/rtc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/dreamcast/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/ec3104/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/harp/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/harp/irq.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/harp/led.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/harp/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/harp/pcidma.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/harp/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/hp6xx/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/hp6xx/hp6xx_apm.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/hp6xx/pm.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/hp6xx/pm_wakeup.S 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/hp6xx/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/landisk/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/landisk/io.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/landisk/irq.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/landisk/landisk_pwb.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/landisk/rtc.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/landisk/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/mpc1211/rtc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/mpc1211/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/overdrive/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/fpga.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/galileo.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/io.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/irq.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/led.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/pcidma.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/overdrive/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/renesas/hs7751rvoip/Kconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/hs7751rvoip/led.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/renesas/hs7751rvoip/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/renesas/r7780rp/Kconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/r7780rp/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/r7780rp/io.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/r7780rp/irq.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/r7780rp/led.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/r7780rp/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/rts7751r2d/Kconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/rts7751r2d/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/renesas/sh7710voipgw/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/sh7710voipgw/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/renesas/systemh/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/saturn/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7300/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7300/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7300/led.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7300/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/73180/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/73180/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/73180/led.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/73180/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7343/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7343/io.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7343/irq.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7343/led.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7343/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/770x/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/770x/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/770x/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/770x/led.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/770x/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/se/770x/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7751/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7751/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7751/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7751/led.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/se/7751/mach.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/se/7751/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/sh03/rtc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/sh03/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/sh2000/Makefile 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/sh2000/setup.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/boards/shmin/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/shmin/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/snapgear/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/snapgear/rtc.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/snapgear/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/titan/Makefile 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/titan/io.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/titan/setup.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boards/unknown/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/boot/compressed/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/cchips/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/cchips/hd6446x/hd64461/io.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/cchips/voyagergx/irq.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/cchips/voyagergx/setup.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/configs/landisk_defconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/configs/se73180_defconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/configs/shmin_defconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/configs/titan_defconfig 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/dma/Kconfig
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/dma/dma-g2.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/dma/dma-pvr2.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/dma/dma-sh.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/fixups-r7780rp.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/fixups-sh03.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/ops-bigsur.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/ops-landisk.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/ops-r7780rp.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/ops-sh4.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/ops-snapgear.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/ops-titan.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-auto.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-sh4.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-sh7751.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-sh7751.h
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-sh7780.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-sh7780.h 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci-st40.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/drivers/pci/pci.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/apm.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cf-enabler.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/clock.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/init.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/irq/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/irq/intc2.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/irq/ipr.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/irq/pint.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/rtc.c 已删除 100644 → 0
浏览文件 @ 28b79ff9
此差异已折叠。
arch/sh/kernel/cpu/sh3/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/clock-sh7706.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/ex.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/probe.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/setup-sh7300.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/setup-sh7705.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/setup-sh7708.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/setup-sh7709.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh3/setup-sh7710.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/Makefile
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/ex.S
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/probe.c
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh4-202.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh73180.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh7343.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh7750.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh7760.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh7770.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
arch/sh/kernel/cpu/sh4/setup-sh7780.c 0 → 100644
浏览文件 @ 8a84fc15
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或