Skip to content

K
Kernel

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

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

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

上级 17ffc7ba fcc18e83
展开全部 隐藏空白更改
内联 并排
Showing with 52166 addition and 22781 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ 62ed948c
......@@ -1573,12 +1573,8 @@ S: 160 00 Praha 6
S: Czech Republic
N: Niels Kristian Bech Jensen
E: nkbj@image.dk
W: http://www.image.dk/~nkbj
E: nkbj1970@hotmail.com
D: Miscellaneous kernel updates and fixes.
S: Dr. Holsts Vej 34, lejl. 164
S: DK-8230 byhj
S: Denmark
N: Michael K. Johnson
E: johnsonm@redhat.com
......
Documentation/ABI/README 0 → 100644
浏览文件 @ 62ed948c
This directory attempts to document the ABI between the Linux kernel and
userspace, and the relative stability of these interfaces. Due to the
everchanging nature of Linux, and the differing maturity levels, these
interfaces should be used by userspace programs in different ways.
We have four different levels of ABI stability, as shown by the four
different subdirectories in this location. Interfaces may change levels
of stability according to the rules described below.
The different levels of stability are:
stable/
This directory documents the interfaces that the developer has
defined to be stable. Userspace programs are free to use these
interfaces with no restrictions, and backward compatibility for
them will be guaranteed for at least 2 years. Most interfaces
(like syscalls) are expected to never change and always be
available.
testing/
This directory documents interfaces that are felt to be stable,
as the main development of this interface has been completed.
The interface can be changed to add new features, but the
current interface will not break by doing this, unless grave
errors or security problems are found in them. Userspace
programs can start to rely on these interfaces, but they must be
aware of changes that can occur before these interfaces move to
be marked stable. Programs that use these interfaces are
strongly encouraged to add their name to the description of
these interfaces, so that the kernel developers can easily
notify them if any changes occur (see the description of the
layout of the files below for details on how to do this.)
obsolete/
This directory documents interfaces that are still remaining in
the kernel, but are marked to be removed at some later point in
time. The description of the interface will document the reason
why it is obsolete and when it can be expected to be removed.
The file Documentation/feature-removal-schedule.txt may describe
some of these interfaces, giving a schedule for when they will
be removed.
removed/
This directory contains a list of the old interfaces that have
been removed from the kernel.
Every file in these directories will contain the following information:
What: Short description of the interface
Date: Date created
KernelVersion: Kernel version this feature first showed up in.
Contact: Primary contact for this interface (may be a mailing list)
Description: Long description of the interface and how to use it.
Users: All users of this interface who wish to be notified when
it changes. This is very important for interfaces in
the "testing" stage, so that kernel developers can work
with userspace developers to ensure that things do not
break in ways that are unacceptable. It is also
important to get feedback for these interfaces to make
sure they are working in a proper way and do not need to
be changed further.
How things move between levels:
Interfaces in stable may move to obsolete, as long as the proper
notification is given.
Interfaces may be removed from obsolete and the kernel as long as the
documented amount of time has gone by.
Interfaces in the testing state can move to the stable state when the
developers feel they are finished. They cannot be removed from the
kernel tree without going through the obsolete state first.
It's up to the developer to place their interfaces in the category they
wish for it to start out in.
Documentation/ABI/obsolete/devfs 0 → 100644
浏览文件 @ 62ed948c
What: devfs
Date: July 2005
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,
along with the the assorted devfs function calls throughout the
kernel tree.
Users:
Documentation/ABI/stable/syscalls 0 → 100644
浏览文件 @ 62ed948c
What: The kernel syscall interface
Description:
This interface matches much of the POSIX interface and is based
on it and other Unix based interfaces. It will only be added to
over time, and not have things removed from it.
Note that this interface is different for every architecture
that Linux supports. Please see the architecture-specific
documentation for details on the syscall numbers that are to be
mapped to each syscall.
Documentation/ABI/stable/sysfs-module 0 → 100644
浏览文件 @ 62ed948c
What: /sys/module
Description:
The /sys/module tree consists of the following structure:
/sys/module/MODULENAME
The name of the module that is in the kernel. This
module name will show up either if the module is built
directly into the kernel, or if it is loaded as a
dyanmic module.
/sys/module/MODULENAME/parameters
This directory contains individual files that are each
individual parameters of the module that are able to be
changed at runtime. See the individual module
documentation as to the contents of these parameters and
what they accomplish.
Note: The individual parameter names and values are not
considered stable, only the fact that they will be
placed in this location within sysfs. See the
individual driver documentation for details as to the
stability of the different parameters.
/sys/module/MODULENAME/refcnt
If the module is able to be unloaded from the kernel, this file
will contain the current reference count of the module.
Note: If the module is built into the kernel, or if the
CONFIG_MODULE_UNLOAD kernel configuration value is not enabled,
this file will not be present.
Documentation/ABI/testing/sysfs-class 0 → 100644
浏览文件 @ 62ed948c
What: /sys/class/
Date: Febuary 2006
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
The /sys/class directory will consist of a group of
subdirectories describing individual classes of devices
in the kernel. The individual directories will consist
of either subdirectories, or symlinks to other
directories.
All programs that use this directory tree must be able
to handle both subdirectories or symlinks in order to
work properly.
Users:
udev <linux-hotplug-devel@lists.sourceforge.net>
Documentation/ABI/testing/sysfs-devices 0 → 100644
浏览文件 @ 62ed948c
What: /sys/devices
Date: February 2006
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
The /sys/devices tree contains a snapshot of the
internal state of the kernel device tree. Devices will
be added and removed dynamically as the machine runs,
and between different kernel versions, the layout of the
devices within this tree will change.
Please do not rely on the format of this tree because of
this. If a program wishes to find different things in
the tree, please use the /sys/class structure and rely
on the symlinks there to point to the proper location
within the /sys/devices tree of the individual devices.
Or rely on the uevent messages to notify programs of
devices being added and removed from this tree to find
the location of those devices.
Note that sometimes not all devices along the directory
chain will have emitted uevent messages, so userspace
programs must be able to handle such occurrences.
Users:
udev <linux-hotplug-devel@lists.sourceforge.net>
Documentation/CodingStyle
浏览文件 @ 62ed948c
......@@ -155,7 +155,83 @@ problem, which is called the function-growth-hormone-imbalance syndrome.
See next chapter.
Chapter 5: Functions
Chapter 5: Typedefs
Please don't use things like "vps_t".
It's a _mistake_ to use typedef for structures and pointers. When you see a
vps_t a;
in the source, what does it mean?
In contrast, if it says
struct virtual_container *a;
you can actually tell what "a" is.
Lots of people think that typedefs "help readability". Not so. They are
useful only for:
(a) totally opaque objects (where the typedef is actively used to _hide_
what the object is).
Example: "pte_t" etc. opaque objects that you can only access using
the proper accessor functions.
NOTE! Opaqueness and "accessor functions" are not good in themselves.
The reason we have them for things like pte_t etc. is that there
really is absolutely _zero_ portably accessible information there.
(b) Clear integer types, where the abstraction _helps_ avoid confusion
whether it is "int" or "long".
u8/u16/u32 are perfectly fine typedefs, although they fit into
category (d) better than here.
NOTE! Again - there needs to be a _reason_ for this. If something is
"unsigned long", then there's no reason to do
typedef unsigned long myflags_t;
but if there is a clear reason for why it under certain circumstances
might be an "unsigned int" and under other configurations might be
"unsigned long", then by all means go ahead and use a typedef.
(c) when you use sparse to literally create a _new_ type for
type-checking.
(d) New types which are identical to standard C99 types, in certain
exceptional circumstances.
Although it would only take a short amount of time for the eyes and
brain to become accustomed to the standard types like 'uint32_t',
some people object to their use anyway.
Therefore, the Linux-specific 'u8/u16/u32/u64' types and their
signed equivalents which are identical to standard types are
permitted -- although they are not mandatory in new code of your
own.
When editing existing code which already uses one or the other set
of types, you should conform to the existing choices in that code.
(e) Types safe for use in userspace.
In certain structures which are visible to userspace, we cannot
require C99 types and cannot use the 'u32' form above. Thus, we
use __u32 and similar types in all structures which are shared
with userspace.
Maybe there are other cases too, but the rule should basically be to NEVER
EVER use a typedef unless you can clearly match one of those rules.
In general, a pointer, or a struct that has elements that can reasonably
be directly accessed should _never_ be a typedef.
Chapter 6: Functions
Functions should be short and sweet, and do just one thing. They should
fit on one or two screenfuls of text (the ISO/ANSI screen size is 80x24,
......@@ -183,7 +259,7 @@ and it gets confused. You know you're brilliant, but maybe you'd like
to understand what you did 2 weeks from now.
Chapter 6: Centralized exiting of functions
Chapter 7: Centralized exiting of functions
Albeit deprecated by some people, the equivalent of the goto statement is
used frequently by compilers in form of the unconditional jump instruction.
......@@ -220,7 +296,7 @@ out:
return result;
}
Chapter 7: Commenting
Chapter 8: Commenting
Comments are good, but there is also a danger of over-commenting. NEVER
try to explain HOW your code works in a comment: it's much better to
......@@ -240,7 +316,7 @@ When commenting the kernel API functions, please use the kerneldoc format.
See the files Documentation/kernel-doc-nano-HOWTO.txt and scripts/kernel-doc
for details.
Chapter 8: You've made a mess of it
Chapter 9: You've made a mess of it
That's OK, we all do. You've probably been told by your long-time Unix
user helper that "GNU emacs" automatically formats the C sources for
......@@ -288,7 +364,7 @@ re-formatting you may want to take a look at the man page. But
remember: "indent" is not a fix for bad programming.
Chapter 9: Configuration-files
Chapter 10: Configuration-files
For configuration options (arch/xxx/Kconfig, and all the Kconfig files),
somewhat different indentation is used.
......@@ -313,7 +389,7 @@ support for file-systems, for instance) should be denoted (DANGEROUS), other
experimental options should be denoted (EXPERIMENTAL).
Chapter 10: Data structures
Chapter 11: Data structures
Data structures that have visibility outside the single-threaded
environment they are created and destroyed in should always have
......@@ -344,7 +420,7 @@ Remember: if another thread can find your data structure, and you don't
have a reference count on it, you almost certainly have a bug.
Chapter 11: Macros, Enums and RTL
Chapter 12: Macros, Enums and RTL
Names of macros defining constants and labels in enums are capitalized.
......@@ -399,7 +475,7 @@ The cpp manual deals with macros exhaustively. The gcc internals manual also
covers RTL which is used frequently with assembly language in the kernel.
Chapter 12: Printing kernel messages
Chapter 13: Printing kernel messages
Kernel developers like to be seen as literate. Do mind the spelling
of kernel messages to make a good impression. Do not use crippled
......@@ -410,7 +486,7 @@ Kernel messages do not have to be terminated with a period.
Printing numbers in parentheses (%d) adds no value and should be avoided.
Chapter 13: Allocating memory
Chapter 14: Allocating memory
The kernel provides the following general purpose memory allocators:
kmalloc(), kzalloc(), kcalloc(), and vmalloc(). Please refer to the API
......@@ -429,7 +505,7 @@ from void pointer to any other pointer type is guaranteed by the C programming
language.
Chapter 14: The inline disease
Chapter 15: The inline disease
There appears to be a common misperception that gcc has a magic "make me
faster" speedup option called "inline". While the use of inlines can be
......@@ -457,7 +533,7 @@ something it would have done anyway.
Chapter 15: References
Appendix I: References
The C Programming Language, Second Edition
by Brian W. Kernighan and Dennis M. Ritchie.
......@@ -481,4 +557,4 @@ Kernel CodingStyle, by greg@kroah.com at OLS 2002:
http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/
--
Last updated on 30 December 2005 by a community effort on LKML.
Last updated on 30 April 2006.
Documentation/DocBook/kernel-api.tmpl
浏览文件 @ 62ed948c
......@@ -62,6 +62,8 @@
<sect1><title>Internal Functions</title>
!Ikernel/exit.c
!Ikernel/signal.c
!Iinclude/linux/kthread.h
!Ekernel/kthread.c
</sect1>
<sect1><title>Kernel objects manipulation</title>
......@@ -114,9 +116,33 @@ X!Ilib/string.c
</sect1>
</chapter>
<chapter id="kernel-lib">
<title>Basic Kernel Library Functions</title>
<para>
The Linux kernel provides more basic utility functions.
</para>
<sect1><title>Bitmap Operations</title>
!Elib/bitmap.c
!Ilib/bitmap.c
</sect1>
<sect1><title>Command-line Parsing</title>
!Elib/cmdline.c
</sect1>
<sect1><title>CRC Functions</title>
!Elib/crc16.c
!Elib/crc32.c
!Elib/crc-ccitt.c
</sect1>
</chapter>
<chapter id="mm">
<title>Memory Management in Linux</title>
<sect1><title>The Slab Cache</title>
!Iinclude/linux/slab.h
!Emm/slab.c
</sect1>
<sect1><title>User Space Memory Access</title>
......@@ -280,12 +306,13 @@ X!Ekernel/module.c
<sect1><title>MTRR Handling</title>
!Earch/i386/kernel/cpu/mtrr/main.c
</sect1>
<sect1><title>PCI Support Library</title>
!Edrivers/pci/pci.c
!Edrivers/pci/pci-driver.c
!Edrivers/pci/remove.c
!Edrivers/pci/pci-acpi.c
<!-- kerneldoc does not understand to __devinit
<!-- kerneldoc does not understand __devinit
X!Edrivers/pci/search.c
-->
!Edrivers/pci/msi.c
......@@ -314,6 +341,13 @@ X!Earch/i386/kernel/mca.c
</sect1>
</chapter>
<chapter id="firmware">
<title>Firmware Interfaces</title>
<sect1><title>DMI Interfaces</title>
!Edrivers/firmware/dmi_scan.c
</sect1>
</chapter>
<chapter id="devfs">
<title>The Device File System</title>
!Efs/devfs/base.c
......@@ -331,6 +365,18 @@ X!Earch/i386/kernel/mca.c
!Esecurity/security.c
</chapter>
<chapter id="audit">
<title>Audit Interfaces</title>
!Ekernel/audit.c
!Ikernel/auditsc.c
!Ikernel/auditfilter.c
</chapter>
<chapter id="accounting">
<title>Accounting Framework</title>
!Ikernel/acct.c
</chapter>
<chapter id="pmfuncs">
<title>Power Management</title>
!Ekernel/power/pm.c
......@@ -390,7 +436,6 @@ X!Edrivers/pnp/system.c
</sect1>
</chapter>
<chapter id="blkdev">
<title>Block Devices</title>
!Eblock/ll_rw_blk.c
......@@ -401,6 +446,14 @@ X!Edrivers/pnp/system.c
!Edrivers/char/misc.c
</chapter>
<chapter id="parportdev">
<title>Parallel Port Devices</title>
!Iinclude/linux/parport.h
!Edrivers/parport/ieee1284.c
!Edrivers/parport/share.c
!Idrivers/parport/daisy.c
</chapter>
<chapter id="viddev">
<title>Video4Linux</title>
!Edrivers/media/video/videodev.c
......
Documentation/DocBook/libata.tmpl
浏览文件 @ 62ed948c
......@@ -169,6 +169,22 @@ void (*tf_read) (struct ata_port *ap, struct ata_taskfile *tf);
</sect2>
<sect2><title>PIO data read/write</title>
<programlisting>
void (*data_xfer) (struct ata_device *, unsigned char *, unsigned int, int);
</programlisting>
<para>
All bmdma-style drivers must implement this hook. This is the low-level
operation that actually copies the data bytes during a PIO data
transfer.
Typically the driver
will choose one of ata_pio_data_xfer_noirq(), ata_pio_data_xfer(), or
ata_mmio_data_xfer().
</para>
</sect2>
<sect2><title>ATA command execute</title>
<programlisting>
void (*exec_command)(struct ata_port *ap, struct ata_taskfile *tf);
......@@ -204,11 +220,10 @@ command.
<programlisting>
u8 (*check_status)(struct ata_port *ap);
u8 (*check_altstatus)(struct ata_port *ap);
u8 (*check_err)(struct ata_port *ap);
</programlisting>
<para>
Reads the Status/AltStatus/Error ATA shadow register from
Reads the Status/AltStatus ATA shadow register from
hardware. On some hardware, reading the Status register has
the side effect of clearing the interrupt condition.
Most drivers for taskfile-based hardware use
......@@ -269,23 +284,6 @@ void (*set_mode) (struct ata_port *ap);
</sect2>
<sect2><title>Reset ATA bus</title>
<programlisting>
void (*phy_reset) (struct ata_port *ap);
</programlisting>
<para>
The very first step in the probe phase. Actions vary depending
on the bus type, typically. After waking up the device and probing
for device presence (PATA and SATA), typically a soft reset
(SRST) will be performed. Drivers typically use the helper
functions ata_bus_reset() or sata_phy_reset() for this hook.
Many SATA drivers use sata_phy_reset() or call it from within
their own phy_reset() functions.
</para>
</sect2>
<sect2><title>Control PCI IDE BMDMA engine</title>
<programlisting>
void (*bmdma_setup) (struct ata_queued_cmd *qc);
......@@ -354,16 +352,74 @@ int (*qc_issue) (struct ata_queued_cmd *qc);
</sect2>
<sect2><title>Timeout (error) handling</title>
<sect2><title>Exception and probe handling (EH)</title>
<programlisting>
void (*eng_timeout) (struct ata_port *ap);
void (*phy_reset) (struct ata_port *ap);
</programlisting>
<para>
Deprecated. Use ->error_handler() instead.
</para>
<programlisting>
void (*freeze) (struct ata_port *ap);
void (*thaw) (struct ata_port *ap);
</programlisting>
<para>
ata_port_freeze() is called when HSM violations or some other
condition disrupts normal operation of the port. A frozen port
is not allowed to perform any operation until the port is
thawed, which usually follows a successful reset.
</para>
<para>
The optional ->freeze() callback can be used for freezing the port
hardware-wise (e.g. mask interrupt and stop DMA engine). If a
port cannot be frozen hardware-wise, the interrupt handler
must ack and clear interrupts unconditionally while the port
is frozen.
</para>
<para>
The optional ->thaw() callback is called to perform the opposite of ->freeze():
prepare the port for normal operation once again. Unmask interrupts,
start DMA engine, etc.
</para>
<programlisting>
void (*error_handler) (struct ata_port *ap);
</programlisting>
<para>
->error_handler() is a driver's hook into probe, hotplug, and recovery
and other exceptional conditions. The primary responsibility of an
implementation is to call ata_do_eh() or ata_bmdma_drive_eh() with a set
of EH hooks as arguments:
</para>
<para>
'prereset' hook (may be NULL) is called during an EH reset, before any other actions
are taken.
</para>
<para>
'postreset' hook (may be NULL) is called after the EH reset is performed. Based on
existing conditions, severity of the problem, and hardware capabilities,
</para>
<para>
Either 'softreset' (may be NULL) or 'hardreset' (may be NULL) will be
called to perform the low-level EH reset.
</para>
<programlisting>
void (*post_internal_cmd) (struct ata_queued_cmd *qc);
</programlisting>
<para>
This is a high level error handling function, called from the
error handling thread, when a command times out. Most newer
hardware will implement its own error handling code here. IDE BMDMA
drivers may use the helper function ata_eng_timeout().
Perform any hardware-specific actions necessary to finish processing
after executing a probe-time or EH-time command via ata_exec_internal().
</para>
</sect2>
......
Documentation/RCU/checklist.txt
浏览文件 @ 62ed948c
......@@ -144,9 +144,47 @@ over a rather long period of time, but improvements are always welcome!
whether the increased speed is worth it.
8. Although synchronize_rcu() is a bit slower than is call_rcu(),
it usually results in simpler code. So, unless update performance
is important or the updaters cannot block, synchronize_rcu()
should be used in preference to call_rcu().
it usually results in simpler code. So, unless update
performance is critically important or the updaters cannot block,
synchronize_rcu() should be used in preference to call_rcu().
An especially important property of the synchronize_rcu()
primitive is that it automatically self-limits: if grace periods
are delayed for whatever reason, then the synchronize_rcu()
primitive will correspondingly delay updates. In contrast,
code using call_rcu() should explicitly limit update rate in
cases where grace periods are delayed, as failing to do so can
result in excessive realtime latencies or even OOM conditions.
Ways of gaining this self-limiting property when using call_rcu()
include:
a. Keeping a count of the number of data-structure elements
used by the RCU-protected data structure, including those
waiting for a grace period to elapse. Enforce a limit
on this number, stalling updates as needed to allow
previously deferred frees to complete.
Alternatively, limit only the number awaiting deferred
free rather than the total number of elements.
b. Limiting update rate. For example, if updates occur only
once per hour, then no explicit rate limiting is required,
unless your system is already badly broken. The dcache
subsystem takes this approach -- updates are guarded
by a global lock, limiting their rate.
c. Trusted update -- if updates can only be done manually by
superuser or some other trusted user, then it might not
be necessary to automatically limit them. The theory
here is that superuser already has lots of ways to crash
the machine.
d. Use call_rcu_bh() rather than call_rcu(), in order to take
advantage of call_rcu_bh()'s faster grace periods.
e. Periodically invoke synchronize_rcu(), permitting a limited
number of updates per grace period.
9. All RCU list-traversal primitives, which include
list_for_each_rcu(), list_for_each_entry_rcu(),
......
Documentation/RCU/whatisRCU.txt
浏览文件 @ 62ed948c
......@@ -184,7 +184,17 @@ synchronize_rcu()
blocking, it registers a function and argument which are invoked
after all ongoing RCU read-side critical sections have completed.
This callback variant is particularly useful in situations where
it is illegal to block.
it is illegal to block or where update-side performance is
critically important.
However, the call_rcu() API should not be used lightly, as use
of the synchronize_rcu() API generally results in simpler code.
In addition, the synchronize_rcu() API has the nice property
of automatically limiting update rate should grace periods
be delayed. This property results in system resilience in face
of denial-of-service attacks. Code using call_rcu() should limit
update rate in order to gain this same sort of resilience. See
checklist.txt for some approaches to limiting the update rate.
rcu_assign_pointer()
......@@ -790,7 +800,6 @@ RCU pointer update:
RCU grace period:
synchronize_kernel (deprecated)
synchronize_net
synchronize_sched
synchronize_rcu
......
Documentation/SubmitChecklist 0 → 100644
浏览文件 @ 62ed948c
Linux Kernel patch sumbittal checklist
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here are some basic things that developers should do if they
want to see their kernel patch submittals accepted quicker.
These are all above and beyond the documentation that is provided
in Documentation/SubmittingPatches and elsewhere about submitting
Linux kernel patches.
- Builds cleanly with applicable or modified CONFIG options =y, =m, and =n.
No gcc warnings/errors, no linker warnings/errors.
- Passes allnoconfig, allmodconfig
- Builds on multiple CPU arch-es by using local cross-compile tools
or something like PLM at OSDL.
- ppc64 is a good architecture for cross-compilation checking because it
tends to use `unsigned long' for 64-bit quantities.
- Matches kernel coding style(!)
- Any new or modified CONFIG options don't muck up the config menu.
- All new Kconfig options have help text.
- Has been carefully reviewed with respect to relevant Kconfig
combinations. This is very hard to get right with testing --
brainpower pays off here.
- Check cleanly with sparse.
- Use 'make checkstack' and 'make namespacecheck' and fix any
problems that they find. Note: checkstack does not point out
problems explicitly, but any one function that uses more than
512 bytes on the stack is a candidate for change.
- Include kernel-doc to document global kernel APIs. (Not required
for static functions, but OK there also.) Use 'make htmldocs'
or 'make mandocs' to check the kernel-doc and fix any issues.
- Has been tested with CONFIG_PREEMPT, CONFIG_DEBUG_PREEMPT,
CONFIG_DEBUG_SLAB, CONFIG_DEBUG_PAGEALLOC, CONFIG_DEBUG_MUTEXES,
CONFIG_DEBUG_SPINLOCK, CONFIG_DEBUG_SPINLOCK_SLEEP all simultaneously
enabled.
- Has been build- and runtime tested with and without CONFIG_SMP and
CONFIG_PREEMPT.
- If the patch affects IO/Disk, etc: has been tested with and without
CONFIG_LBD.
2006-APR-27
Documentation/devices.txt
浏览文件 @ 62ed948c
......@@ -3,7 +3,7 @@
Maintained by Torben Mathiasen <device@lanana.org>
Last revised: 25 January 2005
Last revised: 15 May 2006
This list is the Linux Device List, the official registry of allocated
device numbers and /dev directory nodes for the Linux operating
......@@ -94,7 +94,6 @@ Your cooperation is appreciated.
9 = /dev/urandom Faster, less secure random number gen.
10 = /dev/aio Asyncronous I/O notification interface
11 = /dev/kmsg Writes to this come out as printk's
12 = /dev/oldmem Access to crash dump from kexec kernel
1 block RAM disk
0 = /dev/ram0 First RAM disk
1 = /dev/ram1 Second RAM disk
......@@ -262,13 +261,13 @@ Your cooperation is appreciated.
NOTE: These devices permit both read and write access.
7 block Loopback devices
0 = /dev/loop0 First loopback device
1 = /dev/loop1 Second loopback device
0 = /dev/loop0 First loop device
1 = /dev/loop1 Second loop device
...
The loopback devices are used to mount filesystems not
The loop devices are used to mount filesystems not
associated with block devices. The binding to the
loopback devices is handled by mount(8) or losetup(8).
loop devices is handled by mount(8) or losetup(8).
8 block SCSI disk devices (0-15)
0 = /dev/sda First SCSI disk whole disk
......@@ -943,7 +942,7 @@ Your cooperation is appreciated.
240 = /dev/ftlp FTL on 16th Memory Technology Device
Partitions are handled in the same way as for IDE
disks (see major number 3) expect that the partition
disks (see major number 3) except that the partition
limit is 15 rather than 63 per disk (same as SCSI.)
45 char isdn4linux ISDN BRI driver
......@@ -1168,7 +1167,7 @@ Your cooperation is appreciated.
The filename of the encrypted container and the passwords
are sent via ioctls (using the sdmount tool) to the master
node which then activates them via one of the
/dev/scramdisk/x nodes for loopback mounting (all handled
/dev/scramdisk/x nodes for loop mounting (all handled
through the sdmount tool).
Requested by: andy@scramdisklinux.org
......@@ -2538,18 +2537,32 @@ Your cooperation is appreciated.
0 = /dev/usb/lp0 First USB printer
...
15 = /dev/usb/lp15 16th USB printer
16 = /dev/usb/mouse0 First USB mouse
...
31 = /dev/usb/mouse15 16th USB mouse
32 = /dev/usb/ez0 First USB firmware loader
...
47 = /dev/usb/ez15 16th USB firmware loader
48 = /dev/usb/scanner0 First USB scanner
...
63 = /dev/usb/scanner15 16th USB scanner
64 = /dev/usb/rio500 Diamond Rio 500
65 = /dev/usb/usblcd USBLCD Interface (info@usblcd.de)
66 = /dev/usb/cpad0 Synaptics cPad (mouse/LCD)
96 = /dev/usb/hiddev0 1st USB HID device
...
111 = /dev/usb/hiddev15 16th USB HID device
112 = /dev/usb/auer0 1st auerswald ISDN device
...
127 = /dev/usb/auer15 16th auerswald ISDN device
128 = /dev/usb/brlvgr0 First Braille Voyager device
...
131 = /dev/usb/brlvgr3 Fourth Braille Voyager device
132 = /dev/usb/idmouse ID Mouse (fingerprint scanner) device
133 = /dev/usb/sisusbvga1 First SiSUSB VGA device
...
140 = /dev/usb/sisusbvga8 Eigth SISUSB VGA device
144 = /dev/usb/lcd USB LCD device
160 = /dev/usb/legousbtower0 1st USB Legotower device
...
175 = /dev/usb/legousbtower15 16th USB Legotower device
240 = /dev/usb/dabusb0 First daubusb device
...
243 = /dev/usb/dabusb3 Fourth dabusb device
180 block USB block devices
0 = /dev/uba First USB block device
......@@ -2710,6 +2723,17 @@ Your cooperation is appreciated.
1 = /dev/cpu/1/msr MSRs on CPU 1
...
202 block Xen Virtual Block Device
0 = /dev/xvda First Xen VBD whole disk
16 = /dev/xvdb Second Xen VBD whole disk
32 = /dev/xvdc Third Xen VBD whole disk
...
240 = /dev/xvdp Sixteenth Xen VBD whole disk
Partitions are handled in the same way as for IDE
disks (see major number 3) except that the limit on
partitions is 15.
203 char CPU CPUID information
0 = /dev/cpu/0/cpuid CPUID on CPU 0
1 = /dev/cpu/1/cpuid CPUID on CPU 1
......@@ -2747,11 +2771,27 @@ Your cooperation is appreciated.
46 = /dev/ttyCPM0 PPC CPM (SCC or SMC) - port 0
...
47 = /dev/ttyCPM5 PPC CPM (SCC or SMC) - port 5
50 = /dev/ttyIOC40 Altix serial card
50 = /dev/ttyIOC0 Altix serial card
...
81 = /dev/ttyIOC31 Altix serial card
82 = /dev/ttyVR0 NEC VR4100 series SIU
83 = /dev/ttyVR1 NEC VR4100 series DSIU
84 = /dev/ttyIOC84 Altix ioc4 serial card
...
115 = /dev/ttyIOC115 Altix ioc4 serial card
116 = /dev/ttySIOC0 Altix ioc3 serial card
...
147 = /dev/ttySIOC31 Altix ioc3 serial card
148 = /dev/ttyPSC0 PPC PSC - port 0
...
153 = /dev/ttyPSC5 PPC PSC - port 5
154 = /dev/ttyAT0 ATMEL serial port 0
...
169 = /dev/ttyAT15 ATMEL serial port 15
170 = /dev/ttyNX0 Hilscher netX serial port 0
...
81 = /dev/ttyIOC431 Altix serial card
82 = /dev/ttyVR0 NEC VR4100 series SIU
83 = /dev/ttyVR1 NEC VR4100 series DSIU
185 = /dev/ttyNX15 Hilscher netX serial port 15
186 = /dev/ttyJ0 JTAG1 DCC protocol based serial port emulation
205 char Low-density serial ports (alternate device)
0 = /dev/culu0 Callout device for ttyLU0
......@@ -2786,8 +2826,8 @@ Your cooperation is appreciated.
50 = /dev/cuioc40 Callout device for ttyIOC40
...
81 = /dev/cuioc431 Callout device for ttyIOC431
82 = /dev/cuvr0 Callout device for ttyVR0
83 = /dev/cuvr1 Callout device for ttyVR1
82 = /dev/cuvr0 Callout device for ttyVR0
83 = /dev/cuvr1 Callout device for ttyVR1
206 char OnStream SC-x0 tape devices
......@@ -2897,7 +2937,6 @@ Your cooperation is appreciated.
...
196 = /dev/dvb/adapter3/video0 first video decoder of fourth card
216 char Bluetooth RFCOMM TTY devices
0 = /dev/rfcomm0 First Bluetooth RFCOMM TTY device
1 = /dev/rfcomm1 Second Bluetooth RFCOMM TTY device
......@@ -3002,12 +3041,43 @@ Your cooperation is appreciated.
ioctl()'s can be used to rewind the tape regardless of
the device used to access it.
231 char InfiniBand MAD
231 char InfiniBand
0 = /dev/infiniband/umad0
1 = /dev/infiniband/umad1
...
...
63 = /dev/infiniband/umad63 63rd InfiniBandMad device
64 = /dev/infiniband/issm0 First InfiniBand IsSM device
65 = /dev/infiniband/issm1 Second InfiniBand IsSM device
...
127 = /dev/infiniband/issm63 63rd InfiniBand IsSM device
128 = /dev/infiniband/uverbs0 First InfiniBand verbs device
129 = /dev/infiniband/uverbs1 Second InfiniBand verbs device
...
159 = /dev/infiniband/uverbs31 31st InfiniBand verbs device
232 char Biometric Devices
0 = /dev/biometric/sensor0/fingerprint first fingerprint sensor on first device
1 = /dev/biometric/sensor0/iris first iris sensor on first device
2 = /dev/biometric/sensor0/retina first retina sensor on first device
3 = /dev/biometric/sensor0/voiceprint first voiceprint sensor on first device
4 = /dev/biometric/sensor0/facial first facial sensor on first device
5 = /dev/biometric/sensor0/hand first hand sensor on first device
...
10 = /dev/biometric/sensor1/fingerprint first fingerprint sensor on second device
...
20 = /dev/biometric/sensor2/fingerprint first fingerprint sensor on third device
...
233 char PathScale InfiniPath interconnect
0 = /dev/ipath Primary device for programs (any unit)
1 = /dev/ipath0 Access specifically to unit 0
2 = /dev/ipath1 Access specifically to unit 1
...
4 = /dev/ipath3 Access specifically to unit 3
129 = /dev/ipath_sma Device used by Subnet Management Agent
130 = /dev/ipath_diag Device used by diagnostics programs
232-239 UNASSIGNED
234-239 UNASSIGNED
240-254 char LOCAL/EXPERIMENTAL USE
240-254 block LOCAL/EXPERIMENTAL USE
......@@ -3021,6 +3091,28 @@ Your cooperation is appreciated.
This major is reserved to assist the expansion to a
larger number space. No device nodes with this major
should ever be created on the filesystem.
(This is probaly not true anymore, but I'll leave it
for now /Torben)
---LARGE MAJORS!!!!!---
256 char Equinox SST multi-port serial boards
0 = /dev/ttyEQ0 First serial port on first Equinox SST board
127 = /dev/ttyEQ127 Last serial port on first Equinox SST board
128 = /dev/ttyEQ128 First serial port on second Equinox SST board
...
1027 = /dev/ttyEQ1027 Last serial port on eighth Equinox SST board
256 block Resident Flash Disk Flash Translation Layer
0 = /dev/rfda First RFD FTL layer
16 = /dev/rfdb Second RFD FTL layer
...
240 = /dev/rfdp 16th RFD FTL layer
257 char Phoenix Technologies Cryptographic Services Driver
0 = /dev/ptlsec Crypto Services Driver
**** ADDITIONAL /dev DIRECTORY ENTRIES
......
Documentation/feature-removal-schedule.txt
浏览文件 @ 62ed948c
......@@ -33,21 +33,6 @@ Who: Adrian Bunk <bunk@stusta.de>
---------------------------
What: RCU API moves to EXPORT_SYMBOL_GPL
When: April 2006
Files: include/linux/rcupdate.h, kernel/rcupdate.c
Why: Outside of Linux, the only implementations of anything even
vaguely resembling RCU that I am aware of are in DYNIX/ptx,
VM/XA, Tornado, and K42. I do not expect anyone to port binary
drivers or kernel modules from any of these, since the first two
are owned by IBM and the last two are open-source research OSes.
So these will move to GPL after a grace period to allow
people, who might be using implementations that I am not aware
of, to adjust to this upcoming change.
Who: Paul E. McKenney <paulmck@us.ibm.com>
---------------------------
What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN
When: November 2006
Why: Deprecated in favour of the new ioctl-based rawiso interface, which is
......
Documentation/filesystems/Locking
浏览文件 @ 62ed948c
......@@ -99,7 +99,7 @@ prototypes:
int (*sync_fs)(struct super_block *sb, int wait);
void (*write_super_lockfs) (struct super_block *);
void (*unlockfs) (struct super_block *);
int (*statfs) (struct super_block *, struct kstatfs *);
int (*statfs) (struct dentry *, struct kstatfs *);
int (*remount_fs) (struct super_block *, int *, char *);
void (*clear_inode) (struct inode *);
void (*umount_begin) (struct super_block *);
......@@ -142,15 +142,16 @@ see also dquot_operations section.
--------------------------- file_system_type ---------------------------
prototypes:
struct super_block *(*get_sb) (struct file_system_type *, int,
const char *, void *);
struct int (*get_sb) (struct file_system_type *, int,
const char *, void *, struct vfsmount *);
void (*kill_sb) (struct super_block *);
locking rules:
may block BKL
get_sb yes yes
kill_sb yes yes
->get_sb() returns error or a locked superblock (exclusive on ->s_umount).
->get_sb() returns error or 0 with locked superblock attached to the vfsmount
(exclusive on ->s_umount).
->kill_sb() takes a write-locked superblock, does all shutdown work on it,
unlocks and drops the reference.
......
Documentation/filesystems/automount-support.txt
浏览文件 @ 62ed948c
......@@ -19,7 +19,7 @@ following procedure:
(2) Have the follow_link() op do the following steps:
(a) Call do_kern_mount() to call the appropriate filesystem to set up a
(a) Call vfs_kern_mount() to call the appropriate filesystem to set up a
superblock and gain a vfsmount structure representing it.
(b) Copy the nameidata provided as an argument and substitute the dentry
......
Documentation/filesystems/fuse.txt
浏览文件 @ 62ed948c
......@@ -18,6 +18,14 @@ Non-privileged mount (or user mount):
user. NOTE: this is not the same as mounts allowed with the "user"
option in /etc/fstab, which is not discussed here.
Filesystem connection:
A connection between the filesystem daemon and the kernel. The
connection exists until either the daemon dies, or the filesystem is
umounted. Note that detaching (or lazy umounting) the filesystem
does _not_ break the connection, in this case it will exist until
the last reference to the filesystem is released.
Mount owner:
The user who does the mounting.
......@@ -86,16 +94,20 @@ Mount options
The default is infinite. Note that the size of read requests is
limited anyway to 32 pages (which is 128kbyte on i386).
Sysfs
~~~~~
Control filesystem
~~~~~~~~~~~~~~~~~~
There's a control filesystem for FUSE, which can be mounted by:
FUSE sets up the following hierarchy in sysfs:
mount -t fusectl none /sys/fs/fuse/connections
/sys/fs/fuse/connections/N/
Mounting it under the '/sys/fs/fuse/connections' directory makes it
backwards compatible with earlier versions.
where N is an increasing number allocated to each new connection.
Under the fuse control filesystem each connection has a directory
named by a unique number.
For each connection the following attributes are defined:
For each connection the following files exist within this directory:
'waiting'
......@@ -110,7 +122,47 @@ For each connection the following attributes are defined:
connection. This means that all waiting requests will be aborted an
error returned for all aborted and new requests.
Only a privileged user may read or write these attributes.
Only the owner of the mount may read or write these files.
Interrupting filesystem operations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If a process issuing a FUSE filesystem request is interrupted, the
following will happen:
1) If the request is not yet sent to userspace AND the signal is
fatal (SIGKILL or unhandled fatal signal), then the request is
dequeued and returns immediately.
2) If the request is not yet sent to userspace AND the signal is not
fatal, then an 'interrupted' flag is set for the request. When
the request has been successfully transfered to userspace and
this flag is set, an INTERRUPT request is queued.
3) If the request is already sent to userspace, then an INTERRUPT
request is queued.
INTERRUPT requests take precedence over other requests, so the
userspace filesystem will receive queued INTERRUPTs before any others.
The userspace filesystem may ignore the INTERRUPT requests entirely,
or may honor them by sending a reply to the _original_ request, with
the error set to EINTR.
It is also possible that there's a race between processing the
original request and it's INTERRUPT request. There are two possibilities:
1) The INTERRUPT request is processed before the original request is
processed
2) The INTERRUPT request is processed after the original request has
been answered
If the filesystem cannot find the original request, it should wait for
some timeout and/or a number of new requests to arrive, after which it
should reply to the INTERRUPT request with an EAGAIN error. In case
1) the INTERRUPT request will be requeued. In case 2) the INTERRUPT
reply will be ignored.
Aborting a filesystem connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......@@ -139,8 +191,8 @@ the filesystem. There are several ways to do this:
- Use forced umount (umount -f). Works in all cases but only if
filesystem is still attached (it hasn't been lazy unmounted)
- Abort filesystem through the sysfs interface. Most powerful
method, always works.
- Abort filesystem through the FUSE control filesystem. Most
powerful method, always works.
How do non-privileged mounts work?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......@@ -304,25 +356,7 @@ Scenario 1 - Simple deadlock
| | for "file"]
| | *DEADLOCK*
The solution for this is to allow requests to be interrupted while
they are in userspace:
| [interrupted by signal] |
| <fuse_unlink() |
| [release semaphore] | [semaphore acquired]
| <sys_unlink() |
| | >fuse_unlink()
| | [queue req on fc->pending]
| | [wake up fc->waitq]
| | [sleep on req->waitq]
If the filesystem daemon was single threaded, this will stop here,
since there's no other thread to dequeue and execute the request.
In this case the solution is to kill the FUSE daemon as well. If
there are multiple serving threads, you just have to kill them as
long as any remain.
Moral: a filesystem which deadlocks, can soon find itself dead.
The solution for this is to allow the filesystem to be aborted.
Scenario 2 - Tricky deadlock
----------------------------
......@@ -355,24 +389,14 @@ but is caused by a pagefault.
| | [lock page]
| | * DEADLOCK *
Solution is again to let the the request be interrupted (not
elaborated further).
An additional problem is that while the write buffer is being
copied to the request, the request must not be interrupted. This
is because the destination address of the copy may not be valid
after the request is interrupted.
This is solved with doing the copy atomically, and allowing
interruption while the page(s) belonging to the write buffer are
faulted with get_user_pages(). The 'req->locked' flag indicates
when the copy is taking place, and interruption is delayed until
this flag is unset.
Solution is basically the same as above.
Scenario 3 - Tricky deadlock with asynchronous read
---------------------------------------------------
An additional problem is that while the write buffer is being copied
to the request, the request must not be interrupted/aborted. This is
because the destination address of the copy may not be valid after the
request has returned.
The same situation as above, except thread-1 will wait on page lock
and hence it will be uninterruptible as well. The solution is to
abort the connection with forced umount (if mount is attached) or
through the abort attribute in sysfs.
This is solved with doing the copy atomically, and allowing abort
while the page(s) belonging to the write buffer are faulted with
get_user_pages(). The 'req->locked' flag indicates when the copy is
taking place, and abort is delayed until this flag is unset.
Documentation/filesystems/porting
浏览文件 @ 62ed948c
......@@ -50,10 +50,11 @@ Turn your foo_read_super() into a function that would return 0 in case of
success and negative number in case of error (-EINVAL unless you have more
informative error value to report). Call it foo_fill_super(). Now declare
struct super_block foo_get_sb(struct file_system_type *fs_type,
int flags, const char *dev_name, void *data)
int foo_get_sb(struct file_system_type *fs_type,
int flags, const char *dev_name, void *data, struct vfsmount *mnt)
{
return get_sb_bdev(fs_type, flags, dev_name, data, ext2_fill_super);
return get_sb_bdev(fs_type, flags, dev_name, data, foo_fill_super,
mnt);
}
(or similar with s/bdev/nodev/ or s/bdev/single/, depending on the kind of
......
Documentation/filesystems/ramfs-rootfs-initramfs.txt
浏览文件 @ 62ed948c
......@@ -70,11 +70,13 @@ tmpfs mounts. See Documentation/filesystems/tmpfs.txt for more information.
What is rootfs?
---------------
Rootfs is a special instance of ramfs, which is always present in 2.6 systems.
(It's used internally as the starting and stopping point for searches of the
kernel's doubly-linked list of mount points.)
Rootfs is a special instance of ramfs (or tmpfs, if that's enabled), which is
always present in 2.6 systems. You can't unmount rootfs for approximately the
same reason you can't kill the init process; rather than having special code
to check for and handle an empty list, it's smaller and simpler for the kernel
to just make sure certain lists can't become empty.
Most systems just mount another filesystem over it and ignore it. The
Most systems just mount another filesystem over rootfs and ignore it. The
amount of space an empty instance of ramfs takes up is tiny.
What is initramfs?
......@@ -92,14 +94,16 @@ out of that.
All this differs from the old initrd in several ways:
- The old initrd was a separate file, while the initramfs archive is linked
into the linux kernel image. (The directory linux-*/usr is devoted to
generating this archive during the build.)
- The old initrd was always a separate file, while the initramfs archive is
linked into the linux kernel image. (The directory linux-*/usr is devoted
to generating this archive during the build.)
- The old initrd file was a gzipped filesystem image (in some file format,
such as ext2, that had to be built into the kernel), while the new
such as ext2, that needed a driver built into the kernel), while the new
initramfs archive is a gzipped cpio archive (like tar only simpler,
see cpio(1) and Documentation/early-userspace/buffer-format.txt).
see cpio(1) and Documentation/early-userspace/buffer-format.txt). The
kernel's cpio extraction code is not only extremely small, it's also
__init data that can be discarded during the boot process.
- The program run by the old initrd (which was called /initrd, not /init) did
some setup and then returned to the kernel, while the init program from
......@@ -124,13 +128,14 @@ Populating initramfs:
The 2.6 kernel build process always creates a gzipped cpio format initramfs
archive and links it into the resulting kernel binary. By default, this
archive is empty (consuming 134 bytes on x86). The config option
CONFIG_INITRAMFS_SOURCE (for some reason buried under devices->block devices
in menuconfig, and living in usr/Kconfig) can be used to specify a source for
the initramfs archive, which will automatically be incorporated into the
resulting binary. This option can point to an existing gzipped cpio archive, a
directory containing files to be archived, or a text file specification such
as the following example:
archive is empty (consuming 134 bytes on x86).
The config option CONFIG_INITRAMFS_SOURCE (for some reason buried under
devices->block devices in menuconfig, and living in usr/Kconfig) can be used
to specify a source for the initramfs archive, which will automatically be
incorporated into the resulting binary. This option can point to an existing
gzipped cpio archive, a directory containing files to be archived, or a text
file specification such as the following example:
dir /dev 755 0 0
nod /dev/console 644 0 0 c 5 1
......@@ -146,23 +151,84 @@ as the following example:
Run "usr/gen_init_cpio" (after the kernel build) to get a usage message
documenting the above file format.
One advantage of the text file is that root access is not required to
One advantage of the configuration file is that root access is not required to
set permissions or create device nodes in the new archive. (Note that those
two example "file" entries expect to find files named "init.sh" and "busybox" in
a directory called "initramfs", under the linux-2.6.* directory. See
Documentation/early-userspace/README for more details.)
The kernel does not depend on external cpio tools, gen_init_cpio is created
from usr/gen_init_cpio.c which is entirely self-contained, and the kernel's
boot-time extractor is also (obviously) self-contained. However, if you _do_
happen to have cpio installed, the following command line can extract the
generated cpio image back into its component files:
The kernel does not depend on external cpio tools. If you specify a
directory instead of a configuration file, the kernel's build infrastructure
creates a configuration file from that directory (usr/Makefile calls
scripts/gen_initramfs_list.sh), and proceeds to package up that directory
using the config file (by feeding it to usr/gen_init_cpio, which is created
from usr/gen_init_cpio.c). The kernel's build-time cpio creation code is
entirely self-contained, and the kernel's boot-time extractor is also
(obviously) self-contained.
The one thing you might need external cpio utilities installed for is creating
or extracting your own preprepared cpio files to feed to the kernel build
(instead of a config file or directory).
The following command line can extract a cpio image (either by the above script
or by the kernel build) back into its component files:
cpio -i -d -H newc -F initramfs_data.cpio --no-absolute-filenames
The following shell script can create a prebuilt cpio archive you can
use in place of the above config file:
#!/bin/sh
# Copyright 2006 Rob Landley <rob@landley.net> and TimeSys Corporation.
# Licensed under GPL version 2
if [ $# -ne 2 ]
then
echo "usage: mkinitramfs directory imagename.cpio.gz"
exit 1
fi
if [ -d "$1" ]
then
echo "creating $2 from $1"
(cd "$1"; find . | cpio -o -H newc | gzip) > "$2"
else
echo "First argument must be a directory"
exit 1
fi
Note: The cpio man page contains some bad advice that will break your initramfs
archive if you follow it. It says "A typical way to generate the list
of filenames is with the find command; you should give find the -depth option
to minimize problems with permissions on directories that are unwritable or not
searchable." Don't do this when creating initramfs.cpio.gz images, it won't
work. The Linux kernel cpio extractor won't create files in a directory that
doesn't exist, so the directory entries must go before the files that go in
those directories. The above script gets them in the right order.
External initramfs images:
--------------------------
If the kernel has initrd support enabled, an external cpio.gz archive can also
be passed into a 2.6 kernel in place of an initrd. In this case, the kernel
will autodetect the type (initramfs, not initrd) and extract the external cpio
archive into rootfs before trying to run /init.
This has the memory efficiency advantages of initramfs (no ramdisk block
device) but the separate packaging of initrd (which is nice if you have
non-GPL code you'd like to run from initramfs, without conflating it with
the GPL licensed Linux kernel binary).
It can also be used to supplement the kernel's built-in initamfs image. The
files in the external archive will overwrite any conflicting files in
the built-in initramfs archive. Some distributors also prefer to customize
a single kernel image with task-specific initramfs images, without recompiling.
Contents of initramfs:
----------------------
An initramfs archive is a complete self-contained root filesystem for Linux.
If you don't already understand what shared libraries, devices, and paths
you need to get a minimal root filesystem up and running, here are some
references:
......@@ -176,13 +242,36 @@ code against, along with some related utilities. It is BSD licensed.
I use uClibc (http://www.uclibc.org) and busybox (http://www.busybox.net)
myself. These are LGPL and GPL, respectively. (A self-contained initramfs
package is planned for the busybox 1.2 release.)
package is planned for the busybox 1.3 release.)
In theory you could use glibc, but that's not well suited for small embedded
uses like this. (A "hello world" program statically linked against glibc is
over 400k. With uClibc it's 7k. Also note that glibc dlopens libnss to do
name lookups, even when otherwise statically linked.)
A good first step is to get initramfs to run a statically linked "hello world"
program as init, and test it under an emulator like qemu (www.qemu.org) or
User Mode Linux, like so:
cat > hello.c << EOF
#include <stdio.h>
#include <unistd.h>
int main(int argc, char *argv[])
{
printf("Hello world!\n");
sleep(999999999);
}
EOF
gcc -static hello2.c -o init
echo init | cpio -o -H newc | gzip > test.cpio.gz
# Testing external initramfs using the initrd loading mechanism.
qemu -kernel /boot/vmlinuz -initrd test.cpio.gz /dev/zero
When debugging a normal root filesystem, it's nice to be able to boot with
"init=/bin/sh". The initramfs equivalent is "rdinit=/bin/sh", and it's
just as useful.
Why cpio rather than tar?
-------------------------
......@@ -241,7 +330,7 @@ the above threads) is:
Future directions:
------------------
Today (2.6.14), initramfs is always compiled in, but not always used. The
Today (2.6.16), initramfs is always compiled in, but not always used. The
kernel falls back to legacy boot code that is reached only if initramfs does
not contain an /init program. The fallback is legacy code, there to ensure a
smooth transition and allowing early boot functionality to gradually move to
......@@ -258,8 +347,9 @@ and so on.
This kind of complexity (which inevitably includes policy) is rightly handled
in userspace. Both klibc and busybox/uClibc are working on simple initramfs
packages to drop into a kernel build, and when standard solutions are ready
and widely deployed, the kernel's legacy early boot code will become obsolete
and a candidate for the feature removal schedule.
packages to drop into a kernel build.
But that's a while off yet.
The klibc package has now been accepted into Andrew Morton's 2.6.17-mm tree.
The kernel's current early boot code (partition detection, etc) will probably
be migrated into a default initramfs, automatically created and used by the
kernel build.
Documentation/filesystems/vfs.txt
浏览文件 @ 62ed948c
......@@ -113,8 +113,8 @@ members are defined:
struct file_system_type {
const char *name;
int fs_flags;
struct super_block *(*get_sb) (struct file_system_type *, int,
const char *, void *);
struct int (*get_sb) (struct file_system_type *, int,
const char *, void *, struct vfsmount *);
void (*kill_sb) (struct super_block *);
struct module *owner;
struct file_system_type * next;
......@@ -211,7 +211,7 @@ struct super_operations {
int (*sync_fs)(struct super_block *sb, int wait);
void (*write_super_lockfs) (struct super_block *);
void (*unlockfs) (struct super_block *);
int (*statfs) (struct super_block *, struct kstatfs *);
int (*statfs) (struct dentry *, struct kstatfs *);
int (*remount_fs) (struct super_block *, int *, char *);
void (*clear_inode) (struct inode *);
void (*umount_begin) (struct super_block *);
......
Documentation/hwmon/abituguru 0 → 100644
浏览文件 @ 62ed948c
Kernel driver abituguru
=======================
Supported chips:
* Abit uGuru (Hardware Monitor part only)
Prefix: 'abituguru'
Addresses scanned: ISA 0x0E0
Datasheet: Not available, this driver is based on reverse engineering.
A "Datasheet" has been written based on the reverse engineering it
should be available in the same dir as this file under the name
abituguru-datasheet.
Authors:
Hans de Goede <j.w.r.degoede@hhs.nl>,
(Initial reverse engineering done by Olle Sandberg
<ollebull@gmail.com>)
Module Parameters
-----------------
* force: bool Force detection. Note this parameter only causes the
detection to be skipped, if the uGuru can't be read
the module initialization (insmod) will still fail.
* fan_sensors: int Tell the driver how many fan speed sensors there are
on your motherboard. Default: 0 (autodetect).
* pwms: int Tell the driver how many fan speed controls (fan
pwms) your motherboard has. Default: 0 (autodetect).
* verbose: int How verbose should the driver be? (0-3):
0 normal output
1 + verbose error reporting
2 + sensors type probing info\n"
3 + retryable error reporting
Default: 2 (the driver is still in the testing phase)
Notice if you need any of the first three options above please insmod the
driver with verbose set to 3 and mail me <j.w.r.degoede@hhs.nl> the output of:
dmesg | grep abituguru
Description
-----------
This driver supports the hardware monitoring features of the Abit uGuru chip
found on Abit uGuru featuring motherboards (most modern Abit motherboards).
The uGuru chip in reality is a Winbond W83L950D in disguise (despite Abit
claiming it is "a new microprocessor designed by the ABIT Engineers").
Unfortunatly this doesn't help since the W83L950D is a generic
microcontroller with a custom Abit application running on it.
Despite Abit not releasing any information regarding the uGuru, Olle
Sandberg <ollebull@gmail.com> has managed to reverse engineer the sensor part
of the uGuru. Without his work this driver would not have been possible.
Known Issues
------------
The voltage and frequency control parts of the Abit uGuru are not supported.
Documentation/hwmon/abituguru-datasheet 0 → 100644
浏览文件 @ 62ed948c
uGuru datasheet
===============
First of all, what I know about uGuru is no fact based on any help, hints or
datasheet from Abit. The data I have got on uGuru have I assembled through
my weak knowledge in "backwards engineering".
And just for the record, you may have noticed uGuru isn't a chip developed by
Abit, as they claim it to be. It's realy just an microprocessor (uC) created by
Winbond (W83L950D). And no, reading the manual for this specific uC or
mailing Windbond for help won't give any usefull data about uGuru, as it is
the program inside the uC that is responding to calls.
Olle Sandberg <ollebull@gmail.com>, 2005-05-25
Original version by Olle Sandberg who did the heavy lifting of the initial
reverse engineering. This version has been almost fully rewritten for clarity
and extended with write support and info on more databanks, the write support
is once again reverse engineered by Olle the additional databanks have been
reverse engineered by me. I would like to express my thanks to Olle, this
document and the Linux driver could not have been written without his efforts.
Note: because of the lack of specs only the sensors part of the uGuru is
described here and not the CPU / RAM / etc voltage & frequency control.
Hans de Goede <j.w.r.degoede@hhs.nl>, 28-01-2006
Detection
=========
As far as known the uGuru is always placed at and using the (ISA) I/O-ports
0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two
ports are holding for detection. We will refer to 0xE0 as CMD (command-port)
and 0xE4 as DATA because Abit refers to them with these names.
If DATA holds 0x00 or 0x08 and CMD holds 0x00 or 0xAC an uGuru could be
present. We have to check for two different values at data-port, because
after a reboot uGuru will hold 0x00 here, but if the driver is removed and
later on attached again data-port will hold 0x08, more about this later.
After wider testing of the Linux kernel driver some variants of the uGuru have
turned up which will hold 0x00 instead of 0xAC at the CMD port, thus we also
have to test CMD for two different values. On these uGuru's DATA will initally
hold 0x09 and will only hold 0x08 after reading CMD first, so CMD must be read
first!
To be really sure an uGuru is present a test read of one or more register
sets should be done.
Reading / Writing
=================
Addressing
----------
The uGuru has a number of different addressing levels. The first addressing
level we will call banks. A bank holds data for one or more sensors. The data
in a bank for a sensor is one or more bytes large.
The number of bytes is fixed for a given bank, you should always read or write
that many bytes, reading / writing more will fail, the results when writing
less then the number of bytes for a given bank are undetermined.
See below for all known bank addresses, numbers of sensors in that bank,
number of bytes data per sensor and contents/meaning of those bytes.
Although both this document and the kernel driver have kept the sensor
terminoligy for the addressing within a bank this is not 100% correct, in
bank 0x24 for example the addressing within the bank selects a PWM output not
a sensor.
Notice that some banks have both a read and a write address this is how the
uGuru determines if a read from or a write to the bank is taking place, thus
when reading you should always use the read address and when writing the
write address. The write address is always one (1) more then the read address.
uGuru ready
-----------
Before you can read from or write to the uGuru you must first put the uGuru
in "ready" mode.
To put the uGuru in ready mode first write 0x00 to DATA and then wait for DATA
to hold 0x09, DATA should read 0x09 within 250 read cycles.
Next CMD _must_ be read and should hold 0xAC, usually CMD will hold 0xAC the
first read but sometimes it takes a while before CMD holds 0xAC and thus it
has to be read a number of times (max 50).
After reading CMD, DATA should hold 0x08 which means that the uGuru is ready
for input. As above DATA will usually hold 0x08 the first read but not always.
This step can be skipped, but it is undetermined what happens if the uGuru has
not yet reported 0x08 at DATA and you proceed with writing a bank address.
Sending bank and sensor addresses to the uGuru
----------------------------------------------
First the uGuru must be in "ready" mode as described above, DATA should hold
0x08 indicating that the uGuru wants input, in this case the bank address.
Next write the bank address to DATA. After the bank address has been written
wait for to DATA to hold 0x08 again indicating that it wants / is ready for
more input (max 250 reads).
Once DATA holds 0x08 again write the sensor address to CMD.
Reading
-------
First send the bank and sensor addresses as described above.
Then for each byte of data you want to read wait for DATA to hold 0x01
which indicates that the uGuru is ready to be read (max 250 reads) and once
DATA holds 0x01 read the byte from CMD.
Once all bytes have been read data will hold 0x09, but there is no reason to
test for this. Notice that the number of bytes is bank address dependent see
above and below.
After completing a successfull read it is advised to put the uGuru back in
ready mode, so that it is ready for the next read / write cycle. This way
if your program / driver is unloaded and later loaded again the detection
algorithm described above will still work.
Writing
-------
First send the bank and sensor addresses as described above.
Then for each byte of data you want to write wait for DATA to hold 0x00
which indicates that the uGuru is ready to be written (max 250 reads) and
once DATA holds 0x00 write the byte to CMD.
Once all bytes have been written wait for DATA to hold 0x01 (max 250 reads)
don't ask why this is the way it is.
Once DATA holds 0x01 read CMD it should hold 0xAC now.
After completing a successfull write it is advised to put the uGuru back in
ready mode, so that it is ready for the next read / write cycle. This way
if your program / driver is unloaded and later loaded again the detection
algorithm described above will still work.
Gotchas
-------
After wider testing of the Linux kernel driver some variants of the uGuru have
turned up which do not hold 0x08 at DATA within 250 reads after writing the
bank address. With these versions this happens quite frequent, using larger
timeouts doesn't help, they just go offline for a second or 2, doing some
internal callibration or whatever. Your code should be prepared to handle
this and in case of no response in this specific case just goto sleep for a
while and then retry.
Address Map
===========
Bank 0x20 Alarms (R)
--------------------
This bank contains 0 sensors, iow the sensor address is ignored (but must be
written) just use 0. Bank 0x20 contains 3 bytes:
Byte 0:
This byte holds the alarm flags for sensor 0-7 of Sensor Bank1, with bit 0
corresponding to sensor 0, 1 to 1, etc.
Byte 1:
This byte holds the alarm flags for sensor 8-15 of Sensor Bank1, with bit 0
corresponding to sensor 8, 1 to 9, etc.
Byte 2:
This byte holds the alarm flags for sensor 0-5 of Sensor Bank2, with bit 0
corresponding to sensor 0, 1 to 1, etc.
Bank 0x21 Sensor Bank1 Values / Readings (R)
--------------------------------------------
This bank contains 16 sensors, for each sensor it contains 1 byte.
So far the following sensors are known to be available on all motherboards:
Sensor 0 CPU temp
Sensor 1 SYS temp
Sensor 3 CPU core volt
Sensor 4 DDR volt
Sensor 10 DDR Vtt volt
Sensor 15 PWM temp
Byte 0:
This byte holds the reading from the sensor. Sensors in Bank1 can be both
volt and temp sensors, this is motherboard specific. The uGuru however does
seem to know (be programmed with) what kindoff sensor is attached see Sensor
Bank1 Settings description.
Volt sensors use a linear scale, a reading 0 corresponds with 0 volt and a
reading of 255 with 3494 mV. The sensors for higher voltages however are
connected through a division circuit. The currently known division circuits
in use result in ranges of: 0-4361mV, 0-6248mV or 0-14510mV. 3.3 volt sources
use the 0-4361mV range, 5 volt the 0-6248mV and 12 volt the 0-14510mV .
Temp sensors also use a linear scale, a reading of 0 corresponds with 0 degree
Celsius and a reading of 255 with a reading of 255 degrees Celsius.
Bank 0x22 Sensor Bank1 Settings (R)
Bank 0x23 Sensor Bank1 Settings (W)
-----------------------------------
This bank contains 16 sensors, for each sensor it contains 3 bytes. Each
set of 3 bytes contains the settings for the sensor with the same sensor
address in Bank 0x21 .
Byte 0:
Alarm behaviour for the selected sensor. A 1 enables the described behaviour.
Bit 0: Give an alarm if measured temp is over the warning threshold (RW) *
Bit 1: Give an alarm if measured volt is over the max threshold (RW) **
Bit 2: Give an alarm if measured volt is under the min threshold (RW) **
Bit 3: Beep if alarm (RW)
Bit 4: 1 if alarm cause measured temp is over the warning threshold (R)
Bit 5: 1 if alarm cause measured volt is over the max threshold (R)
Bit 6: 1 if alarm cause measured volt is under the min threshold (R)
Bit 7: Volt sensor: Shutdown if alarm persist for more then 4 seconds (RW)
Temp sensor: Shutdown if temp is over the shutdown threshold (RW)
* This bit is only honored/used by the uGuru if a temp sensor is connected
** This bit is only honored/used by the uGuru if a volt sensor is connected
Note with some trickery this can be used to find out what kinda sensor is
detected see the Linux kernel driver for an example with many comments on
how todo this.
Byte 1:
Temp sensor: warning threshold (scale as bank 0x21)
Volt sensor: min threshold (scale as bank 0x21)
Byte 2:
Temp sensor: shutdown threshold (scale as bank 0x21)
Volt sensor: max threshold (scale as bank 0x21)
Bank 0x24 PWM outputs for FAN's (R)
Bank 0x25 PWM outputs for FAN's (W)
-----------------------------------
This bank contains 3 "sensors", for each sensor it contains 5 bytes.
Sensor 0 usually controls the CPU fan
Sensor 1 usually controls the NB (or chipset for single chip) fan
Sensor 2 usually controls the System fan
Byte 0:
Flag 0x80 to enable control, Fan runs at 100% when disabled.
low nibble (temp)sensor address at bank 0x21 used for control.
Byte 1:
0-255 = 0-12v (linear), specify voltage at which fan will rotate when under
low threshold temp (specified in byte 3)
Byte 2:
0-255 = 0-12v (linear), specify voltage at which fan will rotate when above
high threshold temp (specified in byte 4)
Byte 3:
Low threshold temp (scale as bank 0x21)
byte 4:
High threshold temp (scale as bank 0x21)
Bank 0x26 Sensors Bank2 Values / Readings (R)
---------------------------------------------
This bank contains 6 sensors (AFAIK), for each sensor it contains 1 byte.
So far the following sensors are known to be available on all motherboards:
Sensor 0: CPU fan speed
Sensor 1: NB (or chipset for single chip) fan speed
Sensor 2: SYS fan speed
Byte 0:
This byte holds the reading from the sensor. 0-255 = 0-15300 (linear)
Bank 0x27 Sensors Bank2 Settings (R)
Bank 0x28 Sensors Bank2 Settings (W)
------------------------------------
This bank contains 6 sensors (AFAIK), for each sensor it contains 2 bytes.
Byte 0:
Alarm behaviour for the selected sensor. A 1 enables the described behaviour.
Bit 0: Give an alarm if measured rpm is under the min threshold (RW)
Bit 3: Beep if alarm (RW)
Bit 7: Shutdown if alarm persist for more then 4 seconds (RW)
Byte 1:
min threshold (scale as bank 0x26)
Warning for the adventerous
===========================
A word of caution to those who want to experiment and see if they can figure
the voltage / clock programming out, I tried reading and only reading banks
0-0x30 with the reading code used for the sensor banks (0x20-0x28) and this
resulted in a _permanent_ reprogramming of the voltages, luckily I had the
sensors part configured so that it would shutdown my system on any out of spec
voltages which proprably safed my computer (after a reboot I managed to
immediatly enter the bios and reload the defaults). This probably means that
the read/write cycle for the non sensor part is different from the sensor part.
Documentation/hwmon/lm70 0 → 100644
浏览文件 @ 62ed948c
Kernel driver lm70
==================
Supported chip:
* National Semiconductor LM70
Datasheet: http://www.national.com/pf/LM/LM70.html
Author:
Kaiwan N Billimoria <kaiwan@designergraphix.com>
Description
-----------
This driver implements support for the National Semiconductor LM70
temperature sensor.
The LM70 temperature sensor chip supports a single temperature sensor.
It communicates with a host processor (or microcontroller) via an
SPI/Microwire Bus interface.
Communication with the LM70 is simple: when the temperature is to be sensed,
the driver accesses the LM70 using SPI communication: 16 SCLK cycles
comprise the MOSI/MISO loop. At the end of the transfer, the 11-bit 2's
complement digital temperature (sent via the SIO line), is available in the
driver for interpretation. This driver makes use of the kernel's in-core
SPI support.
Thanks to
---------
Jean Delvare <khali@linux-fr.org> for mentoring the hwmon-side driver
development.
Documentation/hwmon/lm83
浏览文件 @ 62ed948c
......@@ -7,6 +7,10 @@ Supported chips:
Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
Datasheet: Publicly available at the National Semiconductor website
http://www.national.com/pf/LM/LM83.html
* National Semiconductor LM82
Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
Datasheet: Publicly available at the National Semiconductor website
http://www.national.com/pf/LM/LM82.html
Author: Jean Delvare <khali@linux-fr.org>
......@@ -15,10 +19,11 @@ Description
-----------
The LM83 is a digital temperature sensor. It senses its own temperature as
well as the temperature of up to three external diodes. It is compatible
with many other devices such as the LM84 and all other ADM1021 clones.
The main difference between the LM83 and the LM84 in that the later can
only sense the temperature of one external diode.
well as the temperature of up to three external diodes. The LM82 is
a stripped down version of the LM83 that only supports one external diode.
Both are compatible with many other devices such as the LM84 and all
other ADM1021 clones. The main difference between the LM83 and the LM84
in that the later can only sense the temperature of one external diode.
Using the adm1021 driver for a LM83 should work, but only two temperatures
will be reported instead of four.
......@@ -30,12 +35,16 @@ contact us. Note that the LM90 can easily be misdetected as a LM83.
Confirmed motherboards:
SBS P014
SBS PSL09
Unconfirmed motherboards:
Gigabyte GA-8IK1100
Iwill MPX2
Soltek SL-75DRV5
The LM82 is confirmed to have been found on most AMD Geode reference
designs and test platforms.
The driver has been successfully tested by Magnus Forsström, who I'd
like to thank here. More testers will be of course welcome.
......
Documentation/hwmon/smsc47m192 0 → 100644
浏览文件 @ 62ed948c
Kernel driver smsc47m192
========================
Supported chips:
* SMSC LPC47M192 and LPC47M997
Prefix: 'smsc47m192'
Addresses scanned: I2C 0x2c - 0x2d
Datasheet: The datasheet for LPC47M192 is publicly available from
http://www.smsc.com/
The LPC47M997 is compatible for hardware monitoring.
Author: Hartmut Rick <linux@rick.claranet.de>
Special thanks to Jean Delvare for careful checking
of the code and many helpful comments and suggestions.
Description
-----------
This driver implements support for the hardware sensor capabilities
of the SMSC LPC47M192 and LPC47M997 Super-I/O chips.
These chips support 3 temperature channels and 8 voltage inputs
as well as CPU voltage VID input.
They do also have fan monitoring and control capabilities, but the
these features are accessed via ISA bus and are not supported by this
driver. Use the 'smsc47m1' driver for fan monitoring and control.
Voltages and temperatures are measured by an 8-bit ADC, the resolution
of the temperatures is 1 bit per degree C.
Voltages are scaled such that the nominal voltage corresponds to
192 counts, i.e. 3/4 of the full range. Thus the available range for
each voltage channel is 0V ... 255/192*(nominal voltage), the resolution
is 1 bit per (nominal voltage)/192.
Both voltage and temperature values are scaled by 1000, the sys files
show voltages in mV and temperatures in units of 0.001 degC.
The +12V analog voltage input channel (in4_input) is multiplexed with
bit 4 of the encoded CPU voltage. This means that you either get
a +12V voltage measurement or a 5 bit CPU VID, but not both.
The default setting is to use the pin as 12V input, and use only 4 bit VID.
This driver assumes that the information in the configuration register
is correct, i.e. that the BIOS has updated the configuration if
the motherboard has this input wired to VID4.
The temperature and voltage readings are updated once every 1.5 seconds.
Reading them more often repeats the same values.
sysfs interface
---------------
in0_input - +2.5V voltage input
in1_input - CPU voltage input (nominal 2.25V)
in2_input - +3.3V voltage input
in3_input - +5V voltage input
in4_input - +12V voltage input (may be missing if used as VID4)
in5_input - Vcc voltage input (nominal 3.3V)
This is the supply voltage of the sensor chip itself.
in6_input - +1.5V voltage input
in7_input - +1.8V voltage input
in[0-7]_min,
in[0-7]_max - lower and upper alarm thresholds for in[0-7]_input reading
All voltages are read and written in mV.
in[0-7]_alarm - alarm flags for voltage inputs
These files read '1' in case of alarm, '0' otherwise.
temp1_input - chip temperature measured by on-chip diode
temp[2-3]_input - temperature measured by external diodes (one of these would
typically be wired to the diode inside the CPU)
temp[1-3]_min,
temp[1-3]_max - lower and upper alarm thresholds for temperatures
temp[1-3]_offset - temperature offset registers
The chip adds the offsets stored in these registers to
the corresponding temperature readings.
Note that temp1 and temp2 offsets share the same register,
they cannot both be different from zero at the same time.
Writing a non-zero number to one of them will reset the other
offset to zero.
All temperatures and offsets are read and written in
units of 0.001 degC.
temp[1-3]_alarm - alarm flags for temperature inputs, '1' in case of alarm,
'0' otherwise.
temp[2-3]_input_fault - diode fault flags for temperature inputs 2 and 3.
A fault is detected if the two pins for the corresponding
sensor are open or shorted, or any of the two is shorted
to ground or Vcc. '1' indicates a diode fault.
cpu0_vid - CPU voltage as received from the CPU
vrm - CPU VID standard used for decoding CPU voltage
The *_min, *_max, *_offset and vrm files can be read and
written, all others are read-only.
Documentation/hwmon/sysfs-interface
浏览文件 @ 62ed948c
......@@ -3,15 +3,15 @@ Naming and data format standards for sysfs files
The libsensors library offers an interface to the raw sensors data
through the sysfs interface. See libsensors documentation and source for
more further information. As of writing this document, libsensors
(from lm_sensors 2.8.3) is heavily chip-dependant. Adding or updating
further information. As of writing this document, libsensors
(from lm_sensors 2.8.3) is heavily chip-dependent. Adding or updating
support for any given chip requires modifying the library's code.
This is because libsensors was written for the procfs interface
older kernel modules were using, which wasn't standardized enough.
Recent versions of libsensors (from lm_sensors 2.8.2 and later) have
support for the sysfs interface, though.
The new sysfs interface was designed to be as chip-independant as
The new sysfs interface was designed to be as chip-independent as
possible.
Note that motherboards vary widely in the connections to sensor chips.
......@@ -24,7 +24,7 @@ range using external resistors. Since the values of these resistors
can change from motherboard to motherboard, the conversions cannot be
hard coded into the driver and have to be done in user space.
For this reason, even if we aim at a chip-independant libsensors, it will
For this reason, even if we aim at a chip-independent libsensors, it will
still require a configuration file (e.g. /etc/sensors.conf) for proper
values conversion, labeling of inputs and hiding of unused inputs.
......@@ -39,15 +39,16 @@ If you are developing a userspace application please send us feedback on
this standard.
Note that this standard isn't completely established yet, so it is subject
to changes, even important ones. One more reason to use the library instead
of accessing sysfs files directly.
to changes. If you are writing a new hardware monitoring driver those
features can't seem to fit in this interface, please contact us with your
extension proposal. Keep in mind that backward compatibility must be
preserved.
Each chip gets its own directory in the sysfs /sys/devices tree. To
find all sensor chips, it is easier to follow the symlinks from
/sys/i2c/devices/
find all sensor chips, it is easier to follow the device symlinks from
/sys/class/hwmon/hwmon*.
All sysfs values are fixed point numbers. To get the true value of some
of the values, you should divide by the specified value.
All sysfs values are fixed point numbers.
There is only one value per file, unlike the older /proc specification.
The common scheme for files naming is: <type><number>_<item>. Usual
......@@ -69,28 +70,40 @@ to cause an alarm) is chip-dependent.
-------------------------------------------------------------------------
[0-*] denotes any positive number starting from 0
[1-*] denotes any positive number starting from 1
RO read only value
RW read/write value
Read/write values may be read-only for some chips, depending on the
hardware implementation.
All entries are optional, and should only be created in a given driver
if the chip has the feature.
************
* Voltages *
************
in[0-8]_min Voltage min value.
in[0-*]_min Voltage min value.
Unit: millivolt
Read/Write
RW
in[0-8]_max Voltage max value.
in[0-*]_max Voltage max value.
Unit: millivolt
Read/Write
RW
in[0-8]_input Voltage input value.
in[0-*]_input Voltage input value.
Unit: millivolt
Read only
RO
Voltage measured on the chip pin.
Actual voltage depends on the scaling resistors on the
motherboard, as recommended in the chip datasheet.
This varies by chip and by motherboard.
Because of this variation, values are generally NOT scaled
by the chip driver, and must be done by the application.
However, some drivers (notably lm87 and via686a)
do scale, with various degrees of success.
do scale, because of internal resistors built into a chip.
These drivers will output the actual voltage.
Typical usage:
......@@ -104,58 +117,72 @@ in[0-8]_input Voltage input value.
in7_* varies
in8_* varies
cpu[0-1]_vid CPU core reference voltage.
cpu[0-*]_vid CPU core reference voltage.
Unit: millivolt
Read only.
RO
Not always correct.
vrm Voltage Regulator Module version number.
Read only.
Two digit number, first is major version, second is
minor version.
RW (but changing it should no more be necessary)
Originally the VRM standard version multiplied by 10, but now
an arbitrary number, as not all standards have a version
number.
Affects the way the driver calculates the CPU core reference
voltage from the vid pins.
Also see the Alarms section for status flags associated with voltages.
********
* Fans *
********
fan[1-3]_min Fan minimum value
fan[1-*]_min Fan minimum value
Unit: revolution/min (RPM)
Read/Write.
RW
fan[1-3]_input Fan input value.
fan[1-*]_input Fan input value.
Unit: revolution/min (RPM)
Read only.
RO
fan[1-3]_div Fan divisor.
fan[1-*]_div Fan divisor.
Integer value in powers of two (1, 2, 4, 8, 16, 32, 64, 128).
RW
Some chips only support values 1, 2, 4 and 8.
Note that this is actually an internal clock divisor, which
affects the measurable speed range, not the read value.
Also see the Alarms section for status flags associated with fans.
*******
* PWM *
*******
pwm[1-3] Pulse width modulation fan control.
pwm[1-*] Pulse width modulation fan control.
Integer value in the range 0 to 255
Read/Write
RW
255 is max or 100%.
pwm[1-3]_enable
pwm[1-*]_enable
Switch PWM on and off.
Not always present even if fan*_pwm is.
0 to turn off
1 to turn on in manual mode
2 to turn on in automatic mode
Read/Write
0: turn off
1: turn on in manual mode
2+: turn on in automatic mode
Check individual chip documentation files for automatic mode details.
RW
pwm[1-*]_mode
0: DC mode
1: PWM mode
RW
pwm[1-*]_auto_channels_temp
Select which temperature channels affect this PWM output in
auto mode. Bitfield, 1 is temp1, 2 is temp2, 4 is temp3 etc...
Which values are possible depend on the chip used.
RW
pwm[1-*]_auto_point[1-*]_pwm
pwm[1-*]_auto_point[1-*]_temp
......@@ -163,6 +190,7 @@ pwm[1-*]_auto_point[1-*]_temp_hyst
Define the PWM vs temperature curve. Number of trip points is
chip-dependent. Use this for chips which associate trip points
to PWM output channels.
RW
OR
......@@ -172,50 +200,57 @@ temp[1-*]_auto_point[1-*]_temp_hyst
Define the PWM vs temperature curve. Number of trip points is
chip-dependent. Use this for chips which associate trip points
to temperature channels.
RW
****************
* Temperatures *
****************
temp[1-3]_type Sensor type selection.
temp[1-*]_type Sensor type selection.
Integers 1 to 4 or thermistor Beta value (typically 3435)
Read/Write.
RW
1: PII/Celeron Diode
2: 3904 transistor
3: thermal diode
4: thermistor (default/unknown Beta)
Not all types are supported by all chips
temp[1-4]_max Temperature max value.
Unit: millidegree Celcius
Read/Write value.
temp[1-*]_max Temperature max value.
Unit: millidegree Celsius (or millivolt, see below)
RW
temp[1-3]_min Temperature min value.
Unit: millidegree Celcius
Read/Write value.
temp[1-*]_min Temperature min value.
Unit: millidegree Celsius
RW
temp[1-3]_max_hyst
temp[1-*]_max_hyst
Temperature hysteresis value for max limit.
Unit: millidegree Celcius
Unit: millidegree Celsius
Must be reported as an absolute temperature, NOT a delta
from the max value.
Read/Write value.
RW
temp[1-4]_input Temperature input value.
Unit: millidegree Celcius
Read only value.
temp[1-*]_input Temperature input value.
Unit: millidegree Celsius
RO
temp[1-4]_crit Temperature critical value, typically greater than
temp[1-*]_crit Temperature critical value, typically greater than
corresponding temp_max values.
Unit: millidegree Celcius
Read/Write value.
Unit: millidegree Celsius
RW
temp[1-2]_crit_hyst
temp[1-*]_crit_hyst
Temperature hysteresis value for critical limit.
Unit: millidegree Celcius
Unit: millidegree Celsius
Must be reported as an absolute temperature, NOT a delta
from the critical value.
RW
temp[1-4]_offset
Temperature offset which is added to the temperature reading
by the chip.
Unit: millidegree Celsius
Read/Write value.
If there are multiple temperature sensors, temp1_* is
......@@ -225,6 +260,17 @@ temp[1-2]_crit_hyst
itself, for example the thermal diode inside the CPU or
a thermistor nearby.
Some chips measure temperature using external thermistors and an ADC, and
report the temperature measurement as a voltage. Converting this voltage
back to a temperature (or the other way around for limits) requires
mathematical functions not available in the kernel, so the conversion
must occur in user space. For these chips, all temp* files described
above should contain values expressed in millivolt instead of millidegree
Celsius. In other words, such temperature channels are handled as voltage
channels by the driver.
Also see the Alarms section for status flags associated with temperatures.
************
* Currents *
......@@ -233,25 +279,88 @@ temp[1-2]_crit_hyst
Note that no known chip provides current measurements as of writing,
so this part is theoretical, so to say.
curr[1-n]_max Current max value
curr[1-*]_max Current max value
Unit: milliampere
Read/Write.
RW
curr[1-n]_min Current min value.
curr[1-*]_min Current min value.
Unit: milliampere
Read/Write.
RW
curr[1-n]_input Current input value
curr[1-*]_input Current input value
Unit: milliampere
Read only.
RO
*********
* Other *
*********
**********
* Alarms *
**********
Each channel or limit may have an associated alarm file, containing a
boolean value. 1 means than an alarm condition exists, 0 means no alarm.
Usually a given chip will either use channel-related alarms, or
limit-related alarms, not both. The driver should just reflect the hardware
implementation.
in[0-*]_alarm
fan[1-*]_alarm
temp[1-*]_alarm
Channel alarm
0: no alarm
1: alarm
RO
OR
in[0-*]_min_alarm
in[0-*]_max_alarm
fan[1-*]_min_alarm
temp[1-*]_min_alarm
temp[1-*]_max_alarm
temp[1-*]_crit_alarm
Limit alarm
0: no alarm
1: alarm
RO
Each input channel may have an associated fault file. This can be used
to notify open diodes, unconnected fans etc. where the hardware
supports it. When this boolean has value 1, the measurement for that
channel should not be trusted.
in[0-*]_input_fault
fan[1-*]_input_fault
temp[1-*]_input_fault
Input fault condition
0: no fault occured
1: fault condition
RO
Some chips also offer the possibility to get beeped when an alarm occurs:
beep_enable Master beep enable
0: no beeps
1: beeps
RW
in[0-*]_beep
fan[1-*]_beep
temp[1-*]_beep
Channel beep
0: disable
1: enable
RW
In theory, a chip could provide per-limit beep masking, but no such chip
was seen so far.
Old drivers provided a different, non-standard interface to alarms and
beeps. These interface files are deprecated, but will be kept around
for compatibility reasons:
alarms Alarm bitmask.
Read only.
RO
Integer representation of one to four bytes.
A '1' bit means an alarm.
Chips should be programmed for 'comparator' mode so that
......@@ -259,35 +368,26 @@ alarms Alarm bitmask.
if it is still valid.
Generally a direct representation of a chip's internal
alarm registers; there is no standard for the position
of individual bits.
of individual bits. For this reason, the use of this
interface file for new drivers is discouraged. Use
individual *_alarm and *_fault files instead.
Bits are defined in kernel/include/sensors.h.
alarms_in Alarm bitmask relative to in (voltage) channels
Read only
A '1' bit means an alarm, LSB corresponds to in0 and so on
Prefered to 'alarms' for newer chips
alarms_fan Alarm bitmask relative to fan channels
Read only
A '1' bit means an alarm, LSB corresponds to fan1 and so on
Prefered to 'alarms' for newer chips
alarms_temp Alarm bitmask relative to temp (temperature) channels
Read only
A '1' bit means an alarm, LSB corresponds to temp1 and so on
Prefered to 'alarms' for newer chips
beep_mask Bitmask for beep.
Same format as 'alarms' with the same bit locations,
use discouraged for the same reason. Use individual
*_beep files instead.
RW
beep_enable Beep/interrupt enable
0 to disable.
1 to enable.
Read/Write
beep_mask Bitmask for beep.
Same format as 'alarms' with the same bit locations.
Read/Write
*********
* Other *
*********
eeprom Raw EEPROM data in binary form.
Read only.
RO
pec Enable or disable PEC (SMBus only)
Read/Write
0: disable
1: enable
RW
Documentation/hwmon/userspace-tools
浏览文件 @ 62ed948c
......@@ -6,31 +6,32 @@ voltages, fans speed). They are often connected through an I2C bus, but some
are also connected directly through the ISA bus.
The kernel drivers make the data from the sensor chips available in the /sys
virtual filesystem. Userspace tools are then used to display or set or the
data in a more friendly manner.
virtual filesystem. Userspace tools are then used to display the measured
values or configure the chips in a more friendly manner.
Lm-sensors
----------
Core set of utilites that will allow you to obtain health information,
Core set of utilities that will allow you to obtain health information,
setup monitoring limits etc. You can get them on their homepage
http://www.lm-sensors.nu/ or as a package from your Linux distribution.
If from website:
Get lmsensors from project web site. Please note, you need only userspace
part, so compile with "make user_install" target.
Get lm-sensors from project web site. Please note, you need only userspace
part, so compile with "make user" and install with "make user_install".
General hints to get things working:
0) get lm-sensors userspace utils
1) compile all drivers in I2C section as modules in your kernel
1) compile all drivers in I2C and Hardware Monitoring sections as modules
in your kernel
2) run sensors-detect script, it will tell you what modules you need to load.
3) load them and run "sensors" command, you should see some results.
4) fix sensors.conf, labels, limits, fan divisors
5) if any more problems consult FAQ, or documentation
Other utilites
--------------
Other utilities
---------------
If you want some graphical indicators of system health look for applications
like: gkrellm, ksensors, xsensors, wmtemp, wmsensors, wmgtemp, ksysguardd,
......
Documentation/hwmon/w83791d 0 → 100644
浏览文件 @ 62ed948c
Kernel driver w83791d
=====================
Supported chips:
* Winbond W83791D
Prefix: 'w83791d'
Addresses scanned: I2C 0x2c - 0x2f
Datasheet: http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/W83791Da.pdf
Author: Charles Spirakis <bezaur@gmail.com>
This driver was derived from the w83781d.c and w83792d.c source files.
Credits:
w83781d.c:
Frodo Looijaard <frodol@dds.nl>,
Philip Edelbrock <phil@netroedge.com>,
and Mark Studebaker <mdsxyz123@yahoo.com>
w83792d.c:
Chunhao Huang <DZShen@Winbond.com.tw>,
Rudolf Marek <r.marek@sh.cvut.cz>
Module Parameters
-----------------
* init boolean
(default 0)
Use 'init=1' to have the driver do extra software initializations.
The default behavior is to do the minimum initialization possible
and depend on the BIOS to properly setup the chip. If you know you
have a w83791d and you're having problems, try init=1 before trying
reset=1.
* reset boolean
(default 0)
Use 'reset=1' to reset the chip (via index 0x40, bit 7). The default
behavior is no chip reset to preserve BIOS settings.
* force_subclients=bus,caddr,saddr,saddr
This is used to force the i2c addresses for subclients of
a certain chip. Example usage is `force_subclients=0,0x2f,0x4a,0x4b'
to force the subclients of chip 0x2f on bus 0 to i2c addresses
0x4a and 0x4b.
Description
-----------
This driver implements support for the Winbond W83791D chip.
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
currently selected). If you know the address of the chip, use a 'force'
parameter; this will put it into a more well-behaved state first.
The driver implements three temperature sensors, five fan rotation speed
sensors, and ten voltage sensors.
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 the Overtemperature Shutdown value; 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 for fan 1/2/3
and 1, 2, 4, 8, 16, 32, 64 or 128 for fan 4/5) to give the readings more
range or accuracy.
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
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
the beeping for some alarms.
The driver only reads the chip values each 3 seconds; reading them more
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 smart-fan control (still need appropriate motherboard/fans)
Documentation/i2c/busses/i2c-i801
浏览文件 @ 62ed948c
......@@ -21,8 +21,7 @@ Authors:
Module Parameters
-----------------
* force_addr: int
Forcibly enable the ICH at the given address. EXTREMELY DANGEROUS!
None.
Description
......
Documentation/i2c/busses/i2c-nforce2
浏览文件 @ 62ed948c
......@@ -7,6 +7,8 @@ Supported adapters:
* nForce3 250Gb MCP 10de:00E4
* nForce4 MCP 10de:0052
* nForce4 MCP-04 10de:0034
* nForce4 MCP51 10de:0264
* nForce4 MCP55 10de:0368
Datasheet: not publically available, but seems to be similar to the
AMD-8111 SMBus 2.0 adapter.
......
Documentation/i2c/busses/i2c-ocores 0 → 100644
浏览文件 @ 62ed948c
Kernel driver i2c-ocores
Supported adapters:
* OpenCores.org I2C controller by Richard Herveille (see datasheet link)
Datasheet: http://www.opencores.org/projects.cgi/web/i2c/overview
Author: Peter Korsgaard <jacmet@sunsite.dk>
Description
-----------
i2c-ocores is an i2c bus driver for the OpenCores.org I2C controller
IP core by Richard Herveille.
Usage
-----
i2c-ocores uses the platform bus, so you need to provide a struct
platform_device with the base address and interrupt number. The
dev.platform_data of the device should also point to a struct
ocores_i2c_platform_data (see linux/i2c-ocores.h) describing the
distance between registers and the input clock speed.
E.G. something like:
static struct resource ocores_resources[] = {
[0] = {
.start = MYI2C_BASEADDR,
.end = MYI2C_BASEADDR + 8,
.flags = IORESOURCE_MEM,
},
[1] = {
.start = MYI2C_IRQ,
.end = MYI2C_IRQ,
.flags = IORESOURCE_IRQ,
},
};
static struct ocores_i2c_platform_data myi2c_data = {
.regstep = 2, /* two bytes between registers */
.clock_khz = 50000, /* input clock of 50MHz */
};
static struct platform_device myi2c = {
.name = "ocores-i2c",
.dev = {
.platform_data = &myi2c_data,
},
.num_resources = ARRAY_SIZE(ocores_resources),
.resource = ocores_resources,
};
Documentation/i2c/busses/i2c-piix4
浏览文件 @ 62ed948c
......@@ -6,6 +6,8 @@ Supported adapters:
Datasheet: Publicly available at the Intel website
* ServerWorks OSB4, CSB5, CSB6 and HT-1000 southbridges
Datasheet: Only available via NDA from ServerWorks
* ATI IXP southbridges IXP200, IXP300, IXP400
Datasheet: Not publicly available
* Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge
Datasheet: Publicly available at the SMSC website http://www.smsc.com
......@@ -21,8 +23,6 @@ Module Parameters
Forcibly enable the PIIX4. DANGEROUS!
* force_addr: int
Forcibly enable the PIIX4 at the given address. EXTREMELY DANGEROUS!
* fix_hstcfg: int
Fix config register. Needed on some boards (Force CPCI735).
Description
......@@ -63,10 +63,36 @@ The PIIX4E is just an new version of the PIIX4; it is supported as well.
The PIIX/PIIX3 does not implement an SMBus or I2C bus, so you can't use
this driver on those mainboards.
The ServerWorks Southbridges, the Intel 440MX, and the Victory766 are
The ServerWorks Southbridges, the Intel 440MX, and the Victory66 are
identical to the PIIX4 in I2C/SMBus support.
A few OSB4 southbridges are known to be misconfigured by the BIOS. In this
case, you have you use the fix_hstcfg module parameter. Do not use it
unless you know you have to, because in some cases it also breaks
configuration on southbridges that don't need it.
If you own Force CPCI735 motherboard or other OSB4 based systems you may need
to change the SMBus Interrupt Select register so the SMBus controller uses
the SMI mode.
1) Use lspci command and locate the PCI device with the SMBus controller:
00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 4f)
The line may vary for different chipsets. Please consult the driver source
for all possible PCI ids (and lspci -n to match them). Lets assume the
device is located at 00:0f.0.
2) Now you just need to change the value in 0xD2 register. Get it first with
command: lspci -xxx -s 00:0f.0
If the value is 0x3 then you need to change it to 0x1
setpci -s 00:0f.0 d2.b=1
Please note that you don't need to do that in all cases, just when the SMBus is
not working properly.
Hardware-specific issues
------------------------
This driver will refuse to load on IBM systems with an Intel PIIX4 SMBus.
Some of these machines have an RFID EEPROM (24RF08) connected to the SMBus,
which can easily get corrupted due to a state machine bug. These are mostly
Thinkpad laptops, but desktop systems may also be affected. We have no list
of all affected systems, so the only safe solution was to prevent access to
the SMBus on all IBM systems (detected using DMI data.)
For additional information, read:
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/README.thinkpad
Documentation/i2c/busses/scx200_acb
浏览文件 @ 62ed948c
......@@ -2,14 +2,31 @@ Kernel driver scx200_acb
Author: Christer Weinigel <wingel@nano-system.com>
The driver supersedes the older, never merged driver named i2c-nscacb.
Module Parameters
-----------------
* base: int
* base: up to 4 ints
Base addresses for the ACCESS.bus controllers on SCx200 and SC1100 devices
By default the driver uses two base addresses 0x820 and 0x840.
If you want only one base address, specify the second as 0 so as to
override this default.
Description
-----------
Enable the use of the ACCESS.bus controller on the Geode SCx200 and
SC1100 processors and the CS5535 and CS5536 Geode companion devices.
Device-specific notes
---------------------
The SC1100 WRAP boards are known to use base addresses 0x810 and 0x820.
If the scx200_acb driver is built into the kernel, add the following
parameter to your boot command line:
scx200_acb.base=0x810,0x820
If the scx200_acb driver is built as a module, add the following line to
the file /etc/modprobe.conf instead:
options scx200_acb base=0x810,0x820
Documentation/ia64/aliasing.txt 0 → 100644
浏览文件 @ 62ed948c
MEMORY ATTRIBUTE ALIASING ON IA-64
Bjorn Helgaas
<bjorn.helgaas@hp.com>
May 4, 2006
MEMORY ATTRIBUTES
Itanium supports several attributes for virtual memory references.
The attribute is part of the virtual translation, i.e., it is
contained in the TLB entry. The ones of most interest to the Linux
kernel are:
WB Write-back (cacheable)
UC Uncacheable
WC Write-coalescing
System memory typically uses the WB attribute. The UC attribute is
used for memory-mapped I/O devices. The WC attribute is uncacheable
like UC is, but writes may be delayed and combined to increase
performance for things like frame buffers.
The Itanium architecture requires that we avoid accessing the same
page with both a cacheable mapping and an uncacheable mapping[1].
The design of the chipset determines which attributes are supported
on which regions of the address space. For example, some chipsets
support either WB or UC access to main memory, while others support
only WB access.
MEMORY MAP
Platform firmware describes the physical memory map and the
supported attributes for each region. At boot-time, the kernel uses
the EFI GetMemoryMap() interface. ACPI can also describe memory
devices and the attributes they support, but Linux/ia64 currently
doesn't use this information.
The kernel uses the efi_memmap table returned from GetMemoryMap() to
learn the attributes supported by each region of physical address
space. Unfortunately, this table does not completely describe the
address space because some machines omit some or all of the MMIO
regions from the map.
The kernel maintains another table, kern_memmap, which describes the
memory Linux is actually using and the attribute for each region.
This contains only system memory; it does not contain MMIO space.
The kern_memmap table typically contains only a subset of the system
memory described by the efi_memmap. Linux/ia64 can't use all memory
in the system because of constraints imposed by the identity mapping
scheme.
The efi_memmap table is preserved unmodified because the original
boot-time information is required for kexec.
KERNEL IDENTITY MAPPINGS
Linux/ia64 identity mappings are done with large pages, currently
either 16MB or 64MB, referred to as "granules." Cacheable mappings
are speculative[2], so the processor can read any location in the
page at any time, independent of the programmer's intentions. This
means that to avoid attribute aliasing, Linux can create a cacheable
identity mapping only when the entire granule supports cacheable
access.
Therefore, kern_memmap contains only full granule-sized regions that
can referenced safely by an identity mapping.
Uncacheable mappings are not speculative, so the processor will
generate UC accesses only to locations explicitly referenced by
software. This allows UC identity mappings to cover granules that
are only partially populated, or populated with a combination of UC
and WB regions.
USER MAPPINGS
User mappings are typically done with 16K or 64K pages. The smaller
page size allows more flexibility because only 16K or 64K has to be
homogeneous with respect to memory attributes.
POTENTIAL ATTRIBUTE ALIASING CASES
There are several ways the kernel creates new mappings:
mmap of /dev/mem
This uses remap_pfn_range(), which creates user mappings. These
mappings may be either WB or UC. If the region being mapped
happens to be in kern_memmap, meaning that it may also be mapped
by a kernel identity mapping, the user mapping must use the same
attribute as the kernel mapping.
If the region is not in kern_memmap, the user mapping should use
an attribute reported as being supported in the EFI memory map.
Since the EFI memory map does not describe MMIO on some
machines, this should use an uncacheable mapping as a fallback.
mmap of /sys/class/pci_bus/.../legacy_mem
This is very similar to mmap of /dev/mem, except that legacy_mem
only allows mmap of the one megabyte "legacy MMIO" area for a
specific PCI bus. Typically this is the first megabyte of
physical address space, but it may be different on machines with
several VGA devices.
"X" uses this to access VGA frame buffers. Using legacy_mem
rather than /dev/mem allows multiple instances of X to talk to
different VGA cards.
The /dev/mem mmap constraints apply.
However, since this is for mapping legacy MMIO space, WB access
does not make sense. This matters on machines without legacy
VGA support: these machines may have WB memory for the entire
first megabyte (or even the entire first granule).
On these machines, we could mmap legacy_mem as WB, which would
be safe in terms of attribute aliasing, but X has no way of
knowing that it is accessing regular memory, not a frame buffer,
so the kernel should fail the mmap rather than doing it with WB.
read/write of /dev/mem
This uses copy_from_user(), which implicitly uses a kernel
identity mapping. This is obviously safe for things in
kern_memmap.
There may be corner cases of things that are not in kern_memmap,
but could be accessed this way. For example, registers in MMIO
space are not in kern_memmap, but could be accessed with a UC
mapping. This would not cause attribute aliasing. But
registers typically can be accessed only with four-byte or
eight-byte accesses, and the copy_from_user() path doesn't allow
any control over the access size, so this would be dangerous.
ioremap()
This returns a kernel identity mapping for use inside the
kernel.
If the region is in kern_memmap, we should use the attribute
specified there. Otherwise, if the EFI memory map reports that
the entire granule supports WB, we should use that (granules
that are partially reserved or occupied by firmware do not appear
in kern_memmap). Otherwise, we should use a UC mapping.
PAST PROBLEM CASES
mmap of various MMIO regions from /dev/mem by "X" on Intel platforms
The EFI memory map may not report these MMIO regions.
These must be allowed so that X will work. This means that
when the EFI memory map is incomplete, every /dev/mem mmap must
succeed. It may create either WB or UC user mappings, depending
on whether the region is in kern_memmap or the EFI memory map.
mmap of 0x0-0xA0000 /dev/mem by "hwinfo" on HP sx1000 with VGA enabled
See https://bugzilla.novell.com/show_bug.cgi?id=140858.
The EFI memory map reports the following attributes:
0x00000-0x9FFFF WB only
0xA0000-0xBFFFF UC only (VGA frame buffer)
0xC0000-0xFFFFF WB only
This mmap is done with user pages, not kernel identity mappings,
so it is safe to use WB mappings.
The kernel VGA driver may ioremap the VGA frame buffer at 0xA0000,
which will use a granule-sized UC mapping covering 0-0xFFFFF. This
granule covers some WB-only memory, but since UC is non-speculative,
the processor will never generate an uncacheable reference to the
WB-only areas unless the driver explicitly touches them.
mmap of 0x0-0xFFFFF legacy_mem by "X"
If the EFI memory map reports this entire range as WB, there
is no VGA MMIO hole, and the mmap should fail or be done with
a WB mapping.
There's no easy way for X to determine whether the 0xA0000-0xBFFFF
region is a frame buffer or just memory, so I think it's best to
just fail this mmap request rather than using a WB mapping. As
far as I know, there's no need to map legacy_mem with WB
mappings.
Otherwise, a UC mapping of the entire region is probably safe.
The VGA hole means the region will not be in kern_memmap. The
HP sx1000 chipset doesn't support UC access to the memory surrounding
the VGA hole, but X doesn't need that area anyway and should not
reference it.
mmap of 0xA0000-0xBFFFF legacy_mem by "X" on HP sx1000 with VGA disabled
The EFI memory map reports the following attributes:
0x00000-0xFFFFF WB only (no VGA MMIO hole)
This is a special case of the previous case, and the mmap should
fail for the same reason as above.
NOTES
[1] SDM rev 2.2, vol 2, sec 4.4.1.
[2] SDM rev 2.2, vol 2, sec 4.4.6.
Documentation/ioctl-number.txt
浏览文件 @ 62ed948c
......@@ -85,7 +85,9 @@ Code Seq# Include File Comments
<mailto:maassen@uni-freiburg.de>
'C' all linux/soundcard.h
'D' all asm-s390/dasd.h
'E' all linux/input.h
'F' all linux/fb.h
'H' all linux/hiddev.h
'I' all linux/isdn.h
'J' 00-1F drivers/scsi/gdth_ioctl.h
'K' all linux/kd.h
......
Documentation/isdn/README.gigaset
浏览文件 @ 62ed948c
......@@ -124,7 +124,8 @@ GigaSet 307x Device Driver
You can use some configuration tool of your distribution to configure this
"modem" or configure pppd/wvdial manually. There are some example ppp
configuration files and chat scripts in the gigaset-VERSION/ppp directory.
configuration files and chat scripts in the gigaset-VERSION/ppp directory
in the driver packages from http://sourceforge.net/projects/gigaset307x/.
Please note that the USB drivers are not able to change the state of the
control lines (the M105 driver can be configured to use some undocumented
control requests, if you really need the control lines, though). This means
......@@ -164,8 +165,8 @@ GigaSet 307x Device Driver
If you want both of these at once, you are out of luck.
You can also use /sys/module/<name>/parameters/cidmode for changing
the CID mode setting (<name> is usb_gigaset or bas_gigaset).
You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode
setting (ttyGxy is ttyGU0 or ttyGB0).
3. Troubleshooting
......
Documentation/kdump/kdump.txt
浏览文件 @ 62ed948c
Documentation for kdump - the kexec-based crash dumping solution
================================================================
Documentation for Kdump - The kexec-based Crash Dumping Solution
================================================================
DESIGN
======
This document includes overview, setup and installation, and analysis
information.
Kdump uses kexec to reboot to a second kernel whenever a dump needs to be
taken. This second kernel is booted with very little memory. The first kernel
reserves the section of memory that the second kernel uses. This ensures that
on-going DMA from the first kernel does not corrupt the second kernel.
Overview
========
All the necessary information about Core image is encoded in ELF format and
stored in reserved area of memory before crash. Physical address of start of
ELF header is passed to new kernel through command line parameter elfcorehdr=.
Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
dump of the system kernel's memory needs to be taken (for example, when
the system panics). The system kernel's memory image is preserved across
the reboot and is accessible to the dump-capture kernel.
On i386, the first 640 KB of physical memory is needed to boot, irrespective
of where the kernel loads. Hence, this region is backed up by kexec just before
rebooting into the new kernel.
You can use common Linux commands, such as cp and scp, to copy the
memory image to a dump file on the local disk, or across the network to
a remote system.
In the second kernel, "old memory" can be accessed in two ways.
Kdump and kexec are currently supported on the x86, x86_64, and ppc64
architectures.
- The first one is through a /dev/oldmem device interface. A capture utility
can read the device file and write out the memory in raw format. This is raw
dump of memory and analysis/capture tool should be intelligent enough to
determine where to look for the right information. ELF headers (elfcorehdr=)
can become handy here.
When the system kernel boots, it reserves a small section of memory for
the dump-capture kernel. This ensures that ongoing Direct Memory Access
(DMA) from the system kernel does not corrupt the dump-capture kernel.
The kexec -p command loads the dump-capture kernel into this reserved
memory.
- The second interface is through /proc/vmcore. This exports the dump as an ELF
format file which can be written out using any file copy command
(cp, scp, etc). Further, gdb can be used to perform limited debugging on
the dump file. This method ensures methods ensure that there is correct
ordering of the dump pages (corresponding to the first 640 KB that has been
relocated).
On x86 machines, the first 640 KB of physical memory is needed to boot,
regardless of where the kernel loads. Therefore, kexec backs up this
region just before rebooting into the dump-capture kernel.
SETUP
=====
All of the necessary information about the system kernel's core image is
encoded in the ELF format, and stored in a reserved area of memory
before a crash. The physical address of the start of the ELF header is
passed to the dump-capture kernel through the elfcorehdr= boot
parameter.
With the dump-capture kernel, you can access the memory image, or "old
memory," in two ways:
- Through a /dev/oldmem device interface. A capture utility can read the
device file and write out the memory in raw format. This is a raw dump
of memory. Analysis and capture tools must be intelligent enough to
determine where to look for the right information.
- Through /proc/vmcore. This exports the dump as an ELF-format file that
you can write out using file copy commands such as cp or scp. Further,
you can use analysis tools such as the GNU Debugger (GDB) and the Crash
tool to debug the dump file. This method ensures that the dump pages are
correctly ordered.
Setup and Installation
======================
Install kexec-tools and the Kdump patch
---------------------------------------
1) Login as the root user.
2) Download the kexec-tools user-space package from the following URL:
http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz
3) Unpack the tarball with the tar command, as follows:
tar xvpzf kexec-tools-1.101.tar.gz
4) Download the latest consolidated Kdump patch from the following URL:
http://lse.sourceforge.net/kdump/
(This location is being used until all the user-space Kdump patches
are integrated with the kexec-tools package.)
5) Change to the kexec-tools-1.101 directory, as follows:
cd kexec-tools-1.101
6) Apply the consolidated patch to the kexec-tools-1.101 source tree
with the patch command, as follows. (Modify the path to the downloaded
patch as necessary.)
patch -p1 < /path-to-kdump-patch/kexec-tools-1.101-kdump.patch
7) Configure the package, as follows:
./configure
8) Compile the package, as follows:
make
9) Install the package, as follows:
make install
Download and build the system and dump-capture kernels
------------------------------------------------------
Download the mainline (vanilla) kernel source code (2.6.13-rc1 or newer)
from http://www.kernel.org. Two kernels must be built: a system kernel
and a dump-capture kernel. Use the following steps to configure these
kernels with the necessary kexec and Kdump features:
System kernel
-------------
1) Enable "kexec system call" in "Processor type and features."
CONFIG_KEXEC=y
2) Enable "sysfs file system support" in "Filesystem" -> "Pseudo
filesystems." This is usually enabled by default.
CONFIG_SYSFS=y
Note that "sysfs file system support" might not appear in the "Pseudo
filesystems" menu if "Configure standard kernel features (for small
systems)" is not enabled in "General Setup." In this case, check the
.config file itself to ensure that sysfs is turned on, as follows:
grep 'CONFIG_SYSFS' .config
3) Enable "Compile the kernel with debug info" in "Kernel hacking."
CONFIG_DEBUG_INFO=Y
This causes the kernel to be built with debug symbols. The dump
analysis tools require a vmlinux with debug symbols in order to read
and analyze a dump file.
4) Make and install the kernel and its modules. Update the boot loader
(such as grub, yaboot, or lilo) configuration files as necessary.
5) Boot the system kernel with the boot parameter "crashkernel=Y@X",
where Y specifies how much memory to reserve for the dump-capture kernel
and X specifies the beginning of this reserved memory. For example,
"crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
starting at physical address 0x01000000 for the dump-capture kernel.
On x86 and x86_64, use "crashkernel=64M@16M".
On ppc64, use "crashkernel=128M@32M".
The dump-capture kernel
-----------------------
1) Download the upstream kexec-tools userspace package from
http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz.
Apply the latest consolidated kdump patch on top of kexec-tools-1.101
from http://lse.sourceforge.net/kdump/. This arrangment has been made
till all the userspace patches supporting kdump are integrated with
upstream kexec-tools userspace.
2) Download and build the appropriate (2.6.13-rc1 onwards) vanilla kernels.
Two kernels need to be built in order to get this feature working.
Following are the steps to properly configure the two kernels specific
to kexec and kdump features:
A) First kernel or regular kernel:
----------------------------------
a) Enable "kexec system call" feature (in Processor type and features).
CONFIG_KEXEC=y
b) Enable "sysfs file system support" (in Pseudo filesystems).
CONFIG_SYSFS=y
c) make
d) Boot into first kernel with the command line parameter "crashkernel=Y@X".
Use appropriate values for X and Y. Y denotes how much memory to reserve
for the second kernel, and X denotes at what physical address the
reserved memory section starts. For example: "crashkernel=64M@16M".
B) Second kernel or dump capture kernel:
---------------------------------------
a) For i386 architecture enable Highmem support
CONFIG_HIGHMEM=y
b) Enable "kernel crash dumps" feature (under "Processor type and features")
CONFIG_CRASH_DUMP=y
c) Make sure a suitable value for "Physical address where the kernel is
loaded" (under "Processor type and features"). By default this value
is 0x1000000 (16MB) and it should be same as X (See option d above),
e.g., 16 MB or 0x1000000.
CONFIG_PHYSICAL_START=0x1000000
d) Enable "/proc/vmcore support" (Optional, under "Pseudo filesystems").
CONFIG_PROC_VMCORE=y
3) After booting to regular kernel or first kernel, load the second kernel
using the following command:
kexec -p <second-kernel> --args-linux --elf32-core-headers
--append="root=<root-dev> init 1 irqpoll maxcpus=1"
Notes:
======
i) <second-kernel> has to be a vmlinux image ie uncompressed elf image.
bzImage will not work, as of now.
ii) --args-linux has to be speicfied as if kexec it loading an elf image,
it needs to know that the arguments supplied are of linux type.
iii) By default ELF headers are stored in ELF64 format to support systems
with more than 4GB memory. Option --elf32-core-headers forces generation
of ELF32 headers. The reason for this option being, as of now gdb can
not open vmcore file with ELF64 headers on a 32 bit systems. So ELF32
headers can be used if one has non-PAE systems and hence memory less
than 4GB.
iv) Specify "irqpoll" as command line parameter. This reduces driver
initialization failures in second kernel due to shared interrupts.
v) <root-dev> needs to be specified in a format corresponding to the root
device name in the output of mount command.
vi) If you have built the drivers required to mount root file system as
modules in <second-kernel>, then, specify
--initrd=<initrd-for-second-kernel>.
vii) Specify maxcpus=1 as, if during first kernel run, if panic happens on
non-boot cpus, second kernel doesn't seem to be boot up all the cpus.
The other option is to always built the second kernel without SMP
support ie CONFIG_SMP=n
4) After successfully loading the second kernel as above, if a panic occurs
system reboots into the second kernel. A module can be written to force
the panic or "ALT-SysRq-c" can be used initiate a crash dump for testing
purposes.
5) Once the second kernel has booted, write out the dump file using
1) Under "General setup," append "-kdump" to the current string in
"Local version."
2) On x86, enable high memory support under "Processor type and
features":
CONFIG_HIGHMEM64G=y
or
CONFIG_HIGHMEM4G
3) On x86 and x86_64, disable symmetric multi-processing support
under "Processor type and features":
CONFIG_SMP=n
(If CONFIG_SMP=y, then specify maxcpus=1 on the kernel command line
when loading the dump-capture kernel, see section "Load the Dump-capture
Kernel".)
4) On ppc64, disable NUMA support and enable EMBEDDED support:
CONFIG_NUMA=n
CONFIG_EMBEDDED=y
CONFIG_EEH=N for the dump-capture kernel
5) Enable "kernel crash dumps" support under "Processor type and
features":
CONFIG_CRASH_DUMP=y
6) Use a suitable value for "Physical address where the kernel is
loaded" (under "Processor type and features"). This only appears when
"kernel crash dumps" is enabled. By default this value is 0x1000000
(16MB). It should be the same as X in the "crashkernel=Y@X" boot
parameter discussed above.
On x86 and x86_64, use "CONFIG_PHYSICAL_START=0x1000000".
On ppc64 the value is automatically set at 32MB when
CONFIG_CRASH_DUMP is set.
6) Optionally enable "/proc/vmcore support" under "Filesystems" ->
"Pseudo filesystems".
CONFIG_PROC_VMCORE=y
(CONFIG_PROC_VMCORE is set by default when CONFIG_CRASH_DUMP is selected.)
7) Make and install the kernel and its modules. DO NOT add this kernel
to the boot loader configuration files.
Load the Dump-capture Kernel
============================
After booting to the system kernel, load the dump-capture kernel using
the following command:
kexec -p <dump-capture-kernel> \
--initrd=<initrd-for-dump-capture-kernel> --args-linux \
--append="root=<root-dev> init 1 irqpoll"
Notes on loading the dump-capture kernel:
* <dump-capture-kernel> must be a vmlinux image (that is, an
uncompressed ELF image). bzImage does not work at this time.
* By default, the ELF headers are stored in ELF64 format to support
systems with more than 4GB memory. The --elf32-core-headers option can
be used to force the generation of ELF32 headers. This is necessary
because GDB currently cannot open vmcore files with ELF64 headers on
32-bit systems. ELF32 headers can be used on non-PAE systems (that is,
less than 4GB of memory).
* The "irqpoll" boot parameter reduces driver initialization failures
due to shared interrupts in the dump-capture kernel.
* You must specify <root-dev> in the format corresponding to the root
device name in the output of mount command.
* "init 1" boots the dump-capture kernel into single-user mode without
networking. If you want networking, use "init 3."
Kernel Panic
============
After successfully loading the dump-capture kernel as previously
described, the system will reboot into the dump-capture kernel if a
system crash is triggered. Trigger points are located in panic(),
die(), die_nmi() and in the sysrq handler (ALT-SysRq-c).
The following conditions will execute a crash trigger point:
If a hard lockup is detected and "NMI watchdog" is configured, the system
will boot into the dump-capture kernel ( die_nmi() ).
If die() is called, and it happens to be a thread with pid 0 or 1, or die()
is called inside interrupt context or die() is called and panic_on_oops is set,
the system will boot into the dump-capture kernel.
On powererpc systems when a soft-reset is generated, die() is called by all cpus and the system system will boot into the dump-capture kernel.
For testing purposes, you can trigger a crash by using "ALT-SysRq-c",
"echo c > /proc/sysrq-trigger or write a module to force the panic.
Write Out the Dump File
=======================
After the dump-capture kernel is booted, write out the dump file with
the following command:
cp /proc/vmcore <dump-file>
Dump memory can also be accessed as a /dev/oldmem device for a linear/raw
view. To create the device, type:
You can also access dumped memory as a /dev/oldmem device for a linear
and raw view. To create the device, use the following command:
mknod /dev/oldmem c 1 12
mknod /dev/oldmem c 1 12
Use "dd" with suitable options for count, bs and skip to access specific
portions of the dump.
Use the dd command with suitable options for count, bs, and skip to
access specific portions of the dump.
Entire memory: dd if=/dev/oldmem of=oldmem.001
To see the entire memory, use the following command:
dd if=/dev/oldmem of=oldmem.001
ANALYSIS
Analysis
========
Limited analysis can be done using gdb on the dump file copied out of
/proc/vmcore. Use vmlinux built with -g and run
gdb vmlinux <dump-file>
Before analyzing the dump image, you should reboot into a stable kernel.
You can do limited analysis using GDB on the dump file copied out of
/proc/vmcore. Use the debug vmlinux built with -g and run the following
command:
gdb vmlinux <dump-file>
Stack trace for the task on processor 0, register display, memory display
work fine.
Stack trace for the task on processor 0, register display, and memory
display work fine.
Note: gdb cannot analyse core files generated in ELF64 format for i386.
Note: GDB cannot analyze core files generated in ELF64 format for x86.
On systems with a maximum of 4GB of memory, you can generate
ELF32-format headers using the --elf32-core-headers kernel option on the
dump kernel.
Latest "crash" (crash-4.0-2.18) as available on Dave Anderson's site
http://people.redhat.com/~anderson/ works well with kdump format.
You can also use the Crash utility to analyze dump files in Kdump
format. Crash is available on Dave Anderson's site at the following URL:
http://people.redhat.com/~anderson/
To Do
=====
TODO
====
1) Provide a kernel pages filtering mechanism so that core file size is not
insane on systems having huge memory banks.
2) Relocatable kernel can help in maintaining multiple kernels for crashdump
and same kernel as the first kernel can be used to capture the dump.
1) Provide a kernel pages filtering mechanism, so core file size is not
extreme on systems with huge memory banks.
2) Relocatable kernel can help in maintaining multiple kernels for
crash_dump, and the same kernel as the system kernel can be used to
capture the dump.
CONTACT
Contact
=======
Vivek Goyal (vgoyal@in.ibm.com)
Maneesh Soni (maneesh@in.ibm.com)
Trademark
=========
Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.
Documentation/kernel-parameters.txt
浏览文件 @ 62ed948c
......@@ -147,6 +147,9 @@ running once the system is up.
acpi_irq_isa= [HW,ACPI] If irq_balance, mark listed IRQs used by ISA
Format: <irq>,<irq>...
acpi_os_name= [HW,ACPI] Tell ACPI BIOS the name of the OS
Format: To spoof as Windows 98: ="Microsoft Windows"
acpi_osi= [HW,ACPI] empty param disables _OSI
acpi_serialize [HW,ACPI] force serialization of AML methods
......
Documentation/keys.txt
浏览文件 @ 62ed948c
......@@ -19,6 +19,7 @@ This document has the following sections:
- Key overview
- Key service overview
- Key access permissions
- SELinux support
- New procfs files
- Userspace system call interface
- Kernel services
......@@ -232,6 +233,34 @@ For changing the ownership, group ID or permissions mask, being the owner of
the key or having the sysadmin capability is sufficient.
===============
SELINUX SUPPORT
===============
The security class "key" has been added to SELinux so that mandatory access
controls can be applied to keys created within various contexts. This support
is preliminary, and is likely to change quite significantly in the near future.
Currently, all of the basic permissions explained above are provided in SELinux
as well; SE Linux is simply invoked after all basic permission checks have been
performed.
Each key is labeled with the same context as the task to which it belongs.
Typically, this is the same task that was running when the key was created.
The default keyrings are handled differently, but in a way that is very
intuitive:
(*) The user and user session keyrings that are created when the user logs in
are currently labeled with the context of the login manager.
(*) The keyrings associated with new threads are each labeled with the context
of their associated thread, and both session and process keyrings are
handled similarly.
Note, however, that the default keyrings associated with the root user are
labeled with the default kernel context, since they are created early in the
boot process, before root has a chance to log in.
================
NEW PROCFS FILES
================
......@@ -935,6 +964,16 @@ The structure has a number of fields, some of which are mandatory:
It is not safe to sleep in this method; the caller may hold spinlocks.
(*) void (*revoke)(struct key *key);
This method is optional. It is called to discard part of the payload
data upon a key being revoked. The caller will have the key semaphore
write-locked.
It is safe to sleep in this method, though care should be taken to avoid
a deadlock against the key semaphore.
(*) void (*destroy)(struct key *key);
This method is optional. It is called to discard the payload data on a key
......
Documentation/memory-barriers.txt
浏览文件 @ 62ed948c
......@@ -262,9 +262,14 @@ What is required is some way of intervening to instruct the compiler and the
CPU to restrict the order.
Memory barriers are such interventions. They impose a perceived partial
ordering between the memory operations specified on either side of the barrier.
They request that the sequence of memory events generated appears to other
parts of the system as if the barrier is effective on that CPU.
ordering over the memory operations on either side of the barrier.
Such enforcement is important because the CPUs and other devices in a system
can use a variety of tricks to improve performance - including reordering,
deferral and combination of memory operations; speculative loads; speculative
branch prediction and various types of caching. Memory barriers are used to
override or suppress these tricks, allowing the code to sanely control the
interaction of multiple CPUs and/or devices.
VARIETIES OF MEMORY BARRIER
......@@ -282,7 +287,7 @@ Memory barriers come in four basic varieties:
A write barrier is a partial ordering on stores only; it is not required
to have any effect on loads.
A CPU can be viewed as as commiting a sequence of store operations to the
A CPU can be viewed as committing a sequence of store operations to the
memory system as time progresses. All stores before a write barrier will
occur in the sequence _before_ all the stores after the write barrier.
......@@ -413,7 +418,7 @@ There are certain things that the Linux kernel memory barriers do not guarantee:
indirect effect will be the order in which the second CPU sees the effects
of the first CPU's accesses occur, but see the next point:
(*) There is no guarantee that the a CPU will see the correct order of effects
(*) There is no guarantee that a CPU will see the correct order of effects
from a second CPU's accesses, even _if_ the second CPU uses a memory
barrier, unless the first CPU _also_ uses a matching memory barrier (see
the subsection on "SMP Barrier Pairing").
......@@ -461,8 +466,8 @@ Whilst this may seem like a failure of coherency or causality maintenance, it
isn't, and this behaviour can be observed on certain real CPUs (such as the DEC
Alpha).
To deal with this, a data dependency barrier must be inserted between the
address load and the data load:
To deal with this, a data dependency barrier or better must be inserted
between the address load and the data load:
CPU 1 CPU 2
=============== ===============
......@@ -484,7 +489,7 @@ lines. The pointer P might be stored in an odd-numbered cache line, and the
variable B might be stored in an even-numbered cache line. Then, if the
even-numbered bank of the reading CPU's cache is extremely busy while the
odd-numbered bank is idle, one can see the new value of the pointer P (&B),
but the old value of the variable B (1).
but the old value of the variable B (2).
Another example of where data dependency barriers might by required is where a
......@@ -744,7 +749,7 @@ some effectively random order, despite the write barrier issued by CPU 1:
: :
If, however, a read barrier were to be placed between the load of E and the
If, however, a read barrier were to be placed between the load of B and the
load of A on CPU 2:
CPU 1 CPU 2
......@@ -1461,9 +1466,8 @@ instruction itself is complete.
On a UP system - where this wouldn't be a problem - the smp_mb() is just a
compiler barrier, thus making sure the compiler emits the instructions in the
right order without actually intervening in the CPU. Since there there's only
one CPU, that CPU's dependency ordering logic will take care of everything
else.
right order without actually intervening in the CPU. Since there's only one
CPU, that CPU's dependency ordering logic will take care of everything else.
ATOMIC OPERATIONS
......@@ -1640,9 +1644,9 @@ functions:
The PCI bus, amongst others, defines an I/O space concept - which on such
CPUs as i386 and x86_64 cpus readily maps to the CPU's concept of I/O
space. However, it may also mapped as a virtual I/O space in the CPU's
memory map, particularly on those CPUs that don't support alternate
I/O spaces.
space. However, it may also be mapped as a virtual I/O space in the CPU's
memory map, particularly on those CPUs that don't support alternate I/O
spaces.
Accesses to this space may be fully synchronous (as on i386), but
intermediary bridges (such as the PCI host bridge) may not fully honour
......
Documentation/networking/tuntap.txt
浏览文件 @ 62ed948c
......@@ -39,10 +39,13 @@ Copyright (C) 1999-2000 Maxim Krasnyansky <max_mk@yahoo.com>
mknod /dev/net/tun c 10 200
Set permissions:
e.g. chmod 0700 /dev/net/tun
if you want the device only accessible by root. Giving regular users the
right to assign network devices is NOT a good idea. Users could assign
bogus network interfaces to trick firewalls or administrators.
e.g. chmod 0666 /dev/net/tun
There's no harm in allowing the device to be accessible by non-root users,
since CAP_NET_ADMIN is required for creating network devices or for
connecting to network devices which aren't owned by the user in question.
If you want to create persistent devices and give ownership of them to
unprivileged users, then you need the /dev/net/tun device to be usable by
those users.
Driver module autoloading
......
Documentation/pci.txt
浏览文件 @ 62ed948c
......@@ -213,9 +213,17 @@ have been remapped by the kernel.
See Documentation/IO-mapping.txt for how to access device memory.
You still need to call request_region() for I/O regions and
request_mem_region() for memory regions to make sure nobody else is using the
same device.
The device driver needs to call pci_request_region() to make sure
no other device is already using the same resource. The driver is expected
to determine MMIO and IO Port resource availability _before_ calling
pci_enable_device(). Conversely, drivers should call pci_release_region()
_after_ calling pci_disable_device(). The idea is to prevent two devices
colliding on the same address range.
Generic flavors of pci_request_region() are request_mem_region()
(for MMIO ranges) and request_region() (for IO Port ranges).
Use these for address resources that are not described by "normal" PCI
interfaces (e.g. BAR).
All interrupt handlers should be registered with SA_SHIRQ and use the devid
to map IRQs to devices (remember that all PCI interrupts are shared).
......
Documentation/power/devices.txt
浏览文件 @ 62ed948c
......@@ -118,96 +118,6 @@ will fail.
There is currently no way to know what states a device or driver
supports a priori. This will change in the future.
pm_message_t meaning
pm_message_t has two fields. event ("major"), and flags. If driver
does not know event code, it aborts the request, returning error. Some
drivers may need to deal with special cases based on the actual type
of suspend operation being done at the system level. This is why
there are flags.
Event codes are:
ON -- no need to do anything except special cases like broken
HW.
# NOTIFICATION -- pretty much same as ON?
FREEZE -- stop DMA and interrupts, and be prepared to reinit HW from
scratch. That probably means stop accepting upstream requests, the
actual policy of what to do with them beeing specific to a given
driver. It's acceptable for a network driver to just drop packets
while a block driver is expected to block the queue so no request is
lost. (Use IDE as an example on how to do that). FREEZE requires no
power state change, and it's expected for drivers to be able to
quickly transition back to operating state.
SUSPEND -- like FREEZE, but also put hardware into low-power state. If
there's need to distinguish several levels of sleep, additional flag
is probably best way to do that.
Transitions are only from a resumed state to a suspended state, never
between 2 suspended states. (ON -> FREEZE or ON -> SUSPEND can happen,
FREEZE -> SUSPEND or SUSPEND -> FREEZE can not).
All events are:
[NOTE NOTE NOTE: If you are driver author, you should not care; you
should only look at event, and ignore flags.]
#Prepare for suspend -- userland is still running but we are going to
#enter suspend state. This gives drivers chance to load firmware from
#disk and store it in memory, or do other activities taht require
#operating userland, ability to kmalloc GFP_KERNEL, etc... All of these
#are forbiden once the suspend dance is started.. event = ON, flags =
#PREPARE_TO_SUSPEND
Apm standby -- prepare for APM event. Quiesce devices to make life
easier for APM BIOS. event = FREEZE, flags = APM_STANDBY
Apm suspend -- same as APM_STANDBY, but it we should probably avoid
spinning down disks. event = FREEZE, flags = APM_SUSPEND
System halt, reboot -- quiesce devices to make life easier for BIOS. event
= FREEZE, flags = SYSTEM_HALT or SYSTEM_REBOOT
System shutdown -- at least disks need to be spun down, or data may be
lost. Quiesce devices, just to make life easier for BIOS. event =
FREEZE, flags = SYSTEM_SHUTDOWN
Kexec -- turn off DMAs and put hardware into some state where new
kernel can take over. event = FREEZE, flags = KEXEC
Powerdown at end of swsusp -- very similar to SYSTEM_SHUTDOWN, except wake
may need to be enabled on some devices. This actually has at least 3
subtypes, system can reboot, enter S4 and enter S5 at the end of
swsusp. event = FREEZE, flags = SWSUSP and one of SYSTEM_REBOOT,
SYSTEM_SHUTDOWN, SYSTEM_S4
Suspend to ram -- put devices into low power state. event = SUSPEND,
flags = SUSPEND_TO_RAM
Freeze for swsusp snapshot -- stop DMA and interrupts. No need to put
devices into low power mode, but you must be able to reinitialize
device from scratch in resume method. This has two flavors, its done
once on suspending kernel, once on resuming kernel. event = FREEZE,
flags = DURING_SUSPEND or DURING_RESUME
Device detach requested from /sys -- deinitialize device; proably same as
SYSTEM_SHUTDOWN, I do not understand this one too much. probably event
= FREEZE, flags = DEV_DETACH.
#These are not really events sent:
#
#System fully on -- device is working normally; this is probably never
#passed to suspend() method... event = ON, flags = 0
#
#Ready after resume -- userland is now running, again. Time to free any
#memory you ate during prepare to suspend... event = ON, flags =
#READY_AFTER_RESUME
#
pm_message_t meaning
pm_message_t has two fields. event ("major"), and flags. If driver
......
Documentation/power/swsusp.txt
浏览文件 @ 62ed948c
......@@ -18,10 +18,11 @@ Some warnings, first.
*
* (*) suspend/resume support is needed to make it safe.
*
* If you have any filesystems on USB devices mounted before suspend,
* If you have any filesystems on USB devices mounted before software suspend,
* they won't be accessible after resume and you may lose data, as though
* you have unplugged the USB devices with mounted filesystems on them
* (see the FAQ below for details).
* you have unplugged the USB devices with mounted filesystems on them;
* see the FAQ below for details. (This is not true for more traditional
* power states like "standby", which normally don't turn USB off.)
You need to append resume=/dev/your_swap_partition to kernel command
line. Then you suspend by
......@@ -204,7 +205,7 @@ Q: There don't seem to be any generally useful behavioral
distinctions between SUSPEND and FREEZE.
A: Doing SUSPEND when you are asked to do FREEZE is always correct,
but it may be unneccessarily slow. If you want USB to stay simple,
but it may be unneccessarily slow. If you want your driver to stay simple,
slowness may not matter to you. It can always be fixed later.
For devices like disk it does matter, you do not want to spindown for
......@@ -349,25 +350,72 @@ Q: How do I make suspend more verbose?
A: If you want to see any non-error kernel messages on the virtual
terminal the kernel switches to during suspend, you have to set the
kernel console loglevel to at least 5, for example by doing
echo 5 > /proc/sys/kernel/printk
kernel console loglevel to at least 4 (KERN_WARNING), for example by
doing
# save the old loglevel
read LOGLEVEL DUMMY < /proc/sys/kernel/printk
# set the loglevel so we see the progress bar.
# if the level is higher than needed, we leave it alone.
if [ $LOGLEVEL -lt 5 ]; then
echo 5 > /proc/sys/kernel/printk
fi
IMG_SZ=0
read IMG_SZ < /sys/power/image_size
echo -n disk > /sys/power/state
RET=$?
#
# the logic here is:
# if image_size > 0 (without kernel support, IMG_SZ will be zero),
# then try again with image_size set to zero.
if [ $RET -ne 0 -a $IMG_SZ -ne 0 ]; then # try again with minimal image size
echo 0 > /sys/power/image_size
echo -n disk > /sys/power/state
RET=$?
fi
# restore previous loglevel
echo $LOGLEVEL > /proc/sys/kernel/printk
exit $RET
Q: Is this true that if I have a mounted filesystem on a USB device and
I suspend to disk, I can lose data unless the filesystem has been mounted
with "sync"?
A: That's right. It depends on your hardware, and it could be true even for
suspend-to-RAM. In fact, even with "-o sync" you can lose data if your
programs have information in buffers they haven't written out to disk.
A: That's right ... if you disconnect that device, you may lose data.
In fact, even with "-o sync" you can lose data if your programs have
information in buffers they haven't written out to a disk you disconnect,
or if you disconnect before the device finished saving data you wrote.
If you're lucky, your hardware will support low-power modes for USB
controllers while the system is asleep. Lots of hardware doesn't,
however. Shutting off the power to a USB controller is equivalent to
unplugging all the attached devices.
Software suspend normally powers down USB controllers, which is equivalent
to disconnecting all USB devices attached to your system.
Remember that it's always a bad idea to unplug a disk drive containing a
mounted filesystem. With USB that's true even when your system is asleep!
The safest thing is to unmount all USB-based filesystems before suspending
and remount them after resuming.
Your system might well support low-power modes for its USB controllers
while the system is asleep, maintaining the connection, using true sleep
modes like "suspend-to-RAM" or "standby". (Don't write "disk" to the
/sys/power/state file; write "standby" or "mem".) We've not seen any
hardware that can use these modes through software suspend, although in
theory some systems might support "platform" or "firmware" modes that
won't break the USB connections.
Remember that it's always a bad idea to unplug a disk drive containing a
mounted filesystem. That's true even when your system is asleep! The
safest thing is to unmount all filesystems on removable media (such USB,
Firewire, CompactFlash, MMC, external SATA, or even IDE hotplug bays)
before suspending; then remount them after resuming.
Q: I upgraded the kernel from 2.6.15 to 2.6.16. Both kernels were
compiled with the similar configuration files. Anyway I found that
suspend to disk (and resume) is much slower on 2.6.16 compared to
2.6.15. Any idea for why that might happen or how can I speed it up?
A: This is because the size of the suspend image is now greater than
for 2.6.15 (by saving more data we can get more responsive system
after resume).
There's the /sys/power/image_size knob that controls the size of the
image. If you set it to 0 (eg. by echo 0 > /sys/power/image_size as
root), the 2.6.15 behavior should be restored. If it is still too
slow, take a look at suspend.sf.net -- userland suspend is faster and
supports LZF compression to speed it up further.
Documentation/power/video.txt
浏览文件 @ 62ed948c
......@@ -90,6 +90,7 @@ Table of known working notebooks:
Model hack (or "how to do it")
------------------------------------------------------------------------------
Acer Aspire 1406LC ole's late BIOS init (7), turn off DRI
Acer TM 230 s3_bios (2)
Acer TM 242FX vbetool (6)
Acer TM C110 video_post (8)
Acer TM C300 vga=normal (only suspend on console, not in X), vbetool (6) or video_post (8)
......@@ -115,6 +116,7 @@ Dell D610 vga=normal and X (possibly vbestate (6) too, but not tested)
Dell Inspiron 4000 ??? (*)
Dell Inspiron 500m ??? (*)
Dell Inspiron 510m ???
Dell Inspiron 5150 vbetool needed (6)
Dell Inspiron 600m ??? (*)
Dell Inspiron 8200 ??? (*)
Dell Inspiron 8500 ??? (*)
......@@ -125,6 +127,7 @@ HP NX7000 ??? (*)
HP Pavilion ZD7000 vbetool post needed, need open-source nv driver for X
HP Omnibook XE3 athlon version none (1)
HP Omnibook XE3GC none (1), video is S3 Savage/IX-MV
HP Omnibook XE3L-GF vbetool (6)
HP Omnibook 5150 none (1), (S1 also works OK)
IBM TP T20, model 2647-44G none (1), video is S3 Inc. 86C270-294 Savage/IX-MV, vesafb gets "interesting" but X work.
IBM TP A31 / Type 2652-M5G s3_mode (3) [works ok with BIOS 1.04 2002-08-23, but not at all with BIOS 1.11 2004-11-05 :-(]
......@@ -157,6 +160,7 @@ Sony Vaio vgn-s260 X or boot-radeon can init it (5)
Sony Vaio vgn-S580BH vga=normal, but suspend from X. Console will be blank unless you return to X.
Sony Vaio vgn-FS115B s3_bios (2),s3_mode (4)
Toshiba Libretto L5 none (1)
Toshiba Libretto 100CT/110CT vbetool (6)
Toshiba Portege 3020CT s3_mode (3)
Toshiba Satellite 4030CDT s3_mode (3) (S1 also works OK)
Toshiba Satellite 4080XCDT s3_mode (3) (S1 also works OK)
......
Documentation/rtc.txt
浏览文件 @ 62ed948c
......@@ -44,8 +44,10 @@ normal timer interrupt, which is 100Hz.
Programming and/or enabling interrupt frequencies greater than 64Hz is
only allowed by root. This is perhaps a bit conservative, but we don't want
an evil user generating lots of IRQs on a slow 386sx-16, where it might have
a negative impact on performance. Note that the interrupt handler is only
a few lines of code to minimize any possibility of this effect.
a negative impact on performance. This 64Hz limit can be changed by writing
a different value to /proc/sys/dev/rtc/max-user-freq. Note that the
interrupt handler is only a few lines of code to minimize any possibility
of this effect.
Also, if the kernel time is synchronized with an external source, the
kernel will write the time back to the CMOS clock every 11 minutes. In
......@@ -81,6 +83,7 @@ that will be using this driver.
*/
#include <stdio.h>
#include <stdlib.h>
#include <linux/rtc.h>
#include <sys/ioctl.h>
#include <sys/time.h>
......
Documentation/scsi/00-INDEX
浏览文件 @ 62ed948c
......@@ -30,8 +30,6 @@ aic7xxx.txt
- info on driver for Adaptec controllers
aic7xxx_old.txt
- info on driver for Adaptec controllers, old generation
cpqfc.txt
- info on driver for Compaq Tachyon TS adapters
dpti.txt
- info on driver for DPT SmartRAID and Adaptec I2O RAID based adapters
dtc3x80.txt
......
Documentation/scsi/ChangeLog.megaraid_sas
浏览文件 @ 62ed948c
1 Release Date : Wed Feb 03 14:31:44 PST 2006 - Sumant Patro <Sumant.Patro@lsil.com>
2 Current Version : 00.00.02.04
3 Older Version : 00.00.02.04
i. Remove superflous instance_lock
gets rid of the otherwise superflous instance_lock and avoids an unsave
unsynchronized access in the error handler.
- Christoph Hellwig <hch@lst.de>
1 Release Date : Wed Feb 03 14:31:44 PST 2006 - Sumant Patro <Sumant.Patro@lsil.com>
2 Current Version : 00.00.02.04
3 Older Version : 00.00.02.04
......
Documentation/scsi/aacraid.txt
浏览文件 @ 62ed948c
......@@ -24,10 +24,10 @@ Supported Cards/Chipsets
9005:0285:9005:0296 Adaptec 2240S (SabreExpress)
9005:0285:9005:0290 Adaptec 2410SA (Jaguar)
9005:0285:9005:0293 Adaptec 21610SA (Corsair-16)
9005:0285:103c:3227 Adaptec 2610SA (Bearcat)
9005:0285:103c:3227 Adaptec 2610SA (Bearcat HP release)
9005:0285:9005:0292 Adaptec 2810SA (Corsair-8)
9005:0285:9005:0294 Adaptec Prowler
9005:0286:9005:029d Adaptec 2420SA (Intruder)
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)
......@@ -38,7 +38,7 @@ Supported Cards/Chipsets
9005:0285:9005:0297 Adaptec 4005SAS (AvonPark)
9005:0285:9005:0299 Adaptec 4800SAS (Marauder-X)
9005:0285:9005:029a Adaptec 4805SAS (Marauder-E)
9005:0286:9005:02a2 Adaptec 4810SAS (Hurricane)
9005:0286:9005:02a2 Adaptec 3800SAS (Hurricane44)
1011:0046:9005:0364 Adaptec 5400S (Mustang)
1011:0046:9005:0365 Adaptec 5400S (Mustang)
9005:0283:9005:0283 Adaptec Catapult (3210S with arc firmware)
......@@ -72,7 +72,7 @@ Supported Cards/Chipsets
9005:0286:9005:02a1 ICP ICP9087MA (Lancer)
9005:0286:9005:02a4 ICP ICP9085LI (Marauder-X)
9005:0286:9005:02a5 ICP ICP5085BR (Marauder-E)
9005:0286:9005:02a3 ICP ICP5085AU (Hurricane)
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)
......
Documentation/scsi/cpqfc.txt 已删除 100644 → 0
浏览文件 @ 17ffc7ba
Notes for CPQFCTS driver for Compaq Tachyon TS
Fibre Channel Host Bus Adapter, PCI 64-bit, 66MHz
for Linux (RH 6.1, 6.2 kernel 2.2.12-32, 2.2.14-5)
SMP tested
Tested in single and dual HBA configuration, 32 and 64bit busses,
33 and 66MHz. Only supports FC-AL.
SEST size 512 Exchanges (simultaneous I/Os) limited by module kmalloc()
max of 128k bytes contiguous.
Ver 2.5.4 Oct 03, 2002
* fixed memcpy of sense buffer in ioctl to copy the smaller defined size
Ver 2.5.3 Aug 01, 2002
* fix the passthru ioctl to handle the Scsi_Cmnd->request being a pointer
Ver 2.5.1 Jul 30, 2002
* fix ioctl to pay attention to the specified LUN.
Ver 2.5.0 Nov 29, 2001
* eliminated io_request_lock. This change makes the driver specific
to the 2.5.x kernels.
* silenced excessively noisy printks.
Ver 2.1.2 July 23, 2002
* initialize DumCmnd->lun in cpqfcTS_ioctl (used in fcFindLoggedInPorts as LUN index)
Ver 2.1.1 Oct 18, 2001
* reinitialize Cmnd->SCp.sent_command (used to identify commands as
passthrus) on calling scsi_done, since the scsi mid layer does not
use (or reinitialize) this field to prevent subsequent comands from
having it set incorrectly.
Ver 2.1.0 Aug 27, 2001
* Revise driver to use new kernel 2.4.x PCI DMA API, instead of
virt_to_bus(). (enables driver to work w/ ia64 systems with >2Gb RAM.)
Rework main scatter-gather code to handle cases where SG element
lengths are larger than 0x7FFFF bytes and use as many scatter
gather pages as necessary. (Steve Cameron)
* Makefile changes to bring cpqfc into line w/ rest of SCSI drivers
(thanks to Keith Owens)
Ver 2.0.5 Aug 06, 2001
* Reject non-existent luns in the driver rather than letting the
hardware do it. (some HW behaves differently than others in this area.)
* Changed Makefile to rely on "make dep" instead of explicit dependencies
* ifdef'ed out fibre channel analyzer triggering debug code
* fixed a jiffies wrapping issue
Ver 2.0.4 Aug 01, 2001
* Incorporated fix for target device reset from Steeleye
* Fixed passthrough ioctl so it doesn't hang.
* Fixed hang in launch_FCworker_thread() that occurred on some machines.
* Avoid problem when number of volumes in a single cabinet > 8
Ver 2.0.2 July 23, 2001
Changed the semiphore changes so the driver would compile in 2.4.7.
This version is for 2.4.7 and beyond.
Ver 2.0.1 May 7, 2001
Merged version 1.3.6 fixes into version 2.0.0.
Ver 2.0.0 May 7, 2001
Fixed problem so spinlock is being initialized to UNLOCKED.
Fixed updated driver so it compiles in the 2.4 tree.
Ver 1.3.6 Feb 27, 2001
Added Target_Device_Reset function for SCSI error handling
Fixed problem with not reseting addressing mode after implicit logout
Ver 1.3.4 Sep 7, 2000
Added Modinfo information
Fixed problem with statically linking the driver
Ver 1.3.3, Aug 23, 2000
Fixed device/function number in ioctl
Ver 1.3.2, July 27, 2000
Add include for Alpha compile on 2.2.14 kernel (cpq*i2c.c)
Change logic for different FCP-RSP sense_buffer location for HSG80 target
And search for Agilent Tachyon XL2 HBAs (not finished! - in test)
Tested with
(storage):
Compaq RA-4x000, RAID firmware ver 2.40 - 2.54
Seagate FC drives model ST39102FC, rev 0006
Hitachi DK31CJ-72FC rev J8A8
IBM DDYF-T18350R rev F60K
Compaq FC-SCSI bridge w/ DLT 35/70 Gb DLT (tape)
(servers):
Compaq PL-1850R
Compaq PL-6500 Xeon (400MHz)
Compaq PL-8500 (500MHz, 66MHz, 64bit PCI)
Compaq Alpha DS20 (RH 6.1)
(hubs):
Vixel Rapport 1000 (7-port "dumb")
Gadzoox Gibralter (12-port "dumb")
Gadzoox Capellix 2000, 3000
(switches):
Brocade 2010, 2400, 2800, rev 2.0.3a (& later)
Gadzoox 3210 (Fabric blade beta)
Vixel 7100 (Fabric beta firmare - known hot plug issues)
using "qa_test" (esp. io_test script) suite modified from Unix tests.
Installation:
make menuconfig
(select SCSI low-level, Compaq FC HBA)
make modules
make modules_install
e.g. insmod -f cpqfc
Due to Fabric/switch delays, driver requires 4 seconds
to initialize. If adapters are found, there will be a entries at
/proc/scsi/cpqfcTS/*
sample contents of startup messages
*************************
scsi_register allocating 3596 bytes for CPQFCHBA
ioremap'd Membase: c887e600
HBA Tachyon RevId 1.2
Allocating 119808 for 576 Exchanges @ c0dc0000
Allocating 112904 for LinkQ @ c0c20000 (576 elements)
Allocating 110600 for TachSEST for 512 Exchanges
cpqfcTS: writing IMQ BASE 7C0000h PI 7C4000h
cpqfcTS: SEST c0e40000(virt): Wrote base E40000h @ c887e740
cpqfcTS: New FC port 0000E8h WWN: 500507650642499D SCSI Chan/Trgt 0/0
cpqfcTS: New FC port 0000EFh WWN: 50000E100000D5A6 SCSI Chan/Trgt 0/1
cpqfcTS: New FC port 0000E4h WWN: 21000020370097BB SCSI Chan/Trgt 0/2
cpqfcTS: New FC port 0000E2h WWN: 2100002037009946 SCSI Chan/Trgt 0/3
cpqfcTS: New FC port 0000E1h WWN: 21000020370098FE SCSI Chan/Trgt 0/4
cpqfcTS: New FC port 0000E0h WWN: 21000020370097B2 SCSI Chan/Trgt 0/5
cpqfcTS: New FC port 0000DCh WWN: 2100002037006CC1 SCSI Chan/Trgt 0/6
cpqfcTS: New FC port 0000DAh WWN: 21000020370059F6 SCSI Chan/Trgt 0/7
cpqfcTS: New FC port 00000Fh WWN: 500805F1FADB0E20 SCSI Chan/Trgt 0/8
cpqfcTS: New FC port 000008h WWN: 500805F1FADB0EBA SCSI Chan/Trgt 0/9
cpqfcTS: New FC port 000004h WWN: 500805F1FADB1EB9 SCSI Chan/Trgt 0/10
cpqfcTS: New FC port 000002h WWN: 500805F1FADB1ADE SCSI Chan/Trgt 0/11
cpqfcTS: New FC port 000001h WWN: 500805F1FADBA2CA SCSI Chan/Trgt 0/12
scsi4 : Compaq FibreChannel HBA Tachyon TS HPFC-5166A/1.2: WWN 500508B200193F50
on PCI bus 0 device 0xa0fc irq 5 IObaseL 0x3400, MEMBASE 0xc6ef8600
PCI bus width 32 bits, bus speed 33 MHz
FCP-SCSI Driver v1.3.0
GBIC detected: Short-wave. LPSM 0h Monitor
scsi : 5 hosts.
Vendor: IBM Model: DDYF-T18350R Rev: F60K
Type: Direct-Access ANSI SCSI revision: 03
Detected scsi disk sdb at scsi4, channel 0, id 0, lun 0
Vendor: HITACHI Model: DK31CJ-72FC Rev: J8A8
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi4, channel 0, id 1, lun 0
Vendor: SEAGATE Model: ST39102FC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdd at scsi4, channel 0, id 2, lun 0
Vendor: SEAGATE Model: ST39102FC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sde at scsi4, channel 0, id 3, lun 0
Vendor: SEAGATE Model: ST39102FC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdf at scsi4, channel 0, id 4, lun 0
Vendor: SEAGATE Model: ST39102FC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdg at scsi4, channel 0, id 5, lun 0
Vendor: SEAGATE Model: ST39102FC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdh at scsi4, channel 0, id 6, lun 0
Vendor: SEAGATE Model: ST39102FC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdi at scsi4, channel 0, id 7, lun 0
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.48
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdj at scsi4, channel 0, id 8, lun 0
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.48
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdk at scsi4, channel 0, id 8, lun 1
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.40
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdl at scsi4, channel 0, id 9, lun 0
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.40
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdm at scsi4, channel 0, id 9, lun 1
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.54
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdn at scsi4, channel 0, id 10, lun 0
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.54
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdo at scsi4, channel 0, id 11, lun 0
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.54
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdp at scsi4, channel 0, id 11, lun 1
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.54
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdq at scsi4, channel 0, id 12, lun 0
Vendor: COMPAQ Model: LOGICAL VOLUME Rev: 2.54
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdr at scsi4, channel 0, id 12, lun 1
resize_dma_pool: unknown device type 12
resize_dma_pool: unknown device type 12
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB]
sdb: sdb1
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 144410880 [70513 MB] [70.5 GB]
sdc: sdc1
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sdd: sdd1
SCSI device sde: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sde: sde1
SCSI device sdf: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sdf: sdf1
SCSI device sdg: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sdg: sdg1
SCSI device sdh: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sdh: sdh1
SCSI device sdi: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sdi: sdi1
SCSI device sdj: hdwr sector= 512 bytes. Sectors= 2056160 [1003 MB] [1.0 GB]
sdj: sdj1
SCSI device sdk: hdwr sector= 512 bytes. Sectors= 2052736 [1002 MB] [1.0 GB]
sdk: sdk1
SCSI device sdl: hdwr sector= 512 bytes. Sectors= 17764320 [8673 MB] [8.7 GB]
sdl: sdl1
SCSI device sdm: hdwr sector= 512 bytes. Sectors= 8380320 [4091 MB] [4.1 GB]
sdm: sdm1
SCSI device sdn: hdwr sector= 512 bytes. Sectors= 17764320 [8673 MB] [8.7 GB]
sdn: sdn1
SCSI device sdo: hdwr sector= 512 bytes. Sectors= 17764320 [8673 MB] [8.7 GB]
sdo: sdo1
SCSI device sdp: hdwr sector= 512 bytes. Sectors= 17764320 [8673 MB] [8.7 GB]
sdp: sdp1
SCSI device sdq: hdwr sector= 512 bytes. Sectors= 2056160 [1003 MB] [1.0 GB]
sdq: sdq1
SCSI device sdr: hdwr sector= 512 bytes. Sectors= 2052736 [1002 MB] [1.0 GB]
sdr: sdr1
*************************
If a GBIC of type Short-wave, Long-wave, or Copper is detected, it will
print out; otherwise, "none" is displayed. If the cabling is correct
and a loop circuit is completed, you should see "Monitor"; otherwise,
"LoopFail" (on open circuit) or some LPSM number/state with bit 3 set.
ERRATA:
1. Normally, Linux Scsi queries FC devices with INQUIRY strings. All LUNs
found according to INQUIRY should get READ commands at sector 0 to find
partition table, etc. Older kernels only query the first 4 devices. Some
Linux kernels only look for one LUN per target (i.e. FC device).
2. Physically removing a device, or a malfunctioning system which hides a
device, leads to a 30-second timeout and subsequent _abort call.
In some process contexts, this will hang the kernel (crashing the system).
Single bit errors in frames and virtually all hot plugging events are
gracefully handled with internal driver timer and Abort processing.
3. Some SCSI drives with error conditions will not handle the 7 second timeout
in this software driver, leading to infinite retries on timed out SCSI commands.
The 7 secs balances the need to quickly recover from lost frames (esp. on sequence
initiatives) and time needed by older/slower/error-state drives in responding.
This can be easily changed in "Exchanges[].timeOut".
4. Due to the nature of FC soft addressing, there is no assurance that the
same LUNs (drives) will have the same path (e.g. /dev/sdb1) from one boot to
next. Dynamic soft address changes (i.e. 24-bit FC port_id) are
supported during run time (e.g. due to hot plug event) by the use of WWN to
SCSI Nexus (channel/target/LUN) mapping.
5. Compaq RA4x00 firmware version 2.54 and later supports SSP (Selective
Storage Presentation), which maps LUNs to a WWN. If RA4x00 firmware prior
2.54 (e.g. older controller) is used, or the FC HBA is replaced (another WWN
is used), logical volumes on the RA4x00 will no longer be visible.
Send questions/comments to:
Amy Vanzant-Hodge (fibrechannel@compaq.com)
Documentation/scsi/hptiop.txt 0 → 100644
浏览文件 @ 62ed948c
HIGHPOINT ROCKETRAID 3xxx RAID DRIVER (hptiop)
Controller Register Map
-------------------------
The controller IOP is accessed via PCI BAR0.
BAR0 offset Register
0x10 Inbound Message Register 0
0x14 Inbound Message Register 1
0x18 Outbound Message Register 0
0x1C Outbound Message Register 1
0x20 Inbound Doorbell Register
0x24 Inbound Interrupt Status Register
0x28 Inbound Interrupt Mask Register
0x30 Outbound Interrupt Status Register
0x34 Outbound Interrupt Mask Register
0x40 Inbound Queue Port
0x44 Outbound Queue Port
I/O Request Workflow
----------------------
All queued requests are handled via inbound/outbound queue port.
A request packet can be allocated in either IOP or host memory.
To send a request to the controller:
- Get a free request packet by reading the inbound queue port or
allocate a free request in host DMA coherent memory.
The value returned from the inbound queue port is an offset
relative to the IOP BAR0.
Requests allocated in host memory must be aligned on 32-bytes boundary.
- Fill the packet.
- Post the packet to IOP by writing it to inbound queue. For requests
allocated in IOP memory, write the offset to inbound queue port. For
requests allocated in host memory, write (0x80000000|(bus_addr>>5))
to the inbound queue port.
- The IOP process the request. When the request is completed, it
will be put into outbound queue. An outbound interrupt will be
generated.
For requests allocated in IOP memory, the request offset is posted to
outbound queue.
For requests allocated in host memory, (0x80000000|(bus_addr>>5))
is posted to the outbound queue. If IOP_REQUEST_FLAG_OUTPUT_CONTEXT
flag is set in the request, the low 32-bit context value will be
posted instead.
- The host read the outbound queue and complete the request.
For requests allocated in IOP memory, the host driver free the request
by writing it to the outbound queue.
Non-queued requests (reset/flush etc) can be sent via inbound message
register 0. An outbound message with the same value indicates the completion
of an inbound message.
User-level Interface
---------------------
The driver exposes following sysfs attributes:
NAME R/W Description
driver-version R driver version string
firmware-version R firmware version string
The driver registers char device "hptiop" to communicate with HighPoint RAID
management software. Its ioctl routine acts as a general binary interface
between the IOP firmware and HighPoint RAID management software. New management
functions can be implemented in application/firmware without modification
in driver code.
-----------------------------------------------------------------------------
Copyright (C) 2006 HighPoint Technologies, Inc. All Rights Reserved.
This file is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
linux@highpoint-tech.com
http://www.highpoint-tech.com
Documentation/sound/alsa/ALSA-Configuration.txt
浏览文件 @ 62ed948c
......@@ -366,7 +366,9 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module for C-Media CMI8338 and 8738 PCI sound cards.
mpu_port - 0x300,0x310,0x320,0x330, 0 = disable (default)
mpu_port - 0x300,0x310,0x320,0x330 = legacy port,
1 = integrated PCI port,
0 = disable (default)
fm_port - 0x388 (default), 0 = disable (default)
soft_ac3 - Software-conversion of raw SPDIF packets (model 033 only)
(default = 1)
......@@ -468,7 +470,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module for multifunction CS5535 companion PCI device
This module supports multiple cards.
The power-management is supported.
Module snd-dt019x
-----------------
......@@ -707,8 +709,10 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module snd-hda-intel
--------------------
Module for Intel HD Audio (ICH6, ICH6M, ICH7), ATI SB450,
VIA VT8251/VT8237A
Module for Intel HD Audio (ICH6, ICH6M, ESB2, ICH7, ICH8),
ATI SB450, SB600, RS600,
VIA VT8251/VT8237A,
SIS966, ULI M5461
model - force the model name
position_fix - Fix DMA pointer (0 = auto, 1 = none, 2 = POSBUF, 3 = FIFO size)
......@@ -778,6 +782,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
AD1981
basic 3-jack (default)
hp HP nx6320
thinkpad Lenovo Thinkpad T60/X60/Z60
AD1986A
6stack 6-jack, separate surrounds (default)
......@@ -1633,9 +1638,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
About capture IBL, see the description of snd-vx222 module.
Note: the driver is build only when CONFIG_ISA is set.
Note2: snd-vxp440 driver is merged to snd-vxpocket driver since
Note: snd-vxp440 driver is merged to snd-vxpocket driver since
ALSA 1.0.10.
The power-management is supported.
......@@ -1662,8 +1665,6 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module for Sound Core PDAudioCF sound card.
Note: the driver is build only when CONFIG_ISA is set.
The power-management is supported.
......
Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl
浏览文件 @ 62ed948c
......@@ -4215,7 +4215,7 @@ struct _snd_pcm_runtime {
<programlisting>
<![CDATA[
struct snd_rawmidi *rmidi;
snd_mpu401_uart_new(card, 0, MPU401_HW_MPU401, port, integrated,
snd_mpu401_uart_new(card, 0, MPU401_HW_MPU401, port, info_flags,
irq, irq_flags, &rmidi);
]]>
</programlisting>
......@@ -4242,15 +4242,36 @@ struct _snd_pcm_runtime {
</para>
<para>
The 5th argument is bitflags for additional information.
When the i/o port address above is a part of the PCI i/o
region, the MPU401 i/o port might have been already allocated
(reserved) by the driver itself. In such a case, pass non-zero
to the 5th argument
(<parameter>integrated</parameter>). Otherwise, pass 0 to it,
(reserved) by the driver itself. In such a case, pass a bit flag
<constant>MPU401_INFO_INTEGRATED</constant>,
and
the mpu401-uart layer will allocate the i/o ports by itself.
</para>
<para>
When the controller supports only the input or output MIDI stream,
pass <constant>MPU401_INFO_INPUT</constant> or
<constant>MPU401_INFO_OUTPUT</constant> bitflag, respectively.
Then the rawmidi instance is created as a single stream.
</para>
<para>
<constant>MPU401_INFO_MMIO</constant> bitflag is used to change
the access method to MMIO (via readb and writeb) instead of
iob and outb. In this case, you have to pass the iomapped address
to <function>snd_mpu401_uart_new()</function>.
</para>
<para>
When <constant>MPU401_INFO_TX_IRQ</constant> is set, the output
stream isn't checked in the default interrupt handler. The driver
needs to call <function>snd_mpu401_uart_interrupt_tx()</function>
by itself to start processing the output stream in irq handler.
</para>
<para>
Usually, the port address corresponds to the command port and
port + 1 corresponds to the data port. If not, you may change
......@@ -5333,7 +5354,7 @@ struct _snd_pcm_runtime {
<informalexample>
<programlisting>
<![CDATA[
snd_info_set_text_ops(entry, chip, read_size, my_proc_read);
snd_info_set_text_ops(entry, chip, my_proc_read);
]]>
</programlisting>
</informalexample>
......@@ -5394,29 +5415,12 @@ struct _snd_pcm_runtime {
<informalexample>
<programlisting>
<![CDATA[
entry->c.text.write_size = 256;
entry->c.text.write = my_proc_write;
]]>
</programlisting>
</informalexample>
</para>
<para>
The buffer size for read is set to 1024 implicitly by
<function>snd_info_set_text_ops()</function>. It should suffice
in most cases (the size will be aligned to
<constant>PAGE_SIZE</constant> anyway), but if you need to handle
very large text files, you can set it explicitly, too.
<informalexample>
<programlisting>
<![CDATA[
entry->c.text.read_size = 65536;
]]>
</programlisting>
</informalexample>
</para>
<para>
For the write callback, you can use
<function>snd_info_get_line()</function> to get a text line, and
......@@ -5562,7 +5566,7 @@ struct _snd_pcm_runtime {
power status.</para></listitem>
<listitem><para>Call <function>snd_pcm_suspend_all()</function> to suspend the running PCM streams.</para></listitem>
<listitem><para>If AC97 codecs are used, call
<function>snd_ac97_resume()</function> for each codec.</para></listitem>
<function>snd_ac97_suspend()</function> for each codec.</para></listitem>
<listitem><para>Save the register values if necessary.</para></listitem>
<listitem><para>Stop the hardware if necessary.</para></listitem>
<listitem><para>Disable the PCI device by calling
......
Documentation/sparc/sbus_drivers.txt
浏览文件 @ 62ed948c
......@@ -25,42 +25,84 @@ the bits necessary to run your device. The most commonly
used members of this structure, and their typical usage,
will be detailed below.
Here is how probing is performed by an SBUS driver
under Linux:
Here is a piece of skeleton code for perofming a device
probe in an SBUS driverunder Linux:
static void init_one_mydevice(struct sbus_dev *sdev)
static int __devinit mydevice_probe_one(struct sbus_dev *sdev)
{
struct mysdevice *mp = kzalloc(sizeof(*mp), GFP_KERNEL);
if (!mp)
return -ENODEV;
...
dev_set_drvdata(&sdev->ofdev.dev, mp);
return 0;
...
}
static int mydevice_match(struct sbus_dev *sdev)
static int __devinit mydevice_probe(struct of_device *dev,
const struct of_device_id *match)
{
if (some_criteria(sdev))
return 1;
return 0;
struct sbus_dev *sdev = to_sbus_device(&dev->dev);
return mydevice_probe_one(sdev);
}
static void mydevice_probe(void)
static int __devexit mydevice_remove(struct of_device *dev)
{
struct sbus_bus *sbus;
struct sbus_dev *sdev;
struct sbus_dev *sdev = to_sbus_device(&dev->dev);
struct mydevice *mp = dev_get_drvdata(&dev->dev);
for_each_sbus(sbus) {
for_each_sbusdev(sdev, sbus) {
if (mydevice_match(sdev))
init_one_mydevice(sdev);
}
}
return mydevice_remove_one(sdev, mp);
}
All this does is walk through all SBUS devices in the
system, checks each to see if it is of the type which
your driver is written for, and if so it calls the init
routine to attach the device and prepare to drive it.
static struct of_device_id mydevice_match[] = {
{
.name = "mydevice",
},
{},
};
MODULE_DEVICE_TABLE(of, mydevice_match);
"init_one_mydevice" might do things like allocate software
state structures, map in I/O registers, place the hardware
into an initialized state, etc.
static struct of_platform_driver mydevice_driver = {
.name = "mydevice",
.match_table = mydevice_match,
.probe = mydevice_probe,
.remove = __devexit_p(mydevice_remove),
};
static int __init mydevice_init(void)
{
return of_register_driver(&mydevice_driver, &sbus_bus_type);
}
static void __exit mydevice_exit(void)
{
of_unregister_driver(&mydevice_driver);
}
module_init(mydevice_init);
module_exit(mydevice_exit);
The mydevice_match table is a series of entries which
describes what SBUS devices your driver is meant for. In the
simplest case you specify a string for the 'name' field. Every
SBUS device with a 'name' property matching your string will
be passed one-by-one to your .probe method.
You should store away your device private state structure
pointer in the drvdata area so that you can retrieve it later on
in your .remove method.
Any memory allocated, registers mapped, IRQs registered,
etc. must be undone by your .remove method so that all resources
of your device are relased by the time it returns.
You should _NOT_ use the for_each_sbus(), for_each_sbusdev(),
and for_all_sbusdev() interfaces. They are deprecated, will be
removed, and no new driver should reference them ever.
Mapping and Accessing I/O Registers
......@@ -263,10 +305,3 @@ discussed above and plus it handles both PCI and SBUS boards.
Lance driver abuses consistent mappings for data transfer.
It is a nifty trick which we do not particularly recommend...
Just check it out and know that it's legal.
Bad examples, do NOT use
drivers/video/cgsix.c
This one uses result of sbus_ioremap as if it is an address.
This does NOT work on sparc64 and therefore is broken. We will
convert it at a later date.
Documentation/sparse.txt
浏览文件 @ 62ed948c
Copyright 2004 Linus Torvalds
Copyright 2004 Pavel Machek <pavel@suse.cz>
Copyright 2006 Bob Copeland <me@bobcopeland.com>
Using sparse for typechecking
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......@@ -41,15 +42,8 @@ sure that bitwise types don't get mixed up (little-endian vs big-endian
vs cpu-endian vs whatever), and there the constant "0" really _is_
special.
Use
make C=[12] CF=-Wbitwise
or you don't get any checking at all.
Where to get sparse
~~~~~~~~~~~~~~~~~~~
Getting sparse
~~~~~~~~~~~~~~
With git, you can just get it from
......@@ -57,7 +51,7 @@ With git, you can just get it from
and DaveJ has tar-balls at
http://www.codemonkey.org.uk/projects/git-snapshots/sparse/
http://www.codemonkey.org.uk/projects/git-snapshots/sparse/
Once you have it, just do
......@@ -65,8 +59,20 @@ Once you have it, just do
make
make install
as your regular user, and it will install sparse in your ~/bin directory.
After that, doing a kernel make with "make C=1" will run sparse on all the
C files that get recompiled, or with "make C=2" will run sparse on the
files whether they need to be recompiled or not (ie the latter is fast way
to check the whole tree if you have already built it).
as a regular user, and it will install sparse in your ~/bin directory.
Using sparse
~~~~~~~~~~~~
Do a kernel make with "make C=1" to run sparse on all the C files that get
recompiled, or use "make C=2" to run sparse on the files whether they need to
be recompiled or not. The latter is a fast way to check the whole tree if you
have already built it.
The optional make variable CF can be used to pass arguments to sparse. The
build system passes -Wbitwise to sparse automatically. To perform endianness
checks, you may define __CHECK_ENDIAN__:
make C=2 CF="-D__CHECK_ENDIAN__"
These checks are disabled by default as they generate a host of warnings.
Documentation/sysctl/vm.txt
浏览文件 @ 62ed948c
......@@ -29,6 +29,7 @@ Currently, these files are in /proc/sys/vm:
- drop-caches
- zone_reclaim_mode
- zone_reclaim_interval
- panic_on_oom
==============================================================
......@@ -178,3 +179,15 @@ Time is set in seconds and set by default to 30 seconds.
Reduce the interval if undesired off node allocations occur. However, too
frequent scans will have a negative impact onoff node allocation performance.
=============================================================
panic_on_oom
This enables or disables panic on out-of-memory feature. If this is set to 1,
the kernel panics when out-of-memory happens. If this is set to 0, the kernel
will kill some rogue process, called oom_killer. Usually, oom_killer can kill
rogue processes and system will survive. If you want to panic the system
rather than killing rogue processes, set this to 1.
The default value is 0.
Documentation/sysrq.txt
浏览文件 @ 62ed948c
......@@ -115,8 +115,9 @@ trojan program is running at console and which could grab your password
when you would try to login. It will kill all programs on given console
and thus letting you make sure that the login prompt you see is actually
the one from init, not some trojan program.
IMPORTANT:In its true form it is not a true SAK like the one in :IMPORTANT
IMPORTANT:c2 compliant systems, and it should be mistook as such. :IMPORTANT
IMPORTANT: In its true form it is not a true SAK like the one in a :IMPORTANT
IMPORTANT: c2 compliant system, and it should not be mistaken as :IMPORTANT
IMPORTANT: such. :IMPORTANT
It seems other find it useful as (System Attention Key) which is
useful when you want to exit a program that will not let you switch consoles.
(For example, X or a svgalib program.)
......
Documentation/usb/usbmon.txt
浏览文件 @ 62ed948c
......@@ -29,14 +29,13 @@ if usbmon is built into the kernel.
# mount -t debugfs none_debugs /sys/kernel/debug
# modprobe usbmon
#
Verify that bus sockets are present.
[root@lembas zaitcev]# ls /sys/kernel/debug/usbmon
# ls /sys/kernel/debug/usbmon
1s 1t 2s 2t 3s 3t 4s 4t
[root@lembas zaitcev]#
# ls /sys/kernel
#
2. Find which bus connects to the desired device
......@@ -76,7 +75,7 @@ that the file size is not excessive for your favourite editor.
* Raw text data format
The '0t' type data consists of a stream of events, such as URB submission,
The '1t' type data consists of a stream of events, such as URB submission,
URB callback, submission error. Every event is a text line, which consists
of whitespace separated words. The number of position of words may depend
on the event type, but there is a set of words, common for all types.
......@@ -97,20 +96,25 @@ Here is the list of words, from left to right:
Zi Zo Isochronous input and output
Ii Io Interrupt input and output
Bi Bo Bulk input and output
Device address and Endpoint number are decimal numbers with leading zeroes
or 3 and 2 positions, correspondingly.
- URB Status. This field makes no sense for submissions, but is present
to help scripts with parsing. In error case, it contains the error code.
In case of a setup packet, it contains a Setup Tag. If scripts read a number
in this field, they proceed to read Data Length. Otherwise, they read
the setup packet before reading the Data Length.
Device address and Endpoint number are 3-digit and 2-digit (respectively)
decimal numbers, with leading zeroes.
- URB Status. In most cases, this field contains a number, sometimes negative,
which represents a "status" field of the URB. This field makes no sense for
submissions, but is present anyway to help scripts with parsing. When an
error occurs, the field contains the error code. In case of a submission of
a Control packet, this field contains a Setup Tag instead of an error code.
It is easy to tell whether the Setup Tag is present because it is never a
number. Thus if scripts find a number in this field, they proceed to read
Data Length. If they find something else, like a letter, they read the setup
packet before reading the Data Length.
- Setup packet, if present, consists of 5 words: one of each for bmRequestType,
bRequest, wValue, wIndex, wLength, as specified by the USB Specification 2.0.
These words are safe to decode if Setup Tag was 's'. Otherwise, the setup
packet was present, but not captured, and the fields contain filler.
- Data Length. This is the actual length in the URB.
- Data Length. For submissions, this is the requested length. For callbacks,
this is the actual length.
- Data tag. The usbmon may not always capture data, even if length is nonzero.
Only if tag is '=', the data words are present.
The data words are present only if this tag is '='.
- Data words follow, in big endian hexadecimal format. Notice that they are
not machine words, but really just a byte stream split into words to make
it easier to read. Thus, the last word may contain from one to four bytes.
......
Documentation/video4linux/CARDLIST.bttv
浏览文件 @ 62ed948c
......@@ -87,7 +87,7 @@
86 -> Osprey 101/151 w/ svid
87 -> Osprey 200/201/250/251
88 -> Osprey 200/250 [0070:ff01]
89 -> Osprey 210/220
89 -> Osprey 210/220/230
90 -> Osprey 500 [0070:ff02]
91 -> Osprey 540 [0070:ff04]
92 -> Osprey 2000 [0070:ff03]
......@@ -111,7 +111,7 @@
110 -> IVC-100 [ff00:a132]
111 -> IVC-120G [ff00:a182,ff01:a182,ff02:a182,ff03:a182,ff04:a182,ff05:a182,ff06:a182,ff07:a182,ff08:a182,ff09:a182,ff0a:a182,ff0b:a182,ff0c:a182,ff0d:a182,ff0e:a182,ff0f:a182]
112 -> pcHDTV HD-2000 TV [7063:2000]
113 -> Twinhan DST + clones [11bd:0026,1822:0001,270f:fc00]
113 -> Twinhan DST + clones [11bd:0026,1822:0001,270f:fc00,1822:0026]
114 -> Winfast VC100 [107d:6607]
115 -> Teppro TEV-560/InterVision IV-560
116 -> SIMUS GVC1100 [aa6a:82b2]
......
Documentation/video4linux/CARDLIST.cx88
浏览文件 @ 62ed948c
......@@ -15,7 +15,7 @@
14 -> KWorld/VStream XPert DVB-T [17de:08a6]
15 -> DViCO FusionHDTV DVB-T1 [18ac:db00]
16 -> KWorld LTV883RF
17 -> DViCO FusionHDTV 3 Gold-Q [18ac:d810]
17 -> DViCO FusionHDTV 3 Gold-Q [18ac:d810,18ac:d800]
18 -> Hauppauge Nova-T DVB-T [0070:9002,0070:9001]
19 -> Conexant DVB-T reference design [14f1:0187]
20 -> Provideo PV259 [1540:2580]
......@@ -40,8 +40,13 @@
39 -> KWorld DVB-S 100 [17de:08b2]
40 -> Hauppauge WinTV-HVR1100 DVB-T/Hybrid [0070:9400,0070:9402]
41 -> Hauppauge WinTV-HVR1100 DVB-T/Hybrid (Low Profile) [0070:9800,0070:9802]
42 -> digitalnow DNTV Live! DVB-T Pro [1822:0025]
42 -> digitalnow DNTV Live! DVB-T Pro [1822:0025,1822:0019]
43 -> KWorld/VStream XPert DVB-T with cx22702 [17de:08a1]
44 -> DViCO FusionHDTV DVB-T Dual Digital [18ac:db50,18ac:db54]
45 -> KWorld HardwareMpegTV XPert [17de:0840]
46 -> DViCO FusionHDTV DVB-T Hybrid [18ac:db40,18ac:db44]
47 -> pcHDTV HD5500 HDTV [7063:5500]
48 -> Kworld MCE 200 Deluxe [17de:0841]
49 -> PixelView PlayTV P7000 [1554:4813]
50 -> NPG Tech Real TV FM Top 10 [14f1:0842]
51 -> WinFast DTV2000 H [107d:665e]
Documentation/video4linux/CARDLIST.saa7134
浏览文件 @ 62ed948c
......@@ -93,3 +93,4 @@
92 -> AVerMedia A169 B1 [1461:6360]
93 -> Medion 7134 Bridge #2 [16be:0005]
94 -> LifeView FlyDVB-T Hybrid Cardbus [5168:3306,5168:3502]
95 -> LifeView FlyVIDEO3000 (NTSC) [5169:0138]
Documentation/video4linux/CARDLIST.tuner
浏览文件 @ 62ed948c
......@@ -62,7 +62,7 @@ tuner=60 - Thomson DTT 761X (ATSC/NTSC)
tuner=61 - Tena TNF9533-D/IF/TNF9533-B/DF
tuner=62 - Philips TEA5767HN FM Radio
tuner=63 - Philips FMD1216ME MK3 Hybrid Tuner
tuner=64 - LG TDVS-H062F/TUA6034
tuner=64 - LG TDVS-H06xF
tuner=65 - Ymec TVF66T5-B/DFF
tuner=66 - LG TALN series
tuner=67 - Philips TD1316 Hybrid Tuner
......@@ -71,3 +71,4 @@ tuner=69 - Tena TNF 5335 and similar models
tuner=70 - Samsung TCPN 2121P30A
tuner=71 - Xceive xc3028
tuner=72 - Thomson FE6600
tuner=73 - Samsung TCPG 6121P30A
Documentation/video4linux/CQcam.txt
浏览文件 @ 62ed948c
......@@ -185,207 +185,10 @@ this work is documented at the video4linux2 site listed below.
9.0 --- A sample program using v4lgrabber,
This program is a simple image grabber that will copy a frame from the
v4lgrab is a simple image grabber that will copy a frame from the
first video device, /dev/video0 to standard output in portable pixmap
format (.ppm) Using this like: 'v4lgrab | convert - c-qcam.jpg'
produced this picture of me at
http://mug.sys.virginia.edu/~drf5n/extras/c-qcam.jpg
-------------------- 8< ---------------- 8< -----------------------------
/* Simple Video4Linux image grabber. */
/*
* Video4Linux Driver Test/Example Framegrabbing Program
*
* Compile with:
* gcc -s -Wall -Wstrict-prototypes v4lgrab.c -o v4lgrab
* Use as:
* v4lgrab >image.ppm
*
* Copyright (C) 1998-05-03, Phil Blundell <philb@gnu.org>
* Copied from http://www.tazenda.demon.co.uk/phil/vgrabber.c
* with minor modifications (Dave Forrest, drf5n@virginia.edu).
*
*/
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdio.h>
#include <sys/ioctl.h>
#include <stdlib.h>
#include <linux/types.h>
#include <linux/videodev.h>
#define FILE "/dev/video0"
/* Stole this from tvset.c */
#define READ_VIDEO_PIXEL(buf, format, depth, r, g, b) \
{ \
switch (format) \
{ \
case VIDEO_PALETTE_GREY: \
switch (depth) \
{ \
case 4: \
case 6: \
case 8: \
(r) = (g) = (b) = (*buf++ << 8);\
break; \
\
case 16: \
(r) = (g) = (b) = \
*((unsigned short *) buf); \
buf += 2; \
break; \
} \
break; \
\
\
case VIDEO_PALETTE_RGB565: \
{ \
unsigned short tmp = *(unsigned short *)buf; \
(r) = tmp&0xF800; \
(g) = (tmp<<5)&0xFC00; \
(b) = (tmp<<11)&0xF800; \
buf += 2; \
} \
break; \
\
case VIDEO_PALETTE_RGB555: \
(r) = (buf[0]&0xF8)<<8; \
(g) = ((buf[0] << 5 | buf[1] >> 3)&0xF8)<<8; \
(b) = ((buf[1] << 2 ) & 0xF8)<<8; \
buf += 2; \
break; \
\
case VIDEO_PALETTE_RGB24: \
(r) = buf[0] << 8; (g) = buf[1] << 8; \
(b) = buf[2] << 8; \
buf += 3; \
break; \
\
default: \
fprintf(stderr, \
"Format %d not yet supported\n", \
format); \
} \
}
int get_brightness_adj(unsigned char *image, long size, int *brightness) {
long i, tot = 0;
for (i=0;i<size*3;i++)
tot += image[i];
*brightness = (128 - tot/(size*3))/3;
return !((tot/(size*3)) >= 126 && (tot/(size*3)) <= 130);
}
int main(int argc, char ** argv)
{
int fd = open(FILE, O_RDONLY), f;
struct video_capability cap;
struct video_window win;
struct video_picture vpic;
unsigned char *buffer, *src;
int bpp = 24, r, g, b;
unsigned int i, src_depth;
if (fd < 0) {
perror(FILE);
exit(1);
}
if (ioctl(fd, VIDIOCGCAP, &cap) < 0) {
perror("VIDIOGCAP");
fprintf(stderr, "(" FILE " not a video4linux device?)\n");
close(fd);
exit(1);
}
if (ioctl(fd, VIDIOCGWIN, &win) < 0) {
perror("VIDIOCGWIN");
close(fd);
exit(1);
}
if (ioctl(fd, VIDIOCGPICT, &vpic) < 0) {
perror("VIDIOCGPICT");
close(fd);
exit(1);
}
if (cap.type & VID_TYPE_MONOCHROME) {
vpic.depth=8;
vpic.palette=VIDEO_PALETTE_GREY; /* 8bit grey */
if(ioctl(fd, VIDIOCSPICT, &vpic) < 0) {
vpic.depth=6;
if(ioctl(fd, VIDIOCSPICT, &vpic) < 0) {
vpic.depth=4;
if(ioctl(fd, VIDIOCSPICT, &vpic) < 0) {
fprintf(stderr, "Unable to find a supported capture format.\n");
close(fd);
exit(1);
}
}
}
} else {
vpic.depth=24;
vpic.palette=VIDEO_PALETTE_RGB24;
if(ioctl(fd, VIDIOCSPICT, &vpic) < 0) {
vpic.palette=VIDEO_PALETTE_RGB565;
vpic.depth=16;
if(ioctl(fd, VIDIOCSPICT, &vpic)==-1) {
vpic.palette=VIDEO_PALETTE_RGB555;
vpic.depth=15;
if(ioctl(fd, VIDIOCSPICT, &vpic)==-1) {
fprintf(stderr, "Unable to find a supported capture format.\n");
return -1;
}
}
}
}
buffer = malloc(win.width * win.height * bpp);
if (!buffer) {
fprintf(stderr, "Out of memory.\n");
exit(1);
}
do {
int newbright;
read(fd, buffer, win.width * win.height * bpp);
f = get_brightness_adj(buffer, win.width * win.height, &newbright);
if (f) {
vpic.brightness += (newbright << 8);
if(ioctl(fd, VIDIOCSPICT, &vpic)==-1) {
perror("VIDIOSPICT");
break;
}
}
} while (f);
fprintf(stdout, "P6\n%d %d 255\n", win.width, win.height);
src = buffer;
for (i = 0; i < win.width * win.height; i++) {
READ_VIDEO_PIXEL(src, vpic.palette, src_depth, r, g, b);
fputc(r>>8, stdout);
fputc(g>>8, stdout);
fputc(b>>8, stdout);
}
close(fd);
return 0;
}
-------------------- 8< ---------------- 8< -----------------------------
format (.ppm) To produce .jpg output, you can use it like this:
'v4lgrab | convert - c-qcam.jpg'
10.0 --- Other Information
......
Documentation/video4linux/Zoran
浏览文件 @ 62ed948c
......@@ -33,6 +33,21 @@ Inputs/outputs: Composite and S-video
Norms: PAL, SECAM (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)
Card number: 7
AverMedia 6 Eyes AVS6EYES:
* Zoran zr36067 PCI controller
* Zoran zr36060 MJPEG codec
* Samsung ks0127 TV decoder
* Conexant bt866 TV encoder
Drivers to use: videodev, i2c-core, i2c-algo-bit,
videocodec, ks0127, bt866, zr36060, zr36067
Inputs/outputs: Six physical inputs. 1-6 are composite,
1-2, 3-4, 5-6 doubles as S-video,
1-3 triples as component.
One composite output.
Norms: PAL, SECAM (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)
Card number: 8
Not autodetected, card=8 is necessary.
Linux Media Labs LML33:
* Zoran zr36067 PCI controller
* Zoran zr36060 MJPEG codec
......@@ -192,6 +207,10 @@ Micronas vpx3220a TV decoder
was introduced in 1996, is used in the DC30 and DC30+ and
can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC 44, PAL 60, SECAM,NTSC Comb
Samsung ks0127 TV decoder
is used in the AVS6EYES card and
can handle: NTSC-M/N/44, PAL-M/N/B/G/H/I/D/K/L and SECAM
===========================
1.2 What the TV encoder can do an what not
......@@ -221,6 +240,10 @@ ITT mse3000 TV encoder
was introduced in 1991, is used in the DC10 old
can generate: PAL , NTSC , SECAM
Conexant bt866 TV encoder
is used in AVS6EYES, and
can generate: NTSC/PAL, PAL­M, PAL­N
The adv717x, should be able to produce PAL N. But you find nothing PAL N
specific in the registers. Seem that you have to reuse a other standard
to generate PAL N, maybe it would work if you use the PAL M settings.
......
Documentation/video4linux/bttv/CONTRIBUTORS
浏览文件 @ 62ed948c
Contributors to bttv:
Contributors to bttv:
Michael Chu <mmchu@pobox.com>
AverMedia fix and more flexible card recognition
......@@ -8,8 +8,8 @@ Alan Cox <alan@redhat.com>
Chris Kleitsch
Hardware I2C
Gerd Knorr <kraxel@cs.tu-berlin.de>
Gerd Knorr <kraxel@cs.tu-berlin.de>
Radio card (ITT sound processor)
bigfoot <bigfoot@net-way.net>
......@@ -18,7 +18,7 @@ Ragnar Hojland Espinosa <ragnar@macula.net>
+ many more (please mail me if you are missing in this list and would
like to be mentioned)
like to be mentioned)
......
Documentation/video4linux/cx2341x/fw-calling.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/cx2341x/fw-decoder-api.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/cx2341x/fw-dma.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/cx2341x/fw-encoder-api.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/cx2341x/fw-memory.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/cx2341x/fw-osd-api.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/cx2341x/fw-upload.txt 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/ov511.txt
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/video4linux/v4lgrab.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/vm/page_migration
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/w1/masters/ds2490 0 → 100644
浏览文件 @ 62ed948c
Kernel driver ds2490
====================
Supported chips:
* Maxim DS2490 based
Author: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Description
-----------
The Maixm/Dallas Semiconductor DS2490 is a chip
which allows to build USB <-> W1 bridges.
DS9490(R) is a USB <-> W1 bus master device
which has 0x81 family ID integrated chip and DS2490
low-level operational chip.
Documentation/w1/w1.generic
浏览文件 @ 62ed948c
此差异已折叠。
Documentation/w1/w1.netlink 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
MAINTAINERS
浏览文件 @ 62ed948c
此差异已折叠。
arch/alpha/kernel/alpha_ksyms.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ 62ed948c
......@@ -244,7 +244,7 @@ do_osf_statfs(struct dentry * dentry, struct osf_statfs __user *buffer,
unsigned long bufsiz)
{
struct kstatfs linux_stat;
int error = vfs_statfs(dentry->d_inode->i_sb, &linux_stat);
int error = vfs_statfs(dentry, &linux_stat);
if (!error)
error = linux_to_osf_statfs(&linux_stat, buffer, bufsiz);
return error;
......
arch/alpha/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/common/Makefile
浏览文件 @ 62ed948c
......@@ -16,3 +16,4 @@ obj-$(CONFIG_SHARP_PARAM) += sharpsl_param.o
obj-$(CONFIG_SHARPSL_PM) += sharpsl_pm.o
obj-$(CONFIG_SHARP_SCOOP) += scoop.o
obj-$(CONFIG_ARCH_IXP2000) += uengine.o
obj-$(CONFIG_ARCH_IXP23XX) += uengine.o
arch/arm/common/dmabounce.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/common/uengine.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/configs/lpd270_defconfig 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/kernel/bios32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/kernel/iwmmxt.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ep93xx/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ep93xx/clock.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ep93xx/gesbc9312.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ep93xx/ts72xx.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-imx/dma.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp2000/core.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp23xx/core.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp23xx/espresso.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp23xx/ixdp2351.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp23xx/roadrunner.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-power.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-pnx4008/clock.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-pnx4008/serial.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/clock.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/clock.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/cpu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/cpu.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/mach-smdk2413.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/pm-simtec.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410-clock.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412-clock.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c2412.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mach-s3c2410/s3c244x.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/nwfpe/fpmodule.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/plat-omap/timer32k.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/vfp/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/vfp/vfphw.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/arm/vfp/vfpmodule.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/entry.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/frv_ksyms.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/irq-routing.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/pm.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/process.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/sys_frv.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/sysctl.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/kernel/uaccess.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/mb93090-mb00/pci-irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/frv/mm/kmap.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/h8300/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/acpi/boot.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/acpi/processor.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/acpi/sleep.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/acpi/wakeup.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/apic.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/apm.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/cpu/common.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/cpu/cyrix.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/cpu/proc.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/crash.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/doublefault.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/i387.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/i8259.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/io_apic.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/kprobes.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/microcode.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/smpboot.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/srat.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/syscall_table.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/traps.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/kernel/vmlinux.lds.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/lib/usercopy.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/mach-default/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/mach-visws/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/mach-voyager/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/mm/fault.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/mm/init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/mm/pageattr.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/pci/common.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/pci/i386.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/pci/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/pci/mmconfig.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/pci/pci.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/i386/power/cpu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/asm-offsets.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/efi.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/efi_stub.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/entry.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/irq_ia64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/mca_asm.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/sal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/topology.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/kernel/uncached.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/mm/ioremap.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/kernel/io_init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/kernel/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/kernel/sn2/cache.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/kernel/sn2/sn_hwperf.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/pci/pci_dma.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/pci/pcibr/pcibr_dma.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/pci/tioca_provider.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ia64/sn/pci/tioce_provider.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/amiga/amiga_ksyms.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/amiga/amiints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/amiga/cia.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/amiga/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/apollo/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/apollo/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/apollo/dn_ints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/atari/ataints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/atari/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/bvme6000/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/bvme6000/bvmeints.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/m68k/bvme6000/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/hp300/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/hp300/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/hp300/ints.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/m68k/hp300/ints.h 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/m68k/hp300/time.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/dma.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/entry.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/ints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/m68k_ksyms.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/kernel/traps.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/lib/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/lib/uaccess.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/baboon.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/iop.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/macints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/oss.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/psc.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mac/via.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mm/kmap.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mm/motorola.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mm/sun3mmu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mvme147/147ints.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/m68k/mvme147/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mvme147/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mvme16x/16xints.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/m68k/mvme16x/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/mvme16x/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/q40/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/q40/q40ints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/sun3/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/sun3/sun3ints.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68k/sun3x/config.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/kernel/traps.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/mm/init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/platform/5307/pit.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/platform/532x/Makefile 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/m68knommu/platform/532x/config.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/mips/kernel/irixsig.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/mips/kernel/scall32-o32.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/mips/kernel/sysirix.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/parisc/hpux/sys_hpux.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/parisc/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/boot/main.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/boot/prom.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/configs/cell_defconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/configs/mpc85xx_cds_defconfig 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/configs/mpc8641_hpcn_defconfig 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/align.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/cpu_setup_6xx.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/crash.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/crash_dump.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/fpu.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/head_32.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/iomap.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/iommu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/misc_32.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/misc_64.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/nvram_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/pci_32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/pci_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/pci_dn.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/pci_iommu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/proc_ppc64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/process.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/ptrace.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/rtas-rtc.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/rtas_flash.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/rtas_pci.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/setup.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/signal_32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/signal_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/systbl.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/udbg.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/vdso.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/vector.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/lib/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/lib/bitops.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/powerpc/mm/hash_low_32.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/hash_low_64.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/hash_native_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/lmb.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/mmu_context_32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/mmu_context_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/ppc_mmu_32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/slb.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/slb_low.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/stab.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/tlb_32.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/mm/tlb_64.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/oprofile/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/oprofile/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/oprofile/common.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/85xx/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/85xx/mpc85xx_cds.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/85xx/mpc85xx_cds.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/Kconfig 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/Makefile 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/mpc8641_hpcn.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/mpc86xx.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/mpc86xx_hpcn.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/mpc86xx_pcie.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/mpc86xx_smp.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/86xx/pci.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/cbe_regs.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/cbe_regs.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/ras.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/ras.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/cell/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/iseries/dt.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/iseries/mf.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/iseries/vio.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/powerpc/platforms/maple/pci.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/platforms/pseries/vio.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/powerpc/sysdev/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/sysdev/dart_iommu.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/sysdev/mpic.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/boot/lib/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/kernel/pci.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/mm/init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/mm/mmu_context.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/mm/tlb.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/platforms/4xx/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/platforms/4xx/cpci405.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/platforms/4xx/cpci405.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/ppc/syslib/mpc83xx_devices.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/hypfs/Makefile 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/hypfs/hypfs.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/hypfs/hypfs_diag.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/hypfs/hypfs_diag.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/hypfs/inode.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sh64/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/ebus.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/ioport.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/of_device.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/pcic.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/prom.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc/mm/init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/defconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/auxio.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/central.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/chmc.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/devices.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/ebus.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/irq.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/isa.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/of_device.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci_common.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci_impl.h
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci_psycho.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci_sabre.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci_schizo.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/pci_sun4v.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/power.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/prom.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/sbus.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/smp.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/time.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/traps.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/kernel/unaligned.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/mm/init.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/solaris/fs.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/sparc64/solaris/misc.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/um/Kconfig.debug
浏览文件 @ 62ed948c
此差异已折叠。
arch/um/drivers/mconsole_kern.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/um/kernel/time_kern.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/um/sys-ppc/misc.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/v850/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/ia32/ia32entry.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/kernel/acpi/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/kernel/acpi/processor.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
arch/x86_64/kernel/acpi/sleep.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/kernel/apic.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/kernel/i387.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/kernel/setup.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/mm/srat.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/x86_64/pci/mmconfig.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/xtensa/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
arch/xtensa/boot/lib/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
arch/xtensa/kernel/entry.S
浏览文件 @ 62ed948c
此差异已折叠。
arch/xtensa/kernel/pci.c
浏览文件 @ 62ed948c
此差异已折叠。
arch/xtensa/kernel/signal.c
浏览文件 @ 62ed948c
此差异已折叠。
block/Kconfig.iosched
浏览文件 @ 62ed948c
此差异已折叠。
block/as-iosched.c
浏览文件 @ 62ed948c
此差异已折叠。
block/cfq-iosched.c
浏览文件 @ 62ed948c
此差异已折叠。
block/deadline-iosched.c
浏览文件 @ 62ed948c
此差异已折叠。
block/elevator.c
浏览文件 @ 62ed948c
此差异已折叠。
block/genhd.c
浏览文件 @ 62ed948c
此差异已折叠。
block/ll_rw_blk.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/acpi_memhotplug.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/asus_acpi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/bus.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsfield.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsinit.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsmethod.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsmthdat.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsobject.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsopcode.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dsutils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dswexec.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dswload.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dswscope.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/dispatcher/dswstate.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/ec.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evevent.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evgpe.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evgpeblk.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evmisc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evregion.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evrgnini.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evsci.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evxface.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evxfevnt.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/events/evxfregn.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exconfig.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exconvrt.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/excreate.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exdump.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exfield.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exfldio.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exmisc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exmutex.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exnames.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exoparg1.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exoparg2.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exoparg3.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exoparg6.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exprep.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exregion.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exresnte.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exresolv.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exresop.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exstore.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exstoren.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exstorob.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exsystem.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/executer/exutils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/fan.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/hardware/hwacpi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/hardware/hwgpe.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/hardware/hwregs.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/hardware/hwsleep.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/hardware/hwtimer.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/hotkey.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/ibm_acpi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/motherboard.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsaccess.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsalloc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsdump.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsdumpdv.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nseval.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsinit.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsload.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsnames.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsobject.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsparse.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nssearch.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsutils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nswalk.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsxfeval.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsxfname.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/namespace/nsxfobj.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/numa.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/osl.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psargs.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psloop.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psopcode.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psparse.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psscope.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/pstree.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psutils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/pswalk.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/parser/psxface.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/pci_link.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/processor_core.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/processor_idle.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/processor_perflib.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rscalc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rscreate.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rsdump.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rsinfo.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rslist.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rsmisc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rsutils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/resources/rsxface.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/scan.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/sleep/main.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/sleep/wakeup.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/system.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbconvrt.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbget.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbgetall.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbinstal.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbrsdt.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbutils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbxface.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/tables/tbxfroot.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/thermal.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utalloc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utcache.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utcopy.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utdebug.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utdelete.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/uteval.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utglobal.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utinit.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utmath.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utmisc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utmutex.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utobject.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utresrc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utstate.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utilities/utxface.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/utils.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/acpi/video.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/attribute_container.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/base.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/bus.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/class.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/core.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/firmware_class.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/hypervisor.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/init.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/isa.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/platform.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/power/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/power/resume.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/power/suspend.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/power/trace.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/base/sys.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/DAC960.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/amiflop.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/cciss.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/cciss.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/cciss_scsi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/cpqarray.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/loop.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/nbd.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/ub.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/block/viodasd.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/cdrom/mcdx.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/cdrom/viocd.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/agp/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/agp/hp-agp.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/applicom.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/cyclades.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/i915_dma.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/i915_drm.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/i915_drv.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/i915_irq.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/radeon_cp.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/radeon_drm.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/radeon_drv.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/drm/radeon_state.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/esp.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/hpet.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/hvc_console.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/hvc_rtas.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/hvsi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/ip2/ip2main.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/ipmi/ipmi_watchdog.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/isicom.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/keyboard.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/mmtimer.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/mxser.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/n_r3964.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/pcmcia/synclink_cs.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/rocket.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/rtc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/sonypi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/specialix.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/synclink_gt.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/synclinkmp.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/tty_io.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/char/viotape.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/connector/cn_proc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/connector/connector.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/cpufreq/cpufreq_ondemand.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/firmware/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/firmware/dmi_scan.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/abituguru.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/f71805f.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/hdaps.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/hwmon-vid.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/lm70.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/lm83.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/smsc47m192.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/w83627ehf.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/w83791d.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/hwmon/w83792d.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/i2c-i801.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/i2c-nforce2.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/i2c-ocores.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/i2c-piix4.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/busses/scx200_acb.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/chips/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/chips/m41t00.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/i2c-core.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/i2c/i2c-dev.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-cd.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-dma.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-floppy.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-io.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-iops.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-lib.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-tape.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide-taskfile.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/ide.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/legacy/q40ide.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/pci/amd74xx.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/pci/sgiioc4.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ide/pci/trm290.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/ieee1394/nodemgr.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/Kconfig 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/Makefile 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/iscsi_iser.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/iscsi_iser.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/iser_initiator.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/iser_memory.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/infiniband/ulp/iser/iser_verbs.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/input/evdev.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/input/keyboard/amikbd.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/input/misc/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/input/misc/sparcspkr.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/input/serio/i8042-sparcio.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/input/touchscreen/ads7846.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/capi/capifs.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/gigaset/common.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/gigaset/gigaset.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/gigaset/interface.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/gigaset/proc.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/i4l/isdn_common.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/isdn/sc/ioctl.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/leds/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/leds/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/leds/leds-ams-delta.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/leds/ledtrig-heartbeat.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/macintosh/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/macintosh/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/macintosh/adbhid.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/macintosh/via-pmu-backlight.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/macintosh/via-pmu.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/md/raid6algos.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/common/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/common/ir-functions.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/common/ir-keymaps.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/common/saa7146_fops.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/common/saa7146_hlp.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/common/saa7146_vv_ksyms.c 已删除 100644 → 0
浏览文件 @ 17ffc7ba
此差异已折叠。
drivers/media/dvb/b2c2/flexcop.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/bt8xx/bt878.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/bt8xx/dst.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/bt8xx/dst_ca.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/bt8xx/dvb-bt8xx.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/bt8xx/dvb-bt8xx.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/cinergyT2/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-core/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-core/dmxdev.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-core/dvb_math.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-core/dvb_math.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-core/dvbdev.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-core/dvbdev.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/cxusb.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/digitv.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/dvb-usb.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/gp8psk-fe.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/gp8psk.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/gp8psk.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/dvb-usb/umt-010.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/bsbe1.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/bsru6.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/isl6421.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/isl6421.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/lg_h06xf.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/lnbp21.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/mt312.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/mt312.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/mt352.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/frontends/mt352.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/pluto2/pluto2.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/ttpci/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/ttpci/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/ttpci/av7110.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/ttpci/budget-av.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/ttpci/budget-ci.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/dvb/ttpci/budget.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/miropcm20-rds.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-aimslab.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-aztech.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-cadet.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-gemtek.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-maestro.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-rtrack2.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-sf16fmi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-trust.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-typhoon.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/radio/radio-zoltrix.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/arv.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/bt866.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/bt8xx/bttv.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/bt8xx/bttvp.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/bw-qcam.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/c-qcam.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cpia.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cpia.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cpia2/cpia2.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cpia_pp.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cpia_usb.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cx2341x.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cx88/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cx88/cx88-dvb.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cx88/cx88-i2c.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cx88/cx88-vbi.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/cx88/cx88.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/dsbr100.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/em28xx/em28xx.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/ir-kbd-i2c.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/ks0127.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/ks0127.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/meye.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/ov511.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/ov511.h
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/planb.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pms.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/Kconfig
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/Makefile
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-ctrl.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-dec1.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-dec1.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-dec23.c 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-dec23.h 0 → 100644
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-if.c
浏览文件 @ 62ed948c
此差异已折叠。
drivers/media/video/pwc/pwc-kiara.c
浏览文件 @ 62ed948c
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或