Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 2 年 前同步成功

通知 173
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 8c82a17e 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge commit 'v2.6.28-rc1' into sched/urgent

上级 4ce72a2c 57f8f7b6
展开全部 隐藏空白更改
内联 并排
Showing with 56788 addition and 11031 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.mailmap
浏览文件 @ 8c82a17e
......@@ -66,6 +66,7 @@ Kenneth W Chen <kenneth.w.chen@intel.com>
Koushik <raghavendra.koushik@neterion.com>
Leonid I Ananiev <leonid.i.ananiev@intel.com>
Linas Vepstas <linas@austin.ibm.com>
Mark Brown <broonie@sirena.org.uk>
Matthieu CASTET <castet.matthieu@free.fr>
Michael Buesch <mb@bu3sch.de>
Michael Buesch <mbuesch@freenet.de>
......
CREDITS
浏览文件 @ 8c82a17e
......@@ -598,6 +598,11 @@ S: Tamsui town, Taipei county,
S: Taiwan 251
S: Republic of China
N: Reinette Chatre
E: reinette.chatre@intel.com
D: WiMedia Link Protocol implementation
D: UWB stack bits and pieces
N: Michael Elizabeth Chastain
E: mec@shout.net
D: Configure, Menuconfig, xconfig
......@@ -1653,14 +1658,14 @@ S: Chapel Hill, North Carolina 27514-4818
S: USA
N: Dave Jones
E: davej@codemonkey.org.uk
E: davej@redhat.com
W: http://www.codemonkey.org.uk
D: x86 errata/setup maintenance.
D: AGPGART driver.
D: Assorted VIA x86 support.
D: 2.5 AGPGART overhaul.
D: CPUFREQ maintenance.
D: Backport/Forwardport merge monkey.
D: Various Janitor work.
S: United Kingdom
D: Fedora kernel maintainence.
D: Misc/Other.
S: 314 Littleton Rd, Westford, MA 01886, USA
N: Martin Josfsson
E: gandalf@wlug.westbo.se
......@@ -2695,6 +2700,12 @@ S: Demonstratsii 8-382
S: Tula 300000
S: Russia
N: Inaky Perez-Gonzalez
E: inaky.perez-gonzalez@intel.com
D: UWB stack, HWA-RC driver and HWA-HC drivers
D: Wireless USB additions to the USB stack
D: WiMedia Link Protocol bits and pieces
N: Gordon Peters
E: GordPeters@smarttech.com
D: Isochronous receive for IEEE 1394 driver (OHCI module).
......
Documentation/ABI/stable/sysfs-driver-usb-usbtmc 0 → 100644
浏览文件 @ 8c82a17e
What: /sys/bus/usb/drivers/usbtmc/devices/*/interface_capabilities
What: /sys/bus/usb/drivers/usbtmc/devices/*/device_capabilities
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
These files show the various USB TMC capabilities as described
by the device itself. The full description of the bitfields
can be found in the USB TMC documents from the USB-IF entitled
"Universal Serial Bus Test and Measurement Class Specification
(USBTMC) Revision 1.0" section 4.2.1.8.
The files are read only.
What: /sys/bus/usb/drivers/usbtmc/devices/*/usb488_interface_capabilities
What: /sys/bus/usb/drivers/usbtmc/devices/*/usb488_device_capabilities
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
These files show the various USB TMC capabilities as described
by the device itself. The full description of the bitfields
can be found in the USB TMC documents from the USB-IF entitled
"Universal Serial Bus Test and Measurement Class, Subclass
USB488 Specification (USBTMC-USB488) Revision 1.0" section
4.2.2.
The files are read only.
What: /sys/bus/usb/drivers/usbtmc/devices/*/TermChar
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
This file is the TermChar value to be sent to the USB TMC
device as described by the document, "Universal Serial Bus Test
and Measurement Class Specification
(USBTMC) Revision 1.0" as published by the USB-IF.
Note that the TermCharEnabled file determines if this value is
sent to the device or not.
What: /sys/bus/usb/drivers/usbtmc/devices/*/TermCharEnabled
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
This file determines if the TermChar is to be sent to the
device on every transaction or not. For more details about
this, please see the document, "Universal Serial Bus Test and
Measurement Class Specification (USBTMC) Revision 1.0" as
published by the USB-IF.
What: /sys/bus/usb/drivers/usbtmc/devices/*/auto_abort
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
This file determines if the the transaction of the USB TMC
device is to be automatically aborted if there is any error.
For more details about this, please see the document,
"Universal Serial Bus Test and Measurement Class Specification
(USBTMC) Revision 1.0" as published by the USB-IF.
Documentation/ABI/testing/sysfs-bus-umc 0 → 100644
浏览文件 @ 8c82a17e
What: /sys/bus/umc/
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The Wireless Host Controller Interface (WHCI)
specification describes a PCI-based device with
multiple capabilities; the UWB Multi-interface
Controller (UMC).
The umc bus presents each of the individual
capabilties as a device.
What: /sys/bus/umc/devices/.../capability_id
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The ID of this capability, with 0 being the radio
controller capability.
What: /sys/bus/umc/devices/.../version
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The specification version this capability's hardware
interface complies with.
Documentation/ABI/testing/sysfs-bus-usb
浏览文件 @ 8c82a17e
......@@ -85,3 +85,62 @@ Description:
Users:
PowerTOP <power@bughost.org>
http://www.lesswatts.org/projects/powertop/
What: /sys/bus/usb/device/<busnum>-<devnum>...:<config num>-<interface num>/supports_autosuspend
Date: January 2008
KernelVersion: 2.6.27
Contact: Sarah Sharp <sarah.a.sharp@intel.com>
Description:
When read, this file returns 1 if the interface driver
for this interface supports autosuspend. It also
returns 1 if no driver has claimed this interface, as an
unclaimed interface will not stop the device from being
autosuspended if all other interface drivers are idle.
The file returns 0 if autosuspend support has not been
added to the driver.
Users:
USB PM tool
git://git.moblin.org/users/sarah/usb-pm-tool/
What: /sys/bus/usb/device/.../authorized
Date: July 2008
KernelVersion: 2.6.26
Contact: David Vrabel <david.vrabel@csr.com>
Description:
Authorized devices are available for use by device
drivers, non-authorized one are not. By default, wired
USB devices are authorized.
Certified Wireless USB devices are not authorized
initially and should be (by writing 1) after the
device has been authenticated.
What: /sys/bus/usb/device/.../wusb_cdid
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
For Certified Wireless USB devices only.
A devices's CDID, as 16 space-separated hex octets.
What: /sys/bus/usb/device/.../wusb_ck
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
For Certified Wireless USB devices only.
Write the device's connection key (CK) to start the
authentication of the device. The CK is 16
space-separated hex octets.
What: /sys/bus/usb/device/.../wusb_disconnect
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
For Certified Wireless USB devices only.
Write a 1 to force the device to disconnect
(equivalent to unplugging a wired USB device).
Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg 0 → 100644
浏览文件 @ 8c82a17e
Where: /sys/bus/usb/.../powered
Date: August 2008
Kernel Version: 2.6.26
Contact: Harrison Metzger <harrisonmetz@gmail.com>
Description: Controls whether the device's display will powered.
A value of 0 is off and a non-zero value is on.
Where: /sys/bus/usb/.../mode_msb
Where: /sys/bus/usb/.../mode_lsb
Date: August 2008
Kernel Version: 2.6.26
Contact: Harrison Metzger <harrisonmetz@gmail.com>
Description: Controls the devices display mode.
For a 6 character display the values are
MSB 0x06; LSB 0x3F, and
for an 8 character display the values are
MSB 0x08; LSB 0xFF.
Where: /sys/bus/usb/.../textmode
Date: August 2008
Kernel Version: 2.6.26
Contact: Harrison Metzger <harrisonmetz@gmail.com>
Description: Controls the way the device interprets its text buffer.
raw: each character controls its segment manually
hex: each character is between 0-15
ascii: each character is between '0'-'9' and 'A'-'F'.
Where: /sys/bus/usb/.../text
Date: August 2008
Kernel Version: 2.6.26
Contact: Harrison Metzger <harrisonmetz@gmail.com>
Description: The text (or data) for the device to display
Where: /sys/bus/usb/.../decimals
Date: August 2008
Kernel Version: 2.6.26
Contact: Harrison Metzger <harrisonmetz@gmail.com>
Description: Controls the decimal places on the device.
To set the nth decimal place, give this field
the value of 10 ** n. Assume this field has
the value k and has 1 or more decimal places set,
to set the mth place (where m is not already set),
change this fields value to k + 10 ** m.
\ No newline at end of file
Documentation/ABI/testing/sysfs-class-usb_host 0 → 100644
浏览文件 @ 8c82a17e
What: /sys/class/usb_host/usb_hostN/wusb_chid
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
Write the CHID (16 space-separated hex octets) for this host controller.
This starts the host controller, allowing it to accept connection from
WUSB devices.
Set an all zero CHID to stop the host controller.
What: /sys/class/usb_host/usb_hostN/wusb_trust_timeout
Date: July 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
Devices that haven't sent a WUSB packet to the host
within 'wusb_trust_timeout' ms are considered to have
disconnected and are removed. The default value of
4000 ms is the value required by the WUSB
specification.
Since this relates to security (specifically, the
lifetime of PTKs and GTKs) it should not be changed
from the default.
Documentation/ABI/testing/sysfs-class-uwb_rc 0 → 100644
浏览文件 @ 8c82a17e
What: /sys/class/uwb_rc
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
Interfaces for WiMedia Ultra Wideband Common Radio
Platform (UWB) radio controllers.
Familiarity with the ECMA-368 'High Rate Ultra
Wideband MAC and PHY Specification' is assumed.
What: /sys/class/uwb_rc/beacon_timeout_ms
Date: July 2008
KernelVersion: 2.6.27
Description:
If no beacons are received from a device for at least
this time, the device will be considered to have gone
and it will be removed. The default is 3 superframes
(~197 ms) as required by the specification.
What: /sys/class/uwb_rc/uwbN/
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
An individual UWB radio controller.
What: /sys/class/uwb_rc/uwbN/beacon
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
Write:
<channel> [<bpst offset>]
to start beaconing on a specific channel, or stop
beaconing if <channel> is -1. Valid channels depends
on the radio controller's supported band groups.
<bpst offset> may be used to try and join a specific
beacon group if more than one was found during a scan.
What: /sys/class/uwb_rc/uwbN/scan
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
Write:
<channel> <type> [<bpst offset>]
to start (or stop) scanning on a channel. <type> is one of:
0 - scan
1 - scan outside BP
2 - scan while inactive
3 - scanning disabled
4 - scan (with start time of <bpst offset>)
What: /sys/class/uwb_rc/uwbN/mac_address
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
The EUI-48, in colon-separated hex octets, for this
radio controller. A write will change the radio
controller's EUI-48 but only do so while the device is
not beaconing or scanning.
What: /sys/class/uwb_rc/uwbN/wusbhc
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
A symlink to the device (if any) of the WUSB Host
Controller PAL using this radio controller.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
A neighbour UWB device that has either been detected
as part of a scan or is a member of the radio
controllers beacon group.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/BPST
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
The time (using the radio controllers internal 1 ms
interval superframe timer) of the last beacon from
this device was received.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/DevAddr
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
The current DevAddr of this device in colon separated
hex octets.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/EUI_48
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
The EUI-48 of this device in colon separated hex
octets.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/BPST
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
What: /sys/class/uwb_rc/uwbN/<EUI-48>/IEs
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
The latest IEs included in this device's beacon, in
space separated hex octets with one IE per line.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/LQE
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
Link Quality Estimate - the Signal to Noise Ratio
(SNR) of all packets received from this device in dB.
This gives an estimate on a suitable PHY rate. Refer
to [ECMA-368] section 13.3 for more details.
What: /sys/class/uwb_rc/uwbN/<EUI-48>/RSSI
Date: July 2008
KernelVersion: 2.6.27
Contact: linux-usb@vger.kernel.org
Description:
Received Signal Strength Indication - the strength of
the received signal in dB. LQE is a more useful
measure of the radio link quality.
Documentation/ABI/testing/sysfs-wusb_cbaf 0 → 100644
浏览文件 @ 8c82a17e
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_*
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
Various files for managing Cable Based Association of
(wireless) USB devices.
The sequence of operations should be:
1. Device is plugged in.
2. The connection manager (CM) sees a device with CBA capability.
(the wusb_chid etc. files in /sys/devices/blah/OURDEVICE).
3. The CM writes the host name, supported band groups,
and the CHID (host ID) into the wusb_host_name,
wusb_host_band_groups and wusb_chid files. These
get sent to the device and the CDID (if any) for
this host is requested.
4. The CM can verify that the device's supported band
groups (wusb_device_band_groups) are compatible
with the host.
5. The CM reads the wusb_cdid file.
6. The CM looks it up its database.
- If it has a matching CHID,CDID entry, the device
has been authorized before and nothing further
needs to be done.
- If the CDID is zero (or the CM doesn't find a
matching CDID in its database), the device is
assumed to be not known. The CM may associate
the host with device by: writing a randomly
generated CDID to wusb_cdid and then a random CK
to wusb_ck (this uploads the new CC to the
device).
CMD may choose to prompt the user before
associating with a new device.
7. Device is unplugged.
References:
[WUSB-AM] Association Models Supplement to the
Certified Wireless Universal Serial Bus
Specification, version 1.0.
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_chid
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The CHID of the host formatted as 16 space-separated
hex octets.
Writes fetches device's supported band groups and the
the CDID for any existing association with this host.
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_host_name
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
A friendly name for the host as a UTF-8 encoded string.
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_host_band_groups
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The band groups supported by the host, in the format
defined in [WUSB-AM].
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_device_band_groups
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The band groups supported by the device, in the format
defined in [WUSB-AM].
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_cdid
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The device's CDID formatted as 16 space-separated hex
octets.
What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_ck
Date: August 2008
KernelVersion: 2.6.27
Contact: David Vrabel <david.vrabel@csr.com>
Description:
Write 16 space-separated random, hex octets to
associate with the device.
Documentation/DocBook/gadget.tmpl
浏览文件 @ 8c82a17e
......@@ -557,6 +557,9 @@ Near-term plans include converting all of them, except for "gadgetfs".
</para>
!Edrivers/usb/gadget/f_acm.c
!Edrivers/usb/gadget/f_ecm.c
!Edrivers/usb/gadget/f_subset.c
!Edrivers/usb/gadget/f_obex.c
!Edrivers/usb/gadget/f_serial.c
</sect1>
......
Documentation/DocBook/kernel-hacking.tmpl
浏览文件 @ 8c82a17e
......@@ -1105,7 +1105,7 @@ static struct block_device_operations opt_fops = {
</listitem>
<listitem>
<para>
Function names as strings (__FUNCTION__).
Function names as strings (__func__).
</para>
</listitem>
<listitem>
......
Documentation/MSI-HOWTO.txt
浏览文件 @ 8c82a17e
......@@ -236,10 +236,8 @@ software system can set different pages for controlling accesses to the
MSI-X structure. The implementation of MSI support requires the PCI
subsystem, not a device driver, to maintain full control of the MSI-X
table/MSI-X PBA (Pending Bit Array) and MMIO address space of the MSI-X
table/MSI-X PBA. A device driver is prohibited from requesting the MMIO
address space of the MSI-X table/MSI-X PBA. Otherwise, the PCI subsystem
will fail enabling MSI-X on its hardware device when it calls the function
pci_enable_msix().
table/MSI-X PBA. A device driver should not access the MMIO address
space of the MSI-X table/MSI-X PBA.
5.3.2 API pci_enable_msix
......
Documentation/PCI/pci.txt
浏览文件 @ 8c82a17e
......@@ -163,6 +163,10 @@ need pass only as many optional fields as necessary:
o class and classmask fields default to 0
o driver_data defaults to 0UL.
Note that driver_data must match the value used by any of the pci_device_id
entries defined in the driver. This makes the driver_data field mandatory
if all the pci_device_id entries have a non-zero driver_data value.
Once added, the driver probe routine will be invoked for any unclaimed
PCI devices listed in its (newly updated) pci_ids list.
......
Documentation/PCI/pcieaer-howto.txt
浏览文件 @ 8c82a17e
......@@ -203,22 +203,17 @@ to mmio_enabled.
3.3 helper functions
3.3.1 int pci_find_aer_capability(struct pci_dev *dev);
pci_find_aer_capability locates the PCI Express AER capability
in the device configuration space. If the device doesn't support
PCI-Express AER, the function returns 0.
3.3.2 int pci_enable_pcie_error_reporting(struct pci_dev *dev);
3.3.1 int pci_enable_pcie_error_reporting(struct pci_dev *dev);
pci_enable_pcie_error_reporting enables the device to send error
messages to root port when an error is detected. Note that devices
don't enable the error reporting by default, so device drivers need
call this function to enable it.
3.3.3 int pci_disable_pcie_error_reporting(struct pci_dev *dev);
3.3.2 int pci_disable_pcie_error_reporting(struct pci_dev *dev);
pci_disable_pcie_error_reporting disables the device to send error
messages to root port when an error is detected.
3.3.4 int pci_cleanup_aer_uncorrect_error_status(struct pci_dev *dev);
3.3.3 int pci_cleanup_aer_uncorrect_error_status(struct pci_dev *dev);
pci_cleanup_aer_uncorrect_error_status cleanups the uncorrectable
error status register.
......
Documentation/cgroups/freezer-subsystem.txt 0 → 100644
浏览文件 @ 8c82a17e
The cgroup freezer is useful to batch job management system which start
and stop sets of tasks in order to schedule the resources of a machine
according to the desires of a system administrator. This sort of program
is often used on HPC clusters to schedule access to the cluster as a
whole. The cgroup freezer uses cgroups to describe the set of tasks to
be started/stopped by the batch job management system. It also provides
a means to start and stop the tasks composing the job.
The cgroup freezer will also be useful for checkpointing running groups
of tasks. The freezer allows the checkpoint code to obtain a consistent
image of the tasks by attempting to force the tasks in a cgroup into a
quiescent state. Once the tasks are quiescent another task can
walk /proc or invoke a kernel interface to gather information about the
quiesced tasks. Checkpointed tasks can be restarted later should a
recoverable error occur. This also allows the checkpointed tasks to be
migrated between nodes in a cluster by copying the gathered information
to another node and restarting the tasks there.
Sequences of SIGSTOP and SIGCONT are not always sufficient for stopping
and resuming tasks in userspace. Both of these signals are observable
from within the tasks we wish to freeze. While SIGSTOP cannot be caught,
blocked, or ignored it can be seen by waiting or ptracing parent tasks.
SIGCONT is especially unsuitable since it can be caught by the task. Any
programs designed to watch for SIGSTOP and SIGCONT could be broken by
attempting to use SIGSTOP and SIGCONT to stop and resume tasks. We can
demonstrate this problem using nested bash shells:
$ echo $$
16644
$ bash
$ echo $$
16690
From a second, unrelated bash shell:
$ kill -SIGSTOP 16690
$ kill -SIGCONT 16990
<at this point 16990 exits and causes 16644 to exit too>
This happens because bash can observe both signals and choose how it
responds to them.
Another example of a program which catches and responds to these
signals is gdb. In fact any program designed to use ptrace is likely to
have a problem with this method of stopping and resuming tasks.
In contrast, the cgroup freezer uses the kernel freezer code to
prevent the freeze/unfreeze cycle from becoming visible to the tasks
being frozen. This allows the bash example above and gdb to run as
expected.
The freezer subsystem in the container filesystem defines a file named
freezer.state. Writing "FROZEN" to the state file will freeze all tasks in the
cgroup. Subsequently writing "THAWED" will unfreeze the tasks in the cgroup.
Reading will return the current state.
* Examples of usage :
# mkdir /containers/freezer
# mount -t cgroup -ofreezer freezer /containers
# mkdir /containers/0
# echo $some_pid > /containers/0/tasks
to get status of the freezer subsystem :
# cat /containers/0/freezer.state
THAWED
to freeze all tasks in the container :
# echo FROZEN > /containers/0/freezer.state
# cat /containers/0/freezer.state
FREEZING
# cat /containers/0/freezer.state
FROZEN
to unfreeze all tasks in the container :
# echo THAWED > /containers/0/freezer.state
# cat /containers/0/freezer.state
THAWED
This is the basic mechanism which should do the right thing for user space task
in a simple scenario.
It's important to note that freezing can be incomplete. In that case we return
EBUSY. This means that some tasks in the cgroup are busy doing something that
prevents us from completely freezing the cgroup at this time. After EBUSY,
the cgroup will remain partially frozen -- reflected by freezer.state reporting
"FREEZING" when read. The state will remain "FREEZING" until one of these
things happens:
1) Userspace cancels the freezing operation by writing "THAWED" to
the freezer.state file
2) Userspace retries the freezing operation by writing "FROZEN" to
the freezer.state file (writing "FREEZING" is not legal
and returns EIO)
3) The tasks that blocked the cgroup from entering the "FROZEN"
state disappear from the cgroup's set of tasks.
Documentation/controllers/memory.txt
浏览文件 @ 8c82a17e
......@@ -112,14 +112,22 @@ the per cgroup LRU.
2.2.1 Accounting details
All mapped pages (RSS) and unmapped user pages (Page Cache) are accounted.
RSS pages are accounted at the time of page_add_*_rmap() unless they've already
been accounted for earlier. A file page will be accounted for as Page Cache;
it's mapped into the page tables of a process, duplicate accounting is carefully
avoided. Page Cache pages are accounted at the time of add_to_page_cache().
The corresponding routines that remove a page from the page tables or removes
a page from Page Cache is used to decrement the accounting counters of the
cgroup.
All mapped anon pages (RSS) and cache pages (Page Cache) are accounted.
(some pages which never be reclaimable and will not be on global LRU
are not accounted. we just accounts pages under usual vm management.)
RSS pages are accounted at page_fault unless they've already been accounted
for earlier. A file page will be accounted for as Page Cache when it's
inserted into inode (radix-tree). While it's mapped into the page tables of
processes, duplicate accounting is carefully avoided.
A RSS page is unaccounted when it's fully unmapped. A PageCache page is
unaccounted when it's removed from radix-tree.
At page migration, accounting information is kept.
Note: we just account pages-on-lru because our purpose is to control amount
of used pages. not-on-lru pages are tend to be out-of-control from vm view.
2.3 Shared Page Accounting
......
Documentation/cpusets.txt
浏览文件 @ 8c82a17e
......@@ -48,7 +48,7 @@ hooks, beyond what is already present, required to manage dynamic
job placement on large systems.
Cpusets use the generic cgroup subsystem described in
Documentation/cgroup.txt.
Documentation/cgroups/cgroups.txt.
Requests by a task, using the sched_setaffinity(2) system call to
include CPUs in its CPU affinity mask, and using the mbind(2) and
......
Documentation/devices.txt
浏览文件 @ 8c82a17e
......@@ -2571,6 +2571,9 @@ Your cooperation is appreciated.
160 = /dev/usb/legousbtower0 1st USB Legotower device
...
175 = /dev/usb/legousbtower15 16th USB Legotower device
176 = /dev/usb/usbtmc1 First USB TMC device
...
192 = /dev/usb/usbtmc16 16th USB TMC device
240 = /dev/usb/dabusb0 First daubusb device
...
243 = /dev/usb/dabusb3 Fourth dabusb device
......
Documentation/feature-removal-schedule.txt
浏览文件 @ 8c82a17e
......@@ -359,3 +359,11 @@ Why: The 2.6 kernel supports direct writing to ide CD drives, which
eliminates the need for ide-scsi. The new method is more
efficient in every way.
Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
---------------------------
What: i2c_attach_client(), i2c_detach_client(), i2c_driver->detach_client()
When: 2.6.29 (ideally) or 2.6.30 (more likely)
Why: Deprecated by the new (standard) device driver binding model. Use
i2c_driver->probe() and ->remove() instead.
Who: Jean Delvare <khali@linux-fr.org>
Documentation/filesystems/ext3.txt
浏览文件 @ 8c82a17e
......@@ -96,6 +96,11 @@ errors=remount-ro(*) Remount the filesystem read-only on an error.
errors=continue Keep going on a filesystem error.
errors=panic Panic and halt the machine if an error occurs.
data_err=ignore(*) Just print an error message if an error occurs
in a file data buffer in ordered mode.
data_err=abort Abort the journal if an error occurs in a file
data buffer in ordered mode.
grpid Give objects the same group ID as their creator.
bsdgroups
......
Documentation/filesystems/ext4.txt
浏览文件 @ 8c82a17e
......@@ -2,19 +2,24 @@
Ext4 Filesystem
===============
This is a development version of the ext4 filesystem, an advanced level
of the ext3 filesystem which incorporates scalability and reliability
enhancements for supporting large filesystems (64 bit) in keeping with
increasing disk capacities and state-of-the-art feature requirements.
Ext4 is an an advanced level of the ext3 filesystem which incorporates
scalability and reliability enhancements for supporting large filesystems
(64 bit) in keeping with increasing disk capacities and state-of-the-art
feature requirements.
Mailing list: linux-ext4@vger.kernel.org
Mailing list: linux-ext4@vger.kernel.org
Web site: http://ext4.wiki.kernel.org
1. Quick usage instructions:
===========================
Note: More extensive information for getting started with ext4 can be
found at the ext4 wiki site at the URL:
http://ext4.wiki.kernel.org/index.php/Ext4_Howto
- Compile and install the latest version of e2fsprogs (as of this
writing version 1.41) from:
writing version 1.41.3) from:
http://sourceforge.net/project/showfiles.php?group_id=2406
......@@ -36,11 +41,9 @@ Mailing list: linux-ext4@vger.kernel.org
# mke2fs -t ext4 /dev/hda1
Or configure an existing ext3 filesystem to support extents and set
the test_fs flag to indicate that it's ok for an in-development
filesystem to touch this filesystem:
Or to configure an existing ext3 filesystem to support extents:
# tune2fs -O extents -E test_fs /dev/hda1
# tune2fs -O extents /dev/hda1
If the filesystem was created with 128 byte inodes, it can be
converted to use 256 byte for greater efficiency via:
......@@ -104,8 +107,8 @@ exist yet so I'm not sure they're in the near-term roadmap.
The big performance win will come with mballoc, delalloc and flex_bg
grouping of bitmaps and inode tables. Some test results available here:
- http://www.bullopensource.org/ext4/20080530/ffsb-write-2.6.26-rc2.html
- http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html
- http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-write-2.6.27-rc1.html
- http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-readwrite-2.6.27-rc1.html
3. Options
==========
......@@ -214,9 +217,6 @@ noreservation
bsddf (*) Make 'df' act like BSD.
minixdf Make 'df' act like Minix.
check=none Don't do extra checking of bitmaps on mount.
nocheck
debug Extra debugging information is sent to syslog.
errors=remount-ro(*) Remount the filesystem read-only on an error.
......@@ -253,8 +253,6 @@ nobh (a) cache disk block mapping information
"nobh" option tries to avoid associating buffer
heads (supported only for "writeback" mode).
mballoc (*) Use the multiple block allocator for block allocation
nomballoc disabled multiple block allocator for block allocation.
stripe=n Number of filesystem blocks that mballoc will try
to use for allocation size and alignment. For RAID5/6
systems this should be the number of data
......
Documentation/filesystems/proc.txt
浏览文件 @ 8c82a17e
......@@ -1384,15 +1384,18 @@ causes the kernel to prefer to reclaim dentries and inodes.
dirty_background_ratio
----------------------
Contains, as a percentage of total system memory, the number of pages at which
the pdflush background writeback daemon will start writing out dirty data.
Contains, as a percentage of the dirtyable system memory (free pages + mapped
pages + file cache, not including locked pages and HugePages), the number of
pages at which the pdflush background writeback daemon will start writing out
dirty data.
dirty_ratio
-----------------
Contains, as a percentage of total system memory, the number of pages at which
a process which is generating disk writes will itself start writing out dirty
data.
Contains, as a percentage of the dirtyable system memory (free pages + mapped
pages + file cache, not including locked pages and HugePages), the number of
pages at which a process which is generating disk writes will itself start
writing out dirty data.
dirty_writeback_centisecs
-------------------------
......@@ -2412,24 +2415,29 @@ will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
of memory types. If a bit of the bitmask is set, memory segments of the
corresponding memory type are dumped, otherwise they are not dumped.
The following 4 memory types are supported:
The following 7 memory types are supported:
- (bit 0) anonymous private memory
- (bit 1) anonymous shared memory
- (bit 2) file-backed private memory
- (bit 3) file-backed shared memory
- (bit 4) ELF header pages in file-backed private memory areas (it is
effective only if the bit 2 is cleared)
- (bit 5) hugetlb private memory
- (bit 6) hugetlb shared memory
Note that MMIO pages such as frame buffer are never dumped and vDSO pages
are always dumped regardless of the bitmask status.
Default value of coredump_filter is 0x3; this means all anonymous memory
segments are dumped.
Note bit 0-4 doesn't effect any hugetlb memory. hugetlb memory are only
effected by bit 5-6.
Default value of coredump_filter is 0x23; this means all anonymous memory
segments and hugetlb private memory are dumped.
If you don't want to dump all shared memory segments attached to pid 1234,
write 1 to the process's proc file.
write 0x21 to the process's proc file.
$ echo 0x1 > /proc/1234/coredump_filter
$ echo 0x21 > /proc/1234/coredump_filter
When a new process is created, the process inherits the bitmask status from its
parent. It is useful to set up coredump_filter before the program runs.
......
Documentation/filesystems/ubifs.txt
浏览文件 @ 8c82a17e
......@@ -86,6 +86,15 @@ norm_unmount (*) commit on unmount; the journal is committed
fast_unmount do not commit on unmount; this option makes
unmount faster, but the next mount slower
because of the need to replay the journal.
bulk_read read more in one go to take advantage of flash
media that read faster sequentially
no_bulk_read (*) do not bulk-read
no_chk_data_crc skip checking of CRCs on data nodes in order to
improve read performance. Use this option only
if the flash media is highly reliable. The effect
of this option is that corruption of the contents
of a file can go unnoticed.
chk_data_crc (*) do not skip checking CRCs on data nodes
Quick usage instructions
......
Documentation/hwmon/adt7470 0 → 100644
浏览文件 @ 8c82a17e
Kernel driver adt7470
=====================
Supported chips:
* Analog Devices ADT7470
Prefix: 'adt7470'
Addresses scanned: I2C 0x2C, 0x2E, 0x2F
Datasheet: Publicly available at the Analog Devices website
Author: Darrick J. Wong
Description
-----------
This driver implements support for the Analog Devices ADT7470 chip. There may
be other chips that implement this interface.
The ADT7470 uses the 2-wire interface compatible with the SMBus 2.0
specification. Using an analog to digital converter it measures up to ten (10)
external temperatures. It has four (4) 16-bit counters for measuring fan speed.
There are four (4) PWM outputs that can be used to control fan speed.
A sophisticated control system for the PWM outputs is designed into the ADT7470
that allows fan speed to be adjusted automatically based on any of the ten
temperature sensors. Each PWM output is individually adjustable and
programmable. Once configured, the ADT7470 will adjust the PWM outputs in
response to the measured temperatures with further host intervention. This
feature can also be disabled for manual control of the PWM's.
Each of the measured inputs (temperature, fan speed) has corresponding high/low
limit values. The ADT7470 will signal an ALARM if any measured value exceeds
either limit.
The ADT7470 DOES NOT sample all inputs continuously. A single pin on the
ADT7470 is connected to a multitude of thermal diodes, but the chip must be
instructed explicitly to read the multitude of diodes. If you want to use
automatic fan control mode, you must manually read any of the temperature
sensors or the fan control algorithm will not run. The chip WILL NOT DO THIS
AUTOMATICALLY; this must be done from userspace. This may be a bug in the chip
design, given that many other AD chips take care of this. The driver will not
read the registers more often than once every 5 seconds. Further,
configuration data is only read once per minute.
Special Features
----------------
The ADT7470 has a 8-bit ADC and is capable of measuring temperatures with 1
degC resolution.
The Analog Devices datasheet is very detailed and describes a procedure for
determining an optimal configuration for the automatic PWM control.
Configuration Notes
-------------------
Besides standard interfaces driver adds the following:
* PWM Control
* pwm#_auto_point1_pwm and pwm#_auto_point1_temp and
* pwm#_auto_point2_pwm and pwm#_auto_point2_temp -
point1: Set the pwm speed at a lower temperature bound.
point2: Set the pwm speed at a higher temperature bound.
The ADT7470 will scale the pwm between the lower and higher pwm speed when
the temperature is between the two temperature boundaries. PWM values range
from 0 (off) to 255 (full speed). Fan speed will be set to maximum when the
temperature sensor associated with the PWM control exceeds
pwm#_auto_point2_temp.
Notes
-----
As stated above, the temperature inputs must be read periodically from
userspace in order for the automatic pwm algorithm to run.
Documentation/hwmon/it87
浏览文件 @ 8c82a17e
......@@ -136,10 +136,10 @@ once-only alarms.
The IT87xx only updates its values each 1.5 seconds; reading it more often
will do no harm, but will return 'old' values.
To change sensor N to a thermistor, 'echo 2 > tempN_type' where N is 1, 2,
To change sensor N to a thermistor, 'echo 4 > tempN_type' where N is 1, 2,
or 3. To change sensor N to a thermal diode, 'echo 3 > tempN_type'.
Give 0 for unused sensor. Any other value is invalid. To configure this at
startup, consult lm_sensors's /etc/sensors.conf. (2 = thermistor;
startup, consult lm_sensors's /etc/sensors.conf. (4 = thermistor;
3 = thermal diode)
......
Documentation/hwmon/lm85
浏览文件 @ 8c82a17e
......@@ -163,16 +163,6 @@ configured individually according to the following options.
* pwm#_auto_pwm_min - this specifies the PWM value for temp#_auto_temp_off
temperature. (PWM value from 0 to 255)
* pwm#_auto_pwm_freq - select base frequency of PWM output. You can select
in range of 10.0 to 94.0 Hz in .1 Hz units.
(Values 100 to 940).
The pwm#_auto_pwm_freq can be set to one of the following 8 values. Setting the
frequency to a value not on this list, will result in the next higher frequency
being selected. The actual device frequency may vary slightly from this
specification as designed by the manufacturer. Consult the datasheet for more
details. (PWM Frequency values: 100, 150, 230, 300, 380, 470, 620, 940)
* pwm#_auto_pwm_minctl - this flags selects for temp#_auto_temp_off temperature
the bahaviour of fans. Write 1 to let fans spinning at
pwm#_auto_pwm_min or write 0 to let them off.
......
Documentation/hwmon/lm87
浏览文件 @ 8c82a17e
......@@ -65,11 +65,10 @@ The LM87 has four pins which can serve one of two possible functions,
depending on the hardware configuration.
Some functions share pins, so not all functions are available at the same
time. Which are depends on the hardware setup. This driver assumes that
the BIOS configured the chip correctly. In that respect, it differs from
the original driver (from lm_sensors for Linux 2.4), which would force the
LM87 to an arbitrary, compile-time chosen mode, regardless of the actual
chipset wiring.
time. Which are depends on the hardware setup. This driver normally
assumes that firmware configured the chip correctly. Where this is not
the case, platform code must set the I2C client's platform_data to point
to a u8 value to be written to the channel register.
For reference, here is the list of exclusive functions:
- in0+in5 (default) or temp3
......
Documentation/hwmon/lm90
浏览文件 @ 8c82a17e
......@@ -11,7 +11,7 @@ Supported chips:
Prefix: 'lm99'
Addresses scanned: I2C 0x4c and 0x4d
Datasheet: Publicly available at the National Semiconductor website
http://www.national.com/pf/LM/LM89.html
http://www.national.com/mpf/LM/LM89.html
* National Semiconductor LM99
Prefix: 'lm99'
Addresses scanned: I2C 0x4c and 0x4d
......@@ -21,18 +21,32 @@ Supported chips:
Prefix: 'lm86'
Addresses scanned: I2C 0x4c
Datasheet: Publicly available at the National Semiconductor website
http://www.national.com/pf/LM/LM86.html
http://www.national.com/mpf/LM/LM86.html
* Analog Devices ADM1032
Prefix: 'adm1032'
Addresses scanned: I2C 0x4c and 0x4d
Datasheet: Publicly available at the Analog Devices website
http://www.analog.com/en/prod/0,2877,ADM1032,00.html
Datasheet: Publicly available at the ON Semiconductor website
http://www.onsemi.com/PowerSolutions/product.do?id=ADM1032
* Analog Devices ADT7461
Prefix: 'adt7461'
Addresses scanned: I2C 0x4c and 0x4d
Datasheet: Publicly available at the Analog Devices website
http://www.analog.com/en/prod/0,2877,ADT7461,00.html
Note: Only if in ADM1032 compatibility mode
Datasheet: Publicly available at the ON Semiconductor website
http://www.onsemi.com/PowerSolutions/product.do?id=ADT7461
* Maxim MAX6646
Prefix: 'max6646'
Addresses scanned: I2C 0x4d
Datasheet: Publicly available at the Maxim website
http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3497
* Maxim MAX6647
Prefix: 'max6646'
Addresses scanned: I2C 0x4e
Datasheet: Publicly available at the Maxim website
http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3497
* Maxim MAX6649
Prefix: 'max6646'
Addresses scanned: I2C 0x4c
Datasheet: Publicly available at the Maxim website
http://www.maxim-ic.com/quick_view2.cfm/qv_pk/3497
* Maxim MAX6657
Prefix: 'max6657'
Addresses scanned: I2C 0x4c
......@@ -70,25 +84,21 @@ Description
The LM90 is a digital temperature sensor. It senses its own temperature as
well as the temperature of up to one external diode. It is compatible
with many other devices such as the LM86, the LM89, the LM99, the ADM1032,
the MAX6657, MAX6658, MAX6659, MAX6680 and the MAX6681 all of which are
supported by this driver.
with many other devices, many of which are supported by this driver.
Note that there is no easy way to differentiate between the MAX6657,
MAX6658 and MAX6659 variants. The extra address and features of the
MAX6659 are not supported by this driver. The MAX6680 and MAX6681 only
differ in their pinout, therefore they obviously can't (and don't need to)
be distinguished. Additionally, the ADT7461 is supported if found in
ADM1032 compatibility mode.
be distinguished.
The specificity of this family of chipsets over the ADM1021/LM84
family is that it features critical limits with hysteresis, and an
increased resolution of the remote temperature measurement.
The different chipsets of the family are not strictly identical, although
very similar. This driver doesn't handle any specific feature for now,
with the exception of SMBus PEC. For reference, here comes a non-exhaustive
list of specific features:
very similar. For reference, here comes a non-exhaustive list of specific
features:
LM90:
* Filter and alert configuration register at 0xBF.
......@@ -114,9 +124,11 @@ ADT7461:
* Lower resolution for remote temperature
MAX6657 and MAX6658:
* Better local resolution
* Remote sensor type selection
MAX6659:
* Better local resolution
* Selectable address
* Second critical temperature limit
* Remote sensor type selection
......@@ -127,7 +139,8 @@ MAX6680 and MAX6681:
All temperature values are given in degrees Celsius. Resolution
is 1.0 degree for the local temperature, 0.125 degree for the remote
temperature.
temperature, except for the MAX6657, MAX6658 and MAX6659 which have a
resolution of 0.125 degree for both temperatures.
Each sensor has its own high and low limits, plus a critical limit.
Additionally, there is a relative hysteresis value common to both critical
......
Documentation/hwmon/pc87360
浏览文件 @ 8c82a17e
......@@ -5,12 +5,7 @@ Supported chips:
* National Semiconductor PC87360, PC87363, PC87364, PC87365 and PC87366
Prefixes: 'pc87360', 'pc87363', 'pc87364', 'pc87365', 'pc87366'
Addresses scanned: none, address read from Super I/O config space
Datasheets:
http://www.national.com/pf/PC/PC87360.html
http://www.national.com/pf/PC/PC87363.html
http://www.national.com/pf/PC/PC87364.html
http://www.national.com/pf/PC/PC87365.html
http://www.national.com/pf/PC/PC87366.html
Datasheets: No longer available
Authors: Jean Delvare <khali@linux-fr.org>
......
Documentation/hwmon/pc87427
浏览文件 @ 8c82a17e
......@@ -5,7 +5,7 @@ Supported chips:
* National Semiconductor PC87427
Prefix: 'pc87427'
Addresses scanned: none, address read from Super I/O config space
Datasheet: http://www.winbond.com.tw/E-WINBONDHTM/partner/apc_007.html
Datasheet: No longer available
Author: Jean Delvare <khali@linux-fr.org>
......
Documentation/hwmon/w83781d
浏览文件 @ 8c82a17e
......@@ -353,7 +353,7 @@ in6=255
# PWM
Additional info about PWM on the AS99127F (may apply to other Asus
* Additional info about PWM on the AS99127F (may apply to other Asus
chips as well) by Jean Delvare as of 2004-04-09:
AS99127F revision 2 seems to have two PWM registers at 0x59 and 0x5A,
......@@ -396,7 +396,7 @@ Please contact us if you can figure out how it is supposed to work. As
long as we don't know more, the w83781d driver doesn't handle PWM on
AS99127F chips at all.
Additional info about PWM on the AS99127F rev.1 by Hector Martin:
* Additional info about PWM on the AS99127F rev.1 by Hector Martin:
I've been fiddling around with the (in)famous 0x59 register and
found out the following values do work as a form of coarse pwm:
......@@ -418,3 +418,36 @@ change.
My mobo is an ASUS A7V266-E. This behavior is similar to what I got
with speedfan under Windows, where 0-15% would be off, 15-2x% (can't
remember the exact value) would be 70% and higher would be full on.
* Additional info about PWM on the AS99127F rev.1 from lm-sensors
ticket #2350:
I conducted some experiment on Asus P3B-F motherboard with AS99127F
(Ver. 1).
I confirm that 0x59 register control the CPU_Fan Header on this
motherboard, and 0x5a register control PWR_Fan.
In order to reduce the dependency of specific fan, the measurement is
conducted with a digital scope without fan connected. I found out that
P3B-F actually output variable DC voltage on fan header center pin,
looks like PWM is filtered on this motherboard.
Here are some of measurements:
0x80 20 mV
0x81 20 mV
0x82 232 mV
0x83 1.2 V
0x84 2.31 V
0x85 3.44 V
0x86 4.62 V
0x87 5.81 V
0x88 7.01 V
9x89 8.22 V
0x8a 9.42 V
0x8b 10.6 V
0x8c 11.9 V
0x8d 12.4 V
0x8e 12.4 V
0x8f 12.4 V
Documentation/hwmon/w83791d
浏览文件 @ 8c82a17e
......@@ -58,29 +58,35 @@ 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.
The driver implements three temperature sensors, ten voltage sensors,
five fan rotation speed sensors and manual PWM control of each fan.
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.
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.
Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
triggered if the rotation speed has dropped below a programmable limit. Fan
readings can be divided by a programmable divider (1, 2, 4, 8, 16,
32, 64 or 128 for all fans) 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.
Each fan controlled is controlled by PWM. The PWM duty cycle can be read and
set for each fan separately. Valid values range from 0 (stop) to 255 (full).
PWM 1-3 support Thermal Cruise mode, in which the PWMs are automatically
regulated to keep respectively temp 1-3 at a certain target temperature.
See below for the description of the sysfs-interface.
The w83791d has a global bit used to enable beeping from the speaker when an
alarm is triggered as well as a bitmask to enable or disable the beep for
specific alarms. You need both the global beep enable bit and the
corresponding beep bit to be on for a triggered alarm to sound a beep.
The sysfs interface to the gloabal enable is via the sysfs beep_enable file.
The sysfs interface to the global enable is via the sysfs beep_enable file.
This file is used for both legacy and new code.
The sysfs interface to the beep bitmask has migrated from the original legacy
......@@ -105,6 +111,27 @@ going forward.
The driver reads the hardware chip values at most once every three seconds.
User mode code requesting values more often will receive cached values.
/sys files
----------
The sysfs-interface is documented in the 'sysfs-interface' file. Only
chip-specific options are documented here.
pwm[1-3]_enable - this file controls mode of fan/temperature control for
fan 1-3. Fan/PWM 4-5 only support manual mode.
* 1 Manual mode
* 2 Thermal Cruise mode
* 3 Fan Speed Cruise mode (no further support)
temp[1-3]_target - defines the target temperature for Thermal Cruise mode.
Unit: millidegree Celsius
RW
temp[1-3]_tolerance - temperature tolerance for Thermal Cruise mode.
Specifies an interval around the target temperature
in which the fan speed is not changed.
Unit: millidegree Celsius
RW
Alarms bitmap vs. beep_mask bitmask
------------------------------------
For legacy code using the alarms and beep_mask files:
......@@ -132,7 +159,3 @@ tart2 : alarms: 0x020000 beep_mask: 0x080000 <== mismatch
tart3 : alarms: 0x040000 beep_mask: 0x100000 <== mismatch
case_open : alarms: 0x001000 beep_mask: 0x001000
global_enable: alarms: -------- beep_mask: 0x800000 (modified via beep_enable)
W83791D TODO:
---------------
Provide a patch for smart-fan control (still need appropriate motherboard/fans)
Documentation/i2c/busses/i2c-i801
浏览文件 @ 8c82a17e
......@@ -13,8 +13,9 @@ Supported adapters:
* Intel 631xESB/632xESB (ESB2)
* Intel 82801H (ICH8)
* Intel 82801I (ICH9)
* Intel Tolapai
* Intel ICH10
* Intel EP80579 (Tolapai)
* Intel 82801JI (ICH10)
* Intel PCH
Datasheets: Publicly available at the Intel website
Authors:
......@@ -32,7 +33,7 @@ Description
-----------
The ICH (properly known as the 82801AA), ICH0 (82801AB), ICH2 (82801BA),
ICH3 (82801CA/CAM) and later devices are Intel chips that are a part of
ICH3 (82801CA/CAM) and later devices (PCH) are Intel chips that are a part of
Intel's '810' chipset for Celeron-based PCs, '810E' chipset for
Pentium-based PCs, '815E' chipset, and others.
......
Documentation/i2c/porting-clients 已删除 100644 → 0
浏览文件 @ 4ce72a2c
Revision 7, 2007-04-19
Jean Delvare <khali@linux-fr.org>
Greg KH <greg@kroah.com>
This is a guide on how to convert I2C chip drivers from Linux 2.4 to
Linux 2.6. I have been using existing drivers (lm75, lm78) as examples.
Then I converted a driver myself (lm83) and updated this document.
Note that this guide is strongly oriented towards hardware monitoring
drivers. Many points are still valid for other type of drivers, but
others may be irrelevant.
There are two sets of points below. The first set concerns technical
changes. The second set concerns coding policy. Both are mandatory.
Although reading this guide will help you porting drivers, I suggest
you keep an eye on an already ported driver while porting your own
driver. This will help you a lot understanding what this guide
exactly means. Choose the chip driver that is the more similar to
yours for best results.
Technical changes:
* [Driver type] Any driver that was relying on i2c-isa has to be
converted to a proper isa, platform or pci driver. This is not
covered by this guide.
* [Includes] Get rid of "version.h" and <linux/i2c-proc.h>.
Includes typically look like that:
#include <linux/module.h>
#include <linux/init.h>
#include <linux/slab.h>
#include <linux/jiffies.h>
#include <linux/i2c.h>
#include <linux/hwmon.h> /* for hardware monitoring drivers */
#include <linux/hwmon-sysfs.h>
#include <linux/hwmon-vid.h> /* if you need VRM support */
#include <linux/err.h> /* for class registration */
Please respect this inclusion order. Some extra headers may be
required for a given driver (e.g. "lm75.h").
* [Addresses] SENSORS_I2C_END becomes I2C_CLIENT_END, ISA addresses
are no more handled by the i2c core. Address ranges are no more
supported either, define each individual address separately.
SENSORS_INSMOD_<n> becomes I2C_CLIENT_INSMOD_<n>.
* [Client data] Get rid of sysctl_id. Try using standard names for
register values (for example, temp_os becomes temp_max). You're
still relatively free here, but you *have* to follow the standard
names for sysfs files (see the Sysctl section below).
* [Function prototypes] The detect functions loses its flags
parameter. Sysctl (e.g. lm75_temp) and miscellaneous functions
are off the list of prototypes. This usually leaves five
prototypes:
static int lm75_attach_adapter(struct i2c_adapter *adapter);
static int lm75_detect(struct i2c_adapter *adapter, int address,
int kind);
static void lm75_init_client(struct i2c_client *client);
static int lm75_detach_client(struct i2c_client *client);
static struct lm75_data lm75_update_device(struct device *dev);
* [Sysctl] All sysctl stuff is of course gone (defines, ctl_table
and functions). Instead, you have to define show and set functions for
each sysfs file. Only define set for writable values. Take a look at an
existing 2.6 driver for details (it87 for example). Don't forget
to define the attributes for each file (this is that step that
links callback functions). Use the file names specified in
Documentation/hwmon/sysfs-interface for the individual files. Also
convert the units these files read and write to the specified ones.
If you need to add a new type of file, please discuss it on the
sensors mailing list <lm-sensors@lm-sensors.org> by providing a
patch to the Documentation/hwmon/sysfs-interface file.
* [Attach] The attach function should make sure that the adapter's
class has I2C_CLASS_HWMON (or whatever class is suitable for your
driver), using the following construct:
if (!(adapter->class & I2C_CLASS_HWMON))
return 0;
Call i2c_probe() instead of i2c_detect().
* [Detect] As mentioned earlier, the flags parameter is gone.
The type_name and client_name strings are replaced by a single
name string, which will be filled with a lowercase, short string.
The labels used for error paths are reduced to the number needed.
It is advised that the labels are given descriptive names such as
exit and exit_free. Don't forget to properly set err before
jumping to error labels. By the way, labels should be left-aligned.
Use kzalloc instead of kmalloc.
Use i2c_set_clientdata to set the client data (as opposed to
a direct access to client->data).
Use strlcpy instead of strcpy or snprintf to copy the client name.
Replace the sysctl directory registration by calls to
device_create_file. Move the driver initialization before any
sysfs file creation.
Register the client with the hwmon class (using hwmon_device_register)
if applicable.
Drop client->id.
Drop any 24RF08 corruption prevention you find, as this is now done
at the i2c-core level, and doing it twice voids it.
Don't add I2C_CLIENT_ALLOW_USE to client->flags, it's the default now.
* [Init] Limits must not be set by the driver (can be done later in
user-space). Chip should not be reset default (although a module
parameter may be used to force it), and initialization should be
limited to the strictly necessary steps.
* [Detach] Remove the call to i2c_deregister_entry. Do not log an
error message if i2c_detach_client fails, as i2c-core will now do
it for you.
Unregister from the hwmon class if applicable.
* [Update] The function prototype changed, it is now
passed a device structure, which you have to convert to a client
using to_i2c_client(dev). The update function should return a
pointer to the client data.
Don't access client->data directly, use i2c_get_clientdata(client)
instead.
Use time_after() instead of direct jiffies comparison.
* [Interface] Make sure there is a MODULE_LICENSE() line, at the bottom
of the file (after MODULE_AUTHOR() and MODULE_DESCRIPTION(), in this
order).
* [Driver] The flags field of the i2c_driver structure is gone.
I2C_DF_NOTIFY is now the default behavior.
The i2c_driver structure has a driver member, which is itself a
structure, those name member should be initialized to a driver name
string. i2c_driver itself has no name member anymore.
* [Driver model] Instead of shutdown or reboot notifiers, provide a
shutdown() method in your driver.
* [Power management] Use the driver model suspend() and resume()
callbacks instead of the obsolete pm_register() calls.
Coding policy:
* [Copyright] Use (C), not (c), for copyright.
* [Debug/log] Get rid of #ifdef DEBUG/#endif constructs whenever you
can. Calls to printk for debugging purposes are replaced by calls to
dev_dbg where possible, else to pr_debug. Here is an example of how
to call it (taken from lm75_detect):
dev_dbg(&client->dev, "Starting lm75 update\n");
Replace other printk calls with the dev_info, dev_err or dev_warn
function, as appropriate.
* [Constants] Constants defines (registers, conversions) should be
aligned. This greatly improves readability.
Alignments are achieved by the means of tabs, not spaces. Remember
that tabs are set to 8 in the Linux kernel code.
* [Layout] Avoid extra empty lines between comments and what they
comment. Respect the coding style (see Documentation/CodingStyle),
in particular when it comes to placing curly braces.
* [Comments] Make sure that no comment refers to a file that isn't
part of the Linux source tree (typically doc/chips/<chip name>),
and that remaining comments still match the code. Merging comment
lines when possible is encouraged.
Documentation/i2c/writing-clients
浏览文件 @ 8c82a17e
此差异已折叠。
Documentation/ia64/xen.txt 0 → 100644
浏览文件 @ 8c82a17e
Recipe for getting/building/running Xen/ia64 with pv_ops
--------------------------------------------------------
This recipe describes how to get xen-ia64 source and build it,
and run domU with pv_ops.
============
Requirements
============
- python
- mercurial
it (aka "hg") is an open-source source code
management software. See the below.
http://www.selenic.com/mercurial/wiki/
- git
- bridge-utils
=================================
Getting and Building Xen and Dom0
=================================
My environment is;
Machine : Tiger4
Domain0 OS : RHEL5
DomainU OS : RHEL5
1. Download source
# hg clone http://xenbits.xensource.com/ext/ia64/xen-unstable.hg
# cd xen-unstable.hg
# hg clone http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg
2. # make world
3. # make install-tools
4. copy kernels and xen
# cp xen/xen.gz /boot/efi/efi/redhat/
# cp build-linux-2.6.18-xen_ia64/vmlinux.gz \
/boot/efi/efi/redhat/vmlinuz-2.6.18.8-xen
5. make initrd for Dom0/DomU
# make -C linux-2.6.18-xen.hg ARCH=ia64 modules_install \
O=$(/bin/pwd)/build-linux-2.6.18-xen_ia64
# mkinitrd -f /boot/efi/efi/redhat/initrd-2.6.18.8-xen.img \
2.6.18.8-xen --builtin mptspi --builtin mptbase \
--builtin mptscsih --builtin uhci-hcd --builtin ohci-hcd \
--builtin ehci-hcd
================================
Making a disk image for guest OS
================================
1. make file
# dd if=/dev/zero of=/root/rhel5.img bs=1M seek=4096 count=0
# mke2fs -F -j /root/rhel5.img
# mount -o loop /root/rhel5.img /mnt
# cp -ax /{dev,var,etc,usr,bin,sbin,lib} /mnt
# mkdir /mnt/{root,proc,sys,home,tmp}
Note: You may miss some device files. If so, please create them
with mknod. Or you can use tar instead of cp.
2. modify DomU's fstab
# vi /mnt/etc/fstab
/dev/xvda1 / ext3 defaults 1 1
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
3. modify inittab
set runlevel to 3 to avoid X trying to start
# vi /mnt/etc/inittab
id:3:initdefault:
Start a getty on the hvc0 console
X0:2345:respawn:/sbin/mingetty hvc0
tty1-6 mingetty can be commented out
4. add hvc0 into /etc/securetty
# vi /mnt/etc/securetty (add hvc0)
5. umount
# umount /mnt
FYI, virt-manager can also make a disk image for guest OS.
It's GUI tools and easy to make it.
==================
Boot Xen & Domain0
==================
1. replace elilo
elilo of RHEL5 can boot Xen and Dom0.
If you use old elilo (e.g RHEL4), please download from the below
http://elilo.sourceforge.net/cgi-bin/blosxom
and copy into /boot/efi/efi/redhat/
# cp elilo-3.6-ia64.efi /boot/efi/efi/redhat/elilo.efi
2. modify elilo.conf (like the below)
# vi /boot/efi/efi/redhat/elilo.conf
prompt
timeout=20
default=xen
relocatable
image=vmlinuz-2.6.18.8-xen
label=xen
vmm=xen.gz
initrd=initrd-2.6.18.8-xen.img
read-only
append=" -- rhgb root=/dev/sda2"
The append options before "--" are for xen hypervisor,
the options after "--" are for dom0.
FYI, your machine may need console options like
"com1=19200,8n1 console=vga,com1". For example,
append="com1=19200,8n1 console=vga,com1 -- rhgb console=tty0 \
console=ttyS0 root=/dev/sda2"
=====================================
Getting and Building domU with pv_ops
=====================================
1. get pv_ops tree
# git clone http://people.valinux.co.jp/~yamahata/xen-ia64/linux-2.6-xen-ia64.git/
2. git branch (if necessary)
# cd linux-2.6-xen-ia64/
# git checkout -b your_branch origin/xen-ia64-domu-minimal-2008may19
(Note: The current branch is xen-ia64-domu-minimal-2008may19.
But you would find the new branch. You can see with
"git branch -r" to get the branch lists.
http://people.valinux.co.jp/~yamahata/xen-ia64/for_eagl/linux-2.6-ia64-pv-ops.git/
is also available. The tree is based on
git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6 test)
3. copy .config for pv_ops of domU
# cp arch/ia64/configs/xen_domu_wip_defconfig .config
4. make kernel with pv_ops
# make oldconfig
# make
5. install the kernel and initrd
# cp vmlinux.gz /boot/efi/efi/redhat/vmlinuz-2.6-pv_ops-xenU
# make modules_install
# mkinitrd -f /boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img \
2.6.26-rc3xen-ia64-08941-g1b12161 --builtin mptspi \
--builtin mptbase --builtin mptscsih --builtin uhci-hcd \
--builtin ohci-hcd --builtin ehci-hcd
========================
Boot DomainU with pv_ops
========================
1. make config of DomU
# vi /etc/xen/rhel5
kernel = "/boot/efi/efi/redhat/vmlinuz-2.6-pv_ops-xenU"
ramdisk = "/boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img"
vcpus = 1
memory = 512
name = "rhel5"
disk = [ 'file:/root/rhel5.img,xvda1,w' ]
root = "/dev/xvda1 ro"
extra= "rhgb console=hvc0"
2. After boot xen and dom0, start xend
# /etc/init.d/xend start
( In the debugging case, # XEND_DEBUG=1 xend trace_start )
3. start domU
# xm create -c rhel5
=========
Reference
=========
- Wiki of Xen/IA64 upstream merge
http://wiki.xensource.com/xenwiki/XenIA64/UpstreamMerge
Written by Akio Takebe <takebe_akio@jp.fujitsu.com> on 28 May 2008
Documentation/ioctl-number.txt
浏览文件 @ 8c82a17e
......@@ -92,6 +92,7 @@ Code Seq# Include File Comments
'J' 00-1F drivers/scsi/gdth_ioctl.h
'K' all linux/kd.h
'L' 00-1F linux/loop.h
'L' 20-2F driver/usb/misc/vstusb.h
'L' E0-FF linux/ppdd.h encrypted disk device driver
<http://linux01.gwdg.de/~alatham/ppdd.html>
'M' all linux/soundcard.h
......@@ -110,6 +111,8 @@ Code Seq# Include File Comments
'W' 00-1F linux/wanrouter.h conflict!
'X' all linux/xfs_fs.h
'Y' all linux/cyclades.h
'[' 00-07 linux/usb/usbtmc.h USB Test and Measurement Devices
<mailto:gregkh@suse.de>
'a' all ATM on linux
<http://lrcwww.epfl.ch/linux-atm/magic.html>
'b' 00-FF bit3 vme host bridge
......
Documentation/kdump/kdump.txt
浏览文件 @ 8c82a17e
......@@ -109,7 +109,8 @@ There are two possible methods of using Kdump.
2) Or use the system kernel binary itself as dump-capture kernel and there is
no need to build a separate dump-capture kernel. This is possible
only with the architecutres which support a relocatable kernel. As
of today, i386, x86_64 and ia64 architectures support relocatable kernel.
of today, i386, x86_64, ppc64 and ia64 architectures support relocatable
kernel.
Building a relocatable kernel is advantageous from the point of view that
one does not have to build a second kernel for capturing the dump. But
......@@ -207,8 +208,15 @@ Dump-capture kernel config options (Arch Dependent, i386 and x86_64)
Dump-capture kernel config options (Arch Dependent, ppc64)
----------------------------------------------------------
* Make and install the kernel and its modules. DO NOT add this kernel
to the boot loader configuration files.
1) Enable "Build a kdump crash kernel" support under "Kernel" options:
CONFIG_CRASH_DUMP=y
2) Enable "Build a relocatable kernel" support
CONFIG_RELOCATABLE=y
Make and install the kernel and its modules.
Dump-capture kernel config options (Arch Dependent, ia64)
----------------------------------------------------------
......
Documentation/kernel-parameters.txt
浏览文件 @ 8c82a17e
......@@ -101,6 +101,7 @@ parameter is applicable:
X86-64 X86-64 architecture is enabled.
More X86-64 boot options can be found in
Documentation/x86_64/boot-options.txt .
X86 Either 32bit or 64bit x86 (same as X86-32+X86-64)
In addition, the following text indicates that the option:
......@@ -217,20 +218,47 @@ and is between 256 and 4096 characters. It is defined in the file
acpi.debug_level= [HW,ACPI]
Format: <int>
Each bit of the <int> indicates an ACPI debug level,
1: enable, 0: disable. It is useful for boot time
debugging. After system has booted up, it can be set
via /sys/module/acpi/parameters/debug_level.
CONFIG_ACPI_DEBUG must be enabled for this to produce any output.
Available bits (add the numbers together) to enable different
debug output levels of the ACPI subsystem:
0x01 error 0x02 warn 0x04 init 0x08 debug object
0x10 info 0x20 init names 0x40 parse 0x80 load
0x100 dispatch 0x200 execute 0x400 names 0x800 operation region
0x1000 bfield 0x2000 tables 0x4000 values 0x8000 objects
0x10000 resources 0x20000 user requests 0x40000 package.
The number can be in decimal or prefixed with 0x in hex.
Warning: Many of these options can produce a lot of
output and make your system unusable. Be very careful.
which corresponds to the level in an ACPI_DEBUG_PRINT
statement. After system has booted up, this mask
can be set via /sys/module/acpi/parameters/debug_level.
CONFIG_ACPI_DEBUG must be enabled for this to produce
any output. The number can be in decimal or prefixed
with 0x in hex. Some of these options produce so much
output that the system is unusable.
The following global components are defined by the
ACPI CA:
0x01 error
0x02 warn
0x04 init
0x08 debug object
0x10 info
0x20 init names
0x40 parse
0x80 load
0x100 dispatch
0x200 execute
0x400 names
0x800 operation region
0x1000 bfield
0x2000 tables
0x4000 values
0x8000 objects
0x10000 resources
0x20000 user requests
0x40000 package
The number can be in decimal or prefixed with 0x in hex.
Warning: Many of these options can produce a lot of
output and make your system unusable. Be very careful.
acpi.power_nocheck= [HW,ACPI]
Format: 1/0 enable/disable the check of power state.
On some bogus BIOS the _PSC object/_STA object of
power resource can't return the correct device power
state. In such case it is unneccessary to check its
power state again in power transition.
1 : disable the power state check
acpi_pm_good [X86-32,X86-64]
Override the pmtimer bug detection: force the kernel
......@@ -690,7 +718,7 @@ and is between 256 and 4096 characters. It is defined in the file
See Documentation/block/as-iosched.txt and
Documentation/block/deadline-iosched.txt for details.
elfcorehdr= [X86-32, X86_64]
elfcorehdr= [IA64,PPC,SH,X86-32,X86_64]
Specifies physical address of start of kernel core
image elf header. Generally kexec loader will
pass this option to capture kernel.
......@@ -796,6 +824,8 @@ and is between 256 and 4096 characters. It is defined in the file
Defaults to the default architecture's huge page size
if not specified.
hlt [BUGS=ARM,SH]
i8042.debug [HW] Toggle i8042 debug mode
i8042.direct [HW] Put keyboard port into non-translated mode
i8042.dumbkbd [HW] Pretend that controller can only read data from
......@@ -1211,6 +1241,10 @@ and is between 256 and 4096 characters. It is defined in the file
mem=nopentium [BUGS=X86-32] Disable usage of 4MB pages for kernel
memory.
memchunk=nn[KMG]
[KNL,SH] Allow user to override the default size for
per-device physically contiguous DMA buffers.
memmap=exactmap [KNL,X86-32,X86_64] Enable setting of an exact
E820 memory map, as specified by the user.
Such memmap=exactmap lines can be constructed based on
......@@ -1393,6 +1427,8 @@ and is between 256 and 4096 characters. It is defined in the file
nodisconnect [HW,SCSI,M68K] Disables SCSI disconnects.
nodsp [SH] Disable hardware DSP at boot time.
noefi [X86-32,X86-64] Disable EFI runtime services support.
noexec [IA-64]
......@@ -1409,13 +1445,15 @@ and is between 256 and 4096 characters. It is defined in the file
noexec32=off: disable non-executable mappings
read implies executable mappings
nofpu [SH] Disable hardware FPU at boot time.
nofxsr [BUGS=X86-32] Disables x86 floating point extended
register save and restore. The kernel will only save
legacy floating-point registers on task switch.
noclflush [BUGS=X86] Don't use the CLFLUSH instruction
nohlt [BUGS=ARM]
nohlt [BUGS=ARM,SH]
no-hlt [BUGS=X86-32] Tells the kernel that the hlt
instruction doesn't work correctly and not to
......@@ -1578,7 +1616,7 @@ and is between 256 and 4096 characters. It is defined in the file
See also Documentation/paride.txt.
pci=option[,option...] [PCI] various PCI subsystem options:
off [X86-32] don't probe for the PCI bus
off [X86] don't probe for the PCI bus
bios [X86-32] force use of PCI BIOS, don't access
the hardware directly. Use this if your machine
has a non-standard PCI host bridge.
......@@ -1586,9 +1624,9 @@ and is between 256 and 4096 characters. It is defined in the file
hardware access methods are allowed. Use this
if you experience crashes upon bootup and you
suspect they are caused by the BIOS.
conf1 [X86-32] Force use of PCI Configuration
conf1 [X86] Force use of PCI Configuration
Mechanism 1.
conf2 [X86-32] Force use of PCI Configuration
conf2 [X86] Force use of PCI Configuration
Mechanism 2.
noaer [PCIE] If the PCIEAER kernel config parameter is
enabled, this kernel boot option can be used to
......@@ -1608,37 +1646,37 @@ and is between 256 and 4096 characters. It is defined in the file
this option if the kernel is unable to allocate
IRQs or discover secondary PCI buses on your
motherboard.
rom [X86-32] Assign address space to expansion ROMs.
rom [X86] Assign address space to expansion ROMs.
Use with caution as certain devices share
address decoders between ROMs and other
resources.
norom [X86-32,X86_64] Do not assign address space to
norom [X86] Do not assign address space to
expansion ROMs that do not already have
BIOS assigned address ranges.
irqmask=0xMMMM [X86-32] Set a bit mask of IRQs allowed to be
irqmask=0xMMMM [X86] Set a bit mask of IRQs allowed to be
assigned automatically to PCI devices. You can
make the kernel exclude IRQs of your ISA cards
this way.
pirqaddr=0xAAAAA [X86-32] Specify the physical address
pirqaddr=0xAAAAA [X86] Specify the physical address
of the PIRQ table (normally generated
by the BIOS) if it is outside the
F0000h-100000h range.
lastbus=N [X86-32] Scan all buses thru bus #N. Can be
lastbus=N [X86] Scan all buses thru bus #N. Can be
useful if the kernel is unable to find your
secondary buses and you want to tell it
explicitly which ones they are.
assign-busses [X86-32] Always assign all PCI bus
assign-busses [X86] Always assign all PCI bus
numbers ourselves, overriding
whatever the firmware may have done.
usepirqmask [X86-32] Honor the possible IRQ mask stored
usepirqmask [X86] Honor the possible IRQ mask stored
in the BIOS $PIR table. This is needed on
some systems with broken BIOSes, notably
some HP Pavilion N5400 and Omnibook XE3
notebooks. This will have no effect if ACPI
IRQ routing is enabled.
noacpi [X86-32] Do not use ACPI for IRQ routing
noacpi [X86] Do not use ACPI for IRQ routing
or for PCI scanning.
use_crs [X86-32] Use _CRS for PCI resource
use_crs [X86] Use _CRS for PCI resource
allocation.
routeirq Do IRQ routing for all PCI devices.
This is normally done in pci_enable_device(),
......@@ -1667,6 +1705,12 @@ and is between 256 and 4096 characters. It is defined in the file
reserved for the CardBus bridge's memory
window. The default value is 64 megabytes.
pcie_aspm= [PCIE] Forcibly enable or disable PCIe Active State Power
Management.
off Disable ASPM.
force Enable ASPM even on devices that claim not to support it.
WARNING: Forcing ASPM on may cause system lockups.
pcmv= [HW,PCMCIA] BadgePAD 4
pd. [PARIDE]
......@@ -1694,6 +1738,10 @@ and is between 256 and 4096 characters. It is defined in the file
Override pmtimer IOPort with a hex value.
e.g. pmtmr=0x508
pnp.debug [PNP]
Enable PNP debug messages. This depends on the
CONFIG_PNP_DEBUG_MESSAGES option.
pnpacpi= [ACPI]
{ off }
......@@ -2191,7 +2239,7 @@ and is between 256 and 4096 characters. It is defined in the file
thermal.crt= [HW,ACPI]
-1: disable all critical trip points in all thermal zones
<degrees C>: lower all critical trip points
<degrees C>: override all critical trip points
thermal.nocrt= [HW,ACPI]
Set to disable actions on ACPI thermal zone
......@@ -2253,6 +2301,25 @@ and is between 256 and 4096 characters. It is defined in the file
autosuspended. Devices for which the delay is set
to a negative value won't be autosuspended at all.
usbcore.usbfs_snoop=
[USB] Set to log all usbfs traffic (default 0 = off).
usbcore.blinkenlights=
[USB] Set to cycle leds on hubs (default 0 = off).
usbcore.old_scheme_first=
[USB] Start with the old device initialization
scheme (default 0 = off).
usbcore.use_both_schemes=
[USB] Try the other device initialization scheme
if the first one fails (default 1 = enabled).
usbcore.initial_descriptor_timeout=
[USB] Specifies timeout for the initial 64-byte
USB_REQ_GET_DESCRIPTOR request in milliseconds
(default 5000 = 5.0 seconds).
usbhid.mousepoll=
[USBHID] The interval which mice are to be polled at.
......
Documentation/laptops/acer-wmi.txt
浏览文件 @ 8c82a17e
Acer Laptop WMI Extras Driver
http://code.google.com/p/aceracpi
Version 0.1
9th February 2008
Version 0.2
18th August 2008
Copyright 2007-2008 Carlos Corbacho <carlos@strangeworlds.co.uk>
......@@ -87,17 +87,7 @@ acer-wmi come with built-in wireless. However, should you feel so inclined to
ever wish to remove the card, or swap it out at some point, please get in touch
with me, as we may well be able to gain some data on wireless card detection.
To read the status of the wireless radio (0=off, 1=on):
cat /sys/devices/platform/acer-wmi/wireless
To enable the wireless radio:
echo 1 > /sys/devices/platform/acer-wmi/wireless
To disable the wireless radio:
echo 0 > /sys/devices/platform/acer-wmi/wireless
To set the state of the wireless radio when loading acer-wmi, pass:
wireless=X (where X is 0 or 1)
The wireless radio is exposed through rfkill.
Bluetooth
*********
......@@ -117,17 +107,7 @@ For the adventurously minded - if you want to buy an internal bluetooth
module off the internet that is compatible with your laptop and fit it, then
it will work just fine with acer-wmi.
To read the status of the bluetooth module (0=off, 1=on):
cat /sys/devices/platform/acer-wmi/wireless
To enable the bluetooth module:
echo 1 > /sys/devices/platform/acer-wmi/bluetooth
To disable the bluetooth module:
echo 0 > /sys/devices/platform/acer-wmi/bluetooth
To set the state of the bluetooth module when loading acer-wmi, pass:
bluetooth=X (where X is 0 or 1)
Bluetooth is exposed through rfkill.
3G
**
......
Documentation/markers.txt
浏览文件 @ 8c82a17e
......@@ -50,10 +50,12 @@ Connecting a function (probe) to a marker is done by providing a probe (function
to call) for the specific marker through marker_probe_register() and can be
activated by calling marker_arm(). Marker deactivation can be done by calling
marker_disarm() as many times as marker_arm() has been called. Removing a probe
is done through marker_probe_unregister(); it will disarm the probe and make
sure there is no caller left using the probe when it returns. Probe removal is
preempt-safe because preemption is disabled around the probe call. See the
"Probe example" section below for a sample probe module.
is done through marker_probe_unregister(); it will disarm the probe.
marker_synchronize_unregister() must be called before the end of the module exit
function to make sure there is no caller left using the probe. This, and the
fact that preemption is disabled around the probe call, make sure that probe
removal and module unload are safe. See the "Probe example" section below for a
sample probe module.
The marker mechanism supports inserting multiple instances of the same marker.
Markers can be put in inline functions, inlined static functions, and
......
Documentation/mtd/nand_ecc.txt 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
Documentation/powerpc/booting-without-of.txt
浏览文件 @ 8c82a17e
......@@ -1917,6 +1917,8 @@ platforms are moved over to use the flattened-device-tree model.
inverse clock polarity (CPOL) mode
- spi-cpha - (optional) Empty property indicating device requires
shifted clock phase (CPHA) mode
- spi-cs-high - (optional) Empty property indicating device requires
chip select active high
SPI example for an MPC5200 SPI bus:
spi@f00 {
......
Documentation/powerpc/dts-bindings/fsl/board.txt
浏览文件 @ 8c82a17e
......@@ -2,13 +2,13 @@
Required properties:
- device_type : Should be "board-control"
- compatible : Should be "fsl,<board>-bcsr"
- reg : Offset and length of the register set for the device
Example:
bcsr@f8000000 {
device_type = "board-control";
compatible = "fsl,mpc8360mds-bcsr";
reg = <f8000000 8000>;
};
......
Documentation/sysctl/kernel.txt
浏览文件 @ 8c82a17e
......@@ -369,4 +369,5 @@ can be ORed together:
2 - A module was force loaded by insmod -f.
Set by modutils >= 2.4.9 and module-init-tools.
4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
64 - A module from drivers/staging was loaded.
Documentation/sysrq.txt
浏览文件 @ 8c82a17e
......@@ -95,7 +95,9 @@ On all - write a character to /proc/sysrq-trigger. e.g.:
'p' - Will dump the current registers and flags to your console.
'q' - Will dump a list of all running timers.
'q' - Will dump per CPU lists of all armed hrtimers (but NOT regular
timer_list timers) and detailed information about all
clockevent devices.
'r' - Turns off keyboard raw mode and sets it to XLATE.
......
Documentation/tracepoints.txt 0 → 100644
浏览文件 @ 8c82a17e
Using the Linux Kernel Tracepoints
Mathieu Desnoyers
This document introduces Linux Kernel Tracepoints and their use. It provides
examples of how to insert tracepoints in the kernel and connect probe functions
to them and provides some examples of probe functions.
* Purpose of tracepoints
A tracepoint placed in code provides a hook to call a function (probe) that you
can provide at runtime. A tracepoint can be "on" (a probe is connected to it) or
"off" (no probe is attached). When a tracepoint is "off" it has no effect,
except for adding a tiny time penalty (checking a condition for a branch) and
space penalty (adding a few bytes for the function call at the end of the
instrumented function and adds a data structure in a separate section). When a
tracepoint is "on", the function you provide is called each time the tracepoint
is executed, in the execution context of the caller. When the function provided
ends its execution, it returns to the caller (continuing from the tracepoint
site).
You can put tracepoints at important locations in the code. They are
lightweight hooks that can pass an arbitrary number of parameters,
which prototypes are described in a tracepoint declaration placed in a header
file.
They can be used for tracing and performance accounting.
* Usage
Two elements are required for tracepoints :
- A tracepoint definition, placed in a header file.
- The tracepoint statement, in C code.
In order to use tracepoints, you should include linux/tracepoint.h.
In include/trace/subsys.h :
#include <linux/tracepoint.h>
DEFINE_TRACE(subsys_eventname,
TPPTOTO(int firstarg, struct task_struct *p),
TPARGS(firstarg, p));
In subsys/file.c (where the tracing statement must be added) :
#include <trace/subsys.h>
void somefct(void)
{
...
trace_subsys_eventname(arg, task);
...
}
Where :
- subsys_eventname is an identifier unique to your event
- subsys is the name of your subsystem.
- eventname is the name of the event to trace.
- TPPTOTO(int firstarg, struct task_struct *p) is the prototype of the function
called by this tracepoint.
- TPARGS(firstarg, p) are the parameters names, same as found in the prototype.
Connecting a function (probe) to a tracepoint is done by providing a probe
(function to call) for the specific tracepoint through
register_trace_subsys_eventname(). Removing a probe is done through
unregister_trace_subsys_eventname(); it will remove the probe sure there is no
caller left using the probe when it returns. Probe removal is preempt-safe
because preemption is disabled around the probe call. See the "Probe example"
section below for a sample probe module.
The tracepoint mechanism supports inserting multiple instances of the same
tracepoint, but a single definition must be made of a given tracepoint name over
all the kernel to make sure no type conflict will occur. Name mangling of the
tracepoints is done using the prototypes to make sure typing is correct.
Verification of probe type correctness is done at the registration site by the
compiler. Tracepoints can be put in inline functions, inlined static functions,
and unrolled loops as well as regular functions.
The naming scheme "subsys_event" is suggested here as a convention intended
to limit collisions. Tracepoint names are global to the kernel: they are
considered as being the same whether they are in the core kernel image or in
modules.
* Probe / tracepoint example
See the example provided in samples/tracepoints/src
Compile them with your kernel.
Run, as root :
modprobe tracepoint-example (insmod order is not important)
modprobe tracepoint-probe-example
cat /proc/tracepoint-example (returns an expected error)
rmmod tracepoint-example tracepoint-probe-example
dmesg
Documentation/tracers/mmiotrace.txt
浏览文件 @ 8c82a17e
......@@ -36,7 +36,7 @@ $ mount -t debugfs debugfs /debug
$ echo mmiotrace > /debug/tracing/current_tracer
$ cat /debug/tracing/trace_pipe > mydump.txt &
Start X or whatever.
$ echo "X is up" > /debug/tracing/marker
$ echo "X is up" > /debug/tracing/trace_marker
$ echo none > /debug/tracing/current_tracer
Check for lost events.
......@@ -59,9 +59,8 @@ The 'cat' process should stay running (sleeping) in the background.
Load the driver you want to trace and use it. Mmiotrace will only catch MMIO
accesses to areas that are ioremapped while mmiotrace is active.
[Unimplemented feature:]
During tracing you can place comments (markers) into the trace by
$ echo "X is up" > /debug/tracing/marker
$ echo "X is up" > /debug/tracing/trace_marker
This makes it easier to see which part of the (huge) trace corresponds to
which action. It is recommended to place descriptive markers about what you
do.
......
Documentation/usb/WUSB-Design-overview.txt 0 → 100644
浏览文件 @ 8c82a17e
Linux UWB + Wireless USB + WiNET
(C) 2005-2006 Intel Corporation
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License version
2 as published by the Free Software Foundation.
This program 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.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
Please visit http://bughost.org/thewiki/Design-overview.txt-1.8 for
updated content.
* Design-overview.txt-1.8
This code implements a Ultra Wide Band stack for Linux, as well as
drivers for the the USB based UWB radio controllers defined in the
Wireless USB 1.0 specification (including Wireless USB host controller
and an Intel WiNET controller).
1. Introduction
1. HWA: Host Wire adapters, your Wireless USB dongle
2. DWA: Device Wired Adaptor, a Wireless USB hub for wired
devices
3. WHCI: Wireless Host Controller Interface, the PCI WUSB host
adapter
2. The UWB stack
1. Devices and hosts: the basic structure
2. Host Controller life cycle
3. On the air: beacons and enumerating the radio neighborhood
4. Device lists
5. Bandwidth allocation
3. Wireless USB Host Controller drivers
4. Glossary
Introduction
UWB is a wide-band communication protocol that is to serve also as the
low-level protocol for others (much like TCP sits on IP). Currently
these others are Wireless USB and TCP/IP, but seems Bluetooth and
Firewire/1394 are coming along.
UWB uses a band from roughly 3 to 10 GHz, transmitting at a max of
~-41dB (or 0.074 uW/MHz--geography specific data is still being
negotiated w/ regulators, so watch for changes). That band is divided in
a bunch of ~1.5 GHz wide channels (or band groups) composed of three
subbands/subchannels (528 MHz each). Each channel is independent of each
other, so you could consider them different "busses". Initially this
driver considers them all a single one.
Radio time is divided in 65536 us long /superframes/, each one divided
in 256 256us long /MASs/ (Media Allocation Slots), which are the basic
time/media allocation units for transferring data. At the beginning of
each superframe there is a Beacon Period (BP), where every device
transmit its beacon on a single MAS. The length of the BP depends on how
many devices are present and the length of their beacons.
Devices have a MAC (fixed, 48 bit address) and a device (changeable, 16
bit address) and send periodic beacons to advertise themselves and pass
info on what they are and do. They advertise their capabilities and a
bunch of other stuff.
The different logical parts of this driver are:
*
*UWB*: the Ultra-Wide-Band stack -- manages the radio and
associated spectrum to allow for devices sharing it. Allows to
control bandwidth assingment, beaconing, scanning, etc
*
*WUSB*: the layer that sits on top of UWB to provide Wireless USB.
The Wireless USB spec defines means to control a UWB radio and to
do the actual WUSB.
HWA: Host Wire adapters, your Wireless USB dongle
WUSB also defines a device called a Host Wire Adaptor (HWA), which in
mere terms is a USB dongle that enables your PC to have UWB and Wireless
USB. The Wireless USB Host Controller in a HWA looks to the host like a
[Wireless] USB controller connected via USB (!)
The HWA itself is broken in two or three main interfaces:
*
*RC*: Radio control -- this implements an interface to the
Ultra-Wide-Band radio controller. The driver for this implements a
USB-based UWB Radio Controller to the UWB stack.
*
*HC*: the wireless USB host controller. It looks like a USB host
whose root port is the radio and the WUSB devices connect to it.
To the system it looks like a separate USB host. The driver (will)
implement a USB host controller (similar to UHCI, OHCI or EHCI)
for which the root hub is the radio...To reiterate: it is a USB
controller that is connected via USB instead of PCI.
*
*WINET*: some HW provide a WiNET interface (IP over UWB). This
package provides a driver for it (it looks like a network
interface, winetX). The driver detects when there is a link up for
their type and kick into gear.
DWA: Device Wired Adaptor, a Wireless USB hub for wired devices
These are the complement to HWAs. They are a USB host for connecting
wired devices, but it is connected to your PC connected via Wireless
USB. To the system it looks like yet another USB host. To the untrained
eye, it looks like a hub that connects upstream wirelessly.
We still offer no support for this; however, it should share a lot of
code with the HWA-RC driver; there is a bunch of factorization work that
has been done to support that in upcoming releases.
WHCI: Wireless Host Controller Interface, the PCI WUSB host adapter
This is your usual PCI device that implements WHCI. Similar in concept
to EHCI, it allows your wireless USB devices (including DWAs) to connect
to your host via a PCI interface. As in the case of the HWA, it has a
Radio Control interface and the WUSB Host Controller interface per se.
There is still no driver support for this, but will be in upcoming
releases.
The UWB stack
The main mission of the UWB stack is to keep a tally of which devices
are in radio proximity to allow drivers to connect to them. As well, it
provides an API for controlling the local radio controllers (RCs from
now on), such as to start/stop beaconing, scan, allocate bandwidth, etc.
Devices and hosts: the basic structure
The main building block here is the UWB device (struct uwb_dev). For
each device that pops up in radio presence (ie: the UWB host receives a
beacon from it) you get a struct uwb_dev that will show up in
/sys/class/uwb and in /sys/bus/uwb/devices.
For each RC that is detected, a new struct uwb_rc is created. In turn, a
RC is also a device, so they also show in /sys/class/uwb and
/sys/bus/uwb/devices, but at the same time, only radio controllers show
up in /sys/class/uwb_rc.
*
[*] The reason for RCs being also devices is that not only we can
see them while enumerating the system device tree, but also on the
radio (their beacons and stuff), so the handling has to be
likewise to that of a device.
Each RC driver is implemented by a separate driver that plugs into the
interface that the UWB stack provides through a struct uwb_rc_ops. The
spec creators have been nice enough to make the message format the same
for HWA and WHCI RCs, so the driver is really a very thin transport that
moves the requests from the UWB API to the device [/uwb_rc_ops->cmd()/]
and sends the replies and notifications back to the API
[/uwb_rc_neh_grok()/]. Notifications are handled to the UWB daemon, that
is chartered, among other things, to keep the tab of how the UWB radio
neighborhood looks, creating and destroying devices as they show up or
dissapear.
Command execution is very simple: a command block is sent and a event
block or reply is expected back. For sending/receiving command/events, a
handle called /neh/ (Notification/Event Handle) is opened with
/uwb_rc_neh_open()/.
The HWA-RC (USB dongle) driver (drivers/uwb/hwa-rc.c) does this job for
the USB connected HWA. Eventually, drivers/whci-rc.c will do the same
for the PCI connected WHCI controller.
Host Controller life cycle
So let's say we connect a dongle to the system: it is detected and
firmware uploaded if needed [for Intel's i1480
/drivers/uwb/ptc/usb.c:ptc_usb_probe()/] and then it is reenumerated.
Now we have a real HWA device connected and
/drivers/uwb/hwa-rc.c:hwarc_probe()/ picks it up, that will set up the
Wire-Adaptor environment and then suck it into the UWB stack's vision of
the world [/drivers/uwb/lc-rc.c:uwb_rc_add()/].
*
[*] The stack should put a new RC to scan for devices
[/uwb_rc_scan()/] so it finds what's available around and tries to
connect to them, but this is policy stuff and should be driven
from user space. As of now, the operator is expected to do it
manually; see the release notes for documentation on the procedure.
When a dongle is disconnected, /drivers/uwb/hwa-rc.c:hwarc_disconnect()/
takes time of tearing everything down safely (or not...).
On the air: beacons and enumerating the radio neighborhood
So assuming we have devices and we have agreed for a channel to connect
on (let's say 9), we put the new RC to beacon:
*
$ echo 9 0 > /sys/class/uwb_rc/uwb0/beacon
Now it is visible. If there were other devices in the same radio channel
and beacon group (that's what the zero is for), the dongle's radio
control interface will send beacon notifications on its
notification/event endpoint (NEEP). The beacon notifications are part of
the event stream that is funneled into the API with
/drivers/uwb/neh.c:uwb_rc_neh_grok()/ and delivered to the UWBD, the UWB
daemon through a notification list.
UWBD wakes up and scans the event list; finds a beacon and adds it to
the BEACON CACHE (/uwb_beca/). If he receives a number of beacons from
the same device, he considers it to be 'onair' and creates a new device
[/drivers/uwb/lc-dev.c:uwbd_dev_onair()/]. Similarly, when no beacons
are received in some time, the device is considered gone and wiped out
[uwbd calls periodically /uwb/beacon.c:uwb_beca_purge()/ that will purge
the beacon cache of dead devices].
Device lists
All UWB devices are kept in the list of the struct bus_type uwb_bus.
Bandwidth allocation
The UWB stack maintains a local copy of DRP availability through
processing of incoming *DRP Availability Change* notifications. This
local copy is currently used to present the current bandwidth
availability to the user through the sysfs file
/sys/class/uwb_rc/uwbx/bw_avail. In the future the bandwidth
availability information will be used by the bandwidth reservation
routines.
The bandwidth reservation routines are in progress and are thus not
present in the current release. When completed they will enable a user
to initiate DRP reservation requests through interaction with sysfs. DRP
reservation requests from remote UWB devices will also be handled. The
bandwidth management done by the UWB stack will include callbacks to the
higher layers will enable the higher layers to use the reservations upon
completion. [Note: The bandwidth reservation work is in progress and
subject to change.]
Wireless USB Host Controller drivers
*WARNING* This section needs a lot of work!
As explained above, there are three different types of HCs in the WUSB
world: HWA-HC, DWA-HC and WHCI-HC.
HWA-HC and DWA-HC share that they are Wire-Adapters (USB or WUSB
connected controllers), and their transfer management system is almost
identical. So is their notification delivery system.
HWA-HC and WHCI-HC share that they are both WUSB host controllers, so
they have to deal with WUSB device life cycle and maintenance, wireless
root-hub
HWA exposes a Host Controller interface (HWA-HC 0xe0/02/02). This has
three endpoints (Notifications, Data Transfer In and Data Transfer
Out--known as NEP, DTI and DTO in the code).
We reserve UWB bandwidth for our Wireless USB Cluster, create a Cluster
ID and tell the HC to use all that. Then we start it. This means the HC
starts sending MMCs.
*
The MMCs are blocks of data defined somewhere in the WUSB1.0 spec
that define a stream in the UWB channel time allocated for sending
WUSB IEs (host to device commands/notifications) and Device
Notifications (device initiated to host). Each host defines a
unique Wireless USB cluster through MMCs. Devices can connect to a
single cluster at the time. The IEs are Information Elements, and
among them are the bandwidth allocations that tell each device
when can they transmit or receive.
Now it all depends on external stimuli.
*New device connection*
A new device pops up, it scans the radio looking for MMCs that give out
the existence of Wireless USB channels. Once one (or more) are found,
selects which one to connect to. Sends a /DN_Connect/ (device
notification connect) during the DNTS (Device Notification Time
Slot--announced in the MMCs
HC picks the /DN_Connect/ out (nep module sends to notif.c for delivery
into /devconnect/). This process starts the authentication process for
the device. First we allocate a /fake port/ and assign an
unauthenticated address (128 to 255--what we really do is
0x80 | fake_port_idx). We fiddle with the fake port status and /khubd/
sees a new connection, so he moves on to enable the fake port with a reset.
So now we are in the reset path -- we know we have a non-yet enumerated
device with an unauthorized address; we ask user space to authenticate
(FIXME: not yet done, similar to bluetooth pairing), then we do the key
exchange (FIXME: not yet done) and issue a /set address 0/ to bring the
device to the default state. Device is authenticated.
From here, the USB stack takes control through the usb_hcd ops. khubd
has seen the port status changes, as we have been toggling them. It will
start enumerating and doing transfers through usb_hcd->urb_enqueue() to
read descriptors and move our data.
*Device life cycle and keep alives*
Everytime there is a succesful transfer to/from a device, we update a
per-device activity timestamp. If not, every now and then we check and
if the activity timestamp gets old, we ping the device by sending it a
Keep Alive IE; it responds with a /DN_Alive/ pong during the DNTS (this
arrives to us as a notification through
devconnect.c:wusb_handle_dn_alive(). If a device times out, we
disconnect it from the system (cleaning up internal information and
toggling the bits in the fake hub port, which kicks khubd into removing
the rest of the stuff).
This is done through devconnect:__wusb_check_devs(), which will scan the
device list looking for whom needs refreshing.
If the device wants to disconnect, it will either die (ugly) or send a
/DN_Disconnect/ that will prompt a disconnection from the system.
*Sending and receiving data*
Data is sent and received through /Remote Pipes/ (rpipes). An rpipe is
/aimed/ at an endpoint in a WUSB device. This is the same for HWAs and
DWAs.
Each HC has a number of rpipes and buffers that can be assigned to them;
when doing a data transfer (xfer), first the rpipe has to be aimed and
prepared (buffers assigned), then we can start queueing requests for
data in or out.
Data buffers have to be segmented out before sending--so we send first a
header (segment request) and then if there is any data, a data buffer
immediately after to the DTI interface (yep, even the request). If our
buffer is bigger than the max segment size, then we just do multiple
requests.
[This sucks, because doing USB scatter gatter in Linux is resource
intensive, if any...not that the current approach is not. It just has to
be cleaned up a lot :)].
If reading, we don't send data buffers, just the segment headers saying
we want to read segments.
When the xfer is executed, we receive a notification that says data is
ready in the DTI endpoint (handled through
xfer.c:wa_handle_notif_xfer()). In there we read from the DTI endpoint a
descriptor that gives us the status of the transfer, its identification
(given when we issued it) and the segment number. If it was a data read,
we issue another URB to read into the destination buffer the chunk of
data coming out of the remote endpoint. Done, wait for the next guy. The
callbacks for the URBs issued from here are the ones that will declare
the xfer complete at some point and call it's callback.
Seems simple, but the implementation is not trivial.
*
*WARNING* Old!!
The main xfer descriptor, wa_xfer (equivalent to a URB) contains an
array of segments, tallys on segments and buffers and callback
information. Buried in there is a lot of URBs for executing the segments
and buffer transfers.
For OUT xfers, there is an array of segments, one URB for each, another
one of buffer URB. When submitting, we submit URBs for segment request
1, buffer 1, segment 2, buffer 2...etc. Then we wait on the DTI for xfer
result data; when all the segments are complete, we call the callback to
finalize the transfer.
For IN xfers, we only issue URBs for the segments we want to read and
then wait for the xfer result data.
*URB mapping into xfers*
This is done by hwahc_op_urb_[en|de]queue(). In enqueue() we aim an
rpipe to the endpoint where we have to transmit, create a transfer
context (wa_xfer) and submit it. When the xfer is done, our callback is
called and we assign the status bits and release the xfer resources.
In dequeue() we are basically cancelling/aborting the transfer. We issue
a xfer abort request to the HC, cancell all the URBs we had submitted
and not yet done and when all that is done, the xfer callback will be
called--this will call the URB callback.
Glossary
*DWA* -- Device Wire Adapter
USB host, wired for downstream devices, upstream connects wirelessly
with Wireless USB.
*EVENT* -- Response to a command on the NEEP
*HWA* -- Host Wire Adapter / USB dongle for UWB and Wireless USB
*NEH* -- Notification/Event Handle
Handle/file descriptor for receiving notifications or events. The WA
code requires you to get one of this to listen for notifications or
events on the NEEP.
*NEEP* -- Notification/Event EndPoint
Stuff related to the management of the first endpoint of a HWA USB
dongle that is used to deliver an stream of events and notifications to
the host.
*NOTIFICATION* -- Message coming in the NEEP as response to something.
*RC* -- Radio Control
Design-overview.txt-1.8 (last edited 2006-11-04 12:22:24 by
InakyPerezGonzalez)
Documentation/usb/anchors.txt
浏览文件 @ 8c82a17e
......@@ -52,6 +52,11 @@ Therefore no guarantee is made that the URBs have been unlinked when
the call returns. They may be unlinked later but will be unlinked in
finite time.
usb_scuttle_anchored_urbs()
---------------------------
All URBs of an anchor are unanchored en masse.
usb_wait_anchor_empty_timeout()
-------------------------------
......@@ -59,4 +64,16 @@ This function waits for all URBs associated with an anchor to finish
or a timeout, whichever comes first. Its return value will tell you
whether the timeout was reached.
usb_anchor_empty()
------------------
Returns true if no URBs are associated with an anchor. Locking
is the caller's responsibility.
usb_get_from_anchor()
---------------------
Returns the oldest anchored URB of an anchor. The URB is unanchored
and returned with a reference. As you may mix URBs to several
destinations in one anchor you have no guarantee the chronologically
first submitted URB is returned.
\ No newline at end of file
Documentation/usb/misc_usbsevseg.txt 0 → 100644
浏览文件 @ 8c82a17e
USB 7-Segment Numeric Display
Manufactured by Delcom Engineering
Device Information
------------------
USB VENDOR_ID 0x0fc5
USB PRODUCT_ID 0x1227
Both the 6 character and 8 character displays have PRODUCT_ID,
and according to Delcom Engineering no queryable information
can be obtained from the device to tell them apart.
Device Modes
------------
By default, the driver assumes the display is only 6 characters
The mode for 6 characters is:
MSB 0x06; LSB 0x3f
For the 8 character display:
MSB 0x08; LSB 0xff
The device can accept "text" either in raw, hex, or ascii textmode.
raw controls each segment manually,
hex expects a value between 0-15 per character,
ascii expects a value between '0'-'9' and 'A'-'F'.
The default is ascii.
Device Operation
----------------
1. Turn on the device:
echo 1 > /sys/bus/usb/.../powered
2. Set the device's mode:
echo $mode_msb > /sys/bus/usb/.../mode_msb
echo $mode_lsb > /sys/bus/usb/.../mode_lsb
3. Set the textmode:
echo $textmode > /sys/bus/usb/.../textmode
4. set the text (for example):
echo "123ABC" > /sys/bus/usb/.../text (ascii)
echo "A1B2" > /sys/bus/usb/.../text (ascii)
echo -ne "\x01\x02\x03" > /sys/bus/usb/.../text (hex)
5. Set the decimal places.
The device has either 6 or 8 decimal points.
to set the nth decimal place calculate 10 ** n
and echo it in to /sys/bus/usb/.../decimals
To set multiple decimals points sum up each power.
For example, to set the 0th and 3rd decimal place
echo 1001 > /sys/bus/usb/.../decimals
Documentation/usb/power-management.txt
浏览文件 @ 8c82a17e
......@@ -350,12 +350,12 @@ without holding the mutex.
There also are a couple of utility routines drivers can use:
usb_autopm_enable() sets pm_usage_cnt to 1 and then calls
usb_autopm_set_interface(), which will attempt an autoresume.
usb_autopm_disable() sets pm_usage_cnt to 0 and then calls
usb_autopm_enable() sets pm_usage_cnt to 0 and then calls
usb_autopm_set_interface(), which will attempt an autosuspend.
usb_autopm_disable() sets pm_usage_cnt to 1 and then calls
usb_autopm_set_interface(), which will attempt an autoresume.
The conventional usage pattern is that a driver calls
usb_autopm_get_interface() in its open routine and
usb_autopm_put_interface() in its close or release routine. But
......
Documentation/usb/wusb-cbaf 0 → 100644
浏览文件 @ 8c82a17e
#! /bin/bash
#
set -e
progname=$(basename $0)
function help
{
cat <<EOF
Usage: $progname COMMAND DEVICEs [ARGS]
Command for manipulating the pairing/authentication credentials of a
Wireless USB device that supports wired-mode Cable-Based-Association.
Works in conjunction with the wusb-cba.ko driver from http://linuxuwb.org.
DEVICE
sysfs path to the device to authenticate; for example, both this
guys are the same:
/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.4/1-4.4:1.1
/sys/bus/usb/drivers/wusb-cbaf/1-4.4:1.1
COMMAND/ARGS are
start
Start a WUSB host controller (by setting up a CHID)
set-chid DEVICE HOST-CHID HOST-BANDGROUP HOST-NAME
Sets host information in the device; after this you can call the
get-cdid to see how does this device report itself to us.
get-cdid DEVICE
Get the device ID associated to the HOST-CHDI we sent with
'set-chid'. We might not know about it.
set-cc DEVICE
If we allow the device to connect, set a random new CDID and CK
(connection key). Device saves them for the next time it wants to
connect wireless. We save them for that next time also so we can
authenticate the device (when we see the CDID he uses to id
itself) and the CK to crypto talk to it.
CHID is always 16 hex bytes in 'XX YY ZZ...' form
BANDGROUP is almost always 0001
Examples:
You can default most arguments to '' to get a sane value:
$ $progname set-chid '' '' '' "My host name"
A full sequence:
$ $progname set-chid '' '' '' "My host name"
$ $progname get-cdid ''
$ $progname set-cc ''
EOF
}
# Defaults
# FIXME: CHID should come from a database :), band group from the host
host_CHID="00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff"
host_band_group="0001"
host_name=$(hostname)
devs="$(echo /sys/bus/usb/drivers/wusb-cbaf/[0-9]*)"
hdevs="$(for h in /sys/class/uwb_rc/*/wusbhc; do readlink -f $h; done)"
result=0
case $1 in
start)
for dev in ${2:-$hdevs}
do
uwb_rc=$(readlink -f $dev/uwb_rc)
if cat $uwb_rc/beacon | grep -q -- "-1"
then
echo 13 0 > $uwb_rc/beacon
echo I: started beaconing on ch 13 on $(basename $uwb_rc) >&2
fi
echo $host_CHID > $dev/wusb_chid
echo I: started host $(basename $dev) >&2
done
;;
stop)
for dev in ${2:-$hdevs}
do
echo 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > $dev/wusb_chid
echo I: stopped host $(basename $dev) >&2
uwb_rc=$(readlink -f $dev/uwb_rc)
echo -1 | cat > $uwb_rc/beacon
echo I: stopped beaconing on $(basename $uwb_rc) >&2
done
;;
set-chid)
shift
for dev in ${2:-$devs}; do
echo "${4:-$host_name}" > $dev/wusb_host_name
echo "${3:-$host_band_group}" > $dev/wusb_host_band_groups
echo ${2:-$host_CHID} > $dev/wusb_chid
done
;;
get-cdid)
for dev in ${2:-$devs}
do
cat $dev/wusb_cdid
done
;;
set-cc)
for dev in ${2:-$devs}; do
shift
CDID="$(head --bytes=16 /dev/urandom | od -tx1 -An)"
CK="$(head --bytes=16 /dev/urandom | od -tx1 -An)"
echo "$CDID" > $dev/wusb_cdid
echo "$CK" > $dev/wusb_ck
echo I: CC set >&2
echo "CHID: $(cat $dev/wusb_chid)"
echo "CDID:$CDID"
echo "CK: $CK"
done
;;
help|h|--help|-h)
help
;;
*)
echo "E: Unknown usage" 1>&2
help 1>&2
result=1
esac
exit $result
Documentation/video4linux/CARDLIST.au0828
浏览文件 @ 8c82a17e
0 -> Unknown board (au0828)
1 -> Hauppauge HVR950Q (au0828) [2040:7200,2040:7210,2040:7217,2040:721b,2040:721f,2040:7280,0fd9:0008]
1 -> Hauppauge HVR950Q (au0828) [2040:7200,2040:7210,2040:7217,2040:721b,2040:721e,2040:721f,2040:7280,0fd9:0008]
2 -> Hauppauge HVR850 (au0828) [2040:7240]
3 -> DViCO FusionHDTV USB (au0828) [0fe9:d620]
4 -> Hauppauge HVR950Q rev xxF8 (au0828) [2040:7201,2040:7211,2040:7281]
......
Documentation/video4linux/CARDLIST.tuner
浏览文件 @ 8c82a17e
......@@ -75,3 +75,4 @@ tuner=73 - Samsung TCPG 6121P30A
tuner=75 - Philips TEA5761 FM Radio
tuner=76 - Xceive 5000 tuner
tuner=77 - TCL tuner MF02GIP-5N-E
tuner=78 - Philips FMD1216MEX MK3 Hybrid Tuner
Documentation/vm/unevictable-lru.txt 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
MAINTAINERS
浏览文件 @ 8c82a17e
......@@ -378,8 +378,9 @@ T: git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux-2.6-iommu.git
S: Supported
AMD MICROCODE UPDATE SUPPORT
P: Peter Oruba
M: peter.oruba@amd.com
P: Andreas Herrmann
M: andeas.herrmann3@amd.com
L: amd64-microcode@amd64.org
S: Supported
AMS (Apple Motion Sensor) DRIVER
......@@ -1053,6 +1054,12 @@ L: cbe-oss-dev@ozlabs.org
W: http://www.ibm.com/developerworks/power/cell/
S: Supported
CERTIFIED WIRELESS USB (WUSB) SUBSYSTEM:
P: David Vrabel
M: david.vrabel@csr.com
L: linux-usb@vger.kernel.org
S: Supported
CFAG12864B LCD DRIVER
P: Miguel Ojeda Sandonis
M: miguel.ojeda.sandonis@gmail.com
......@@ -1198,7 +1205,7 @@ S: Maintained
CPU FREQUENCY DRIVERS
P: Dave Jones
M: davej@codemonkey.org.uk
M: davej@redhat.com
L: cpufreq@vger.kernel.org
W: http://www.codemonkey.org.uk/projects/cpufreq/
T: git kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git
......@@ -1427,8 +1434,8 @@ M: rdunlap@xenotime.net
S: Maintained
DOCKING STATION DRIVER
P: Kristen Carlson Accardi
M: kristen.c.accardi@intel.com
P: Shaohua Li
M: shaohua.li@intel.com
L: linux-acpi@vger.kernel.org
S: Supported
......@@ -2103,6 +2110,12 @@ L: linux-ide@vger.kernel.org
L: linux-scsi@vger.kernel.org
S: Orphan
IDLE-I7300
P: Andy Henroid
M: andrew.d.henroid@intel.com
L: linux-pm@lists.linux-foundation.org
S: Supported
IEEE 1394 SUBSYSTEM (drivers/ieee1394)
P: Ben Collins
M: ben.collins@ubuntu.com
......@@ -2176,6 +2189,13 @@ M: maciej.sosnowski@intel.com
L: linux-kernel@vger.kernel.org
S: Supported
INTEL IOMMU (VT-d)
P: David Woodhouse
M: dwmw2@infradead.org
L: iommu@lists.linux-foundation.org
T: git://git.infradead.org/iommu-2.6.git
S: Supported
INTEL IOP-ADMA DMA DRIVER
P: Dan Williams
M: dan.j.williams@intel.com
......@@ -2928,9 +2948,9 @@ S: Maintained
NETEFFECT IWARP RNIC DRIVER (IW_NES)
P: Faisal Latif
M: flatif@neteffect.com
M: faisal.latif@intel.com
P: Chien Tung
M: ctung@neteffect.com
M: chien.tin.tung@intel.com
L: general@lists.openfabrics.org
W: http://www.neteffect.com
S: Supported
......@@ -3173,6 +3193,11 @@ M: olof@lixom.net
L: i2c@lm-sensors.org
S: Maintained
PANASONIC LAPTOP ACPI EXTRAS DRIVER
P: Harald Welte
M: laforge@gnumonks.org
S: Maintained
PANASONIC MN10300/AM33 PORT
P: David Howells
M: dhowells@redhat.com
......@@ -3244,11 +3269,6 @@ L: linux-pci@vger.kernel.org
T: git kernel.org:/pub/scm/linux/kernel/git/jbarnes/pci-2.6.git
S: Supported
PCI HOTPLUG CORE
P: Kristen Carlson Accardi
M: kristen.c.accardi@intel.com
S: Supported
PCIE HOTPLUG DRIVER
P: Kristen Carlson Accardi
M: kristen.c.accardi@intel.com
......@@ -3937,7 +3957,7 @@ M: jbglaw@lug-owl.de
L: linux-kernel@vger.kernel.org
S: Maintained
STABLE BRANCH:
STABLE BRANCH
P: Greg Kroah-Hartman
M: greg@kroah.com
P: Chris Wright
......@@ -3945,6 +3965,13 @@ M: chrisw@sous-sol.org
L: stable@kernel.org
S: Maintained
STAGING SUBSYSTEM
P: Greg Kroah-Hartman
M: gregkh@suse.de
L: linux-kernel@vger.kernel.org
T: quilt kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
S: Maintained
STARFIRE/DURALAN NETWORK DRIVER
P: Ion Badulescu
M: ionut@cs.columbia.edu
......@@ -4184,6 +4211,12 @@ L: sparclinux@vger.kernel.org
T: git kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6.git
S: Maintained
ULTRA-WIDEBAND (UWB) SUBSYSTEM:
P: David Vrabel
M: david.vrabel@csr.com
L: linux-usb@vger.kernel.org
S: Supported
UNIFORM CDROM DRIVER
P: Jens Axboe
M: axboe@kernel.dk
......@@ -4609,6 +4642,11 @@ M: zaga@fly.cc.fer.hr
L: linux-scsi@vger.kernel.org
S: Maintained
WIMEDIA LLC PROTOCOL (WLP) SUBSYSTEM
P: David Vrabel
M: david.vrabel@csr.com
S: Maintained
WISTRON LAPTOP BUTTON DRIVER
P: Miloslav Trmac
M: mitr@volny.cz
......
Makefile
浏览文件 @ 8c82a17e
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 27
EXTRAVERSION =
NAME = Rotary Wombat
SUBLEVEL = 28
EXTRAVERSION = -rc1
NAME = Killer Bat of Doom
# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
......@@ -437,7 +437,7 @@ ifeq ($(config-targets),1)
# KBUILD_DEFCONFIG may point out an alternative default configuration
# used for 'make defconfig'
include $(srctree)/arch/$(SRCARCH)/Makefile
export KBUILD_DEFCONFIG
export KBUILD_DEFCONFIG KBUILD_KCONFIG
config %config: scripts_basic outputmakefile FORCE
$(Q)mkdir -p include/linux include/config
......
arch/alpha/Kconfig
浏览文件 @ 8c82a17e
......@@ -70,6 +70,7 @@ config AUTO_IRQ_AFFINITY
default y
source "init/Kconfig"
source "kernel/Kconfig.freezer"
menu "System setup"
......
arch/alpha/include/asm/thread_info.h
浏览文件 @ 8c82a17e
......@@ -74,12 +74,14 @@ register struct thread_info *__current_thread_info __asm__("$8");
#define TIF_UAC_SIGBUS 7
#define TIF_MEMDIE 8
#define TIF_RESTORE_SIGMASK 9 /* restore signal mask in do_signal */
#define TIF_FREEZE 16 /* is freezing for suspend */
#define _TIF_SYSCALL_TRACE (1<<TIF_SYSCALL_TRACE)
#define _TIF_SIGPENDING (1<<TIF_SIGPENDING)
#define _TIF_NEED_RESCHED (1<<TIF_NEED_RESCHED)
#define _TIF_POLLING_NRFLAG (1<<TIF_POLLING_NRFLAG)
#define _TIF_RESTORE_SIGMASK (1<<TIF_RESTORE_SIGMASK)
#define _TIF_FREEZE (1<<TIF_FREEZE)
/* Work to do on interrupt/exception return. */
#define _TIF_WORK_MASK (_TIF_SIGPENDING | _TIF_NEED_RESCHED)
......
arch/alpha/kernel/core_marvel.c
浏览文件 @ 8c82a17e
......@@ -655,7 +655,7 @@ __marvel_rtc_io(u8 b, unsigned long addr, int write)
case 0x71: /* RTC_PORT(1) */
rtc_access.index = index;
rtc_access.data = BCD_TO_BIN(b);
rtc_access.data = bcd2bin(b);
rtc_access.function = 0x48 + !write; /* GET/PUT_TOY */
#ifdef CONFIG_SMP
......@@ -668,7 +668,7 @@ __marvel_rtc_io(u8 b, unsigned long addr, int write)
#else
__marvel_access_rtc(&rtc_access);
#endif
ret = BIN_TO_BCD(rtc_access.data);
ret = bin2bcd(rtc_access.data);
break;
default:
......
arch/alpha/kernel/osf_sys.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/alpha/kernel/sys_sable.c
浏览文件 @ 8c82a17e
......@@ -47,7 +47,7 @@ typedef struct irq_swizzle_struct
static irq_swizzle_t *sable_lynx_irq_swizzle;
static void sable_lynx_init_irq(int nr_irqs);
static void sable_lynx_init_irq(int nr_of_irqs);
#if defined(CONFIG_ALPHA_GENERIC) || defined(CONFIG_ALPHA_SABLE)
......@@ -530,11 +530,11 @@ sable_lynx_srm_device_interrupt(unsigned long vector)
}
static void __init
sable_lynx_init_irq(int nr_irqs)
sable_lynx_init_irq(int nr_of_irqs)
{
long i;
for (i = 0; i < nr_irqs; ++i) {
for (i = 0; i < nr_of_irqs; ++i) {
irq_desc[i].status = IRQ_DISABLED | IRQ_LEVEL;
irq_desc[i].chip = &sable_lynx_irq_type;
}
......
arch/alpha/kernel/time.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/alpha/oprofile/common.c
浏览文件 @ 8c82a17e
......@@ -106,7 +106,7 @@ op_axp_stop(void)
}
static int
op_axp_create_files(struct super_block * sb, struct dentry * root)
op_axp_create_files(struct super_block *sb, struct dentry *root)
{
int i;
......
arch/arm/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 8c82a17e
......@@ -141,7 +141,7 @@ endif
machine-$(CONFIG_ARCH_MX3) := mx3
machine-$(CONFIG_ARCH_ORION5X) := orion5x
plat-$(CONFIG_PLAT_ORION) := orion
machine-$(CONFIG_ARCH_MSM7X00A) := msm
machine-$(CONFIG_ARCH_MSM) := msm
machine-$(CONFIG_ARCH_LOKI) := loki
machine-$(CONFIG_ARCH_MV78XX0) := mv78xx0
......
arch/arm/common/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/common/sa1111.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/configs/corgi_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/configs/msm_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/configs/spitz_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/configs/trizeps4_defconfig
浏览文件 @ 8c82a17e
......@@ -147,6 +147,7 @@ CONFIG_ARCH_PXA=y
# CONFIG_MACH_MAINSTONE is not set
# CONFIG_ARCH_PXA_IDP is not set
# CONFIG_PXA_SHARPSL is not set
CONFIG_TRIZEPS_PXA=y
CONFIG_MACH_TRIZEPS4=y
CONFIG_MACH_TRIZEPS4_CONXS=y
# CONFIG_MACH_TRIZEPS4_ANY is not set
......
arch/arm/include/asm/div64.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-at91/gpio.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-ixp2000/ixdp2x00.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-ixp4xx/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-kirkwood/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-kirkwood/common.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-kirkwood/common.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/board-halibut.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/clock-7x01a.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/clock.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/clock.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/common.c 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/arm/mach-msm/devices.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/devices.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/dma.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/include/mach/vreg.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/proc_comm.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/proc_comm.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/timer.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-msm/vreg.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-omap2/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-orion5x/common.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-orion5x/common.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/corgi_lcd.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/corgi_ssp.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/pwm.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/sharpsl_pm.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-s3c2443/clock.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mach-sa1100/include/mach/ide.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mm/cache-v4.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/mm/proc-v7.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/plat-mxc/include/mach/mxc_nand.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/plat-s3c24xx/pwm-clock.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/arm/plat-s3c24xx/pwm.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/atngw100/Kconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/atngw100/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/atngw100/evklcd10x.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/atngw100/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/favr-32/Kconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/favr-32/Makefile 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/favr-32/flash.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/favr-32/setup.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/mimc200/Makefile 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/mimc200/flash.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/mimc200/fram.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/boards/mimc200/setup.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/configs/atngw100_evklcd100_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/configs/atngw100_evklcd101_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/configs/favr-32_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/configs/mimc200_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/mach-at32ap/at32ap700x.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/mach-at32ap/cpufreq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/avr32/mach-at32ap/extint.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/blackfin/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/cris/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/cris/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/cris/arch-v10/drivers/ds1302.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/cris/kernel/time.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/frv/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/h8300/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/configs/generic_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/configs/tiger_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/dig/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/dig/dig_vtd_iommu.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/dig/machvec_vtd.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/ia32/audit.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/ia32/ia32_entry.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/break.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/cacheflush.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/device.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/dma-mapping.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/iommu.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/kregs.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/machvec.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/machvec_dig_vtd.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/machvec_xen.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/meminit.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/native/inst.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/native/pvchk_inst.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/paravirt.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/pci.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/ptrace.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/pvclock-abi.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/swiotlb.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/sync_bitops.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/syscall.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/thread_info.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/timex.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/unistd.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/events.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/grant_table.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/hypercall.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/hypervisor.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/inst.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/interface.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/irq.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/minstate.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/page.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/privop.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/xcom_hcall.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/include/asm/xen/xencomm.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/asm-offsets.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/crash_dump.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/efi.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/ivt.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/msi_ia64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/nr-irqs.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/paravirt.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/paravirt_inst.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/pci-dma.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/pci-swiotlb.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/process.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/ptrace.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kernel/signal.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/kvm/kvm-ia64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/lib/flush.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/mm/tlb.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/oprofile/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/oprofile/perfmon.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/scripts/pvcheck.sed 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/sn/kernel/io_acpi_init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/Kconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/Makefile 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/grant-table.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/hypercall.S 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/hypervisor.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/irq_xen.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/irq_xen.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/machvec.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/suspend.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/time.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/time.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/xcom_hcall.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/xen_pv_ops.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/xencomm.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/xenivt.S 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/ia64/xen/xensetup.S 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m32r/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m32r/kernel/smpboot.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m32r/oprofile/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/amiga/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/atari/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/atari/stram.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/bvme6000/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/bvme6000/rtc.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/kernel/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/mvme147/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/mvme16x/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/q40/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/sun3/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68k/sun3x/config.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/m68knommu/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/dec/time.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/include/asm/txx9/tx4938.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/oprofile/common.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/oprofile/op_impl.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/sibyte/swarm/rtc_m41t81.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mips/txx9/rbtx4938/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mn10300/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/mn10300/kernel/rtc.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/hpux/fs.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/ide.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/pdc.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/ptrace.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/ropes.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/thread_info.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/unistd.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/include/asm/unwind.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/.gitignore 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/asm-offsets.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/firmware.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/head.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/ptrace.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/real2.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/syscall_table.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/time.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/kernel/unwind.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/parisc/oprofile/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/addnote.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/cuboot-52xx.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/cuboot-acadia.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/dts/acadia.dts 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/dts/hcu4.dts 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/dts/mpc8536ds.dts
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/dts/mpc8572ds.dts
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/libfdt-wrapper.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/main.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/ops.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/string.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/boot/wrapper
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/configs/40x/acadia_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/configs/40x/hcu4_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/include/asm/kdump.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/include/asm/page.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/include/asm/pci.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/include/asm/ps3av.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/include/asm/ptrace.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/include/asm/signal.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/crash_dump.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/iommu.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/machine_kexec.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/misc_64.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/pci-common.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/signal.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/signal_64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/kernel/udbg_16550.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/40x/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/40x/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/40x/hcu4.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/40x/ppc40x_simple.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/44x/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/cell/ras.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/platforms/cell/smp.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/sysdev/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/powerpc/sysdev/ppc4xx_gpio.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/s390/include/asm/thread_info.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/Kconfig.debug
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/board-ap325rxa.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/board-edosk7760.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/board-magicpanelr2.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/board-rsk7203.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/board-sh7785lcr.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/board-shmin.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-edosk7705/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-highlander/pinmux-r7785rp.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-hp6xx/pm.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-hp6xx/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-lboxre2/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-lboxre2/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-microdev/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-microdev/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-migor/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-r2d/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-r2d/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-sdk7780/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-sdk7780/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-sh7763rdp/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-systemh/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-systemh/irq.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-systemh/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-titan/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boards/mach-titan/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boot/.gitignore
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boot/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boot/compressed/Makefile_32
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/boot/compressed/misc_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/ap325rxa_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/cayman_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/dreamcast_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/edosk7760_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/hp6xx_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/landisk_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/lboxre2_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/microdev_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/migor_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/r7780mp_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/r7785rp_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/rsk7203_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/rts7751r2dplus_qemu_defconfig 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/sdk7780_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7206_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7343_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7619_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7705_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7712_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7721_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7722_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7750_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7751_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/se7780_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/sh03_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/sh7763rdp_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/sh7785lcr_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/shmin_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/shx3_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/snapgear_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/systemh_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/configs/titan_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/drivers/pci/ops-lboxre2.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/drivers/pci/ops-r7780rp.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/drivers/pci/ops-sdk7780.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/drivers/pci/ops-titan.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/bitops-llsc.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/bitops.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/clock.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/cmpxchg-llsc.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/elf.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/fpu.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/ftrace.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/gpio.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/hw_irq.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/io.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/io_generic.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/irq.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/kdebug.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/kprobes.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/machvec.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/migor.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/sh/include/asm/mmzone.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/page.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/pgtable.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/processor.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/processor_32.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/processor_64.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/ptrace.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/r7780rp.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/sh/include/asm/rtc.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/setup.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/sh_mobile_lcdc.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/sh/include/asm/sizes.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/smp.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/syscall.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/syscall_32.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/syscall_64.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/syscalls.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/syscalls_32.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/syscalls_64.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/system.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/system_32.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/thread_info.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/asm/uaccess_64.h
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/cpu-sh2a/cpu/sh7203.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/cpu-sh3/cpu/sh7720.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/cpu-sh4/cpu/sh7722.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/cpu-sh4/cpu/sh7723.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/cpu-sh4/cpu/sh7785.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/mach-common/mach/highlander.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/include/mach-common/mach/migor.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/Makefile_32
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/Makefile_64
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/clock.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/irq/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/irq/intc.c 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/sh/kernel/cpu/irq/ipr.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh2a/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh2a/pinmux-sh7203.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh3/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh3/pinmux-sh7720.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4/fpu.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4/softfloat.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4a/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4a/pinmux-sh7722.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4a/pinmux-sh7723.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4a/pinmux-sh7785.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh4a/smp-shx3.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh5/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/cpu/sh5/clock-sh5.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/crash_dump.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/dump_task.c 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/sh/kernel/entry-common.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/gpio.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/io_generic.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/kprobes.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/machvec.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/process_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/process_64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/ptrace_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/ptrace_64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/setup.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/sh_ksyms_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/signal_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/signal_64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/smp.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/stacktrace.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/sys_sh.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/sys_sh32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/time_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/time_64.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/timers/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/timers/timer-broadcast.c 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/timers/timer-cmt.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/timers/timer-tmu.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/kernel/traps_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/lib/div64-generic.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/lib/io.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/cache-debugfs.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/cache-sh4.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/consistent.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/fault_32.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/pg-nommu.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/pmb.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/mm/tlb-nommu.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sh/tools/mach-types
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc/kernel/apc.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc/kernel/head.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc/oprofile/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc64/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc64/kernel/trampoline.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/sparc64/oprofile/init.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/Kconfig 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/Kconfig.common 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/Kconfig.i386 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/Kconfig.rest 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/Kconfig.um 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/Kconfig.x86 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/Kconfig.x86_64 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/Makefile-os-Linux
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/drivers/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/drivers/ubd_kern.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/as-layout.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/asm/fixmap.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/asm/page.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/asm/pgtable.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/asm/ptrace-generic.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/asm/system.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/asm/thread_info.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/common-offsets.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/os.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/shared/as-layout.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/shared/common-offsets.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/shared/ldt.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/shared/os.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/shared/um_mmu.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/shared/user.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/include/sigcontext.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/sysdep-i386/ptrace.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/sysdep-i386/stub.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/sysdep-i386/tls.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/sysdep-x86_64/ptrace.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/sysdep-x86_64/stub.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/sysdep-x86_64/tls.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/um_mmu.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/include/user.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/kernel/exec.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/kernel/internal.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/kernel/signal.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/kernel/syscall.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/os-Linux/include/file.h 已删除 100644 → 0
浏览文件 @ 4ce72a2c
此差异已折叠。
arch/um/os-Linux/skas/mem.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/asm/archparam.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/asm/processor.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/asm/ptrace.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/shared/sysdep/host_ldt.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/shared/sysdep/ptrace.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/shared/sysdep/stub.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/shared/sysdep/system.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/shared/sysdep/tls.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/signal.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/stub.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-i386/syscalls.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/asm/processor.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/asm/ptrace.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/shared/sysdep/host_ldt.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/shared/sysdep/ptrace.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/shared/sysdep/stub.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/shared/sysdep/system.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/shared/sysdep/tls.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/stub.S
浏览文件 @ 8c82a17e
此差异已折叠。
arch/um/sys-x86_64/syscall_table.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/Kconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/Makefile
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/boot/compressed/misc.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/boot/video-bios.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/boot/video-vesa.c
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/configs/i386_defconfig
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/a.out-core.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/a.out.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/acpi.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/agp.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/alternative.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/amd_iommu.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/amd_iommu_types.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/apic.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/apicdef.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/arch_hooks.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/asm.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/atomic_32.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/atomic_64.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/auxvec.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/bigsmp/apic.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/bios_ebda.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/bitops.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/boot.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/bootparam.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/bug.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/bugs.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/byteorder.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/cache.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/cacheflush.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/calgary.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/checksum_32.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/checksum_64.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/cmpxchg_32.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/cmpxchg_64.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/compat.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/cpu.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/cpufeature.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/current.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/debugreg.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/delay.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/desc.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/desc_defs.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/device.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/div64.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/dma-mapping.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/dma.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/dmi.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/ds.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/dwarf2.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/e820.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/edac.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/efi.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/elf.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/emergency-restart.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/es7000/apic.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
arch/x86/include/asm/fb.h 0 → 100644
浏览文件 @ 8c82a17e
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或