Skip to content

K
kernel_linux

OpenHarmony / kernel_linux
上一次同步 4 年多

通知 15
Star 8
Fork 2
K
kernel_linux
提交 91d0322b 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge branch 'linus' into x86/urgent

上级 065cb3df 50515af2
展开全部 显示空白变更内容
内联 并排
Showing with 73036 addition and 28646 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
Documentation/ABI/testing/sysfs-block
浏览文件 @ 91d0322b
......@@ -26,3 +26,37 @@ Description:
I/O statistics of partition <part>. The format is the
same as the above-written /sys/block/<disk>/stat
format.
What: /sys/block/<disk>/integrity/format
Date: June 2008
Contact: Martin K. Petersen <martin.petersen@oracle.com>
Description:
Metadata format for integrity capable block device.
E.g. T10-DIF-TYPE1-CRC.
What: /sys/block/<disk>/integrity/read_verify
Date: June 2008
Contact: Martin K. Petersen <martin.petersen@oracle.com>
Description:
Indicates whether the block layer should verify the
integrity of read requests serviced by devices that
support sending integrity metadata.
What: /sys/block/<disk>/integrity/tag_size
Date: June 2008
Contact: Martin K. Petersen <martin.petersen@oracle.com>
Description:
Number of bytes of integrity tag space available per
512 bytes of data.
What: /sys/block/<disk>/integrity/write_generate
Date: June 2008
Contact: Martin K. Petersen <martin.petersen@oracle.com>
Description:
Indicates whether the block layer should automatically
generate checksums for write requests bound for
devices that support receiving integrity metadata.
Documentation/ABI/testing/sysfs-bus-css 0 → 100644
浏览文件 @ 91d0322b
What: /sys/bus/css/devices/.../type
Date: March 2008
Contact: Cornelia Huck <cornelia.huck@de.ibm.com>
linux-s390@vger.kernel.org
Description: Contains the subchannel type, as reported by the hardware.
This attribute is present for all subchannel types.
What: /sys/bus/css/devices/.../modalias
Date: March 2008
Contact: Cornelia Huck <cornelia.huck@de.ibm.com>
linux-s390@vger.kernel.org
Description: Contains the module alias as reported with uevents.
It is of the format css:t<type> and present for all
subchannel types.
What: /sys/bus/css/drivers/io_subchannel/.../chpids
Date: December 2002
Contact: Cornelia Huck <cornelia.huck@de.ibm.com>
linux-s390@vger.kernel.org
Description: Contains the ids of the channel paths used by this
subchannel, as reported by the channel subsystem
during subchannel recognition.
Note: This is an I/O-subchannel specific attribute.
Users: s390-tools, HAL
What: /sys/bus/css/drivers/io_subchannel/.../pimpampom
Date: December 2002
Contact: Cornelia Huck <cornelia.huck@de.ibm.com>
linux-s390@vger.kernel.org
Description: Contains the PIM/PAM/POM values, as reported by the
channel subsystem when last queried by the common I/O
layer (this implies that this attribute is not neccessarily
in sync with the values current in the channel subsystem).
Note: This is an I/O-subchannel specific attribute.
Users: s390-tools, HAL
Documentation/ABI/testing/sysfs-firmware-memmap 0 → 100644
浏览文件 @ 91d0322b
What: /sys/firmware/memmap/
Date: June 2008
Contact: Bernhard Walle <bwalle@suse.de>
Description:
On all platforms, the firmware provides a memory map which the
kernel reads. The resources from that memory map are registered
in the kernel resource tree and exposed to userspace via
/proc/iomem (together with other resources).
However, on most architectures that firmware-provided memory
map is modified afterwards by the kernel itself, either because
the kernel merges that memory map with other information or
just because the user overwrites that memory map via command
line.
kexec needs the raw firmware-provided memory map to setup the
parameter segment of the kernel that should be booted with
kexec. Also, the raw memory map is useful for debugging. For
that reason, /sys/firmware/memmap is an interface that provides
the raw memory map to userspace.
The structure is as follows: Under /sys/firmware/memmap there
are subdirectories with the number of the entry as their name:
/sys/firmware/memmap/0
/sys/firmware/memmap/1
/sys/firmware/memmap/2
/sys/firmware/memmap/3
...
The maximum depends on the number of memory map entries provided
by the firmware. The order is just the order that the firmware
provides.
Each directory contains three files:
start : The start address (as hexadecimal number with the
'0x' prefix).
end : The end address, inclusive (regardless whether the
firmware provides inclusive or exclusive ranges).
type : Type of the entry as string. See below for a list of
valid types.
So, for example:
/sys/firmware/memmap/0/start
/sys/firmware/memmap/0/end
/sys/firmware/memmap/0/type
/sys/firmware/memmap/1/start
...
Currently following types exist:
- System RAM
- ACPI Tables
- ACPI Non-volatile Storage
- reserved
Following shell snippet can be used to display that memory
map in a human-readable format:
-------------------- 8< ----------------------------------------
#!/bin/bash
cd /sys/firmware/memmap
for dir in * ; do
start=$(cat $dir/start)
end=$(cat $dir/end)
type=$(cat $dir/type)
printf "%016x-%016x (%s)\n" $start $[ $end +1] "$type"
done
-------------------- >8 ----------------------------------------
Documentation/HOWTO
浏览文件 @ 91d0322b
......@@ -377,7 +377,7 @@ Bug Reporting
bugzilla.kernel.org is where the Linux kernel developers track kernel
bugs. Users are encouraged to report all bugs that they find in this
tool. For details on how to use the kernel bugzilla, please see:
http://test.kernel.org/bugzilla/faq.html
http://bugzilla.kernel.org/page.cgi?id=faq.html
The file REPORTING-BUGS in the main kernel source directory has a good
template for how to report a possible kernel bug, and details what kind
......
Documentation/block/data-integrity.txt 0 → 100644
浏览文件 @ 91d0322b
----------------------------------------------------------------------
1. INTRODUCTION
Modern filesystems feature checksumming of data and metadata to
protect against data corruption. However, the detection of the
corruption is done at read time which could potentially be months
after the data was written. At that point the original data that the
application tried to write is most likely lost.
The solution is to ensure that the disk is actually storing what the
application meant it to. Recent additions to both the SCSI family
protocols (SBC Data Integrity Field, SCC protection proposal) as well
as SATA/T13 (External Path Protection) try to remedy this by adding
support for appending integrity metadata to an I/O. The integrity
metadata (or protection information in SCSI terminology) includes a
checksum for each sector as well as an incrementing counter that
ensures the individual sectors are written in the right order. And
for some protection schemes also that the I/O is written to the right
place on disk.
Current storage controllers and devices implement various protective
measures, for instance checksumming and scrubbing. But these
technologies are working in their own isolated domains or at best
between adjacent nodes in the I/O path. The interesting thing about
DIF and the other integrity extensions is that the protection format
is well defined and every node in the I/O path can verify the
integrity of the I/O and reject it if corruption is detected. This
allows not only corruption prevention but also isolation of the point
of failure.
----------------------------------------------------------------------
2. THE DATA INTEGRITY EXTENSIONS
As written, the protocol extensions only protect the path between
controller and storage device. However, many controllers actually
allow the operating system to interact with the integrity metadata
(IMD). We have been working with several FC/SAS HBA vendors to enable
the protection information to be transferred to and from their
controllers.
The SCSI Data Integrity Field works by appending 8 bytes of protection
information to each sector. The data + integrity metadata is stored
in 520 byte sectors on disk. Data + IMD are interleaved when
transferred between the controller and target. The T13 proposal is
similar.
Because it is highly inconvenient for operating systems to deal with
520 (and 4104) byte sectors, we approached several HBA vendors and
encouraged them to allow separation of the data and integrity metadata
scatter-gather lists.
The controller will interleave the buffers on write and split them on
read. This means that the Linux can DMA the data buffers to and from
host memory without changes to the page cache.
Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
is somewhat heavy to compute in software. Benchmarks found that
calculating this checksum had a significant impact on system
performance for a number of workloads. Some controllers allow a
lighter-weight checksum to be used when interfacing with the operating
system. Emulex, for instance, supports the TCP/IP checksum instead.
The IP checksum received from the OS is converted to the 16-bit CRC
when writing and vice versa. This allows the integrity metadata to be
generated by Linux or the application at very low cost (comparable to
software RAID5).
The IP checksum is weaker than the CRC in terms of detecting bit
errors. However, the strength is really in the separation of the data
buffers and the integrity metadata. These two distinct buffers much
match up for an I/O to complete.
The separation of the data and integrity metadata buffers as well as
the choice in checksums is referred to as the Data Integrity
Extensions. As these extensions are outside the scope of the protocol
bodies (T10, T13), Oracle and its partners are trying to standardize
them within the Storage Networking Industry Association.
----------------------------------------------------------------------
3. KERNEL CHANGES
The data integrity framework in Linux enables protection information
to be pinned to I/Os and sent to/received from controllers that
support it.
The advantage to the integrity extensions in SCSI and SATA is that
they enable us to protect the entire path from application to storage
device. However, at the same time this is also the biggest
disadvantage. It means that the protection information must be in a
format that can be understood by the disk.
Generally Linux/POSIX applications are agnostic to the intricacies of
the storage devices they are accessing. The virtual filesystem switch
and the block layer make things like hardware sector size and
transport protocols completely transparent to the application.
However, this level of detail is required when preparing the
protection information to send to a disk. Consequently, the very
concept of an end-to-end protection scheme is a layering violation.
It is completely unreasonable for an application to be aware whether
it is accessing a SCSI or SATA disk.
The data integrity support implemented in Linux attempts to hide this
from the application. As far as the application (and to some extent
the kernel) is concerned, the integrity metadata is opaque information
that's attached to the I/O.
The current implementation allows the block layer to automatically
generate the protection information for any I/O. Eventually the
intent is to move the integrity metadata calculation to userspace for
user data. Metadata and other I/O that originates within the kernel
will still use the automatic generation interface.
Some storage devices allow each hardware sector to be tagged with a
16-bit value. The owner of this tag space is the owner of the block
device. I.e. the filesystem in most cases. The filesystem can use
this extra space to tag sectors as they see fit. Because the tag
space is limited, the block interface allows tagging bigger chunks by
way of interleaving. This way, 8*16 bits of information can be
attached to a typical 4KB filesystem block.
This also means that applications such as fsck and mkfs will need
access to manipulate the tags from user space. A passthrough
interface for this is being worked on.
----------------------------------------------------------------------
4. BLOCK LAYER IMPLEMENTATION DETAILS
4.1 BIO
The data integrity patches add a new field to struct bio when
CONFIG_BLK_DEV_INTEGRITY is enabled. bio->bi_integrity is a pointer
to a struct bip which contains the bio integrity payload. Essentially
a bip is a trimmed down struct bio which holds a bio_vec containing
the integrity metadata and the required housekeeping information (bvec
pool, vector count, etc.)
A kernel subsystem can enable data integrity protection on a bio by
calling bio_integrity_alloc(bio). This will allocate and attach the
bip to the bio.
Individual pages containing integrity metadata can subsequently be
attached using bio_integrity_add_page().
bio_free() will automatically free the bip.
4.2 BLOCK DEVICE
Because the format of the protection data is tied to the physical
disk, each block device has been extended with a block integrity
profile (struct blk_integrity). This optional profile is registered
with the block layer using blk_integrity_register().
The profile contains callback functions for generating and verifying
the protection data, as well as getting and setting application tags.
The profile also contains a few constants to aid in completing,
merging and splitting the integrity metadata.
Layered block devices will need to pick a profile that's appropriate
for all subdevices. blk_integrity_compare() can help with that. DM
and MD linear, RAID0 and RAID1 are currently supported. RAID4/5/6
will require extra work due to the application tag.
----------------------------------------------------------------------
5.0 BLOCK LAYER INTEGRITY API
5.1 NORMAL FILESYSTEM
The normal filesystem is unaware that the underlying block device
is capable of sending/receiving integrity metadata. The IMD will
be automatically generated by the block layer at submit_bio() time
in case of a WRITE. A READ request will cause the I/O integrity
to be verified upon completion.
IMD generation and verification can be toggled using the
/sys/block/<bdev>/integrity/write_generate
and
/sys/block/<bdev>/integrity/read_verify
flags.
5.2 INTEGRITY-AWARE FILESYSTEM
A filesystem that is integrity-aware can prepare I/Os with IMD
attached. It can also use the application tag space if this is
supported by the block device.
int bdev_integrity_enabled(block_device, int rw);
bdev_integrity_enabled() will return 1 if the block device
supports integrity metadata transfer for the data direction
specified in 'rw'.
bdev_integrity_enabled() honors the write_generate and
read_verify flags in sysfs and will respond accordingly.
int bio_integrity_prep(bio);
To generate IMD for WRITE and to set up buffers for READ, the
filesystem must call bio_integrity_prep(bio).
Prior to calling this function, the bio data direction and start
sector must be set, and the bio should have all data pages
added. It is up to the caller to ensure that the bio does not
change while I/O is in progress.
bio_integrity_prep() should only be called if
bio_integrity_enabled() returned 1.
int bio_integrity_tag_size(bio);
If the filesystem wants to use the application tag space it will
first have to find out how much storage space is available.
Because tag space is generally limited (usually 2 bytes per
sector regardless of sector size), the integrity framework
supports interleaving the information between the sectors in an
I/O.
Filesystems can call bio_integrity_tag_size(bio) to find out how
many bytes of storage are available for that particular bio.
Another option is bdev_get_tag_size(block_device) which will
return the number of available bytes per hardware sector.
int bio_integrity_set_tag(bio, void *tag_buf, len);
After a successful return from bio_integrity_prep(),
bio_integrity_set_tag() can be used to attach an opaque tag
buffer to a bio. Obviously this only makes sense if the I/O is
a WRITE.
int bio_integrity_get_tag(bio, void *tag_buf, len);
Similarly, at READ I/O completion time the filesystem can
retrieve the tag buffer using bio_integrity_get_tag().
6.3 PASSING EXISTING INTEGRITY METADATA
Filesystems that either generate their own integrity metadata or
are capable of transferring IMD from user space can use the
following calls:
struct bip * bio_integrity_alloc(bio, gfp_mask, nr_pages);
Allocates the bio integrity payload and hangs it off of the bio.
nr_pages indicate how many pages of protection data need to be
stored in the integrity bio_vec list (similar to bio_alloc()).
The integrity payload will be freed at bio_free() time.
int bio_integrity_add_page(bio, page, len, offset);
Attaches a page containing integrity metadata to an existing
bio. The bio must have an existing bip,
i.e. bio_integrity_alloc() must have been called. For a WRITE,
the integrity metadata in the pages must be in a format
understood by the target device with the notable exception that
the sector numbers will be remapped as the request traverses the
I/O stack. This implies that the pages added using this call
will be modified during I/O! The first reference tag in the
integrity metadata must have a value of bip->bip_sector.
Pages can be added using bio_integrity_add_page() as long as
there is room in the bip bio_vec array (nr_pages).
Upon completion of a READ operation, the attached pages will
contain the integrity metadata received from the storage device.
It is up to the receiver to process them and verify data
integrity upon completion.
6.4 REGISTERING A BLOCK DEVICE AS CAPABLE OF EXCHANGING INTEGRITY
METADATA
To enable integrity exchange on a block device the gendisk must be
registered as capable:
int blk_integrity_register(gendisk, blk_integrity);
The blk_integrity struct is a template and should contain the
following:
static struct blk_integrity my_profile = {
.name = "STANDARDSBODY-TYPE-VARIANT-CSUM",
.generate_fn = my_generate_fn,
.verify_fn = my_verify_fn,
.get_tag_fn = my_get_tag_fn,
.set_tag_fn = my_set_tag_fn,
.tuple_size = sizeof(struct my_tuple_size),
.tag_size = <tag bytes per hw sector>,
};
'name' is a text string which will be visible in sysfs. This is
part of the userland API so chose it carefully and never change
it. The format is standards body-type-variant.
E.g. T10-DIF-TYPE1-IP or T13-EPP-0-CRC.
'generate_fn' generates appropriate integrity metadata (for WRITE).
'verify_fn' verifies that the data buffer matches the integrity
metadata.
'tuple_size' must be set to match the size of the integrity
metadata per sector. I.e. 8 for DIF and EPP.
'tag_size' must be set to identify how many bytes of tag space
are available per hardware sector. For DIF this is either 2 or
0 depending on the value of the Control Mode Page ATO bit.
See 6.2 for a description of get_tag_fn and set_tag_fn.
----------------------------------------------------------------------
2007-12-24 Martin K. Petersen <martin.petersen@oracle.com>
Documentation/ftrace.txt 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
Documentation/ioctl-number.txt
浏览文件 @ 91d0322b
......@@ -117,6 +117,7 @@ Code Seq# Include File Comments
<mailto:natalia@nikhefk.nikhef.nl>
'c' 00-7F linux/comstats.h conflict!
'c' 00-7F linux/coda.h conflict!
'c' 80-9F asm-s390/chsc.h
'd' 00-FF linux/char/drm/drm/h conflict!
'd' 00-DF linux/video_decoder.h conflict!
'd' F0-FF linux/digi1.h
......
Documentation/kdump/kdump.txt
浏览文件 @ 91d0322b
......@@ -109,7 +109,7 @@ 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 and ia64 architectures support relocatable kernel.
of today, i386, x86_64 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
......
Documentation/kernel-parameters.txt
浏览文件 @ 91d0322b
......@@ -271,6 +271,17 @@ and is between 256 and 4096 characters. It is defined in the file
aic79xx= [HW,SCSI]
See Documentation/scsi/aic79xx.txt.
amd_iommu= [HW,X86-84]
Pass parameters to the AMD IOMMU driver in the system.
Possible values are:
isolate - enable device isolation (each device, as far
as possible, will get its own protection
domain)
amd_iommu_size= [HW,X86-64]
Define the size of the aperture for the AMD IOMMU
driver. Possible values are:
'32M', '64M' (default), '128M', '256M', '512M', '1G'
amijoy.map= [HW,JOY] Amiga joystick support
Map of devices attached to JOY0DAT and JOY1DAT
Format: <a>,<b>
......@@ -599,6 +610,29 @@ and is between 256 and 4096 characters. It is defined in the file
See drivers/char/README.epca and
Documentation/digiepca.txt.
disable_mtrr_cleanup [X86]
enable_mtrr_cleanup [X86]
The kernel tries to adjust MTRR layout from continuous
to discrete, to make X server driver able to add WB
entry later. This parameter enables/disables that.
mtrr_chunk_size=nn[KMG] [X86]
used for mtrr cleanup. It is largest continous chunk
that could hold holes aka. UC entries.
mtrr_gran_size=nn[KMG] [X86]
Used for mtrr cleanup. It is granularity of mtrr block.
Default is 1.
Large value could prevent small alignment from
using up MTRRs.
mtrr_spare_reg_nr=n [X86]
Format: <integer>
Range: 0,7 : spare reg number
Default : 1
Used for mtrr cleanup. It is spare mtrr entries number.
Set to 2 or more if your graphical card needs more.
disable_mtrr_trim [X86, Intel and AMD only]
By default the kernel will trim any uncacheable
memory out of your available memory pool based on
......@@ -1208,6 +1242,11 @@ and is between 256 and 4096 characters. It is defined in the file
mtdparts= [MTD]
See drivers/mtd/cmdlinepart.c.
mtdset= [ARM]
ARM/S3C2412 JIVE boot control
See arch/arm/mach-s3c2412/mach-jive.c
mtouchusb.raw_coordinates=
[HW] Make the MicroTouch USB driver use raw coordinates
('y', default) or cooked coordinates ('n')
......@@ -2116,6 +2155,9 @@ and is between 256 and 4096 characters. It is defined in the file
usbhid.mousepoll=
[USBHID] The interval which mice are to be polled at.
add_efi_memmap [EFI; x86-32,X86-64] Include EFI memory map in
kernel's map of available physical RAM.
vdso= [X86-32,SH,x86-64]
vdso=2: enable compat VDSO (default with COMPAT_VDSO)
vdso=1: enable VDSO (default)
......
Documentation/networking/ip-sysctl.txt
浏览文件 @ 91d0322b
......@@ -148,9 +148,9 @@ tcp_available_congestion_control - STRING
but not loaded.
tcp_base_mss - INTEGER
The initial value of search_low to be used by Packetization Layer
Path MTU Discovery (MTU probing). If MTU probing is enabled,
this is the inital MSS used by the connection.
The initial value of search_low to be used by the packetization layer
Path MTU discovery (MTU probing). If MTU probing is enabled,
this is the initial MSS used by the connection.
tcp_congestion_control - STRING
Set the congestion control algorithm to be used for new
......@@ -186,9 +186,8 @@ tcp_frto - INTEGER
where packet loss is typically due to random radio interference
rather than intermediate router congestion. F-RTO is sender-side
only modification. Therefore it does not require any support from
the peer, but in a typical case, however, where wireless link is
the local access link and most of the data flows downlink, the
faraway servers should have F-RTO enabled to take advantage of it.
the peer.
If set to 1, basic version is enabled. 2 enables SACK enhanced
F-RTO if flow uses SACK. The basic version can be used also when
SACK is in use though scenario(s) with it exists where F-RTO
......@@ -276,7 +275,7 @@ tcp_mem - vector of 3 INTEGERs: min, pressure, max
memory.
tcp_moderate_rcvbuf - BOOLEAN
If set, TCP performs receive buffer autotuning, attempting to
If set, TCP performs receive buffer auto-tuning, attempting to
automatically size the buffer (no greater than tcp_rmem[2]) to
match the size required by the path for full throughput. Enabled by
default.
......@@ -336,7 +335,7 @@ tcp_rmem - vector of 3 INTEGERs: min, default, max
pressure.
Default: 8K
default: default size of receive buffer used by TCP sockets.
default: initial size of receive buffer used by TCP sockets.
This value overrides net.core.rmem_default used by other protocols.
Default: 87380 bytes. This value results in window of 65535 with
default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
......@@ -344,8 +343,10 @@ tcp_rmem - vector of 3 INTEGERs: min, default, max
max: maximal size of receive buffer allowed for automatically
selected receiver buffers for TCP socket. This value does not override
net.core.rmem_max, "static" selection via SO_RCVBUF does not use this.
Default: 87380*2 bytes.
net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
automatic tuning of that socket's receive buffer size, in which
case this value is ignored.
Default: between 87380B and 4MB, depending on RAM size.
tcp_sack - BOOLEAN
Enable select acknowledgments (SACKS).
......@@ -358,7 +359,7 @@ tcp_slow_start_after_idle - BOOLEAN
Default: 1
tcp_stdurg - BOOLEAN
Use the Host requirements interpretation of the TCP urg pointer field.
Use the Host requirements interpretation of the TCP urgent pointer field.
Most hosts use the older BSD interpretation, so if you turn this on
Linux might not communicate correctly with them.
Default: FALSE
......@@ -371,12 +372,12 @@ tcp_synack_retries - INTEGER
tcp_syncookies - BOOLEAN
Only valid when the kernel was compiled with CONFIG_SYNCOOKIES
Send out syncookies when the syn backlog queue of a socket
overflows. This is to prevent against the common 'syn flood attack'
overflows. This is to prevent against the common 'SYN flood attack'
Default: FALSE
Note, that syncookies is fallback facility.
It MUST NOT be used to help highly loaded servers to stand
against legal connection rate. If you see synflood warnings
against legal connection rate. If you see SYN flood warnings
in your logs, but investigation shows that they occur
because of overload with legal connections, you should tune
another parameters until this warning disappear.
......@@ -386,7 +387,7 @@ tcp_syncookies - BOOLEAN
to use TCP extensions, can result in serious degradation
of some services (f.e. SMTP relaying), visible not by you,
but your clients and relays, contacting you. While you see
synflood warnings in logs not being really flooded, your server
SYN flood warnings in logs not being really flooded, your server
is seriously misconfigured.
tcp_syn_retries - INTEGER
......@@ -419,19 +420,21 @@ tcp_window_scaling - BOOLEAN
Enable window scaling as defined in RFC1323.
tcp_wmem - vector of 3 INTEGERs: min, default, max
min: Amount of memory reserved for send buffers for TCP socket.
min: Amount of memory reserved for send buffers for TCP sockets.
Each TCP socket has rights to use it due to fact of its birth.
Default: 4K
default: Amount of memory allowed for send buffers for TCP socket
by default. This value overrides net.core.wmem_default used
by other protocols, it is usually lower than net.core.wmem_default.
default: initial size of send buffer used by TCP sockets. This
value overrides net.core.wmem_default used by other protocols.
It is usually lower than net.core.wmem_default.
Default: 16K
max: Maximal amount of memory allowed for automatically selected
send buffers for TCP socket. This value does not override
net.core.wmem_max, "static" selection via SO_SNDBUF does not use this.
Default: 128K
max: Maximal amount of memory allowed for automatically tuned
send buffers for TCP sockets. This value does not override
net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
automatic tuning of that socket's send buffer size, in which case
this value is ignored.
Default: between 64K and 4MB, depending on RAM size.
tcp_workaround_signed_windows - BOOLEAN
If set, assume no receipt of a window scaling option means the
......@@ -1060,24 +1063,193 @@ bridge-nf-filter-pppoe-tagged - BOOLEAN
Default: 1
UNDOCUMENTED:
proc/sys/net/sctp/* Variables:
addip_enable - BOOLEAN
Enable or disable extension of Dynamic Address Reconfiguration
(ADD-IP) functionality specified in RFC5061. This extension provides
the ability to dynamically add and remove new addresses for the SCTP
associations.
1: Enable extension.
0: Disable extension.
Default: 0
addip_noauth_enable - BOOLEAN
Dynamic Address Reconfiguration (ADD-IP) requires the use of
authentication to protect the operations of adding or removing new
addresses. This requirement is mandated so that unauthorized hosts
would not be able to hijack associations. However, older
implementations may not have implemented this requirement while
allowing the ADD-IP extension. For reasons of interoperability,
we provide this variable to control the enforcement of the
authentication requirement.
1: Allow ADD-IP extension to be used without authentication. This
should only be set in a closed environment for interoperability
with older implementations.
0: Enforce the authentication requirement
Default: 0
auth_enable - BOOLEAN
Enable or disable Authenticated Chunks extension. This extension
provides the ability to send and receive authenticated chunks and is
required for secure operation of Dynamic Address Reconfiguration
(ADD-IP) extension.
1: Enable this extension.
0: Disable this extension.
Default: 0
prsctp_enable - BOOLEAN
Enable or disable the Partial Reliability extension (RFC3758) which
is used to notify peers that a given DATA should no longer be expected.
1: Enable extension
0: Disable
Default: 1
max_burst - INTEGER
The limit of the number of new packets that can be initially sent. It
controls how bursty the generated traffic can be.
Default: 4
association_max_retrans - INTEGER
Set the maximum number for retransmissions that an association can
attempt deciding that the remote end is unreachable. If this value
is exceeded, the association is terminated.
Default: 10
max_init_retransmits - INTEGER
The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
that an association will attempt before declaring the destination
unreachable and terminating.
Default: 8
path_max_retrans - INTEGER
The maximum number of retransmissions that will be attempted on a given
path. Once this threshold is exceeded, the path is considered
unreachable, and new traffic will use a different path when the
association is multihomed.
Default: 5
rto_initial - INTEGER
The initial round trip timeout value in milliseconds that will be used
in calculating round trip times. This is the initial time interval
for retransmissions.
Default: 3000
dev_weight FIXME
discovery_slots FIXME
discovery_timeout FIXME
fast_poll_increase FIXME
ip6_queue_maxlen FIXME
lap_keepalive_time FIXME
lo_cong FIXME
max_baud_rate FIXME
max_dgram_qlen FIXME
max_noreply_time FIXME
max_tx_data_size FIXME
max_tx_window FIXME
min_tx_turn_time FIXME
mod_cong FIXME
no_cong FIXME
no_cong_thresh FIXME
slot_timeout FIXME
warn_noreply_time FIXME
rto_max - INTEGER
The maximum value (in milliseconds) of the round trip timeout. This
is the largest time interval that can elapse between retransmissions.
Default: 60000
rto_min - INTEGER
The minimum value (in milliseconds) of the round trip timeout. This
is the smallest time interval the can elapse between retransmissions.
Default: 1000
hb_interval - INTEGER
The interval (in milliseconds) between HEARTBEAT chunks. These chunks
are sent at the specified interval on idle paths to probe the state of
a given path between 2 associations.
Default: 30000
sack_timeout - INTEGER
The amount of time (in milliseconds) that the implementation will wait
to send a SACK.
Default: 200
valid_cookie_life - INTEGER
The default lifetime of the SCTP cookie (in milliseconds). The cookie
is used during association establishment.
Default: 60000
cookie_preserve_enable - BOOLEAN
Enable or disable the ability to extend the lifetime of the SCTP cookie
that is used during the establishment phase of SCTP association
1: Enable cookie lifetime extension.
0: Disable
Default: 1
rcvbuf_policy - INTEGER
Determines if the receive buffer is attributed to the socket or to
association. SCTP supports the capability to create multiple
associations on a single socket. When using this capability, it is
possible that a single stalled association that's buffering a lot
of data may block other associations from delivering their data by
consuming all of the receive buffer space. To work around this,
the rcvbuf_policy could be set to attribute the receiver buffer space
to each association instead of the socket. This prevents the described
blocking.
1: rcvbuf space is per association
0: recbuf space is per socket
Default: 0
sndbuf_policy - INTEGER
Similar to rcvbuf_policy above, this applies to send buffer space.
1: Send buffer is tracked per association
0: Send buffer is tracked per socket.
Default: 0
sctp_mem - vector of 3 INTEGERs: min, pressure, max
Number of pages allowed for queueing by all SCTP sockets.
min: Below this number of pages SCTP is not bothered about its
memory appetite. When amount of memory allocated by SCTP exceeds
this number, SCTP starts to moderate memory usage.
pressure: This value was introduced to follow format of tcp_mem.
max: Number of pages allowed for queueing by all SCTP sockets.
Default is calculated at boot time from amount of available memory.
sctp_rmem - vector of 3 INTEGERs: min, default, max
See tcp_rmem for a description.
sctp_wmem - vector of 3 INTEGERs: min, default, max
See tcp_wmem for a description.
UNDOCUMENTED:
/proc/sys/net/core/*
dev_weight FIXME
/proc/sys/net/unix/*
max_dgram_qlen FIXME
/proc/sys/net/irda/*
fast_poll_increase FIXME
warn_noreply_time FIXME
discovery_slots FIXME
slot_timeout FIXME
max_baud_rate FIXME
discovery_timeout FIXME
lap_keepalive_time FIXME
max_noreply_time FIXME
max_tx_data_size FIXME
max_tx_window FIXME
min_tx_turn_time FIXME
Documentation/nmi_watchdog.txt
浏览文件 @ 91d0322b
......@@ -22,8 +22,7 @@ CONFIG_X86_UP_IOAPIC is for uniprocessor with an IO-APIC. [Note: certain
kernel debugging options, such as Kernel Stack Meter or Kernel Tracer,
may implicitly disable the NMI watchdog.]
For x86-64, the needed APIC is always compiled in, and the NMI watchdog is
always enabled with I/O-APIC mode (nmi_watchdog=1).
For x86-64, the needed APIC is always compiled in.
Using local APIC (nmi_watchdog=2) needs the first performance register, so
you can't use it for other purposes (such as high precision performance
......@@ -67,12 +66,11 @@ time. The I/O APIC watchdog is driven externally and has no such shortcoming.
But its NMI frequency is much higher, resulting in a more significant hit
to the overall system performance.
NOTE: starting with 2.4.2-ac18 the NMI-oopser is disabled by default,
you have to enable it with a boot time parameter. Prior to 2.4.2-ac18
the NMI-oopser is enabled unconditionally on x86 SMP boxes.
On x86 nmi_watchdog is disabled by default so you have to enable it with
a boot time parameter.
On x86-64 the NMI oopser is on by default. On 64bit Intel CPUs
it uses IO-APIC by default and on AMD it uses local APIC.
NOTE: In kernels prior to 2.4.2-ac18 the NMI-oopser is enabled unconditionally
on x86 SMP boxes.
[ feel free to send bug reports, suggestions and patches to
Ingo Molnar <mingo@redhat.com> or the Linux SMP mailing
......
Documentation/scheduler/sched-domains.txt
浏览文件 @ 91d0322b
......@@ -61,10 +61,7 @@ builder by #define'ing ARCH_HASH_SCHED_DOMAIN, and exporting your
arch_init_sched_domains function. This function will attach domains to all
CPUs using cpu_attach_domain.
Implementors should change the line
#undef SCHED_DOMAIN_DEBUG
to
#define SCHED_DOMAIN_DEBUG
in kernel/sched.c as this enables an error checking parse of the sched domains
The sched-domains debugging infrastructure can be enabled by enabling
CONFIG_SCHED_DEBUG. This enables an error checking parse of the sched domains
which should catch most possible errors (described above). It also prints out
the domain structure in a visual format.
Documentation/scheduler/sched-rt-group.txt
浏览文件 @ 91d0322b
......@@ -51,9 +51,9 @@ needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s =
0.00015s. So this group can be scheduled with a period of 0.005s and a run time
of 0.00015s.
The remaining CPU time will be used for user input and other tass. Because
The remaining CPU time will be used for user input and other tasks. Because
realtime tasks have explicitly allocated the CPU time they need to perform
their tasks, buffer underruns in the graphocs or audio can be eliminated.
their tasks, buffer underruns in the graphics or audio can be eliminated.
NOTE: the above example is not fully implemented as of yet (2.6.25). We still
lack an EDF scheduler to make non-uniform periods usable.
......
Documentation/sound/alsa/ALSA-Configuration.txt
浏览文件 @ 91d0322b
......@@ -753,8 +753,11 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
[Multiple options for each card instance]
model - force the model name
position_fix - Fix DMA pointer (0 = auto, 1 = none, 2 = POSBUF, 3 = FIFO size)
position_fix - Fix DMA pointer (0 = auto, 1 = use LPIB, 2 = POSBUF)
probe_mask - Bitmask to probe codecs (default = -1, meaning all slots)
bdl_pos_adj - Specifies the DMA IRQ timing delay in samples.
Passing -1 will make the driver to choose the appropriate
value based on the controller chip.
[Single (global) options]
single_cmd - Use single immediate commands to communicate with
......@@ -845,7 +848,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
ALC269
basic Basic preset
ALC662
ALC662/663
3stack-dig 3-stack (2-channel) with SPDIF
3stack-6ch 3-stack (6-channel)
3stack-6ch-dig 3-stack (6-channel) with SPDIF
......@@ -853,6 +856,10 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
lenovo-101e Lenovo laptop
eeepc-p701 ASUS Eeepc P701
eeepc-ep20 ASUS Eeepc EP20
m51va ASUS M51VA
g71v ASUS G71V
h13 ASUS H13
g50v ASUS G50V
auto auto-config reading BIOS (default)
ALC882/885
......@@ -1091,7 +1098,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
This occurs when the access to non-existing or non-working codec slot
(likely a modem one) causes a stall of the communication via HD-audio
bus. You can see which codec slots are probed by enabling
CONFIG_SND_DEBUG_DETECT, or simply from the file name of the codec
CONFIG_SND_DEBUG_VERBOSE, or simply from the file name of the codec
proc files. Then limit the slots to probe by probe_mask option.
For example, probe_mask=1 means to probe only the first slot, and
probe_mask=4 means only the third slot.
......@@ -2267,6 +2274,10 @@ case above again, the first two slots are already reserved. If any
other driver (e.g. snd-usb-audio) is loaded before snd-interwave or
snd-ens1371, it will be assigned to the third or later slot.
When a module name is given with '!', the slot will be given for any
modules but that name. For example, "slots=!snd-pcsp" will reserve
the first slot for any modules but snd-pcsp.
ALSA PCM devices to OSS devices mapping
=======================================
......
Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl
浏览文件 @ 91d0322b
......@@ -6127,8 +6127,8 @@ struct _snd_pcm_runtime {
<para>
<function>snd_printdd()</function> is compiled in only when
<constant>CONFIG_SND_DEBUG_DETECT</constant> is set. Please note
that <constant>DEBUG_DETECT</constant> is not set as default
<constant>CONFIG_SND_DEBUG_VERBOSE</constant> is set. Please note
that <constant>CONFIG_SND_DEBUG_VERBOSE</constant> is not set as default
even if you configure the alsa-driver with
<option>--with-debug=full</option> option. You need to give
explicitly <option>--with-debug=detect</option> option instead.
......
Documentation/tracers/mmiotrace.txt 0 → 100644
浏览文件 @ 91d0322b
In-kernel memory-mapped I/O tracing
Home page and links to optional user space tools:
http://nouveau.freedesktop.org/wiki/MmioTrace
MMIO tracing was originally developed by Intel around 2003 for their Fault
Injection Test Harness. In Dec 2006 - Jan 2007, using the code from Intel,
Jeff Muizelaar created a tool for tracing MMIO accesses with the Nouveau
project in mind. Since then many people have contributed.
Mmiotrace was built for reverse engineering any memory-mapped IO device with
the Nouveau project as the first real user. Only x86 and x86_64 architectures
are supported.
Out-of-tree mmiotrace was originally modified for mainline inclusion and
ftrace framework by Pekka Paalanen <pq@iki.fi>.
Preparation
-----------
Mmiotrace feature is compiled in by the CONFIG_MMIOTRACE option. Tracing is
disabled by default, so it is safe to have this set to yes. SMP systems are
supported, but tracing is unreliable and may miss events if more than one CPU
is on-line, therefore mmiotrace takes all but one CPU off-line during run-time
activation. You can re-enable CPUs by hand, but you have been warned, there
is no way to automatically detect if you are losing events due to CPUs racing.
Usage Quick Reference
---------------------
$ 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 none > /debug/tracing/current_tracer
Check for lost events.
Usage
-----
Make sure debugfs is mounted to /debug. If not, (requires root privileges)
$ mount -t debugfs debugfs /debug
Check that the driver you are about to trace is not loaded.
Activate mmiotrace (requires root privileges):
$ echo mmiotrace > /debug/tracing/current_tracer
Start storing the trace:
$ cat /debug/tracing/trace_pipe > mydump.txt &
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
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.
Shut down mmiotrace (requires root privileges):
$ echo none > /debug/tracing/current_tracer
The 'cat' process exits. If it does not, kill it by issuing 'fg' command and
pressing ctrl+c.
Check that mmiotrace did not lose events due to a buffer filling up. Either
$ grep -i lost mydump.txt
which tells you exactly how many events were lost, or use
$ dmesg
to view your kernel log and look for "mmiotrace has lost events" warning. If
events were lost, the trace is incomplete. You should enlarge the buffers and
try again. Buffers are enlarged by first seeing how large the current buffers
are:
$ cat /debug/tracing/trace_entries
gives you a number. Approximately double this number and write it back, for
instance:
$ echo 128000 > /debug/tracing/trace_entries
Then start again from the top.
If you are doing a trace for a driver project, e.g. Nouveau, you should also
do the following before sending your results:
$ lspci -vvv > lspci.txt
$ dmesg > dmesg.txt
$ tar zcf pciid-nick-mmiotrace.tar.gz mydump.txt lspci.txt dmesg.txt
and then send the .tar.gz file. The trace compresses considerably. Replace
"pciid" and "nick" with the PCI ID or model name of your piece of hardware
under investigation and your nick name.
How Mmiotrace Works
-------------------
Access to hardware IO-memory is gained by mapping addresses from PCI bus by
calling one of the ioremap_*() functions. Mmiotrace is hooked into the
__ioremap() function and gets called whenever a mapping is created. Mapping is
an event that is recorded into the trace log. Note, that ISA range mappings
are not caught, since the mapping always exists and is returned directly.
MMIO accesses are recorded via page faults. Just before __ioremap() returns,
the mapped pages are marked as not present. Any access to the pages causes a
fault. The page fault handler calls mmiotrace to handle the fault. Mmiotrace
marks the page present, sets TF flag to achieve single stepping and exits the
fault handler. The instruction that faulted is executed and debug trap is
entered. Here mmiotrace again marks the page as not present. The instruction
is decoded to get the type of operation (read/write), data width and the value
read or written. These are stored to the trace log.
Setting the page present in the page fault handler has a race condition on SMP
machines. During the single stepping other CPUs may run freely on that page
and events can be missed without a notice. Re-enabling other CPUs during
tracing is discouraged.
Trace Log Format
----------------
The raw log is text and easily filtered with e.g. grep and awk. One record is
one line in the log. A record starts with a keyword, followed by keyword
dependant arguments. Arguments are separated by a space, or continue until the
end of line. The format for version 20070824 is as follows:
Explanation Keyword Space separated arguments
---------------------------------------------------------------------------
read event R width, timestamp, map id, physical, value, PC, PID
write event W width, timestamp, map id, physical, value, PC, PID
ioremap event MAP timestamp, map id, physical, virtual, length, PC, PID
iounmap event UNMAP timestamp, map id, PC, PID
marker MARK timestamp, text
version VERSION the string "20070824"
info for reader LSPCI one line from lspci -v
PCI address map PCIDEV space separated /proc/bus/pci/devices data
unk. opcode UNKNOWN timestamp, map id, physical, data, PC, PID
Timestamp is in seconds with decimals. Physical is a PCI bus address, virtual
is a kernel virtual address. Width is the data width in bytes and value is the
data value. Map id is an arbitrary id number identifying the mapping that was
used in an operation. PC is the program counter and PID is process id. PC is
zero if it is not recorded. PID is always zero as tracing MMIO accesses
originating in user space memory is not yet supported.
For instance, the following awk filter will pass all 32-bit writes that target
physical addresses in the range [0xfb73ce40, 0xfb800000[
$ awk '/W 4 / { adr=strtonum($5); if (adr >= 0xfb73ce40 &&
adr < 0xfb800000) print; }'
Tools for Developers
--------------------
The user space tools include utilities for:
- replacing numeric addresses and values with hardware register names
- replaying MMIO logs, i.e., re-executing the recorded writes
Documentation/i386/boot.txt → Documentation/x86/i386/boot.txt
浏览文件 @ 91d0322b
THE LINUX/I386 BOOT PROTOCOL
----------------------------
THE LINUX/x86 BOOT PROTOCOL
---------------------------
H. Peter Anvin <hpa@zytor.com>
Last update 2007-05-23
On the i386 platform, the Linux kernel uses a rather complicated boot
On the x86 platform, the Linux kernel uses a rather complicated boot
convention. This has evolved partially due to historical aspects, as
well as the desire in the early days to have the kernel itself be a
bootable image, the complicated PC memory model and due to changed
expectations in the PC industry caused by the effective demise of
real-mode DOS as a mainstream operating system.
Currently, the following versions of the Linux/i386 boot protocol exist.
Currently, the following versions of the Linux/x86 boot protocol exist.
Old kernels: zImage/Image support only. Some very early kernels
may not even support a command line.
......@@ -372,10 +369,17 @@ Protocol: 2.00+
- If 0, the protected-mode code is loaded at 0x10000.
- If 1, the protected-mode code is loaded at 0x100000.
Bit 5 (write): QUIET_FLAG
- If 0, print early messages.
- If 1, suppress early messages.
This requests to the kernel (decompressor and early
kernel) to not write early messages that require
accessing the display hardware directly.
Bit 6 (write): KEEP_SEGMENTS
Protocol: 2.07+
- if 0, reload the segment registers in the 32bit entry point.
- if 1, do not reload the segment registers in the 32bit entry point.
- If 0, reload the segment registers in the 32bit entry point.
- If 1, do not reload the segment registers in the 32bit entry point.
Assume that %cs %ds %ss %es are all set to flat segments with
a base of 0 (or the equivalent for their environment).
......@@ -504,7 +508,7 @@ Protocol: 2.06+
maximum size was 255.
Field name: hardware_subarch
Type: write
Type: write (optional, defaults to x86/PC)
Offset/size: 0x23c/4
Protocol: 2.07+
......@@ -520,11 +524,13 @@ Protocol: 2.07+
0x00000002 Xen
Field name: hardware_subarch_data
Type: write
Type: write (subarch-dependent)
Offset/size: 0x240/8
Protocol: 2.07+
A pointer to data that is specific to hardware subarch
This field is currently unused for the default x86/PC environment,
do not modify.
Field name: payload_offset
Type: read
......@@ -545,6 +551,34 @@ Protocol: 2.08+
The length of the payload.
Field name: setup_data
Type: write (special)
Offset/size: 0x250/8
Protocol: 2.09+
The 64-bit physical pointer to NULL terminated single linked list of
struct setup_data. This is used to define a more extensible boot
parameters passing mechanism. The definition of struct setup_data is
as follow:
struct setup_data {
u64 next;
u32 type;
u32 len;
u8 data[0];
};
Where, the next is a 64-bit physical pointer to the next node of
linked list, the next field of the last node is 0; the type is used
to identify the contents of data; the len is the length of data
field; the data holds the real payload.
This list may be modified at a number of points during the bootup
process. Therefore, when modifying this list one should always make
sure to consider the case where the linked list already contains
entries.
**** THE IMAGE CHECKSUM
From boot protocol version 2.08 onwards the CRC-32 is calculated over
......@@ -553,6 +587,7 @@ initial remainder of 0xffffffff. The checksum is appended to the
file; therefore the CRC of the file up to the limit specified in the
syssize field of the header is always 0.
**** THE KERNEL COMMAND LINE
The kernel command line has become an important way for the boot
......@@ -584,28 +619,6 @@ command line is entered using the following protocol:
covered by setup_move_size, so you may need to adjust this
field.
Field name: setup_data
Type: write (obligatory)
Offset/size: 0x250/8
Protocol: 2.09+
The 64-bit physical pointer to NULL terminated single linked list of
struct setup_data. This is used to define a more extensible boot
parameters passing mechanism. The definition of struct setup_data is
as follow:
struct setup_data {
u64 next;
u32 type;
u32 len;
u8 data[0];
};
Where, the next is a 64-bit physical pointer to the next node of
linked list, the next field of the last node is 0; the type is used
to identify the contents of data; the len is the length of data
field; the data holds the real payload.
**** MEMORY LAYOUT OF THE REAL-MODE CODE
......
Documentation/x86_64/mm.txt → Documentation/x86/x86_64/mm.txt
浏览文件 @ 91d0322b
......@@ -11,9 +11,8 @@ ffffc10000000000 - ffffc1ffffffffff (=40 bits) hole
ffffc20000000000 - ffffe1ffffffffff (=45 bits) vmalloc/ioremap space
ffffe20000000000 - ffffe2ffffffffff (=40 bits) virtual memory map (1TB)
... unused hole ...
ffffffff80000000 - ffffffff82800000 (=40 MB) kernel text mapping, from phys 0
... unused hole ...
ffffffff88000000 - fffffffffff00000 (=1919 MB) module mapping space
ffffffff80000000 - ffffffffa0000000 (=512 MB) kernel text mapping, from phys 0
ffffffffa0000000 - fffffffffff00000 (=1536 MB) module mapping space
The direct mapping covers all memory in the system up to the highest
memory address (this means in some cases it can also include PCI memory
......
Documentation/x86_64/uefi.txt → Documentation/x86/x86_64/uefi.txt
浏览文件 @ 91d0322b
......@@ -36,3 +36,7 @@ Mechanics:
services.
noefi turn off all EFI runtime services
reboot_type=k turn off EFI reboot runtime service
- If the EFI memory map has additional entries not in the E820 map,
you can include those entries in the kernels memory map of available
physical RAM by using the following kernel command line parameter.
add_efi_memmap include EFI memory map of available physical RAM
MAINTAINERS
浏览文件 @ 91d0322b
......@@ -376,6 +376,12 @@ L: linux-geode@lists.infradead.org (moderated for non-subscribers)
W: http://www.amd.com/us-en/ConnectivitySolutions/TechnicalResources/0,,50_2334_2452_11363,00.html
S: Supported
AMD IOMMU (AMD-VI)
P: Joerg Roedel
M: joerg.roedel@amd.com
L: iommu@lists.linux-foundation.org
S: Supported
AMS (Apple Motion Sensor) DRIVER
P: Stelian Pop
M: stelian@popies.net
......@@ -3082,8 +3088,8 @@ L: linux-scsi@vger.kernel.org
S: Maintained
OPROFILE
P: Philippe Elie
M: phil.el@wanadoo.fr
P: Robert Richter
M: robert.richter@amd.com
L: oprofile-list@lists.sf.net
S: Maintained
......
Makefile
浏览文件 @ 91d0322b
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 26
EXTRAVERSION = -rc8
EXTRAVERSION =
NAME = Rotary Wombat
# *DOCUMENTATION*
......@@ -450,7 +450,7 @@ scripts: scripts_basic include/config/auto.conf
# Objects we will link into vmlinux / subdirs we need to visit
init-y := init/
drivers-y := drivers/ sound/
drivers-y := drivers/ sound/ firmware/
net-y := net/
libs-y := lib/
core-y := usr/
......@@ -528,6 +528,10 @@ KBUILD_CFLAGS += -g
KBUILD_AFLAGS += -gdwarf-2
endif
ifdef CONFIG_FTRACE
KBUILD_CFLAGS += -pg
endif
# We trigger additional mismatches with less inlining
ifdef CONFIG_DEBUG_SECTION_MISMATCH
KBUILD_CFLAGS += $(call cc-option, -fno-inline-functions-called-once)
......@@ -994,6 +998,16 @@ PHONY += depend dep
depend dep:
@echo '*** Warning: make $@ is unnecessary now.'
# ---------------------------------------------------------------------------
# Firmware install
INSTALL_FW_PATH=$(INSTALL_MOD_PATH)/lib/firmware
export INSTALL_FW_PATH
PHONY += firmware_install
firmware_install: FORCE
@mkdir -p $(objtree)/firmware
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.fwinst obj=firmware __fw_install
# ---------------------------------------------------------------------------
# Kernel headers
INSTALL_HDR_PATH=$(objtree)/usr
......@@ -1080,6 +1094,7 @@ _modinst_:
# boot script depmod is the master version.
PHONY += _modinst_post
_modinst_post: _modinst_
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.fwinst obj=firmware __fw_modinst
$(call cmd,depmod)
else # CONFIG_MODULES
......@@ -1197,6 +1212,8 @@ help:
@echo '* vmlinux - Build the bare kernel'
@echo '* modules - Build all modules'
@echo ' modules_install - Install all modules to INSTALL_MOD_PATH (default: /)'
@echo ' firmware_install- Install all firmware to INSTALL_FW_PATH'
@echo ' (default: $$(INSTALL_MOD_PATH)/lib/firmware)'
@echo ' dir/ - Build all files in dir and below'
@echo ' dir/file.[ois] - Build specified target only'
@echo ' dir/file.ko - Build module including final link'
......
arch/arm/Kconfig
浏览文件 @ 91d0322b
......@@ -14,6 +14,8 @@ config ARM
select HAVE_OPROFILE
select HAVE_KPROBES if (!XIP_KERNEL)
select HAVE_KRETPROBES if (HAVE_KPROBES)
select HAVE_FTRACE if (!XIP_KERNEL)
select HAVE_DYNAMIC_FTRACE if (HAVE_FTRACE)
help
The ARM series is a line of low-power-consumption RISC chip designs
licensed by ARM Ltd and targeted at embedded applications and
......@@ -22,6 +24,9 @@ config ARM
Europe. There is an ARM Linux project with a web page at
<http://www.arm.linux.org.uk/>.
config HAVE_PWM
bool
config SYS_SUPPORTS_APM_EMULATION
bool
......@@ -84,6 +89,11 @@ config STACKTRACE_SUPPORT
bool
default y
config HAVE_LATENCYTOP_SUPPORT
bool
depends on !SMP
default y
config LOCKDEP_SUPPORT
bool
default y
......@@ -147,6 +157,10 @@ config FIQ
config ARCH_MTD_XIP
bool
config GENERIC_HARDIRQS_NO__DO_IRQ
bool
def_bool y
if OPROFILE
config OPROFILE_ARMV6
......@@ -232,13 +246,6 @@ config ARCH_CLPS711X
help
Support for Cirrus Logic 711x/721x based boards.
config ARCH_CO285
bool "Co-EBSA285"
select FOOTBRIDGE
select FOOTBRIDGE_ADDIN
help
Support for Intel's EBSA285 companion chip.
config ARCH_EBSA110
bool "EBSA-110"
select ISA
......@@ -299,6 +306,8 @@ config ARCH_IOP32X
depends on MMU
select PLAT_IOP
select PCI
select GENERIC_GPIO
select HAVE_GPIO_LIB
help
Support for Intel's 80219 and IOP32X (XScale) family of
processors.
......@@ -308,6 +317,8 @@ config ARCH_IOP33X
depends on MMU
select PLAT_IOP
select PCI
select GENERIC_GPIO
select HAVE_GPIO_LIB
help
Support for Intel's IOP33X (XScale) family of processors.
......@@ -347,6 +358,16 @@ config ARCH_L7200
If you have any questions or comments about the Linux kernel port
to this board, send e-mail to <sjhill@cotw.com>.
config ARCH_KIRKWOOD
bool "Marvell Kirkwood"
select PCI
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
help
Support for the following Marvell Kirkwood series SoCs:
88F6180, 88F6192 and 88F6281.
config ARCH_KS8695
bool "Micrel/Kendin KS8695"
select GENERIC_GPIO
......@@ -365,9 +386,31 @@ config ARCH_NS9XXX
<http://www.digi.com/products/microprocessors/index.jsp>
config ARCH_LOKI
bool "Marvell Loki (88RC8480)"
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
help
Support for the Marvell Loki (88RC8480) SoC.
config ARCH_MV78XX0
bool "Marvell MV78xx0"
select PCI
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
help
Support for the following Marvell MV78xx0 series SoCs:
MV781x0, MV782x0.
config ARCH_MXC
bool "Freescale MXC/iMX-based"
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select ARCH_MTD_XIP
select GENERIC_GPIO
select HAVE_GPIO_LIB
help
Support for Freescale MXC/iMX-based family of processors
......@@ -381,7 +424,8 @@ config ARCH_ORION5X
select PLAT_ORION
help
Support for the following Marvell Orion 5x series SoCs:
Orion-1 (5181), Orion-NAS (5182), Orion-2 (5281.)
Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
Orion-2 (5281).
config ARCH_PNX4008
bool "Philips Nexperia PNX4008 Mobile"
......@@ -406,6 +450,7 @@ config ARCH_RPC
select FIQ
select TIMER_ACORN
select ARCH_MAY_HAVE_PC_FDC
select HAVE_PATA_PLATFORM
select ISA_DMA_API
select NO_IOPORT
help
......@@ -502,6 +547,10 @@ source "arch/arm/mach-ixp2000/Kconfig"
source "arch/arm/mach-ixp23xx/Kconfig"
source "arch/arm/mach-loki/Kconfig"
source "arch/arm/mach-mv78xx0/Kconfig"
source "arch/arm/mach-pxa/Kconfig"
source "arch/arm/mach-sa1100/Kconfig"
......@@ -514,6 +563,8 @@ source "arch/arm/mach-omap2/Kconfig"
source "arch/arm/mach-orion5x/Kconfig"
source "arch/arm/mach-kirkwood/Kconfig"
source "arch/arm/plat-s3c24xx/Kconfig"
source "arch/arm/plat-s3c/Kconfig"
......@@ -703,27 +754,6 @@ config PREEMPT
Say Y here if you are building a kernel for a desktop, embedded
or real-time system. Say N if you are unsure.
config NO_IDLE_HZ
bool "Dynamic tick timer"
depends on !GENERIC_CLOCKEVENTS
help
Select this option if you want to disable continuous timer ticks
and have them programmed to occur as required. This option saves
power as the system can remain in idle state for longer.
By default dynamic tick is disabled during the boot, and can be
manually enabled with:
echo 1 > /sys/devices/system/timer/timer0/dyn_tick
Alternatively, if you want dynamic tick automatically enabled
during boot, pass "dyntick=enable" via the kernel command string.
Please note that dynamic tick may affect the accuracy of
timekeeping on some platforms depending on the implementation.
Currently at least OMAP, PXA2xx and SA11x0 platforms are known
to have accurate timekeeping with dynamic tick.
config HZ
int
default 128 if ARCH_L7200
......@@ -789,7 +819,7 @@ source "mm/Kconfig"
config LEDS
bool "Timer and CPU usage LEDs"
depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
depends on ARCH_CDB89712 || ARCH_EBSA110 || \
ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
......
arch/arm/Makefile
浏览文件 @ 91d0322b
......@@ -100,8 +100,6 @@ textofs-y := 0x00008000
incdir-$(CONFIG_ARCH_CLPS7500) := cl7500
machine-$(CONFIG_FOOTBRIDGE) := footbridge
incdir-$(CONFIG_FOOTBRIDGE) := ebsa285
machine-$(CONFIG_ARCH_CO285) := footbridge
incdir-$(CONFIG_ARCH_CO285) := ebsa285
machine-$(CONFIG_ARCH_SHARK) := shark
machine-$(CONFIG_ARCH_SA1100) := sa1100
ifeq ($(CONFIG_ARCH_SA1100),y)
......@@ -135,11 +133,15 @@ endif
machine-$(CONFIG_ARCH_NETX) := netx
machine-$(CONFIG_ARCH_NS9XXX) := ns9xxx
machine-$(CONFIG_ARCH_DAVINCI) := davinci
machine-$(CONFIG_ARCH_KIRKWOOD) := kirkwood
machine-$(CONFIG_ARCH_KS8695) := ks8695
incdir-$(CONFIG_ARCH_MXC) := mxc
machine-$(CONFIG_ARCH_MX2) := mx2
machine-$(CONFIG_ARCH_MX3) := mx3
machine-$(CONFIG_ARCH_ORION5X) := orion5x
machine-$(CONFIG_ARCH_MSM7X00A) := msm
machine-$(CONFIG_ARCH_LOKI) := loki
machine-$(CONFIG_ARCH_MV78XX0) := mv78xx0
ifeq ($(CONFIG_ARCH_EBSA110),y)
# This is what happens if you forget the IOCS16 line.
......@@ -190,8 +192,6 @@ core-$(CONFIG_PLAT_S3C24XX) += arch/arm/plat-s3c24xx/
core-$(CONFIG_ARCH_MXC) += arch/arm/plat-mxc/
drivers-$(CONFIG_OPROFILE) += arch/arm/oprofile/
drivers-$(CONFIG_ARCH_CLPS7500) += drivers/acorn/char/
drivers-$(CONFIG_ARCH_L7200) += drivers/acorn/char/
libs-y := arch/arm/lib/ $(libs-y)
......
arch/arm/boot/compressed/Makefile
浏览文件 @ 91d0322b
......@@ -69,6 +69,12 @@ SEDFLAGS = s/TEXT_START/$(ZTEXTADDR)/;s/BSS_START/$(ZBSSADDR)/
targets := vmlinux vmlinux.lds piggy.gz piggy.o font.o font.c \
head.o misc.o $(OBJS)
ifeq ($(CONFIG_FTRACE),y)
ORIG_CFLAGS := $(KBUILD_CFLAGS)
KBUILD_CFLAGS = $(subst -pg, , $(ORIG_CFLAGS))
endif
EXTRA_CFLAGS := -fpic -fno-builtin
EXTRA_AFLAGS :=
......
arch/arm/boot/compressed/head.S
浏览文件 @ 91d0322b
......@@ -623,8 +623,8 @@ proc_types:
b __armv4_mmu_cache_off
b __armv4_mmu_cache_flush
.word 0x56055310 @ Feroceon
.word 0xfffffff0
.word 0x56050000 @ Feroceon
.word 0xff0f0000
b __armv4_mmu_cache_on
b __armv4_mmu_cache_off
b __armv5tej_mmu_cache_flush
......
arch/arm/common/Makefile
浏览文件 @ 91d0322b
......@@ -2,7 +2,6 @@
# Makefile for the linux kernel.
#
obj-y += rtctime.o
obj-$(CONFIG_ARM_GIC) += gic.o
obj-$(CONFIG_ARM_VIC) += vic.o
obj-$(CONFIG_ICST525) += icst525.o
......
arch/arm/common/rtctime.c 已删除 100644 → 0
浏览文件 @ 065cb3df
/*
* linux/arch/arm/common/rtctime.c
*
* Copyright (C) 2003 Deep Blue Solutions Ltd.
* Based on sa1100-rtc.c, Nils Faerber, CIH, Nicolas Pitre.
* Based on rtc.c by Paul Gortmaker
*
* 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.
*/
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/time.h>
#include <linux/rtc.h>
#include <linux/poll.h>
#include <linux/proc_fs.h>
#include <linux/miscdevice.h>
#include <linux/spinlock.h>
#include <linux/capability.h>
#include <linux/device.h>
#include <linux/mutex.h>
#include <asm/rtc.h>
static DECLARE_WAIT_QUEUE_HEAD(rtc_wait);
static struct fasync_struct *rtc_async_queue;
/*
* rtc_lock protects rtc_irq_data
*/
static DEFINE_SPINLOCK(rtc_lock);
static unsigned long rtc_irq_data;
/*
* rtc_sem protects rtc_inuse and rtc_ops
*/
static DEFINE_MUTEX(rtc_mutex);
static unsigned long rtc_inuse;
static struct rtc_ops *rtc_ops;
#define rtc_epoch 1900UL
/*
* Calculate the next alarm time given the requested alarm time mask
* and the current time.
*/
void rtc_next_alarm_time(struct rtc_time *next, struct rtc_time *now, struct rtc_time *alrm)
{
unsigned long next_time;
unsigned long now_time;
next->tm_year = now->tm_year;
next->tm_mon = now->tm_mon;
next->tm_mday = now->tm_mday;
next->tm_hour = alrm->tm_hour;
next->tm_min = alrm->tm_min;
next->tm_sec = alrm->tm_sec;
rtc_tm_to_time(now, &now_time);
rtc_tm_to_time(next, &next_time);
if (next_time < now_time) {
/* Advance one day */
next_time += 60 * 60 * 24;
rtc_time_to_tm(next_time, next);
}
}
EXPORT_SYMBOL(rtc_next_alarm_time);
static inline int rtc_arm_read_time(struct rtc_ops *ops, struct rtc_time *tm)
{
memset(tm, 0, sizeof(struct rtc_time));
return ops->read_time(tm);
}
static inline int rtc_arm_set_time(struct rtc_ops *ops, struct rtc_time *tm)
{
int ret;
ret = rtc_valid_tm(tm);
if (ret == 0)
ret = ops->set_time(tm);
return ret;
}
static inline int rtc_arm_read_alarm(struct rtc_ops *ops, struct rtc_wkalrm *alrm)
{
int ret = -EINVAL;
if (ops->read_alarm) {
memset(alrm, 0, sizeof(struct rtc_wkalrm));
ret = ops->read_alarm(alrm);
}
return ret;
}
static inline int rtc_arm_set_alarm(struct rtc_ops *ops, struct rtc_wkalrm *alrm)
{
int ret = -EINVAL;
if (ops->set_alarm)
ret = ops->set_alarm(alrm);
return ret;
}
void rtc_update(unsigned long num, unsigned long events)
{
spin_lock(&rtc_lock);
rtc_irq_data = (rtc_irq_data + (num << 8)) | events;
spin_unlock(&rtc_lock);
wake_up_interruptible(&rtc_wait);
kill_fasync(&rtc_async_queue, SIGIO, POLL_IN);
}
EXPORT_SYMBOL(rtc_update);
static ssize_t
rtc_read(struct file *file, char __user *buf, size_t count, loff_t *ppos)
{
DECLARE_WAITQUEUE(wait, current);
unsigned long data;
ssize_t ret;
if (count < sizeof(unsigned long))
return -EINVAL;
add_wait_queue(&rtc_wait, &wait);
do {
__set_current_state(TASK_INTERRUPTIBLE);
spin_lock_irq(&rtc_lock);
data = rtc_irq_data;
rtc_irq_data = 0;
spin_unlock_irq(&rtc_lock);
if (data != 0) {
ret = 0;
break;
}
if (file->f_flags & O_NONBLOCK) {
ret = -EAGAIN;
break;
}
if (signal_pending(current)) {
ret = -ERESTARTSYS;
break;
}
schedule();
} while (1);
set_current_state(TASK_RUNNING);
remove_wait_queue(&rtc_wait, &wait);
if (ret == 0) {
ret = put_user(data, (unsigned long __user *)buf);
if (ret == 0)
ret = sizeof(unsigned long);
}
return ret;
}
static unsigned int rtc_poll(struct file *file, poll_table *wait)
{
unsigned long data;
poll_wait(file, &rtc_wait, wait);
spin_lock_irq(&rtc_lock);
data = rtc_irq_data;
spin_unlock_irq(&rtc_lock);
return data != 0 ? POLLIN | POLLRDNORM : 0;
}
static int rtc_ioctl(struct inode *inode, struct file *file, unsigned int cmd,
unsigned long arg)
{
struct rtc_ops *ops = file->private_data;
struct rtc_time tm;
struct rtc_wkalrm alrm;
void __user *uarg = (void __user *)arg;
int ret = -EINVAL;
switch (cmd) {
case RTC_ALM_READ:
ret = rtc_arm_read_alarm(ops, &alrm);
if (ret)
break;
ret = copy_to_user(uarg, &alrm.time, sizeof(tm));
if (ret)
ret = -EFAULT;
break;
case RTC_ALM_SET:
ret = copy_from_user(&alrm.time, uarg, sizeof(tm));
if (ret) {
ret = -EFAULT;
break;
}
alrm.enabled = 0;
alrm.pending = 0;
alrm.time.tm_mday = -1;
alrm.time.tm_mon = -1;
alrm.time.tm_year = -1;
alrm.time.tm_wday = -1;
alrm.time.tm_yday = -1;
alrm.time.tm_isdst = -1;
ret = rtc_arm_set_alarm(ops, &alrm);
break;
case RTC_RD_TIME:
ret = rtc_arm_read_time(ops, &tm);
if (ret)
break;
ret = copy_to_user(uarg, &tm, sizeof(tm));
if (ret)
ret = -EFAULT;
break;
case RTC_SET_TIME:
if (!capable(CAP_SYS_TIME)) {
ret = -EACCES;
break;
}
ret = copy_from_user(&tm, uarg, sizeof(tm));
if (ret) {
ret = -EFAULT;
break;
}
ret = rtc_arm_set_time(ops, &tm);
break;
case RTC_EPOCH_SET:
#ifndef rtc_epoch
/*
* There were no RTC clocks before 1900.
*/
if (arg < 1900) {
ret = -EINVAL;
break;
}
if (!capable(CAP_SYS_TIME)) {
ret = -EACCES;
break;
}
rtc_epoch = arg;
ret = 0;
#endif
break;
case RTC_EPOCH_READ:
ret = put_user(rtc_epoch, (unsigned long __user *)uarg);
break;
case RTC_WKALM_SET:
ret = copy_from_user(&alrm, uarg, sizeof(alrm));
if (ret) {
ret = -EFAULT;
break;
}
ret = rtc_arm_set_alarm(ops, &alrm);
break;
case RTC_WKALM_RD:
ret = rtc_arm_read_alarm(ops, &alrm);
if (ret)
break;
ret = copy_to_user(uarg, &alrm, sizeof(alrm));
if (ret)
ret = -EFAULT;
break;
default:
if (ops->ioctl)
ret = ops->ioctl(cmd, arg);
break;
}
return ret;
}
static int rtc_open(struct inode *inode, struct file *file)
{
int ret;
mutex_lock(&rtc_mutex);
if (rtc_inuse) {
ret = -EBUSY;
} else if (!rtc_ops || !try_module_get(rtc_ops->owner)) {
ret = -ENODEV;
} else {
file->private_data = rtc_ops;
ret = rtc_ops->open ? rtc_ops->open() : 0;
if (ret == 0) {
spin_lock_irq(&rtc_lock);
rtc_irq_data = 0;
spin_unlock_irq(&rtc_lock);
rtc_inuse = 1;
}
}
mutex_unlock(&rtc_mutex);
return ret;
}
static int rtc_release(struct inode *inode, struct file *file)
{
struct rtc_ops *ops = file->private_data;
if (ops->release)
ops->release();
spin_lock_irq(&rtc_lock);
rtc_irq_data = 0;
spin_unlock_irq(&rtc_lock);
module_put(rtc_ops->owner);
rtc_inuse = 0;
return 0;
}
static int rtc_fasync(int fd, struct file *file, int on)
{
return fasync_helper(fd, file, on, &rtc_async_queue);
}
static const struct file_operations rtc_fops = {
.owner = THIS_MODULE,
.llseek = no_llseek,
.read = rtc_read,
.poll = rtc_poll,
.ioctl = rtc_ioctl,
.open = rtc_open,
.release = rtc_release,
.fasync = rtc_fasync,
};
static struct miscdevice rtc_miscdev = {
.minor = RTC_MINOR,
.name = "rtc",
.fops = &rtc_fops,
};
static int rtc_read_proc(char *page, char **start, off_t off, int count, int *eof, void *data)
{
struct rtc_ops *ops = data;
struct rtc_wkalrm alrm;
struct rtc_time tm;
char *p = page;
if (rtc_arm_read_time(ops, &tm) == 0) {
p += sprintf(p,
"rtc_time\t: %02d:%02d:%02d\n"
"rtc_date\t: %04d-%02d-%02d\n"
"rtc_epoch\t: %04lu\n",
tm.tm_hour, tm.tm_min, tm.tm_sec,
tm.tm_year + 1900, tm.tm_mon + 1, tm.tm_mday,
rtc_epoch);
}
if (rtc_arm_read_alarm(ops, &alrm) == 0) {
p += sprintf(p, "alrm_time\t: ");
if ((unsigned int)alrm.time.tm_hour <= 24)
p += sprintf(p, "%02d:", alrm.time.tm_hour);
else
p += sprintf(p, "**:");
if ((unsigned int)alrm.time.tm_min <= 59)
p += sprintf(p, "%02d:", alrm.time.tm_min);
else
p += sprintf(p, "**:");
if ((unsigned int)alrm.time.tm_sec <= 59)
p += sprintf(p, "%02d\n", alrm.time.tm_sec);
else
p += sprintf(p, "**\n");
p += sprintf(p, "alrm_date\t: ");
if ((unsigned int)alrm.time.tm_year <= 200)
p += sprintf(p, "%04d-", alrm.time.tm_year + 1900);
else
p += sprintf(p, "****-");
if ((unsigned int)alrm.time.tm_mon <= 11)
p += sprintf(p, "%02d-", alrm.time.tm_mon + 1);
else
p += sprintf(p, "**-");
if ((unsigned int)alrm.time.tm_mday <= 31)
p += sprintf(p, "%02d\n", alrm.time.tm_mday);
else
p += sprintf(p, "**\n");
p += sprintf(p, "alrm_wakeup\t: %s\n",
alrm.enabled ? "yes" : "no");
p += sprintf(p, "alrm_pending\t: %s\n",
alrm.pending ? "yes" : "no");
}
if (ops->proc)
p += ops->proc(p);
return p - page;
}
int register_rtc(struct rtc_ops *ops)
{
int ret = -EBUSY;
mutex_lock(&rtc_mutex);
if (rtc_ops == NULL) {
rtc_ops = ops;
ret = misc_register(&rtc_miscdev);
if (ret == 0)
create_proc_read_entry("driver/rtc", 0, NULL,
rtc_read_proc, ops);
}
mutex_unlock(&rtc_mutex);
return ret;
}
EXPORT_SYMBOL(register_rtc);
void unregister_rtc(struct rtc_ops *rtc)
{
mutex_lock(&rtc_mutex);
if (rtc == rtc_ops) {
remove_proc_entry("driver/rtc", NULL);
misc_deregister(&rtc_miscdev);
rtc_ops = NULL;
}
mutex_unlock(&rtc_mutex);
}
EXPORT_SYMBOL(unregister_rtc);
arch/arm/common/sharpsl_pm.c
浏览文件 @ 91d0322b
......@@ -31,6 +31,7 @@
#include <asm/irq.h>
#include <asm/arch/pm.h>
#include <asm/arch/pxa-regs.h>
#include <asm/arch/pxa2xx-regs.h>
#include <asm/arch/sharpsl.h>
#include <asm/hardware/sharpsl_pm.h>
......@@ -157,6 +158,7 @@ static void sharpsl_battery_thread(struct work_struct *private_)
dev_dbg(sharpsl_pm.dev, "Battery: voltage: %d, status: %d, percentage: %d, time: %ld\n", voltage,
sharpsl_pm.battstat.mainbat_status, sharpsl_pm.battstat.mainbat_percent, jiffies);
#ifdef CONFIG_BACKLIGHT_CORGI
/* If battery is low. limit backlight intensity to save power. */
if ((sharpsl_pm.battstat.ac_status != APM_AC_ONLINE)
&& ((sharpsl_pm.battstat.mainbat_status == APM_BATTERY_STATUS_LOW) ||
......@@ -169,6 +171,7 @@ static void sharpsl_battery_thread(struct work_struct *private_)
sharpsl_pm.machinfo->backlight_limit(0);
sharpsl_pm.flags &= ~SHARPSL_BL_LIMIT;
}
#endif
/* Suspend if critical battery level */
if ((sharpsl_pm.battstat.ac_status != APM_AC_ONLINE)
......
arch/arm/configs/at91cap9adk_defconfig
浏览文件 @ 91d0322b
......@@ -213,7 +213,6 @@ CONFIG_CPU_CP15_MMU=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
......@@ -907,7 +906,32 @@ CONFIG_USB_MON=y
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
CONFIG_USB_GADGET_SELECTED=y
# CONFIG_USB_GADGET_AMD5536UDC is not set
CONFIG_USB_GADGET_ATMEL_USBA=y
CONFIG_USB_ATMEL_USBA=y
# CONFIG_USB_GADGET_FSL_USB2 is not set
# CONFIG_USB_GADGET_NET2280 is not set
# CONFIG_USB_GADGET_PXA2XX is not set
# CONFIG_USB_GADGET_M66592 is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_S3C2410 is not set
# CONFIG_USB_GADGET_AT91 is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
CONFIG_USB_GADGET_DUALSPEED=y
# CONFIG_USB_ZERO is not set
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
# CONFIG_USB_GADGETFS is not set
CONFIG_USB_FILE_STORAGE=m
# CONFIG_USB_FILE_STORAGE_TEST is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
......@@ -926,7 +950,59 @@ CONFIG_MMC_AT91=y
# CONFIG_MMC_SPI is not set
# CONFIG_NEW_LEDS is not set
CONFIG_RTC_LIB=y
# CONFIG_RTC_CLASS is not set
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_AT91SAM9=y
CONFIG_RTC_DRV_AT91SAM9_RTT=0
CONFIG_RTC_DRV_AT91SAM9_GPBR=0
#
# File systems
......
arch/arm/configs/at91rm9200dk_defconfig
浏览文件 @ 91d0322b
......@@ -169,7 +169,6 @@ CONFIG_AT91_CF=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
......
arch/arm/configs/at91rm9200ek_defconfig
浏览文件 @ 91d0322b
......@@ -160,7 +160,6 @@ CONFIG_ISA_DMA_API=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
......
arch/arm/configs/at91sam9260ek_defconfig
浏览文件 @ 91d0322b
......@@ -220,7 +220,6 @@ CONFIG_CPU_CP15_MMU=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/at91sam9261ek_defconfig
浏览文件 @ 91d0322b
......@@ -213,7 +213,6 @@ CONFIG_CPU_CP15_MMU=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/at91sam9263ek_defconfig
浏览文件 @ 91d0322b
......@@ -213,7 +213,6 @@ CONFIG_CPU_CP15_MMU=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/at91sam9rlek_defconfig
浏览文件 @ 91d0322b
......@@ -211,7 +211,6 @@ CONFIG_CPU_CP15_MMU=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/ateb9200_defconfig
浏览文件 @ 91d0322b
......@@ -171,7 +171,6 @@ CONFIG_AT91_CF=m
# Kernel Features
#
CONFIG_PREEMPT=y
CONFIG_NO_IDLE_HZ=y
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/collie_defconfig
浏览文件 @ 91d0322b
......@@ -166,7 +166,6 @@ CONFIG_PCMCIA_SA1100=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
......
arch/arm/configs/corgi_defconfig
浏览文件 @ 91d0322b
......@@ -165,7 +165,6 @@ CONFIG_PCMCIA_PXA2XX=y
# Kernel Features
#
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
......
arch/arm/configs/ecbat91_defconfig
浏览文件 @ 91d0322b
......@@ -230,7 +230,6 @@ CONFIG_AT91_CF=y
#
# CONFIG_TICK_ONESHOT is not set
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/ep93xx_defconfig
浏览文件 @ 91d0322b
......@@ -184,7 +184,6 @@ CONFIG_ARM_AMBA=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/eseries_pxa_defconfig
浏览文件 @ 91d0322b
......@@ -251,7 +251,6 @@ CONFIG_PCMCIA_PXA2XX=m
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
......
arch/arm/configs/imx27ads_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/iop13xx_defconfig
浏览文件 @ 91d0322b
......@@ -197,7 +197,6 @@ CONFIG_PCI_LEGACY=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/iop32x_defconfig
浏览文件 @ 91d0322b
......@@ -201,7 +201,6 @@ CONFIG_PCI_LEGACY=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/iop33x_defconfig
浏览文件 @ 91d0322b
......@@ -197,7 +197,6 @@ CONFIG_PCI_LEGACY=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/ixp2000_defconfig
浏览文件 @ 91d0322b
......@@ -184,7 +184,6 @@ CONFIG_PCI=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/ixp23xx_defconfig
浏览文件 @ 91d0322b
......@@ -180,7 +180,6 @@ CONFIG_PCI=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/ixp4xx_defconfig
浏览文件 @ 91d0322b
......@@ -165,6 +165,7 @@ CONFIG_ARCH_PRPMC1100=y
CONFIG_MACH_NAS100D=y
CONFIG_MACH_DSMG600=y
CONFIG_ARCH_IXDP4XX=y
CONFIG_MACH_FSG=y
CONFIG_CPU_IXP46X=y
CONFIG_CPU_IXP43X=y
CONFIG_MACH_GTWX5715=y
......@@ -770,7 +771,7 @@ CONFIG_ATA=y
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
CONFIG_SATA_VIA=y
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
......@@ -1143,7 +1144,7 @@ CONFIG_HWMON=y
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
CONFIG_SENSORS_W83781D=y
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
......@@ -1334,8 +1335,8 @@ CONFIG_LEDS_CLASS=y
#
# LED drivers
#
# CONFIG_LEDS_IXP4XX is not set
CONFIG_LEDS_GPIO=y
CONFIG_LEDS_FSG=y
#
# LED Triggers
......@@ -1367,7 +1368,7 @@ CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
CONFIG_RTC_DRV_ISL1208=y
CONFIG_RTC_DRV_X1205=y
CONFIG_RTC_DRV_PCF8563=y
# CONFIG_RTC_DRV_PCF8583 is not set
......
arch/arm/configs/kafa_defconfig
浏览文件 @ 91d0322b
......@@ -162,7 +162,6 @@ CONFIG_CPU_TLB_V4WBI=y
# Kernel Features
#
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/kb9202_defconfig
浏览文件 @ 91d0322b
......@@ -126,7 +126,6 @@ CONFIG_ISA_DMA_API=y
#
# Kernel Features
#
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
......
arch/arm/configs/kirkwood_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/ks8695_defconfig
浏览文件 @ 91d0322b
......@@ -174,7 +174,6 @@ CONFIG_PCCARD_NONSTATIC=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/loki_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/lpd270_defconfig
浏览文件 @ 91d0322b
......@@ -173,7 +173,6 @@ CONFIG_XSCALE_PMU=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/lpd7a404_defconfig
浏览文件 @ 91d0322b
......@@ -148,7 +148,6 @@ CONFIG_ARM_AMBA=y
# Kernel Features
#
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_AEABI is not set
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
......
arch/arm/configs/mv78xx0_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/mx31ads_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/mx31litekit_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/netx_defconfig
浏览文件 @ 91d0322b
......@@ -154,7 +154,6 @@ CONFIG_ARM_AMBA=y
# Kernel Features
#
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/onearm_defconfig
浏览文件 @ 91d0322b
......@@ -202,7 +202,6 @@ CONFIG_AT91_CF=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/orion5x_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/pcm037_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/pcm038_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/picotux200_defconfig
浏览文件 @ 91d0322b
......@@ -201,7 +201,6 @@ CONFIG_ARM_THUMB=y
# Kernel Features
#
# CONFIG_PREEMPT is not set
CONFIG_NO_IDLE_HZ=y
CONFIG_HZ=100
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
......
arch/arm/configs/pnx4008_defconfig
浏览文件 @ 91d0322b
......@@ -151,7 +151,6 @@ CONFIG_ARM_THUMB=y
# Kernel Features
#
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/qil-a9260_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/realview-smp_defconfig
浏览文件 @ 91d0322b
......@@ -177,7 +177,6 @@ CONFIG_NR_CPUS=4
CONFIG_HOTPLUG_CPU=y
CONFIG_LOCAL_TIMERS=y
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/realview_defconfig
浏览文件 @ 91d0322b
......@@ -126,7 +126,6 @@ CONFIG_ISA_DMA_API=y
#
# Kernel Features
#
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
......
arch/arm/configs/rpc_defconfig
浏览文件 @ 91d0322b
......@@ -190,7 +190,6 @@ CONFIG_ISA_DMA_API=y
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_PREEMPT is not set
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/s3c2410_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/sam9_l9260_defconfig
浏览文件 @ 91d0322b
......@@ -211,7 +211,6 @@ CONFIG_ARM_THUMB=y
#
# CONFIG_TICK_ONESHOT is not set
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
CONFIG_HZ=100
# CONFIG_AEABI is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
......
arch/arm/configs/spitz_defconfig
浏览文件 @ 91d0322b
......@@ -164,7 +164,6 @@ CONFIG_PCMCIA_PXA2XX=y
# Kernel Features
#
CONFIG_PREEMPT=y
# CONFIG_NO_IDLE_HZ is not set
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
......
arch/arm/configs/trizeps4_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/usb-a9260_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/configs/usb-a9263_defconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/armksyms.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/atags.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/ecard.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/ecard.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/entry-common.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/ftrace.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/kprobes.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/stacktrace.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/kernel/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/lib/copy_template.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/lib/memmove.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/lib/memset.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/lib/memzero.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/at91sam9260.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-cap9adk.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-carmeva.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-csb637.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-dk.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-eb9200.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-ek.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-kb9202.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-qil-a9260.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-sam9g20ek.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-usb-a9260.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-usb-a9263.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/board-yl-9200.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-ep93xx/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-footbridge/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-footbridge/co285.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/arm/mach-footbridge/common.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-footbridge/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/clock.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/cpufreq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/dma.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/generic.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/mx1ads.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-imx/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-integrator/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-ixp4xx/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-ixp4xx/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-ixp4xx/fsg-pci.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-ixp4xx/fsg-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/Kconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/Makefile.boot 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/addr-map.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/common.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/common.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/db88f6281-bp-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/irq.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/pcie.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/rd88f6192-nas-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-kirkwood/rd88f6281-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/Kconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/Makefile.boot 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/addr-map.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/common.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/common.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/irq.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-loki/lb88rc8480-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/Kconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/Makefile.boot 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/addr-map.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/common.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/common.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/db78x00-bp-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/irq.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mv78xx0/pcie.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/Kconfig 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/Makefile.boot 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/clock_imx27.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/cpu_imx27.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/crm_regs.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/devices.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/generic.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/mx27ads.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/pcm038.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/pcm970-baseboard.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/serial.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx2/system.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/clock.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/crm_regs.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/devices.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/iomux.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/mx31ads.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/mx31lite.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/pcm037.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-mx3/time.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/arm/mach-omap1/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap1/fpga.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap1/mcbsp.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap1/pm.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/clock.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/clock24xx.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/clock24xx.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/clock34xx.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/clock34xx.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/cm.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/control.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/id.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/mcbsp.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/memory.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/pm.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/prcm-common.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/prm.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/sdrc.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/sram243x.S 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-omap2/timer-gp.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/addr-map.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/common.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/common.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/gpio.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/irq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/mpp.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/mpp.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/mss2-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/mv2120-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/pci.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/rd88f5181l-fxo-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/rd88f5181l-ge-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/ts209-setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/ts409-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/ts78xx-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/tsx09-common.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/tsx09-common.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/wnr854t-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-orion5x/wrt350n-v2-setup.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/clock.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/cm-x270-pci.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/cm-x270.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/corgi_pm.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/devices.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/generic.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/irq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/lubbock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/mfp-pxa2xx.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/pwm.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/pxa25x.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/pxa27x.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/pxa2xx.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/pxa3xx.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/spitz_pm.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/standby.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/trizeps4.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/zylonite.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa300.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa320.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/bast-ide.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/mach-bast.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/mach-n30.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/mach-vr1000.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/nor-simtec.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2410/nor-simtec.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2412/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2412/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2412/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2412/mach-jive.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2440/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2440/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2440/mach-anubis.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2440/mach-at2440evb.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2440/mach-osiris.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mach-s3c2443/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mm/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mm/cache-feroceon-l2.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mm/fault-armv.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mm/flush.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/mm/proc-feroceon.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-iop/gpio.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/clock.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/gpio.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/iomux-mx1-mx2.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/irq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-mxc/time.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/clock.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/common.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/devices.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/dmtimer.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/mcbsp.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-omap/usb.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-orion/irq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-orion/pcie.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-orion/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-s3c24xx/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-s3c24xx/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-s3c24xx/devs.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-s3c24xx/gpiolib.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-s3c24xx/pwm-clock.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/plat-s3c24xx/pwm.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/boards/atngw100/setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/kernel/entry-avr32b.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/kernel/signal.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/kernel/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/kernel/vmlinux.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/lib/io-readsb.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/at32ap700x.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/intc.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/pio.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/pio.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/pm.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mach-at32ap/sdramc.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mm/init.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/avr32/mm/tlb.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/blackfin/mach-bf561/coreb.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/cris/arch-v10/drivers/eeprom.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/cris/arch-v10/drivers/gpio.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/cris/arch-v10/drivers/i2c.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/cris/arch-v32/drivers/i2c.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/m68k/bvme6000/rtc.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/m68k/mvme16x/rtc.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/mips/kernel/rtlx.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/mips/kernel/vpe.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/mips/mm/c-r3k.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/mips/mm/page.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/mips/mm/sc-rm7k.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/mips/sibyte/common/sb_tbprof.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/parisc/kernel/perf.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/parisc/kernel/vmlinux.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/entry_32.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/ftrace.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/io.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/legacy_serial.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/of_platform.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/appldata/appldata.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/appldata/appldata_mem.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/appldata/appldata_os.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/crypto/crypt_s390.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/crypto/prng.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/hypfs/inode.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/binfmt_elf32.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/s390/kernel/compat_ptrace.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/early.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/ipl.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/kprobes.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/machine_kexec.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/mem_detect.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/process.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/ptrace.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/topology.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/vmlinux.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/kernel/vtime.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/boards/landisk/gio.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/configs/landisk_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/configs/lboxre2_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/configs/se7705_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/configs/se7712_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/configs/se7750_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/kernel/vmlinux_32.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/sh/kernel/vmlinux_64.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc/kernel/apc.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/Kconfig.debug
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/kernel/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/kernel/ftrace.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/kernel/sparc64_ksyms.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/kernel/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/sparc64/lib/mcount.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/um/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/um/Makefile-i386
浏览文件 @ 91d0322b
此差异已折叠。
arch/um/Makefile-x86_64
浏览文件 @ 91d0322b
此差异已折叠。
arch/um/drivers/harddog_kern.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/um/drivers/mmapper_kern.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/um/drivers/random.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/Kconfig.cpu
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/Kconfig.debug
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/a20.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/compressed/head_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/compressed/misc.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/compressed/relocs.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/cpu.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/main.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/memory.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/pmjump.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/boot/video-vga.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/configs/i386_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/configs/x86_64_defconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/ia32/ia32entry.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/.gitignore
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/acpi/boot.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/acpi/sleep.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/alternative.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/amd_iommu.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/amd_iommu_init.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/aperture_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/apic_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/apic_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/apm_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/asm-offsets_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/asm-offsets_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/amd.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/amd_64.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/bugs.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/centaur_64.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/common.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/cpu.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/intel.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/intel_64.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/mcheck/k7.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/mcheck/mce_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/mcheck/p4.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/mtrr/generic.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/mtrr/main.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpu/mtrr/mtrr.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/cpuid.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/e820_32.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/kernel/early-quirks.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/early_printk.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/efi.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/efi_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/entry_32.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/entry_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/ftrace.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/genapic_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/genx2apic_uv_x.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/head.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/head32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/head64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/head_32.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/head_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/hpet.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/i386_ksyms_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/i387.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/io_apic_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/io_apic_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/ipi.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/irq_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/irq_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/irqinit_32.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/ldt.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/machine_kexec_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/machine_kexec_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/microcode.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/mmconf-fam10h_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/mpparse.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/msr.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/nmi_64.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/kernel/numaq_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/paravirt.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/paravirt_patch_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/paravirt_patch_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/pci-calgary_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/pci-dma.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/pci-gart_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/pci-swiotlb_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/probe_roms_32.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/process.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/process_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/process_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/ptrace.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/quirks.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/reboot.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/reboot_fixups_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/setup_32.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/kernel/setup_64.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/kernel/setup_percpu.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/smpboot.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/summit_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/sys_i386_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/time_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/time_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/tlb_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/tlb_uv.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/trampoline.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/traps_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/traps_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/tsc_32.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/kernel/vmi_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/vmiclock_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/vmlinux_32.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/vmlinux_64.lds.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/vsmp_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/vsyscall_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/kernel/x8664_ksyms_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lguest/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lguest/boot.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lib/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lib/copy_user_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lib/copy_user_nocache_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lib/delay_64.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/lib/getuser_32.S 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/lib/putuser_64.S 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/lib/thunk_32.S 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lib/thunk_64.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/lib/usercopy_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-default/setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-es7000/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-es7000/es7000plat.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-generic/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-generic/bigsmp.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-generic/numaq.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-generic/probe.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-visws/Makefile 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/mach-visws/mpparse.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/mach-visws/reboot.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/mach-visws/setup.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/mach-visws/traps.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/mach-voyager/setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mach-voyager/voyager_smp.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/math-emu/reg_constant.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/discontig_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/dump_pagetables.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/fault.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/init_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/init_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/ioremap.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/k8topology_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/kmmio.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/mmio-mod.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/numa_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pageattr-test.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pageattr.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pat.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pf_in.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pf_in.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pgtable.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/pgtable_32.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/srat_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/mm/testmmiotrace.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/oprofile/nmi_int.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/Makefile_32 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/pci/Makefile_64 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/pci/acpi.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/common.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/direct.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/i386.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/init.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/irq.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/legacy.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/mmconfig-shared.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/mp_bus_to_node.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
arch/x86/pci/numa.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/pci.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/pci/visws.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/power/hibernate_64.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/vdso/vclock_gettime.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/vdso/vdso32-setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/vdso/vgetcpu.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/vdso/vma.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/enlighten.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/mmu.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/mmu.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/multicalls.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/multicalls.h
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/setup.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/smp.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/suspend.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/time.c
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/xen-head.S
浏览文件 @ 91d0322b
此差异已折叠。
arch/x86/xen/xen-ops.h
浏览文件 @ 91d0322b
此差异已折叠。
block/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
block/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
block/as-iosched.c
浏览文件 @ 91d0322b
此差异已折叠。
block/blk-core.c
浏览文件 @ 91d0322b
此差异已折叠。
block/blk-integrity.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
block/blk-map.c
浏览文件 @ 91d0322b
此差异已折叠。
block/blk-merge.c
浏览文件 @ 91d0322b
此差异已折叠。
block/blk-settings.c
浏览文件 @ 91d0322b
此差异已折叠。
block/blk.h
浏览文件 @ 91d0322b
此差异已折叠。
block/blktrace.c
浏览文件 @ 91d0322b
此差异已折叠。
block/bsg.c
浏览文件 @ 91d0322b
此差异已折叠。
block/cfq-iosched.c
浏览文件 @ 91d0322b
此差异已折叠。
block/cmd-filter.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
block/elevator.c
浏览文件 @ 91d0322b
此差异已折叠。
block/genhd.c
浏览文件 @ 91d0322b
此差异已折叠。
block/scsi_ioctl.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
crypto/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
crypto/ahash.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/api.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/camellia.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/chainiv.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/crc32c.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/cryptd.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/digest.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/hash.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/hmac.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/internal.h
浏览文件 @ 91d0322b
此差异已折叠。
crypto/prng.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/prng.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/ripemd.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/rmd128.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/rmd160.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/rmd256.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/rmd320.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
crypto/tcrypt.c
浏览文件 @ 91d0322b
此差异已折叠。
crypto/tcrypt.h
浏览文件 @ 91d0322b
此差异已折叠。
drivers/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
drivers/acorn/char/Makefile 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/acorn/char/defkeymap-l7200.c 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/acpi/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ata/ahci.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ata/libata-acpi.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ata/libata-scsi.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ata/pata_sis.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/atm/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
drivers/atm/ambassador.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/atm/ambassador.h
浏览文件 @ 91d0322b
此差异已折叠。
drivers/atm/atmsar11.data 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/atm/atmsar11.regions 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/atm/atmsar11.start 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/base/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
drivers/base/firmware_class.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/base/power/trace.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/base/topology.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/DAC960.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/aoe/aoechr.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/aoe/aoecmd.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/paride/pg.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/paride/pt.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/pktcdvd.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/block/xen-blkfront.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/bluetooth/bfusb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/bluetooth/bt3c_cs.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/bluetooth/hci_vhci.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/cdrom/cdrom.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/agp/amd64-agp.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/agp/frontend.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/apm-emulation.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/briq_panel.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/cs5535_gpio.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/cyclades.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/drm/Makefile 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/char/ds1286.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ds1620.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/dsp56k.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/dtlk.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/efirtc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/genrtc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/hpet.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/hvc_xen.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/hw_random/core.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ip2/fip_firm.h 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/char/ip2/ip2base.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ip2/ip2main.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ip27-rtc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ipmi/ipmi_devintf.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ipmi/ipmi_watchdog.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/lcd.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/lp.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/mbcs.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/mem.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/misc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/moxa.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/mwave/mwavedd.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/nvram.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/pc8736x_gpio.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/pcmcia/cm4000_cs.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/pcmcia/cm4040_cs.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/ppdev.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/raw.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/rtc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/scx200_gpio.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/snsc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/sonypi.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/tb0219.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/tlclk.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/tpm/tpm.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/tpm/tpm_tis.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/tty_io.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/vc_screen.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/viotape.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/char/vr41xx_giu.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/hifn_795x.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/ixp4xx_crypto.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/padlock-aes.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/padlock-sha.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/talitos.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/crypto/talitos.h 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/firmware/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
drivers/firmware/Makefile
浏览文件 @ 91d0322b
此差异已折叠。
drivers/firmware/dell_rbu.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/firmware/dmi_scan.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/firmware/memmap.c 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/i810/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/i830/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/i915/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/mga/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/r128/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/radeon/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/savage/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/sis/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/tdfx/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/gpu/drm/via/Makefile 0 → 100644
浏览文件 @ 91d0322b
此差异已折叠。
drivers/hid/hidraw.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/i2c/busses/i2c-pxa.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/i2c/chips/isp1301_omap.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/i2c/i2c-dev.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/arm/palm_bk3710.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/ide-probe.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/ide-tape.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/ide.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/legacy/ide-cs.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/pci/it8213.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/ide/pci/ns87415.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/infiniband/core/ucm.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/infiniband/core/ucma.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/infiniband/core/user_mad.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/input/input.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/input/misc/hp_sdc_rtc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/input/misc/uinput.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/input/mousedev.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/input/serio/serio_raw.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/input/xen-kbdfront.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/isdn/capi/capi.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/isdn/i4l/isdn_common.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/lguest/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
drivers/lguest/lg.h
浏览文件 @ 91d0322b
此差异已折叠。
drivers/macintosh/adb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/macintosh/ans-lcd.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/macintosh/smu.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/macintosh/via-pmu.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/md/linear.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/md/raid0.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/md/raid10.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/md/raid5.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/dvb/dvb-core/dvbdev.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/dvb/dvb-usb/cxusb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/dvb/dvb-usb/gp8psk.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/radio/miropcm20-rds.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/video/cpia2/cpia2patch.h 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/media/video/dabfirmware.h 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/media/video/dabusb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/video/ov7670.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/media/video/videodev.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/message/fusion/mptbase.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/message/fusion/mptctl.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/message/fusion/mptspi.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/message/i2o/i2o_config.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/misc/atmel_pwm.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/misc/phantom.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/misc/sony-laptop.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mmc/host/imxmmc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mmc/host/pxamci.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mtd/ftl.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mtd/maps/omap_nor.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mtd/maps/pcmciamtd.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mtd/mtdchar.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mtd/nand/orion_nand.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/mtd/ubi/cdev.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/Kconfig
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/arm/etherh.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/cxgb3/common.h
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/cxgb3/t3_hw.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/ehea/ehea.h
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/ehea/ehea_main.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/forcedeth.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/fs_enet/mac-fcc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/ibm_newemac/core.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/irda/irda-usb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/irda/nsc-ircc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/irda/pxaficp_ir.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/irda/via-ircc.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/macb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/myri10ge/myri10ge.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/pasemi_mac.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/ppp_generic.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/tokenring/smctr.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/tokenring/smctr.h
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/tokenring/smctr_firmware.h 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/net/tun.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/usb/kaweth.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/usb/kawethfw.h 已删除 100644 → 0
浏览文件 @ 065cb3df
此差异已折叠。
drivers/net/wan/cosa.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/wan/hdlc_fr.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/wireless/atmel.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/wireless/p54/p54usb.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/wireless/zd1201.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/net/xen-netfront.c
浏览文件 @ 91d0322b
此差异已折叠。
drivers/parisc/eisa_eeprom.c
浏览文件 @ 91d0322b
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或