Skip to content

cloud-kernel
cloud-kernel

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

通知 158
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

提交 f5a8eb63 编写于 作者: L Linus Torvalds
浏览文件
操作

Merge tag 'arch-removal' of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic 

Pul removal of obsolete architecture ports from Arnd Bergmann:
 "This removes the entire architecture code for blackfin, cris, frv,
  m32r, metag, mn10300, score, and tile, including the associated device
  drivers.

  I have been working with the (former) maintainers for each one to
  ensure that my interpretation was right and the code is definitely
  unused in mainline kernels. Many had fond memories of working on the
  respective ports to start with and getting them included in upstream,
  but also saw no point in keeping the port alive without any users.

  In the end, it seems that while the eight architectures are extremely
  different, they all suffered the same fate: There was one company in
  charge of an SoC line, a CPU microarchitecture and a software
  ecosystem, which was more costly than licensing newer off-the-shelf
  CPU cores from a third party (typically ARM, MIPS, or RISC-V). It
  seems that all the SoC product lines are still around, but have not
  used the custom CPU architectures for several years at this point. In
  contrast, CPU instruction sets that remain popular and have actively
  maintained kernel ports tend to all be used across multiple licensees.

  [ See the new nds32 port merged in the previous commit for the next
    generation of "one company in charge of an SoC line, a CPU
    microarchitecture and a software ecosystem"   - Linus ]

  The removal came out of a discussion that is now documented at
  https://lwn.net/Articles/748074/. Unlike the original plans, I'm not
  marking any ports as deprecated but remove them all at once after I
  made sure that they are all unused. Some architectures (notably tile,
  mn10300, and blackfin) are still being shipped in products with old
  kernels, but those products will never be updated to newer kernel
  releases.

  After this series, we still have a few architectures without mainline
  gcc support:

   - unicore32 and hexagon both have very outdated gcc releases, but the
     maintainers promised to work on providing something newer. At least
     in case of hexagon, this will only be llvm, not gcc.

   - openrisc, risc-v and nds32 are still in the process of finishing
     their support or getting it added to mainline gcc in the first
     place. They all have patched gcc-7.3 ports that work to some
     degree, but complete upstream support won't happen before gcc-8.1.
     Csky posted their first kernel patch set last week, their situation
     will be similar

  [ Palmer Dabbelt points out that RISC-V support is in mainline gcc
    since gcc-7, although gcc-7.3.0 is the recommended minimum  - Linus ]"

This really says it all:

 2498 files changed, 95 insertions(+), 467668 deletions(-)

* tag 'arch-removal' of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic: (74 commits)
  MAINTAINERS: UNICORE32: Change email account
  staging: iio: remove iio-trig-bfin-timer driver
  tty: hvc: remove tile driver
  tty: remove bfin_jtag_comm and hvc_bfin_jtag drivers
  serial: remove tile uart driver
  serial: remove m32r_sio driver
  serial: remove blackfin drivers
  serial: remove cris/etrax uart drivers
  usb: Remove Blackfin references in USB support
  usb: isp1362: remove blackfin arch glue
  usb: musb: remove blackfin port
  usb: host: remove tilegx platform glue
  pwm: remove pwm-bfin driver
  i2c: remove bfin-twi driver
  spi: remove blackfin related host drivers
  watchdog: remove bfin_wdt driver
  can: remove bfin_can driver
  mmc: remove bfin_sdh driver
  input: misc: remove blackfin rotary driver
  input: keyboard: remove bf54x driver
  ...
上级 c9297d28 dd3b8c32
展开全部 隐藏空白更改
内联 并排
Showing with 11 addition and 229390 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ f5a8eb63
......@@ -1564,6 +1564,11 @@ W: http://www.carumba.com/
D: bug toaster (A1 sauce makes all the difference)
D: Random linux hacker
N: James Hogan
E: jhogan@kernel.org
D: Metag architecture maintainer
D: TZ1090 SoC maintainer
N: Tim Hockin
E: thockin@hockin.org
W: http://www.hockin.org/~thockin
......
Documentation/00-INDEX
浏览文件 @ f5a8eb63
......@@ -66,8 +66,6 @@ backlight/
- directory with info on controlling backlights in flat panel displays
bcache.txt
- Block-layer cache on fast SSDs to improve slow (raid) I/O performance.
blackfin/
- directory with documentation for the Blackfin arch.
block/
- info on the Block I/O (BIO) layer.
blockdev/
......@@ -114,8 +112,6 @@ cputopology.txt
- documentation on how CPU topology info is exported via sysfs.
crc32.txt
- brief tutorial on CRC computation
cris/
- directory with info about Linux on CRIS architecture.
crypto/
- directory with info on the Crypto API.
dcdbas.txt
......@@ -172,8 +168,6 @@ fmc/
- information about the FMC bus abstraction
fpga/
- FPGA Manager Core.
frv/
- Fujitsu FR-V Linux documentation.
futex-requeue-pi.txt
- info on requeueing of tasks from a non-PI futex to a PI futex
gcc-plugins.txt
......@@ -276,8 +270,6 @@ memory-hotplug.txt
- Hotpluggable memory support, how to use and current status.
men-chameleon-bus.txt
- info on MEN chameleon bus.
metag/
- directory with info about Linux on Meta architecture.
mic/
- Intel Many Integrated Core (MIC) architecture device driver.
mips/
......@@ -286,8 +278,6 @@ misc-devices/
- directory with info about devices using the misc dev subsystem
mmc/
- directory with info about the MMC subsystem
mn10300/
- directory with info about the mn10300 architecture port
mtd/
- directory with info about memory technology devices (flash)
namespaces/
......
Documentation/admin-guide/README.rst
浏览文件 @ f5a8eb63
......@@ -26,8 +26,8 @@ On what hardware does it run?
Although originally developed first for 32-bit x86-based PCs (386 or higher),
today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
Xtensa, Tilera TILE, ARC and Renesas M32R architectures.
IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
ARC architectures.
Linux is easily portable to most general-purpose 32- or 64-bit architectures
as long as they have a paged memory management unit (PMMU) and a port of the
......
Documentation/admin-guide/kernel-parameters.rst
浏览文件 @ f5a8eb63
......@@ -89,7 +89,6 @@ parameter is applicable::
APM Advanced Power Management support is enabled.
ARM ARM architecture is enabled.
AX25 Appropriate AX.25 support is enabled.
BLACKFIN Blackfin architecture is enabled.
CLK Common clock infrastructure is enabled.
CMA Contiguous Memory Area support is enabled.
DRM Direct Rendering Management support is enabled.
......
Documentation/admin-guide/kernel-parameters.txt
浏览文件 @ f5a8eb63
......@@ -1025,7 +1025,7 @@
address. The serial port must already be setup
and configured. Options are not yet supported.
earlyprintk= [X86,SH,BLACKFIN,ARM,M68k,S390]
earlyprintk= [X86,SH,ARM,M68k,S390]
earlyprintk=vga
earlyprintk=efi
earlyprintk=sclp
......@@ -1347,10 +1347,6 @@
If specified, z/VM IUCV HVC accepts connections
from listed z/VM user IDs only.
hwthread_map= [METAG] Comma-separated list of Linux cpu id to
hardware thread id mappings.
Format: <cpu>:<hwthread>
keep_bootcon [KNL]
Do not unregister boot console at start. This is only
useful for debugging when something happens in the window
......
Documentation/blackfin/00-INDEX 已删除 100644 → 0
浏览文件 @ c9297d28
00-INDEX
- This file
bfin-gpio-notes.txt
- Notes in developing/using bfin-gpio driver.
bfin-spi-notes.txt
- Notes for using bfin spi bus driver.
Documentation/blackfin/bfin-gpio-notes.txt 已删除 100644 → 0
浏览文件 @ c9297d28
/*
* File: Documentation/blackfin/bfin-gpio-notes.txt
* Based on:
* Author:
*
* Created: $Id: bfin-gpio-note.txt 2008-11-24 16:42 grafyang $
* Description: This file contains the notes in developing/using bfin-gpio.
*
*
* Rev:
*
* Modified:
* Copyright 2004-2008 Analog Devices Inc.
*
* Bugs: Enter bugs at http://blackfin.uclinux.org/
*
*/
1. Blackfin GPIO introduction
There are many GPIO pins on Blackfin. Most of these pins are muxed to
multi-functions. They can be configured as peripheral, or just as GPIO,
configured to input with interrupt enabled, or output.
For detailed information, please see "arch/blackfin/kernel/bfin_gpio.c",
or the relevant HRM.
2. Avoiding resource conflict
Followed function groups are used to avoiding resource conflict,
- Use the pin as peripheral,
int peripheral_request(unsigned short per, const char *label);
int peripheral_request_list(const unsigned short per[], const char *label);
void peripheral_free(unsigned short per);
void peripheral_free_list(const unsigned short per[]);
- Use the pin as GPIO,
int bfin_gpio_request(unsigned gpio, const char *label);
void bfin_gpio_free(unsigned gpio);
- Use the pin as GPIO interrupt,
int bfin_gpio_irq_request(unsigned gpio, const char *label);
void bfin_gpio_irq_free(unsigned gpio);
The request functions will record the function state for a certain pin,
the free functions will clear its function state.
Once a pin is requested, it can't be requested again before it is freed by
previous caller, otherwise kernel will dump stacks, and the request
function fail.
These functions are wrapped by other functions, most of the users need not
care.
3. But there are some exceptions
- Kernel permit the identical GPIO be requested both as GPIO and GPIO
interrupt.
Some drivers, like gpio-keys, need this behavior. Kernel only print out
warning messages like,
bfin-gpio: GPIO 24 is already reserved by gpio-keys: BTN0, and you are
configuring it as IRQ!
Note: Consider the case that, if there are two drivers need the
identical GPIO, one of them use it as GPIO, the other use it as
GPIO interrupt. This will really cause resource conflict. So if
there is any abnormal driver behavior, please check the bfin-gpio
warning messages.
- Kernel permit the identical GPIO be requested from the same driver twice.
Documentation/blackfin/bfin-spi-notes.txt 已删除 100644 → 0
浏览文件 @ c9297d28
SPI Chip Select behavior:
With the Blackfin on-chip SPI peripheral, there is some logic tied to the CPHA
bit whether the Slave Select Line is controlled by hardware (CPHA=0) or
controlled by software (CPHA=1). However, the Linux SPI bus driver assumes that
the Slave Select is always under software control and being asserted during
the entire SPI transfer. - And not just bits_per_word duration.
In most cases you can utilize SPI MODE_3 instead of MODE_0 to work-around this
behavior. If your SPI slave device in question requires SPI MODE_0 or MODE_2
timing, you can utilize the GPIO controlled SPI Slave Select option instead.
In this case, you should use GPIO based CS for all of your slaves and not just
the ones using mode 0 or 2 in order to guarantee correct CS toggling behavior.
You can even use the same pin whose peripheral role is a SSEL,
but use it as a GPIO instead.
Documentation/cris/README 已删除 100644 → 0
浏览文件 @ c9297d28
Linux on the CRIS architecture
==============================
This is a port of Linux to Axis Communications ETRAX 100LX,
ETRAX FS and ARTPEC-3 embedded network CPUs.
For more information about CRIS and ETRAX please see further below.
In order to compile this you need a version of gcc with support for the
ETRAX chip family. Please see this link for more information on how to
download the compiler and other tools useful when building and booting
software for the ETRAX platform:
http://developer.axis.com/wiki/doku.php?id=axis:install-howto-2_20
What is CRIS ?
--------------
CRIS is an acronym for 'Code Reduced Instruction Set'. It is the CPU
architecture in Axis Communication AB's range of embedded network CPU's,
called ETRAX.
The ETRAX 100LX chip
--------------------
For reference, please see the following link:
http://www.axis.com/products/dev_etrax_100lx/index.htm
The ETRAX 100LX is a 100 MIPS processor with 8kB cache, MMU, and a very broad
range of built-in interfaces, all with modern scatter/gather DMA.
Memory interfaces:
* SRAM
* NOR-flash/ROM
* EDO or page-mode DRAM
* SDRAM
I/O interfaces:
* one 10/100 Mbit/s ethernet controller
* four serial-ports (up to 6 Mbit/s)
* two synchronous serial-ports for multimedia codec's etc.
* USB host controller and USB slave
* ATA
* SCSI
* two parallel-ports
* two generic 8-bit ports
(not all interfaces are available at the same time due to chip pin
multiplexing)
ETRAX 100LX is CRISv10 architecture.
The ETRAX FS and ARTPEC-3 chips
-------------------------------
The ETRAX FS is a 200MHz 32-bit RISC processor with on-chip 16kB
I-cache and 16kB D-cache and with a wide range of device interfaces
including multiple high speed serial ports and an integrated USB 1.1 PHY.
The ARTPEC-3 is a variant of the ETRAX FS with additional IO-units
used by the Axis Communications network cameras.
See below link for more information:
http://www.axis.com/products/dev_etrax_fs/index.htm
ETRAX FS and ARTPEC-3 are both CRISv32 architectures.
Bootlog
-------
Just as an example, this is the debug-output from a boot of Linux 2.4 on
a board with ETRAX 100LX. The displayed BogoMIPS value is 5 times too small :)
At the end you see some user-mode programs booting like telnet and ftp daemons.
Linux version 2.4.1 (bjornw@godzilla.axis.se) (gcc version 2.96 20000427 (experimental)) #207 Wed Feb 21 15:48:15 CET 2001
ROM fs in RAM, size 1376256 bytes
Setting up paging and the MMU.
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Linux/CRIS port on ETRAX 100LX (c) 2001 Axis Communications AB
Kernel command line:
Calibrating delay loop... 19.91 BogoMIPS
Memory: 13872k/16384k available (587k kernel code, 2512k reserved, 44k data, 24k init)
kmem_create: Forcing size word alignment - vm_area_struct
kmem_create: Forcing size word alignment - filp
Dentry-cache hash table entries: 2048 (order: 1, 16384 bytes)
Buffer-cache hash table entries: 2048 (order: 0, 8192 bytes)
Page-cache hash table entries: 2048 (order: 0, 8192 bytes)
kmem_create: Forcing size word alignment - kiobuf
kmem_create: Forcing size word alignment - bdev_cache
Inode-cache hash table entries: 1024 (order: 0, 8192 bytes)
kmem_create: Forcing size word alignment - inode_cache
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
kmem_create: Forcing size word alignment - file lock cache
kmem_create: Forcing size word alignment - blkdev_requests
block: queued sectors max/low 9109kB/3036kB, 64 slots per queue
ETRAX 100LX 10/100MBit ethernet v2.0 (c) 2000 Axis Communications AB
eth0 initialized
eth0: changed MAC to 00:40:8C:CD:00:00
ETRAX 100LX serial-driver $Revision: 1.7 $, (c) 2000 Axis Communications AB
ttyS0 at 0xb0000060 is a builtin UART with DMA
ttyS1 at 0xb0000068 is a builtin UART with DMA
ttyS2 at 0xb0000070 is a builtin UART with DMA
ttyS3 at 0xb0000078 is a builtin UART with DMA
Axis flash mapping: 200000 at 50000000
Axis flash: Found 1 x16 CFI device at 0x0 in 16 bit mode
Amd/Fujitsu Extended Query Table v1.0 at 0x0040
Axis flash: JEDEC Device ID is 0xC4. Assuming broken CFI table.
Axis flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
Using default partition table
I2C driver v2.2, (c) 1999-2001 Axis Communications AB
ETRAX 100LX GPIO driver v2.1, (c) 2001 Axis Communications AB
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
kmem_create: Forcing size word alignment - ip_dst_cache
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 2048 bind 2048)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (cramfs filesystem) readonly.
Init starts up...
Mounted none on /proc ok.
Setting up eth0 with ip 10.13.9.116 and mac 00:40:8c:18:04:60
eth0: changed MAC to 00:40:8C:18:04:60
Setting up lo with ip 127.0.0.1
Default gateway is 10.13.9.1
Hostname is bbox1
Telnetd starting, using port 23.
using /bin/sash as shell.
sftpd[15]: sftpd $Revision: 1.7 $ starting up
And here is how some /proc entries look:
17# cd /proc
17# cat cpuinfo
cpu : CRIS
cpu revision : 10
cpu model : ETRAX 100LX
cache size : 8 kB
fpu : no
mmu : yes
ethernet : 10/100 Mbps
token ring : no
scsi : yes
ata : yes
usb : yes
bogomips : 99.84
17# cat meminfo
total: used: free: shared: buffers: cached:
Mem: 7028736 925696 6103040 114688 0 229376
Swap: 0 0 0
MemTotal: 6864 kB
MemFree: 5960 kB
MemShared: 112 kB
Buffers: 0 kB
Cached: 224 kB
Active: 224 kB
Inact_dirty: 0 kB
Inact_clean: 0 kB
Inact_target: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 6864 kB
LowFree: 5960 kB
SwapTotal: 0 kB
SwapFree: 0 kB
17# ls -l /bin
-rwxr-xr-x 1 342 100 10356 Jan 01 00:00 ifconfig
-rwxr-xr-x 1 342 100 17548 Jan 01 00:00 init
-rwxr-xr-x 1 342 100 9488 Jan 01 00:00 route
-rwxr-xr-x 1 342 100 46036 Jan 01 00:00 sftpd
-rwxr-xr-x 1 342 100 48104 Jan 01 00:00 sh
-rwxr-xr-x 1 342 100 16252 Jan 01 00:00 telnetd
Documentation/dev-tools/kmemleak.rst
浏览文件 @ f5a8eb63
......@@ -8,7 +8,7 @@ with the difference that the orphan objects are not freed but only
reported via /sys/kernel/debug/kmemleak. A similar method is used by the
Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
user-space applications.
Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, ppc, mips, s390, metag and tile.
Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, ppc, mips, s390 and tile.
Usage
-----
......
Documentation/devicetree/bindings/cris/axis.txt 已删除 100644 → 0
浏览文件 @ c9297d28
Axis Communications AB
ARTPEC series SoC Device Tree Bindings
CRISv32 based SoCs are ETRAX FS and ARTPEC-3:
- compatible = "axis,crisv32";
Documentation/devicetree/bindings/cris/boards.txt 已删除 100644 → 0
浏览文件 @ c9297d28
Boards based on the CRIS SoCs:
Required root node properties:
- compatible = should be one or more of the following:
- "axis,dev88" - for Axis devboard 88 with ETRAX FS
Optional:
Documentation/devicetree/bindings/gpio/gpio-etraxfs.txt 已删除 100644 → 0
浏览文件 @ c9297d28
Axis ETRAX FS General I/O controller bindings
Required properties:
- compatible: one of:
- "axis,etraxfs-gio"
- "axis,artpec3-gio"
- reg: Physical base address and length of the controller's registers.
- #gpio-cells: Should be 3
- The first cell is the gpio offset number.
- The second cell is reserved and is currently unused.
- The third cell is the port number (hex).
- gpio-controller: Marks the device node as a GPIO controller.
Example:
gio: gpio@b001a000 {
compatible = "axis,etraxfs-gio";
reg = <0xb001a000 0x1000>;
gpio-controller;
#gpio-cells = <3>;
};
Documentation/devicetree/bindings/interrupt-controller/axis,crisv32-intc.txt 已删除 100644 → 0
浏览文件 @ c9297d28
* CRISv32 Interrupt Controller
Interrupt controller for the CRISv32 SoCs.
Main node required properties:
- compatible : should be:
"axis,crisv32-intc"
- interrupt-controller : Identifies the node as an interrupt controller
- #interrupt-cells : Specifies the number of cells needed to encode an
interrupt source. The type shall be a <u32> and the value shall be 1.
- reg: physical base address and size of the intc registers map.
Example:
intc: interrupt-controller {
compatible = "axis,crisv32-intc";
reg = <0xb001c000 0x1000>;
interrupt-controller;
#interrupt-cells = <1>;
};
Documentation/devicetree/bindings/metag/meta.txt 已删除 100644 → 0
浏览文件 @ c9297d28
* Meta Processor Binding
This binding specifies what properties must be available in the device tree
representation of a Meta Processor Core, which is the root node in the tree.
Required properties:
- compatible: Specifies the compatibility list for the Meta processor.
The type shall be <string> and the value shall include "img,meta".
Optional properties:
- clocks: Clock consumer specifiers as described in
Documentation/devicetree/bindings/clock/clock-bindings.txt
- clock-names: Clock consumer names as described in
Documentation/devicetree/bindings/clock/clock-bindings.txt.
Clocks are identified by name. Valid clocks are:
- "core": The Meta core clock from which the Meta timers are derived.
* Examples
/ {
compatible = "toumaz,tz1090", "img,meta";
clocks = <&meta_core_clk>;
clock-names = "core";
};
Documentation/devicetree/bindings/serial/axis,etraxfs-uart.txt 已删除 100644 → 0
浏览文件 @ c9297d28
ETRAX FS UART
Required properties:
- compatible : "axis,etraxfs-uart"
- reg: offset and length of the register set for the device.
- interrupts: device interrupt
Optional properties:
- {dtr,dsr,rng,dcd}-gpios: specify a GPIO for DTR/DSR/RI/DCD
line respectively.
Example:
serial@b00260000 {
compatible = "axis,etraxfs-uart";
reg = <0xb0026000 0x1000>;
interrupts = <68>;
dtr-gpios = <&sysgpio 0 GPIO_ACTIVE_LOW>;
dsr-gpios = <&sysgpio 1 GPIO_ACTIVE_LOW>;
rng-gpios = <&sysgpio 2 GPIO_ACTIVE_LOW>;
dcd-gpios = <&sysgpio 3 GPIO_ACTIVE_LOW>;
};
Documentation/driver-api/usb/writing_musb_glue_layer.rst
浏览文件 @ f5a8eb63
......@@ -718,6 +718,3 @@ http://www.maximintegrated.com/app-notes/index.mvp/id/1822
Texas Instruments USB Configuration Wiki Page:
http://processors.wiki.ti.com/index.php/Usbgeneralpage
Analog Devices Blackfin MUSB Configuration:
http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:drivers:musb
Documentation/features/core/BPF-JIT/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | ok |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/core/generic-idle-thread/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | ok |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | ok |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | ok |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | ok |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/core/jump-labels/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | ok |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/core/tracehook/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | ok |
| c6x: | ok |
| cris: | TODO |
| frv: | ok |
| h8300: | TODO |
| hexagon: | ok |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | ok |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | ok |
| nios2: | ok |
| openrisc: | ok |
| parisc: | ok |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/KASAN/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok | 64-bit only
......
Documentation/features/debug/gcov-profile-all/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | ok |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/kgdb/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | ok |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | ok |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | ok |
| mips: | ok |
| mn10300: | ok |
| nios2: | ok |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/kprobes-on-ftrace/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/kprobes/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/kretprobes/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/optprobes/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/stackprotector/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | ok |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/uprobes/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/debug/user-ret-profiler/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/io/dma-api-debug/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | ok |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | ok |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/io/dma-contiguous/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/io/sg-chain/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | ok |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/lib/strncasecmp/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | TODO |
......
Documentation/features/locking/cmpxchg-local/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/locking/lockdep/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | ok |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | ok |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | ok |
| microblaze: | ok |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | ok |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | ok |
| unicore32: | ok |
| x86: | ok |
......
Documentation/features/locking/queued-rwlocks/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/locking/queued-spinlocks/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/locking/rwsem-optimized/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/perf/kprobes-event/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | ok |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | TODO |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/perf/perf-regs/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/perf/perf-stackdump/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/sched/membarrier-sync-core/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -33,28 +33,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/sched/numa-balancing/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | .. |
| arm: | .. |
| arm64: | .. |
| blackfin: | .. |
| c6x: | .. |
| cris: | .. |
| frv: | .. |
| h8300: | .. |
| hexagon: | .. |
| ia64: | TODO |
| m32r: | .. |
| m68k: | .. |
| metag: | .. |
| microblaze: | .. |
| mips: | TODO |
| mn10300: | .. |
| nios2: | .. |
| openrisc: | .. |
| parisc: | .. |
| powerpc: | ok |
| s390: | .. |
| score: | .. |
| sh: | .. |
| sparc: | TODO |
| tile: | TODO |
| um: | .. |
| unicore32: | .. |
| x86: | ok |
......
Documentation/features/seccomp/seccomp-filter/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | ok |
| um: | ok |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/time/arch-tick-broadcast/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | TODO |
......
Documentation/features/time/clockevents/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | ok |
| c6x: | ok |
| cris: | ok |
| frv: | TODO |
| h8300: | ok |
| hexagon: | ok |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | ok |
| metag: | ok |
| microblaze: | ok |
| mips: | ok |
| mn10300: | ok |
| nios2: | ok |
| openrisc: | ok |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | ok |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | ok |
| unicore32: | ok |
| x86: | ok |
......
Documentation/features/time/context-tracking/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/time/irq-time-acct/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | .. |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | .. |
| powerpc: | .. |
| s390: | .. |
| score: | TODO |
| sh: | TODO |
| sparc: | .. |
| tile: | .. |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/time/modern-timekeeping/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | TODO |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | ok |
| cris: | TODO |
| frv: | ok |
| h8300: | ok |
| hexagon: | ok |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | ok |
| microblaze: | ok |
| mips: | ok |
| mn10300: | ok |
| nios2: | ok |
| openrisc: | ok |
| parisc: | ok |
| powerpc: | ok |
| s390: | ok |
| score: | ok |
| sh: | ok |
| sparc: | ok |
| tile: | ok |
| um: | ok |
| unicore32: | ok |
| x86: | ok |
......
Documentation/features/time/virt-cpuacct/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | ok |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | ok |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/vm/ELF-ASLR/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | ok |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/vm/PG_uncached/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | ok |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/vm/THP/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | .. |
| c6x: | .. |
| cris: | .. |
| frv: | .. |
| h8300: | .. |
| hexagon: | .. |
| ia64: | TODO |
| m32r: | .. |
| m68k: | .. |
| metag: | TODO |
| microblaze: | .. |
| mips: | ok |
| mn10300: | .. |
| nios2: | .. |
| openrisc: | .. |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | .. |
| sh: | .. |
| sparc: | ok |
| tile: | TODO |
| um: | .. |
| unicore32: | .. |
| x86: | ok |
......
Documentation/features/vm/TLB/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | .. |
| cris: | .. |
| frv: | .. |
| h8300: | .. |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | .. |
| metag: | TODO |
| microblaze: | .. |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | .. |
| openrisc: | .. |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | .. |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | .. |
| unicore32: | .. |
| x86: | ok |
......
Documentation/features/vm/huge-vmap/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | TODO |
| arm: | TODO |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | TODO |
| s390: | TODO |
| score: | TODO |
| sh: | TODO |
| sparc: | TODO |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/vm/ioremap_prot/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | TODO |
| arm64: | TODO |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | TODO |
| score: | TODO |
| sh: | ok |
| sparc: | TODO |
| tile: | ok |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/features/vm/numa-memblock/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | .. |
| arm: | .. |
| arm64: | .. |
| blackfin: | .. |
| c6x: | .. |
| cris: | .. |
| frv: | .. |
| h8300: | .. |
| hexagon: | .. |
| ia64: | ok |
| m32r: | TODO |
| m68k: | .. |
| metag: | ok |
| microblaze: | ok |
| mips: | ok |
| mn10300: | TODO |
| nios2: | .. |
| openrisc: | .. |
| parisc: | .. |
| powerpc: | ok |
| s390: | ok |
| score: | ok |
| sh: | ok |
| sparc: | ok |
| tile: | TODO |
| um: | .. |
| unicore32: | .. |
| x86: | ok |
......
Documentation/features/vm/pte_special/arch-support.txt
浏览文件 @ f5a8eb63
......@@ -10,28 +10,20 @@
| arc: | ok |
| arm: | ok |
| arm64: | ok |
| blackfin: | TODO |
| c6x: | TODO |
| cris: | TODO |
| frv: | TODO |
| h8300: | TODO |
| hexagon: | TODO |
| ia64: | TODO |
| m32r: | TODO |
| m68k: | TODO |
| metag: | TODO |
| microblaze: | TODO |
| mips: | TODO |
| mn10300: | TODO |
| nios2: | TODO |
| openrisc: | TODO |
| parisc: | TODO |
| powerpc: | ok |
| s390: | ok |
| score: | TODO |
| sh: | ok |
| sparc: | ok |
| tile: | TODO |
| um: | TODO |
| unicore32: | TODO |
| x86: | ok |
......
Documentation/frv/README.txt 已删除 100644 → 0
浏览文件 @ c9297d28
================================
Fujitsu FR-V LINUX DOCUMENTATION
================================
This directory contains documentation for the Fujitsu FR-V CPU architecture
port of Linux.
The following documents are available:
(*) features.txt
A description of the basic features inherent in this architecture port.
(*) configuring.txt
A summary of the configuration options particular to this architecture.
(*) booting.txt
A description of how to boot the kernel image and a summary of the kernel
command line options.
(*) gdbstub.txt
A description of how to debug the kernel using GDB attached by serial
port, and a summary of the services available.
(*) mmu-layout.txt
A description of the virtual and physical memory layout used in the
MMU linux kernel, and the registers used to support it.
(*) gdbinit
An example .gdbinit file for use with GDB. It includes macros for viewing
MMU state on the FR451. See mmu-layout.txt for more information.
(*) clock.txt
A description of the CPU clock scaling interface.
(*) atomic-ops.txt
A description of how the FR-V kernel's atomic operations work.
Documentation/frv/atomic-ops.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=====================================
FUJITSU FR-V KERNEL ATOMIC OPERATIONS
=====================================
On the FR-V CPUs, there is only one atomic Read-Modify-Write operation: the SWAP/SWAPI
instruction. Unfortunately, this alone can't be used to implement the following operations:
(*) Atomic add to memory
(*) Atomic subtract from memory
(*) Atomic bit modification (set, clear or invert)
(*) Atomic compare and exchange
On such CPUs, the standard way of emulating such operations in uniprocessor mode is to disable
interrupts, but on the FR-V CPUs, modifying the PSR takes a lot of clock cycles, and it has to be
done twice. This means the CPU runs for a relatively long time with interrupts disabled,
potentially having a great effect on interrupt latency.
=============
NEW ALGORITHM
=============
To get around this, the following algorithm has been implemented. It operates in a way similar to
the LL/SC instruction pairs supported on a number of platforms.
(*) The CCCR.CC3 register is reserved within the kernel to act as an atomic modify abort flag.
(*) In the exception prologues run on kernel->kernel entry, CCCR.CC3 is set to 0 (Undefined
state).
(*) All atomic operations can then be broken down into the following algorithm:
(1) Set ICC3.Z to true and set CC3 to True (ORCC/CKEQ/ORCR).
(2) Load the value currently in the memory to be modified into a register.
(3) Make changes to the value.
(4) If CC3 is still True, simultaneously and atomically (by VLIW packing):
(a) Store the modified value back to memory.
(b) Set ICC3.Z to false (CORCC on GR29 is sufficient for this - GR29 holds the current
task pointer in the kernel, and so is guaranteed to be non-zero).
(5) If ICC3.Z is still true, go back to step (1).
This works in a non-SMP environment because any interrupt or other exception that happens between
steps (1) and (4) will set CC3 to the Undefined, thus aborting the store in (4a), and causing the
condition in ICC3 to remain with the Z flag set, thus causing step (5) to loop back to step (1).
This algorithm suffers from two problems:
(1) The condition CCCR.CC3 is cleared unconditionally by an exception, irrespective of whether or
not any changes were made to the target memory location during that exception.
(2) The branch from step (5) back to step (1) may have to happen more than once until the store
manages to take place. In theory, this loop could cycle forever because there are too many
interrupts coming in, but it's unlikely.
=======
EXAMPLE
=======
Taking an example from include/asm-frv/atomic.h:
static inline int atomic_add_return(int i, atomic_t *v)
{
unsigned long val;
asm("0: \n"
It starts by setting ICC3.Z to true for later use, and also transforming that into CC3 being in the
True state.
" orcc gr0,gr0,gr0,icc3 \n" <-- (1)
" ckeq icc3,cc7 \n" <-- (1)
Then it does the load. Note that the final phase of step (1) is done at the same time as the
load. The VLIW packing ensures they are done simultaneously. The ".p" on the load must not be
removed without swapping the order of these two instructions.
" ld.p %M0,%1 \n" <-- (2)
" orcr cc7,cc7,cc3 \n" <-- (1)
Then the proposed modification is generated. Note that the old value can be retained if required
(such as in test_and_set_bit()).
" add%I2 %1,%2,%1 \n" <-- (3)
Then it attempts to store the value back, contingent on no exception having cleared CC3 since it
was set to True.
" cst.p %1,%M0 ,cc3,#1 \n" <-- (4a)
It simultaneously records the success or failure of the store in ICC3.Z.
" corcc gr29,gr29,gr0 ,cc3,#1 \n" <-- (4b)
Such that the branch can then be taken if the operation was aborted.
" beq icc3,#0,0b \n" <-- (5)
: "+U"(v->counter), "=&r"(val)
: "NPr"(i)
: "memory", "cc7", "cc3", "icc3"
);
return val;
}
=============
CONFIGURATION
=============
The atomic ops implementation can be made inline or out-of-line by changing the
CONFIG_FRV_OUTOFLINE_ATOMIC_OPS configuration variable. Making it out-of-line has a number of
advantages:
- The resulting kernel image may be smaller
- Debugging is easier as atomic ops can just be stepped over and they can be breakpointed
Keeping it inline also has a number of advantages:
- The resulting kernel may be Faster
- no out-of-line function calls need to be made
- the compiler doesn't have half its registers clobbered by making a call
The out-of-line implementations live in arch/frv/lib/atomic-ops.S.
Documentation/frv/booting.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=========================
BOOTING FR-V LINUX KERNEL
=========================
======================
PROVIDING A FILESYSTEM
======================
First of all, a root filesystem must be made available. This can be done in
one of two ways:
(1) NFS Export
A filesystem should be constructed in a directory on an NFS server that
the target board can reach. This directory should then be NFS exported
such that the target board can read and write into it as root.
(2) Flash Filesystem (JFFS2 Recommended)
In this case, the image must be stored or built up on flash before it
can be used. A complete image can be built using the mkfs.jffs2 or
similar program and then downloaded and stored into flash by RedBoot.
========================
LOADING THE KERNEL IMAGE
========================
The kernel will need to be loaded into RAM by RedBoot (or by some alternative
boot loader) before it can be run. The kernel image (arch/frv/boot/Image) may
be loaded in one of three ways:
(1) Load from Flash
This is the simplest. RedBoot can store an image in the flash (see the
RedBoot documentation) and then load it back into RAM. RedBoot keeps
track of the load address, entry point and size, so the command to do
this is simply:
fis load linux
The image is then ready to be executed.
(2) Load by TFTP
The following command will download a raw binary kernel image from the
default server (as negotiated by BOOTP) and store it into RAM:
load -b 0x00100000 -r /tftpboot/image.bin
The image is then ready to be executed.
(3) Load by Y-Modem
The following command will download a raw binary kernel image across the
serial port that RedBoot is currently using:
load -m ymodem -b 0x00100000 -r zImage
The serial client (such as minicom) must then be told to transmit the
program by Y-Modem.
When finished, the image will then be ready to be executed.
==================
BOOTING THE KERNEL
==================
Boot the image with the following RedBoot command:
exec -c "<CMDLINE>" 0x00100000
For example:
exec -c "console=ttySM0,115200 ip=:::::dhcp root=/dev/mtdblock2 rw"
This will start the kernel running. Note that if the GDB-stub is compiled in,
then the kernel will immediately wait for GDB to connect over serial before
doing anything else. See the section on kernel debugging with GDB.
The kernel command line <CMDLINE> tells the kernel where its console is and
how to find its root filesystem. This is made up of the following components,
separated by spaces:
(*) console=ttyS<x>[,<baud>[<parity>[<bits>[<flow>]]]]
This specifies that the system console should output through on-chip
serial port <x> (which can be "0" or "1").
<baud> is a standard baud rate between 1200 and 115200 (default 9600).
<parity> is a parity setting of "N", "O", "E", "M" or "S" for None, Odd,
Even, Mark or Space. "None" is the default.
<stop> is "7" or "8" for the number of bits per character. "8" is the
default.
<flow> is "r" to use flow control (XCTS on serial port 2 only). The
default is to not use flow control.
For example:
console=ttyS0,115200
To use the first on-chip serial port at baud rate 115200, no parity, 8
bits, and no flow control.
(*) root=<xxxx>
This specifies the device upon which the root filesystem resides. It
may be specified by major and minor number, device path, or even
partition uuid, if supported. For example:
/dev/nfs NFS root filesystem
/dev/mtdblock3 Fourth RedBoot partition on the System Flash
PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF/PARTNROFF=1
first partition after the partition with the given UUID
253:0 Device with major 253 and minor 0
Authoritative information can be found in
"Documentation/admin-guide/kernel-parameters.rst".
(*) rw
Start with the root filesystem mounted Read/Write.
The remaining components are all optional:
(*) ip=<ip>::::<host>:<iface>:<cfg>
Configure the network interface. If <cfg> is "off" then <ip> should
specify the IP address for the network device <iface>. <host> provide
the hostname for the device.
If <cfg> is "bootp" or "dhcp", then all of these parameters will be
discovered by consulting a BOOTP or DHCP server.
For example, the following might be used:
ip=192.168.73.12::::frv:eth0:off
This sets the IP address on the VDK motherboard RTL8029 ethernet chipset
(eth0) to be 192.168.73.12, and sets the board's hostname to be "frv".
(*) nfsroot=<server>:<dir>[,v<vers>]
This is mandatory if "root=/dev/nfs" is given as an option. It tells the
kernel the IP address of the NFS server providing its root filesystem,
and the pathname on that server of the filesystem.
The NFS version to use can also be specified. v2 and v3 are supported by
Linux.
For example:
nfsroot=192.168.73.1:/nfsroot-frv
(*) profile=1
Turns on the kernel profiler (accessible through /proc/profile).
(*) console=gdb0
This can be used as an alternative to the "console=ttyS..." listed
above. I tells the kernel to pass the console output to GDB if the
gdbstub is compiled in to the kernel.
If this is used, then the gdbstub passes the text to GDB, which then
simply dumps it to its standard output.
(*) mem=<xxx>M
Normally the kernel will work out how much SDRAM it has by reading the
SDRAM controller registers. That can be overridden with this
option. This allows the kernel to be told that it has <xxx> megabytes of
memory available.
(*) init=<prog> [<arg> [<arg> [<arg> ...]]]
This tells the kernel what program to run initially. By default this is
/sbin/init, but /sbin/sash or /bin/sh are common alternatives.
Documentation/frv/clock.txt 已删除 100644 → 0
浏览文件 @ c9297d28
Clock scaling
-------------
The kernel supports scaling of CLCK.CMODE, CLCK.CM and CLKC.P0 clock
registers. If built with CONFIG_PM and CONFIG_SYSCTL options enabled, four
extra files will appear in the directory /proc/sys/pm/. Reading these files
will show:
p0 -- current value of the P0 bit in CLKC register.
cm -- current value of the CM bits in CLKC register.
cmode -- current value of the CMODE bits in CLKC register.
On all boards, the 'p0' file should also be writable, and either '1' or '0'
can be rewritten, to set or clear the CLKC_P0 bit respectively, hence
controlling whether the resource bus rate clock is halved.
The 'cm' file should also be available on all boards. '0' can be written to it
to shift the board into High-Speed mode (normal), and '1' can be written to
shift the board into Medium-Speed mode. Selecting Low-Speed mode is not
supported by this interface, even though some CPUs do support it.
On the boards with FR405 CPU (i.e. CB60 and CB70), the 'cmode' file is also
writable, allowing the CPU core speed (and other clock speeds) to be
controlled from userspace.
Determining current and possible settings
-----------------------------------------
The current state and the available masks can be found in /proc/cpuinfo. For
example, on the CB70:
# cat /proc/cpuinfo
CPU-Series: fr400
CPU-Core: fr405, gr0-31, BE, CCCR
CPU: mb93405
MMU: Prot
FP-Media: fr0-31, Media
System: mb93091-cb70, mb93090-mb00
PM-Controls: cmode=0xd31f, cm=0x3, p0=0x3, suspend=0x9
PM-Status: cmode=3, cm=0, p0=0
Clock-In: 50.00 MHz
Clock-Core: 300.00 MHz
Clock-SDRAM: 100.00 MHz
Clock-CBus: 100.00 MHz
Clock-Res: 50.00 MHz
Clock-Ext: 50.00 MHz
Clock-DSU: 25.00 MHz
BogoMips: 300.00
And on the PDK, the PM lines look like the following:
PM-Controls: cm=0x3, p0=0x3, suspend=0x9
PM-Status: cmode=9, cm=0, p0=0
The PM-Controls line, if present, will indicate which /proc/sys/pm files can
be set to what values. The specification values are bitmasks; so, for example,
"suspend=0x9" indicates that 0 and 3 can be written validly to
/proc/sys/pm/suspend.
The PM-Controls line will only be present if CONFIG_PM is configured to Y.
The PM-Status line indicates which clock controls are set to which value. If
the file can be read, then the suspend value must be 0, and so that's not
included.
Documentation/frv/configuring.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=======================================
FUJITSU FR-V LINUX KERNEL CONFIGURATION
=======================================
=====================
CONFIGURATION OPTIONS
=====================
The most important setting is in the "MMU support options" tab (the first
presented in the configuration tools available):
(*) "Kernel Type"
This options allows selection of normal, MMU-requiring linux, and uClinux
(which doesn't require an MMU and doesn't have inter-process protection).
There are a number of settings in the "Processor type and features" section of
the kernel configuration that need to be considered.
(*) "CPU"
The register and instruction sets at the core of the processor. This can
only be set to "FR40x/45x/55x" at the moment - but this permits usage of
the kernel with MB93091 CB10, CB11, CB30, CB41, CB60, CB70 and CB451
CPU boards, and with the MB93093 PDK board.
(*) "System"
This option allows a choice of basic system. This governs the peripherals
that are expected to be available.
(*) "Motherboard"
This specifies the type of motherboard being used, and the peripherals
upon it. Currently only "MB93090-MB00" can be set here.
(*) "Default cache-write mode"
This controls the initial data cache write management mode. By default
Write-Through is selected, but Write-Back (Copy-Back) can also be
selected. This can be changed dynamically once the kernel is running (see
features.txt).
There are some architecture specific configuration options in the "General
Setup" section of the kernel configuration too:
(*) "Reserve memory uncached for (PCI) DMA"
This requests that a uClinux kernel set aside some memory in an uncached
window for the use as consistent DMA memory (mainly for PCI). At least a
megabyte will be allocated in this way, possibly more. Any memory so
reserved will not be available for normal allocations.
(*) "Kernel support for ELF-FDPIC binaries"
This enables the binary-format driver for the new FDPIC ELF binaries that
this platform normally uses. These binaries are totally relocatable -
their separate sections can relocated independently, allowing them to be
shared on uClinux where possible. This should normally be enabled.
(*) "Kernel image protection"
This makes the protection register governing access to the core kernel
image prohibit access by userspace programs. This option is available on
uClinux only.
There are also a number of settings in the "Kernel Hacking" section of the
kernel configuration especially for debugging a kernel on this
architecture. See the "gdbstub.txt" file for information about those.
======================
DEFAULT CONFIGURATIONS
======================
The kernel sources include a number of example default configurations:
(*) defconfig-mb93091
Default configuration for the MB93091-VDK with both CPU board and
MB93090-MB00 motherboard running uClinux.
(*) defconfig-mb93091-fb
Default configuration for the MB93091-VDK with CPU board,
MB93090-MB00 motherboard, and DAV board running uClinux.
Includes framebuffer driver.
(*) defconfig-mb93093
Default configuration for the MB93093-PDK board running uClinux.
(*) defconfig-cb70-standalone
Default configuration for the MB93091-VDK with only CB70 CPU board
running uClinux. This will use the CB70's DM9000 for network access.
(*) defconfig-mmu
Default configuration for the MB93091-VDK with both CB451 CPU board and
MB93090-MB00 motherboard running MMU linux.
(*) defconfig-mmu-audio
Default configuration for the MB93091-VDK with CB451 CPU board, DAV
board, and MB93090-MB00 motherboard running MMU linux. Includes
audio driver.
(*) defconfig-mmu-fb
Default configuration for the MB93091-VDK with CB451 CPU board, DAV
board, and MB93090-MB00 motherboard running MMU linux. Includes
framebuffer driver.
(*) defconfig-mmu-standalone
Default configuration for the MB93091-VDK with only CB451 CPU board
running MMU linux.
Documentation/frv/features.txt 已删除 100644 → 0
浏览文件 @ c9297d28
===========================
FUJITSU FR-V LINUX FEATURES
===========================
This kernel port has a number of features of which the user should be aware:
(*) Linux and uClinux
The FR-V architecture port supports both normal MMU linux and uClinux out
of the same sources.
(*) CPU support
Support for the FR401, FR403, FR405, FR451 and FR555 CPUs should work with
the same uClinux kernel configuration.
In normal (MMU) Linux mode, only the FR451 CPU will work as that is the
only one with a suitably featured CPU.
The kernel is written and compiled with the assumption that only the
bottom 32 GR registers and no FR registers will be used by the kernel
itself, however all extra userspace registers will be saved on context
switch. Note that since most CPUs can't support lazy switching, no attempt
is made to do lazy register saving where that would be possible (FR555
only currently).
(*) Board support
The board on which the kernel will run can be configured on the "Processor
type and features" configuration tab.
Set the System to "MB93093-PDK" to boot from the MB93093 (FR403) PDK.
Set the System to "MB93091-VDK" to boot from the CB11, CB30, CB41, CB60,
CB70 or CB451 VDK boards. Set the Motherboard setting to "MB93090-MB00" to
boot with the standard ATA90590B VDK motherboard, and set it to "None" to
boot without any motherboard.
(*) Binary Formats
The only userspace binary format supported is FDPIC ELF. Normal ELF, FLAT
and AOUT binaries are not supported for this architecture.
FDPIC ELF supports shared library and program interpreter facilities.
(*) Scheduler Speed
The kernel scheduler runs at 100Hz irrespective of the clock speed on this
architecture. This value is set in asm/param.h (see the HZ macro defined
there).
(*) Normal (MMU) Linux Memory Layout.
See mmu-layout.txt in this directory for a description of the normal linux
memory layout
See include/asm-frv/mem-layout.h for constants pertaining to the memory
layout.
See include/asm-frv/mb-regs.h for the constants pertaining to the I/O bus
controller configuration.
(*) uClinux Memory Layout
The memory layout used by the uClinux kernel is as follows:
0x00000000 - 0x00000FFF Null pointer catch page
0x20000000 - 0x200FFFFF CS2# [PDK] FPGA
0xC0000000 - 0xCFFFFFFF SDRAM
0xC0000000 Base of Linux kernel image
0xE0000000 - 0xEFFFFFFF CS2# [VDK] SLBUS/PCI window
0xF0000000 - 0xF0FFFFFF CS5# MB93493 CSC area (DAV daughter board)
0xF1000000 - 0xF1FFFFFF CS7# [CB70/CB451] CPU-card PCMCIA port space
0xFC000000 - 0xFC0FFFFF CS1# [VDK] MB86943 config space
0xFC100000 - 0xFC1FFFFF CS6# [CB70/CB451] CPU-card DM9000 NIC space
0xFC100000 - 0xFC1FFFFF CS6# [PDK] AX88796 NIC space
0xFC200000 - 0xFC2FFFFF CS3# MB93493 CSR area (DAV daughter board)
0xFD000000 - 0xFDFFFFFF CS4# [CB70/CB451] CPU-card extra flash space
0xFE000000 - 0xFEFFFFFF Internal CPU peripherals
0xFF000000 - 0xFF1FFFFF CS0# Flash 1
0xFF200000 - 0xFF3FFFFF CS0# Flash 2
0xFFC00000 - 0xFFC0001F CS0# [VDK] FPGA
The kernel reads the size of the SDRAM from the memory bus controller
registers by default.
The kernel initialisation code (1) adjusts the SDRAM base addresses to
move the SDRAM to desired address, (2) moves the kernel image down to the
bottom of SDRAM, (3) adjusts the bus controller registers to move I/O
windows, and (4) rearranges the protection registers to protect all of
this.
The reasons for doing this are: (1) the page at address 0 should be
inaccessible so that NULL pointer errors can be caught; and (2) the bottom
three quarters are left unoccupied so that an FR-V CPU with an MMU can use
it for virtual userspace mappings.
See include/asm-frv/mem-layout.h for constants pertaining to the memory
layout.
See include/asm-frv/mb-regs.h for the constants pertaining to the I/O bus
controller configuration.
(*) uClinux Memory Protection
A DAMPR register is used to cover the entire region used for I/O
(0xE0000000 - 0xFFFFFFFF). This permits the kernel to make uncached
accesses to this region. Userspace is not permitted to access it.
The DAMPR/IAMPR protection registers not in use for any other purpose are
tiled over the top of the SDRAM such that:
(1) The core kernel image is covered by as small a tile as possible
granting only the kernel access to the underlying data, whilst
making sure no SDRAM is actually made unavailable by this approach.
(2) All other tiles are arranged to permit userspace access to the rest
of the SDRAM.
Barring point (1), there is nothing to protect kernel data against
userspace damage - but this is uClinux.
(*) Exceptions and Fixups
Since the FR40x and FR55x CPUs that do not have full MMUs generate
imprecise data error exceptions, there are currently no automatic fixup
services available in uClinux. This includes misaligned memory access
fixups.
Userspace EFAULT errors can be trapped by issuing a MEMBAR instruction and
forcing the fault to happen there.
On the FR451, however, data exceptions are mostly precise, and so
exception fixup handling is implemented as normal.
(*) Userspace Breakpoints
The ptrace() system call supports the following userspace debugging
features:
(1) Hardware assisted single step.
(2) Breakpoint via the FR-V "BREAK" instruction.
(3) Breakpoint via the FR-V "TIRA GR0, #1" instruction.
(4) Syscall entry/exit trap.
Each of the above generates a SIGTRAP.
(*) On-Chip Serial Ports
The FR-V on-chip serial ports are made available as ttyS0 and ttyS1. Note
that if the GDB stub is compiled in, ttyS1 will not actually be available
as it will be being used for the GDB stub.
These ports can be made by:
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
(*) Maskable Interrupts
Level 15 (Non-maskable) interrupts are dealt with by the GDB stub if
present, and cause a panic if not. If the GDB stub is present, ttyS1's
interrupts are rated at level 15.
All other interrupts are distributed over the set of available priorities
so that no IRQs are shared where possible. The arch interrupt handling
routines attempt to disentangle the various sources available through the
CPU's own multiplexor, and those on off-CPU peripherals.
(*) Accessing PCI Devices
Where PCI is available, care must be taken when dealing with drivers that
access PCI devices. PCI devices present their data in little-endian form,
but the CPU sees it in big-endian form. The macros in asm/io.h try to get
this right, but may not under all circumstances...
(*) Ax88796 Ethernet Driver
The MB93093 PDK board has an Ax88796 ethernet chipset (an NE2000 clone). A
driver has been written to deal specifically with this. The driver
provides MII services for the card.
The driver can be configured by running make xconfig, and going to:
(*) Network device support
- turn on "Network device support"
(*) Ethernet (10 or 100Mbit)
- turn on "Ethernet (10 or 100Mbit)"
- turn on "AX88796 NE2000 compatible chipset"
The driver can be found in:
drivers/net/ax88796.c
include/asm/ax88796.h
(*) WorkRAM Driver
This driver provides a character device that permits access to the WorkRAM
that can be found on the FR451 CPU. Each page is accessible through a
separate minor number, thereby permitting each page to have its own
filesystem permissions set on the device file.
The device files should be:
mknod /dev/frv/workram0 c 240 0
mknod /dev/frv/workram1 c 240 1
mknod /dev/frv/workram2 c 240 2
...
The driver will not permit the opening of any device file that does not
correspond to at least a partial page of WorkRAM. So the first device file
is the only one available on the FR451. If any other CPU is detected, none
of the devices will be openable.
The devices can be accessed with read, write and llseek, and can also be
mmapped. If they're mmapped, they will only map at the appropriate
0x7e8nnnnn address on linux and at the 0xfe8nnnnn address on uClinux. If
MAP_FIXED is not specified, the appropriate address will be chosen anyway.
The mappings must be MAP_SHARED not MAP_PRIVATE, and must not be
PROT_EXEC. They must also start at file offset 0, and must not be longer
than one page in size.
This driver can be configured by running make xconfig, and going to:
(*) Character devices
- turn on "Fujitsu FR-V CPU WorkRAM support"
(*) Dynamic data cache write mode changing
It is possible to view and to change the data cache's write mode through
the /proc/sys/frv/cache-mode file while the kernel is running. There are
two modes available:
NAME MEANING
===== ==========================================
wthru Data cache is in Write-Through mode
wback Data cache is in Write-Back/Copy-Back mode
To read the cache mode:
# cat /proc/sys/frv/cache-mode
wthru
To change the cache mode:
# echo wback >/proc/sys/frv/cache-mode
# cat /proc/sys/frv/cache-mode
wback
(*) MMU Context IDs and Pinning
On MMU Linux the CPU supports the concept of a context ID in its MMU to
make it more efficient (TLB entries are labelled with a context ID to link
them to specific tasks).
Normally once a context ID is allocated, it will remain affixed to a task
or CLONE_VM'd group of tasks for as long as it exists. However, since the
kernel is capable of supporting more tasks than there are possible ID
numbers, the kernel will pass context IDs from one task to another if
there are insufficient available.
The context ID currently in use by a task can be viewed in /proc:
# grep CXNR /proc/1/status
CXNR: 1
Note that kernel threads do not have a userspace context, and so will not
show a CXNR entry in that file.
Under some circumstances, however, it is desirable to pin a context ID on
a process such that the kernel won't pass it on. This can be done by
writing the process ID of the target process to a special file:
# echo 17 >/proc/sys/frv/pin-cxnr
Reading from the file will then show the context ID pinned.
# cat /proc/sys/frv/pin-cxnr
4
The context ID will remain pinned as long as any process is using that
context, i.e.: when the all the subscribing processes have exited or
exec'd; or when an unpinning request happens:
# echo 0 >/proc/sys/frv/pin-cxnr
When there isn't a pinned context, the file shows -1:
# cat /proc/sys/frv/pin-cxnr
-1
Documentation/frv/gdbinit 已删除 100644 → 0
浏览文件 @ c9297d28
set remotebreak 1
define _amr
printf "AMRx DAMR IAMR \n"
printf "==== ===================== =====================\n"
printf "amr0 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x0].L,__debug_mmu.damr[0x0].P,__debug_mmu.iamr[0x0].L,__debug_mmu.iamr[0x0].P
printf "amr1 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x1].L,__debug_mmu.damr[0x1].P,__debug_mmu.iamr[0x1].L,__debug_mmu.iamr[0x1].P
printf "amr2 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x2].L,__debug_mmu.damr[0x2].P,__debug_mmu.iamr[0x2].L,__debug_mmu.iamr[0x2].P
printf "amr3 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x3].L,__debug_mmu.damr[0x3].P,__debug_mmu.iamr[0x3].L,__debug_mmu.iamr[0x3].P
printf "amr4 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x4].L,__debug_mmu.damr[0x4].P,__debug_mmu.iamr[0x4].L,__debug_mmu.iamr[0x4].P
printf "amr5 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x5].L,__debug_mmu.damr[0x5].P,__debug_mmu.iamr[0x5].L,__debug_mmu.iamr[0x5].P
printf "amr6 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x6].L,__debug_mmu.damr[0x6].P,__debug_mmu.iamr[0x6].L,__debug_mmu.iamr[0x6].P
printf "amr7 : L:%08lx P:%08lx : L:%08lx P:%08lx\n",__debug_mmu.damr[0x7].L,__debug_mmu.damr[0x7].P,__debug_mmu.iamr[0x7].L,__debug_mmu.iamr[0x7].P
printf "amr8 : L:%08lx P:%08lx\n",__debug_mmu.damr[0x8].L,__debug_mmu.damr[0x8].P
printf "amr9 : L:%08lx P:%08lx\n",__debug_mmu.damr[0x9].L,__debug_mmu.damr[0x9].P
printf "amr10: L:%08lx P:%08lx\n",__debug_mmu.damr[0xa].L,__debug_mmu.damr[0xa].P
printf "amr11: L:%08lx P:%08lx\n",__debug_mmu.damr[0xb].L,__debug_mmu.damr[0xb].P
end
define _tlb
printf "tlb[0x00]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x0].L,__debug_mmu.tlb[0x0].P,__debug_mmu.tlb[0x40+0x0].L,__debug_mmu.tlb[0x40+0x0].P
printf "tlb[0x01]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1].L,__debug_mmu.tlb[0x1].P,__debug_mmu.tlb[0x40+0x1].L,__debug_mmu.tlb[0x40+0x1].P
printf "tlb[0x02]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2].L,__debug_mmu.tlb[0x2].P,__debug_mmu.tlb[0x40+0x2].L,__debug_mmu.tlb[0x40+0x2].P
printf "tlb[0x03]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3].L,__debug_mmu.tlb[0x3].P,__debug_mmu.tlb[0x40+0x3].L,__debug_mmu.tlb[0x40+0x3].P
printf "tlb[0x04]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x4].L,__debug_mmu.tlb[0x4].P,__debug_mmu.tlb[0x40+0x4].L,__debug_mmu.tlb[0x40+0x4].P
printf "tlb[0x05]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x5].L,__debug_mmu.tlb[0x5].P,__debug_mmu.tlb[0x40+0x5].L,__debug_mmu.tlb[0x40+0x5].P
printf "tlb[0x06]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x6].L,__debug_mmu.tlb[0x6].P,__debug_mmu.tlb[0x40+0x6].L,__debug_mmu.tlb[0x40+0x6].P
printf "tlb[0x07]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x7].L,__debug_mmu.tlb[0x7].P,__debug_mmu.tlb[0x40+0x7].L,__debug_mmu.tlb[0x40+0x7].P
printf "tlb[0x08]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x8].L,__debug_mmu.tlb[0x8].P,__debug_mmu.tlb[0x40+0x8].L,__debug_mmu.tlb[0x40+0x8].P
printf "tlb[0x09]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x9].L,__debug_mmu.tlb[0x9].P,__debug_mmu.tlb[0x40+0x9].L,__debug_mmu.tlb[0x40+0x9].P
printf "tlb[0x0a]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0xa].L,__debug_mmu.tlb[0xa].P,__debug_mmu.tlb[0x40+0xa].L,__debug_mmu.tlb[0x40+0xa].P
printf "tlb[0x0b]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0xb].L,__debug_mmu.tlb[0xb].P,__debug_mmu.tlb[0x40+0xb].L,__debug_mmu.tlb[0x40+0xb].P
printf "tlb[0x0c]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0xc].L,__debug_mmu.tlb[0xc].P,__debug_mmu.tlb[0x40+0xc].L,__debug_mmu.tlb[0x40+0xc].P
printf "tlb[0x0d]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0xd].L,__debug_mmu.tlb[0xd].P,__debug_mmu.tlb[0x40+0xd].L,__debug_mmu.tlb[0x40+0xd].P
printf "tlb[0x0e]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0xe].L,__debug_mmu.tlb[0xe].P,__debug_mmu.tlb[0x40+0xe].L,__debug_mmu.tlb[0x40+0xe].P
printf "tlb[0x0f]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0xf].L,__debug_mmu.tlb[0xf].P,__debug_mmu.tlb[0x40+0xf].L,__debug_mmu.tlb[0x40+0xf].P
printf "tlb[0x10]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x10].L,__debug_mmu.tlb[0x10].P,__debug_mmu.tlb[0x40+0x10].L,__debug_mmu.tlb[0x40+0x10].P
printf "tlb[0x11]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x11].L,__debug_mmu.tlb[0x11].P,__debug_mmu.tlb[0x40+0x11].L,__debug_mmu.tlb[0x40+0x11].P
printf "tlb[0x12]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x12].L,__debug_mmu.tlb[0x12].P,__debug_mmu.tlb[0x40+0x12].L,__debug_mmu.tlb[0x40+0x12].P
printf "tlb[0x13]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x13].L,__debug_mmu.tlb[0x13].P,__debug_mmu.tlb[0x40+0x13].L,__debug_mmu.tlb[0x40+0x13].P
printf "tlb[0x14]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x14].L,__debug_mmu.tlb[0x14].P,__debug_mmu.tlb[0x40+0x14].L,__debug_mmu.tlb[0x40+0x14].P
printf "tlb[0x15]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x15].L,__debug_mmu.tlb[0x15].P,__debug_mmu.tlb[0x40+0x15].L,__debug_mmu.tlb[0x40+0x15].P
printf "tlb[0x16]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x16].L,__debug_mmu.tlb[0x16].P,__debug_mmu.tlb[0x40+0x16].L,__debug_mmu.tlb[0x40+0x16].P
printf "tlb[0x17]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x17].L,__debug_mmu.tlb[0x17].P,__debug_mmu.tlb[0x40+0x17].L,__debug_mmu.tlb[0x40+0x17].P
printf "tlb[0x18]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x18].L,__debug_mmu.tlb[0x18].P,__debug_mmu.tlb[0x40+0x18].L,__debug_mmu.tlb[0x40+0x18].P
printf "tlb[0x19]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x19].L,__debug_mmu.tlb[0x19].P,__debug_mmu.tlb[0x40+0x19].L,__debug_mmu.tlb[0x40+0x19].P
printf "tlb[0x1a]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1a].L,__debug_mmu.tlb[0x1a].P,__debug_mmu.tlb[0x40+0x1a].L,__debug_mmu.tlb[0x40+0x1a].P
printf "tlb[0x1b]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1b].L,__debug_mmu.tlb[0x1b].P,__debug_mmu.tlb[0x40+0x1b].L,__debug_mmu.tlb[0x40+0x1b].P
printf "tlb[0x1c]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1c].L,__debug_mmu.tlb[0x1c].P,__debug_mmu.tlb[0x40+0x1c].L,__debug_mmu.tlb[0x40+0x1c].P
printf "tlb[0x1d]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1d].L,__debug_mmu.tlb[0x1d].P,__debug_mmu.tlb[0x40+0x1d].L,__debug_mmu.tlb[0x40+0x1d].P
printf "tlb[0x1e]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1e].L,__debug_mmu.tlb[0x1e].P,__debug_mmu.tlb[0x40+0x1e].L,__debug_mmu.tlb[0x40+0x1e].P
printf "tlb[0x1f]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x1f].L,__debug_mmu.tlb[0x1f].P,__debug_mmu.tlb[0x40+0x1f].L,__debug_mmu.tlb[0x40+0x1f].P
printf "tlb[0x20]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x20].L,__debug_mmu.tlb[0x20].P,__debug_mmu.tlb[0x40+0x20].L,__debug_mmu.tlb[0x40+0x20].P
printf "tlb[0x21]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x21].L,__debug_mmu.tlb[0x21].P,__debug_mmu.tlb[0x40+0x21].L,__debug_mmu.tlb[0x40+0x21].P
printf "tlb[0x22]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x22].L,__debug_mmu.tlb[0x22].P,__debug_mmu.tlb[0x40+0x22].L,__debug_mmu.tlb[0x40+0x22].P
printf "tlb[0x23]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x23].L,__debug_mmu.tlb[0x23].P,__debug_mmu.tlb[0x40+0x23].L,__debug_mmu.tlb[0x40+0x23].P
printf "tlb[0x24]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x24].L,__debug_mmu.tlb[0x24].P,__debug_mmu.tlb[0x40+0x24].L,__debug_mmu.tlb[0x40+0x24].P
printf "tlb[0x25]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x25].L,__debug_mmu.tlb[0x25].P,__debug_mmu.tlb[0x40+0x25].L,__debug_mmu.tlb[0x40+0x25].P
printf "tlb[0x26]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x26].L,__debug_mmu.tlb[0x26].P,__debug_mmu.tlb[0x40+0x26].L,__debug_mmu.tlb[0x40+0x26].P
printf "tlb[0x27]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x27].L,__debug_mmu.tlb[0x27].P,__debug_mmu.tlb[0x40+0x27].L,__debug_mmu.tlb[0x40+0x27].P
printf "tlb[0x28]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x28].L,__debug_mmu.tlb[0x28].P,__debug_mmu.tlb[0x40+0x28].L,__debug_mmu.tlb[0x40+0x28].P
printf "tlb[0x29]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x29].L,__debug_mmu.tlb[0x29].P,__debug_mmu.tlb[0x40+0x29].L,__debug_mmu.tlb[0x40+0x29].P
printf "tlb[0x2a]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2a].L,__debug_mmu.tlb[0x2a].P,__debug_mmu.tlb[0x40+0x2a].L,__debug_mmu.tlb[0x40+0x2a].P
printf "tlb[0x2b]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2b].L,__debug_mmu.tlb[0x2b].P,__debug_mmu.tlb[0x40+0x2b].L,__debug_mmu.tlb[0x40+0x2b].P
printf "tlb[0x2c]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2c].L,__debug_mmu.tlb[0x2c].P,__debug_mmu.tlb[0x40+0x2c].L,__debug_mmu.tlb[0x40+0x2c].P
printf "tlb[0x2d]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2d].L,__debug_mmu.tlb[0x2d].P,__debug_mmu.tlb[0x40+0x2d].L,__debug_mmu.tlb[0x40+0x2d].P
printf "tlb[0x2e]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2e].L,__debug_mmu.tlb[0x2e].P,__debug_mmu.tlb[0x40+0x2e].L,__debug_mmu.tlb[0x40+0x2e].P
printf "tlb[0x2f]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x2f].L,__debug_mmu.tlb[0x2f].P,__debug_mmu.tlb[0x40+0x2f].L,__debug_mmu.tlb[0x40+0x2f].P
printf "tlb[0x30]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x30].L,__debug_mmu.tlb[0x30].P,__debug_mmu.tlb[0x40+0x30].L,__debug_mmu.tlb[0x40+0x30].P
printf "tlb[0x31]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x31].L,__debug_mmu.tlb[0x31].P,__debug_mmu.tlb[0x40+0x31].L,__debug_mmu.tlb[0x40+0x31].P
printf "tlb[0x32]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x32].L,__debug_mmu.tlb[0x32].P,__debug_mmu.tlb[0x40+0x32].L,__debug_mmu.tlb[0x40+0x32].P
printf "tlb[0x33]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x33].L,__debug_mmu.tlb[0x33].P,__debug_mmu.tlb[0x40+0x33].L,__debug_mmu.tlb[0x40+0x33].P
printf "tlb[0x34]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x34].L,__debug_mmu.tlb[0x34].P,__debug_mmu.tlb[0x40+0x34].L,__debug_mmu.tlb[0x40+0x34].P
printf "tlb[0x35]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x35].L,__debug_mmu.tlb[0x35].P,__debug_mmu.tlb[0x40+0x35].L,__debug_mmu.tlb[0x40+0x35].P
printf "tlb[0x36]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x36].L,__debug_mmu.tlb[0x36].P,__debug_mmu.tlb[0x40+0x36].L,__debug_mmu.tlb[0x40+0x36].P
printf "tlb[0x37]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x37].L,__debug_mmu.tlb[0x37].P,__debug_mmu.tlb[0x40+0x37].L,__debug_mmu.tlb[0x40+0x37].P
printf "tlb[0x38]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x38].L,__debug_mmu.tlb[0x38].P,__debug_mmu.tlb[0x40+0x38].L,__debug_mmu.tlb[0x40+0x38].P
printf "tlb[0x39]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x39].L,__debug_mmu.tlb[0x39].P,__debug_mmu.tlb[0x40+0x39].L,__debug_mmu.tlb[0x40+0x39].P
printf "tlb[0x3a]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3a].L,__debug_mmu.tlb[0x3a].P,__debug_mmu.tlb[0x40+0x3a].L,__debug_mmu.tlb[0x40+0x3a].P
printf "tlb[0x3b]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3b].L,__debug_mmu.tlb[0x3b].P,__debug_mmu.tlb[0x40+0x3b].L,__debug_mmu.tlb[0x40+0x3b].P
printf "tlb[0x3c]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3c].L,__debug_mmu.tlb[0x3c].P,__debug_mmu.tlb[0x40+0x3c].L,__debug_mmu.tlb[0x40+0x3c].P
printf "tlb[0x3d]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3d].L,__debug_mmu.tlb[0x3d].P,__debug_mmu.tlb[0x40+0x3d].L,__debug_mmu.tlb[0x40+0x3d].P
printf "tlb[0x3e]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3e].L,__debug_mmu.tlb[0x3e].P,__debug_mmu.tlb[0x40+0x3e].L,__debug_mmu.tlb[0x40+0x3e].P
printf "tlb[0x3f]: %08lx %08lx %08lx %08lx\n",__debug_mmu.tlb[0x3f].L,__debug_mmu.tlb[0x3f].P,__debug_mmu.tlb[0x40+0x3f].L,__debug_mmu.tlb[0x40+0x3f].P
end
define _pgd
p (pgd_t[0x40])*(pgd_t*)(__debug_mmu.damr[0x3].L)
end
define _ptd_i
p (pte_t[0x1000])*(pte_t*)(__debug_mmu.damr[0x4].L)
end
define _ptd_d
p (pte_t[0x1000])*(pte_t*)(__debug_mmu.damr[0x5].L)
end
Documentation/frv/gdbstub.txt 已删除 100644 → 0
浏览文件 @ c9297d28
====================
DEBUGGING FR-V LINUX
====================
The kernel contains a GDB stub that talks GDB remote protocol across a serial
port. This permits GDB to single step through the kernel, set breakpoints and
trap exceptions that happen in kernel space and interrupt execution. It also
permits the NMI interrupt button or serial port events to jump the kernel into
the debugger.
On the CPUs that have on-chip UARTs (FR400, FR403, FR405, FR555), the
GDB stub hijacks a serial port for its own purposes, and makes it
generate level 15 interrupts (NMI). The kernel proper cannot see the serial
port in question under these conditions.
On the MB93091-VDK CPU boards, the GDB stub uses UART1, which would otherwise
be /dev/ttyS1. On the MB93093-PDK, the GDB stub uses UART0. Therefore, on the
PDK there is no externally accessible serial port and the serial port to
which the touch screen is attached becomes /dev/ttyS0.
Note that the GDB stub runs entirely within CPU debug mode, and so should not
incur any exceptions or interrupts whilst it is active. In particular, note
that the clock will lose time since it is implemented in software.
==================
KERNEL PREPARATION
==================
Firstly, a debuggable kernel must be built. To do this, unpack the kernel tree
and copy the configuration that you wish to use to .config. Then reconfigure
the following things on the "Kernel Hacking" tab:
(*) "Include debugging information"
Set this to "Y". This causes all C and Assembly files to be compiled
to include debugging information.
(*) "In-kernel GDB stub"
Set this to "Y". This causes the GDB stub to be compiled into the
kernel.
(*) "Immediate activation"
Set this to "Y" if you want the GDB stub to activate as soon as possible
and wait for GDB to connect. This allows you to start tracing right from
the beginning of start_kernel() in init/main.c.
(*) "Console through GDB stub"
Set this to "Y" if you wish to be able to use "console=gdb0" on the
command line. That tells the kernel to pass system console messages to
GDB (which then prints them on its standard output). This is useful when
debugging the serial drivers that'd otherwise be used to pass console
messages to the outside world.
Then build as usual, download to the board and execute. Note that if
"Immediate activation" was selected, then the kernel will wait for GDB to
attach. If not, then the kernel will boot immediately and GDB will have to
interrupt it or wait for an exception to occur before doing anything with
the kernel.
=========================
KERNEL DEBUGGING WITH GDB
=========================
Set the serial port on the computer that's going to run GDB to the appropriate
baud rate. Assuming the board's debug port is connected to ttyS0/COM1 on the
computer doing the debugging:
stty -F /dev/ttyS0 115200
Then start GDB in the base of the kernel tree:
frv-uclinux-gdb linux [uClinux]
Or:
frv-uclinux-gdb vmlinux [MMU linux]
When the prompt appears:
GNU gdb frv-031024
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=frv-uclinux"...
(gdb)
Attach to the board like this:
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
start_kernel () at init/main.c:395
(gdb)
This should show the appropriate lines from the source too. The kernel can
then be debugged almost as if it's any other program.
===============================
INTERRUPTING THE RUNNING KERNEL
===============================
The kernel can be interrupted whilst it is running, causing a jump back to the
GDB stub and the debugger:
(*) Pressing Ctrl-C in GDB. This will cause GDB to try and interrupt the
kernel by sending an RS232 BREAK over the serial line to the GDB
stub. This will (mostly) immediately interrupt the kernel and return it
to the debugger.
(*) Pressing the NMI button on the board will also cause a jump into the
debugger.
(*) Setting a software breakpoint. This sets a break instruction at the
desired location which the GDB stub then traps the exception for.
(*) Setting a hardware breakpoint. The GDB stub is capable of using the IBAR
and DBAR registers to assist debugging.
Furthermore, the GDB stub will intercept a number of exceptions automatically
if they are caused by kernel execution. It will also intercept BUG() macro
invocation.
Documentation/frv/kernel-ABI.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=================================
INTERNAL KERNEL ABI FOR FR-V ARCH
=================================
The internal FRV kernel ABI is not quite the same as the userspace ABI. A
number of the registers are used for special purposed, and the ABI is not
consistent between modules vs core, and MMU vs no-MMU.
This partly stems from the fact that FRV CPUs do not have a separate
supervisor stack pointer, and most of them do not have any scratch
registers, thus requiring at least one general purpose register to be
clobbered in such an event. Also, within the kernel core, it is possible to
simply jump or call directly between functions using a relative offset.
This cannot be extended to modules for the displacement is likely to be too
far. Thus in modules the address of a function to call must be calculated
in a register and then used, requiring two extra instructions.
This document has the following sections:
(*) System call register ABI
(*) CPU operating modes
(*) Internal kernel-mode register ABI
(*) Internal debug-mode register ABI
(*) Virtual interrupt handling
========================
SYSTEM CALL REGISTER ABI
========================
When a system call is made, the following registers are effective:
REGISTERS CALL RETURN
=============== ======================= =======================
GR7 System call number Preserved
GR8 Syscall arg #1 Return value
GR9-GR13 Syscall arg #2-6 Preserved
===================
CPU OPERATING MODES
===================
The FR-V CPU has three basic operating modes. In order of increasing
capability:
(1) User mode.
Basic userspace running mode.
(2) Kernel mode.
Normal kernel mode. There are many additional control registers
available that may be accessed in this mode, in addition to all the
stuff available to user mode. This has two submodes:
(a) Exceptions enabled (PSR.T == 1).
Exceptions will invoke the appropriate normal kernel mode
handler. On entry to the handler, the PSR.T bit will be cleared.
(b) Exceptions disabled (PSR.T == 0).
No exceptions or interrupts may happen. Any mandatory exceptions
will cause the CPU to halt unless the CPU is told to jump into
debug mode instead.
(3) Debug mode.
No exceptions may happen in this mode. Memory protection and
management exceptions will be flagged for later consideration, but
the exception handler won't be invoked. Debugging traps such as
hardware breakpoints and watchpoints will be ignored. This mode is
entered only by debugging events obtained from the other two modes.
All kernel mode registers may be accessed, plus a few extra debugging
specific registers.
=================================
INTERNAL KERNEL-MODE REGISTER ABI
=================================
There are a number of permanent register assignments that are set up by
entry.S in the exception prologue. Note that there is a complete set of
exception prologues for each of user->kernel transition and kernel->kernel
transition. There are also user->debug and kernel->debug mode transition
prologues.
REGISTER FLAVOUR USE
=============== ======= ==============================================
GR1 Supervisor stack pointer
GR15 Current thread info pointer
GR16 GP-Rel base register for small data
GR28 Current exception frame pointer (__frame)
GR29 Current task pointer (current)
GR30 Destroyed by kernel mode entry
GR31 NOMMU Destroyed by debug mode entry
GR31 MMU Destroyed by TLB miss kernel mode entry
CCR.ICC2 Virtual interrupt disablement tracking
CCCR.CC3 Cleared by exception prologue
(atomic op emulation)
SCR0 MMU See mmu-layout.txt.
SCR1 MMU See mmu-layout.txt.
SCR2 MMU Save for EAR0 (destroyed by icache insns
in debug mode)
SCR3 MMU Save for GR31 during debug exceptions
DAMR/IAMR NOMMU Fixed memory protection layout.
DAMR/IAMR MMU See mmu-layout.txt.
Certain registers are also used or modified across function calls:
REGISTER CALL RETURN
=============== =============================== ======================
GR0 Fixed Zero -
GR2 Function call frame pointer
GR3 Special Preserved
GR3-GR7 - Clobbered
GR8 Function call arg #1 Return value
(or clobbered)
GR9 Function call arg #2 Return value MSW
(or clobbered)
GR10-GR13 Function call arg #3-#6 Clobbered
GR14 - Clobbered
GR15-GR16 Special Preserved
GR17-GR27 - Preserved
GR28-GR31 Special Only accessed
explicitly
LR Return address after CALL Clobbered
CCR/CCCR - Mostly Clobbered
================================
INTERNAL DEBUG-MODE REGISTER ABI
================================
This is the same as the kernel-mode register ABI for functions calls. The
difference is that in debug-mode there's a different stack and a different
exception frame. Almost all the global registers from kernel-mode
(including the stack pointer) may be changed.
REGISTER FLAVOUR USE
=============== ======= ==============================================
GR1 Debug stack pointer
GR16 GP-Rel base register for small data
GR31 Current debug exception frame pointer
(__debug_frame)
SCR3 MMU Saved value of GR31
Note that debug mode is able to interfere with the kernel's emulated atomic
ops, so it must be exceedingly careful not to do any that would interact
with the main kernel in this regard. Hence the debug mode code (gdbstub) is
almost completely self-contained. The only external code used is the
sprintf family of functions.
Furthermore, break.S is so complicated because single-step mode does not
switch off on entry to an exception. That means unless manually disabled,
single-stepping will blithely go on stepping into things like interrupts.
See gdbstub.txt for more information.
==========================
VIRTUAL INTERRUPT HANDLING
==========================
Because accesses to the PSR is so slow, and to disable interrupts we have
to access it twice (once to read and once to write), we don't actually
disable interrupts at all if we don't have to. What we do instead is use
the ICC2 condition code flags to note virtual disablement, such that if we
then do take an interrupt, we note the flag, really disable interrupts, set
another flag and resume execution at the point the interrupt happened.
Setting condition flags as a side effect of an arithmetic or logical
instruction is really fast. This use of the ICC2 only occurs within the
kernel - it does not affect userspace.
The flags we use are:
(*) CCR.ICC2.Z [Zero flag]
Set to virtually disable interrupts, clear when interrupts are
virtually enabled. Can be modified by logical instructions without
affecting the Carry flag.
(*) CCR.ICC2.C [Carry flag]
Clear to indicate hardware interrupts are really disabled, set otherwise.
What happens is this:
(1) Normal kernel-mode operation.
ICC2.Z is 0, ICC2.C is 1.
(2) An interrupt occurs. The exception prologue examines ICC2.Z and
determines that nothing needs doing. This is done simply with an
unlikely BEQ instruction.
(3) The interrupts are disabled (local_irq_disable)
ICC2.Z is set to 1.
(4) If interrupts were then re-enabled (local_irq_enable):
ICC2.Z would be set to 0.
A TIHI #2 instruction (trap #2 if condition HI - Z==0 && C==0) would
be used to trap if interrupts were now virtually enabled, but
physically disabled - which they're not, so the trap isn't taken. The
kernel would then be back to state (1).
(5) An interrupt occurs. The exception prologue examines ICC2.Z and
determines that the interrupt shouldn't actually have happened. It
jumps aside, and there disabled interrupts by setting PSR.PIL to 14
and then it clears ICC2.C.
(6) If interrupts were then saved and disabled again (local_irq_save):
ICC2.Z would be shifted into the save variable and masked off
(giving a 1).
ICC2.Z would then be set to 1 (thus unchanged), and ICC2.C would be
unaffected (ie: 0).
(7) If interrupts were then restored from state (6) (local_irq_restore):
ICC2.Z would be set to indicate the result of XOR'ing the saved
value (ie: 1) with 1, which gives a result of 0 - thus leaving
ICC2.Z set.
ICC2.C would remain unaffected (ie: 0).
A TIHI #2 instruction would be used to again assay the current state,
but this would do nothing as Z==1.
(8) If interrupts were then enabled (local_irq_enable):
ICC2.Z would be cleared. ICC2.C would be left unaffected. Both
flags would now be 0.
A TIHI #2 instruction again issued to assay the current state would
then trap as both Z==0 [interrupts virtually enabled] and C==0
[interrupts really disabled] would then be true.
(9) The trap #2 handler would simply enable hardware interrupts
(set PSR.PIL to 0), set ICC2.C to 1 and return.
(10) Immediately upon returning, the pending interrupt would be taken.
(11) The interrupt handler would take the path of actually processing the
interrupt (ICC2.Z is clear, BEQ fails as per step (2)).
(12) The interrupt handler would then set ICC2.C to 1 since hardware
interrupts are definitely enabled - or else the kernel wouldn't be here.
(13) On return from the interrupt handler, things would be back to state (1).
This trap (#2) is only available in kernel mode. In user mode it will
result in SIGILL.
Documentation/frv/mmu-layout.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=================================
FR451 MMU LINUX MEMORY MANAGEMENT
=================================
============
MMU HARDWARE
============
FR451 MMU Linux puts the MMU into EDAT mode whilst running. This means that it uses both the SAT
registers and the DAT TLB to perform address translation.
There are 8 IAMLR/IAMPR register pairs and 16 DAMLR/DAMPR register pairs for SAT mode.
In DAT mode, there is also a TLB organised in cache format as 64 lines x 2 ways. Each line spans a
16KB range of addresses, but can match a larger region.
===========================
MEMORY MANAGEMENT REGISTERS
===========================
Certain control registers are used by the kernel memory management routines:
REGISTERS USAGE
====================== ==================================================
IAMR0, DAMR0 Kernel image and data mappings
IAMR1, DAMR1 First-chance TLB lookup mapping
DAMR2 Page attachment for cache flush by page
DAMR3 Current PGD mapping
SCR0, DAMR4 Instruction TLB PGE/PTD cache
SCR1, DAMR5 Data TLB PGE/PTD cache
DAMR6-10 kmap_atomic() mappings
DAMR11 I/O mapping
CXNR mm_struct context ID
TTBR Page directory (PGD) pointer (physical address)
=====================
GENERAL MEMORY LAYOUT
=====================
The physical memory layout is as follows:
PHYSICAL ADDRESS CONTROLLER DEVICE
=================== ============== =======================================
00000000 - BFFFFFFF SDRAM SDRAM area
E0000000 - EFFFFFFF L-BUS CS2# VDK SLBUS/PCI window
F0000000 - F0FFFFFF L-BUS CS5# MB93493 CSC area (DAV daughter board)
F1000000 - F1FFFFFF L-BUS CS7# (CB70 CPU-card PCMCIA port I/O space)
FC000000 - FC0FFFFF L-BUS CS1# VDK MB86943 config space
FC100000 - FC1FFFFF L-BUS CS6# DM9000 NIC I/O space
FC200000 - FC2FFFFF L-BUS CS3# MB93493 CSR area (DAV daughter board)
FD000000 - FDFFFFFF L-BUS CS4# (CB70 CPU-card extra flash space)
FE000000 - FEFFFFFF Internal CPU peripherals
FF000000 - FF1FFFFF L-BUS CS0# Flash 1
FF200000 - FF3FFFFF L-BUS CS0# Flash 2
FFC00000 - FFC0001F L-BUS CS0# FPGA
The virtual memory layout is:
VIRTUAL ADDRESS PHYSICAL TRANSLATOR FLAGS SIZE OCCUPATION
================= ======== ============== ======= ======= ===================================
00004000-BFFFFFFF various TLB,xAMR1 D-N-??V 3GB Userspace
C0000000-CFFFFFFF 00000000 xAMPR0 -L-S--V 256MB Kernel image and data
D0000000-D7FFFFFF various TLB,xAMR1 D-NS??V 128MB vmalloc area
D8000000-DBFFFFFF various TLB,xAMR1 D-NS??V 64MB kmap() area
DC000000-DCFFFFFF various TLB 1MB Secondary kmap_atomic() frame
DD000000-DD27FFFF various DAMR 160KB Primary kmap_atomic() frame
DD040000 DAMR2/IAMR2 -L-S--V page Page cache flush attachment point
DD080000 DAMR3 -L-SC-V page Page Directory (PGD)
DD0C0000 DAMR4 -L-SC-V page Cached insn TLB Page Table lookup
DD100000 DAMR5 -L-SC-V page Cached data TLB Page Table lookup
DD140000 DAMR6 -L-S--V page kmap_atomic(KM_BOUNCE_READ)
DD180000 DAMR7 -L-S--V page kmap_atomic(KM_SKB_SUNRPC_DATA)
DD1C0000 DAMR8 -L-S--V page kmap_atomic(KM_SKB_DATA_SOFTIRQ)
DD200000 DAMR9 -L-S--V page kmap_atomic(KM_USER0)
DD240000 DAMR10 -L-S--V page kmap_atomic(KM_USER1)
E0000000-FFFFFFFF E0000000 DAMR11 -L-SC-V 512MB I/O region
IAMPR1 and DAMPR1 are used as an extension to the TLB.
====================
KMAP AND KMAP_ATOMIC
====================
To access pages in the page cache (which may not be directly accessible if highmem is available),
the kernel calls kmap(), does the access and then calls kunmap(); or it calls kmap_atomic(), does
the access and then calls kunmap_atomic().
kmap() creates an attachment between an arbitrary inaccessible page and a range of virtual
addresses by installing a PTE in a special page table. The kernel can then access this page as it
wills. When it's finished, the kernel calls kunmap() to clear the PTE.
kmap_atomic() does something slightly different. In the interests of speed, it chooses one of two
strategies:
(1) If possible, kmap_atomic() attaches the requested page to one of DAMPR5 through DAMPR10
register pairs; and the matching kunmap_atomic() clears the DAMPR. This makes high memory
support really fast as there's no need to flush the TLB or modify the page tables. The DAMLR
registers being used for this are preset during boot and don't change over the lifetime of the
process. There's a direct mapping between the first few kmap_atomic() types, DAMR number and
virtual address slot.
However, there are more kmap_atomic() types defined than there are DAMR registers available,
so we fall back to:
(2) kmap_atomic() uses a slot in the secondary frame (determined by the type parameter), and then
locks an entry in the TLB to translate that slot to the specified page. The number of slots is
obviously limited, and their positions are controlled such that each slot is matched by a
different line in the TLB. kunmap() ejects the entry from the TLB.
Note that the first three kmap atomic types are really just declared as placeholders. The DAMPR
registers involved are actually modified directly.
Also note that kmap() itself may sleep, kmap_atomic() may never sleep and both always succeed;
furthermore, a driver using kmap() may sleep before calling kunmap(), but may not sleep before
calling kunmap_atomic() if it had previously called kmap_atomic().
===============================
USING MORE THAN 256MB OF MEMORY
===============================
The kernel cannot access more than 256MB of memory directly. The physical layout, however, permits
up to 3GB of SDRAM (possibly 3.25GB) to be made available. By using CONFIG_HIGHMEM, the kernel can
allow userspace (by way of page tables) and itself (by way of kmap) to deal with the memory
allocation.
External devices can, of course, still DMA to and from all of the SDRAM, even if the kernel can't
see it directly. The kernel translates page references into real addresses for communicating to the
devices.
===================
PAGE TABLE TOPOLOGY
===================
The page tables are arranged in 2-layer format. There is a middle layer (PMD) that would be used in
3-layer format tables but that is folded into the top layer (PGD) and so consumes no extra memory
or processing power.
+------+ PGD PMD
| TTBR |--->+-------------------+
+------+ | | : STE |
| PGE0 | PME0 : STE |
| | : STE |
+-------------------+ Page Table
| | : STE -------------->+--------+ +0x0000
| PGE1 | PME0 : STE -----------+ | PTE0 |
| | : STE -------+ | +--------+
+-------------------+ | | | PTE63 |
| | : STE | | +-->+--------+ +0x0100
| PGE2 | PME0 : STE | | | PTE64 |
| | : STE | | +--------+
+-------------------+ | | PTE127 |
| | : STE | +------>+--------+ +0x0200
| PGE3 | PME0 : STE | | PTE128 |
| | : STE | +--------+
+-------------------+ | PTE191 |
+--------+ +0x0300
Each Page Directory (PGD) is 16KB (page size) in size and is divided into 64 entries (PGEs). Each
PGE contains one Page Mid Directory (PMD).
Each PMD is 256 bytes in size and contains a single entry (PME). Each PME holds 64 FR451 MMU
segment table entries of 4 bytes apiece. Each PME "points to" a page table. In practice, each STE
points to a subset of the page table, the first to PT+0x0000, the second to PT+0x0100, the third to
PT+0x200, and so on.
Each PGE and PME covers 64MB of the total virtual address space.
Each Page Table (PTD) is 16KB (page size) in size, and is divided into 4096 entries (PTEs). Each
entry can point to one 16KB page. In practice, each Linux page table is subdivided into 64 FR451
MMU page tables. But they are all grouped together to make management easier, in particular rmap
support is then trivial.
Grouping page tables in this fashion makes PGE caching in SCR0/SCR1 more efficient because the
coverage of the cached item is greater.
Page tables for the vmalloc area are allocated at boot time and shared between all mm_structs.
=================
USER SPACE LAYOUT
=================
For MMU capable Linux, the regions userspace code are allowed to access are kept entirely separate
from those dedicated to the kernel:
VIRTUAL ADDRESS SIZE PURPOSE
================= ===== ===================================
00000000-00003fff 4KB NULL pointer access trap
00004000-01ffffff ~32MB lower mmap space (grows up)
02000000-021fffff 2MB Stack space (grows down from top)
02200000-nnnnnnnn Executable mapping
nnnnnnnn- brk space (grows up)
-bfffffff upper mmap space (grows down)
This is so arranged so as to make best use of the 16KB page tables and the way in which PGEs/PMEs
are cached by the TLB handler. The lower mmap space is filled first, and then the upper mmap space
is filled.
===============================
GDB-STUB MMU DEBUGGING SERVICES
===============================
The gdb-stub included in this kernel provides a number of services to aid in the debugging of MMU
related kernel services:
(*) Every time the kernel stops, certain state information is dumped into __debug_mmu. This
variable is defined in arch/frv/kernel/gdb-stub.c. Note that the gdbinit file in this
directory has some useful macros for dealing with this.
(*) __debug_mmu.tlb[]
This receives the current TLB contents. This can be viewed with the _tlb GDB macro:
(gdb) _tlb
tlb[0x00]: 01000005 00718203 01000002 00718203
tlb[0x01]: 01004002 006d4201 01004005 006d4203
tlb[0x02]: 01008002 006d0201 01008006 00004200
tlb[0x03]: 0100c006 007f4202 0100c002 0064c202
tlb[0x04]: 01110005 00774201 01110002 00774201
tlb[0x05]: 01114005 00770201 01114002 00770201
tlb[0x06]: 01118002 0076c201 01118005 0076c201
...
tlb[0x3d]: 010f4002 00790200 001f4002 0054ca02
tlb[0x3e]: 010f8005 0078c201 010f8002 0078c201
tlb[0x3f]: 001fc002 0056ca01 001fc005 00538a01
(*) __debug_mmu.iamr[]
(*) __debug_mmu.damr[]
These receive the current IAMR and DAMR contents. These can be viewed with the _amr
GDB macro:
(gdb) _amr
AMRx DAMR IAMR
==== ===================== =====================
amr0 : L:c0000000 P:00000cb9 : L:c0000000 P:000004b9
amr1 : L:01070005 P:006f9203 : L:0102c005 P:006a1201
amr2 : L:d8d00000 P:00000000 : L:d8d00000 P:00000000
amr3 : L:d8d04000 P:00534c0d : L:00000000 P:00000000
amr4 : L:d8d08000 P:00554c0d : L:00000000 P:00000000
amr5 : L:d8d0c000 P:00554c0d : L:00000000 P:00000000
amr6 : L:d8d10000 P:00000000 : L:00000000 P:00000000
amr7 : L:d8d14000 P:00000000 : L:00000000 P:00000000
amr8 : L:d8d18000 P:00000000
amr9 : L:d8d1c000 P:00000000
amr10: L:d8d20000 P:00000000
amr11: L:e0000000 P:e0000ccd
(*) The current task's page directory is bound to DAMR3.
This can be viewed with the _pgd GDB macro:
(gdb) _pgd
$3 = {{pge = {{ste = {0x554001, 0x554101, 0x554201, 0x554301, 0x554401,
0x554501, 0x554601, 0x554701, 0x554801, 0x554901, 0x554a01,
0x554b01, 0x554c01, 0x554d01, 0x554e01, 0x554f01, 0x555001,
0x555101, 0x555201, 0x555301, 0x555401, 0x555501, 0x555601,
0x555701, 0x555801, 0x555901, 0x555a01, 0x555b01, 0x555c01,
0x555d01, 0x555e01, 0x555f01, 0x556001, 0x556101, 0x556201,
0x556301, 0x556401, 0x556501, 0x556601, 0x556701, 0x556801,
0x556901, 0x556a01, 0x556b01, 0x556c01, 0x556d01, 0x556e01,
0x556f01, 0x557001, 0x557101, 0x557201, 0x557301, 0x557401,
0x557501, 0x557601, 0x557701, 0x557801, 0x557901, 0x557a01,
0x557b01, 0x557c01, 0x557d01, 0x557e01, 0x557f01}}}}, {pge = {{
ste = {0x0 <repeats 64 times>}}}} <repeats 51 times>, {pge = {{ste = {
0x248001, 0x248101, 0x248201, 0x248301, 0x248401, 0x248501,
0x248601, 0x248701, 0x248801, 0x248901, 0x248a01, 0x248b01,
0x248c01, 0x248d01, 0x248e01, 0x248f01, 0x249001, 0x249101,
0x249201, 0x249301, 0x249401, 0x249501, 0x249601, 0x249701,
0x249801, 0x249901, 0x249a01, 0x249b01, 0x249c01, 0x249d01,
0x249e01, 0x249f01, 0x24a001, 0x24a101, 0x24a201, 0x24a301,
0x24a401, 0x24a501, 0x24a601, 0x24a701, 0x24a801, 0x24a901,
0x24aa01, 0x24ab01, 0x24ac01, 0x24ad01, 0x24ae01, 0x24af01,
0x24b001, 0x24b101, 0x24b201, 0x24b301, 0x24b401, 0x24b501,
0x24b601, 0x24b701, 0x24b801, 0x24b901, 0x24ba01, 0x24bb01,
0x24bc01, 0x24bd01, 0x24be01, 0x24bf01}}}}, {pge = {{ste = {
0x0 <repeats 64 times>}}}} <repeats 11 times>}
(*) The PTD last used by the instruction TLB miss handler is attached to DAMR4.
(*) The PTD last used by the data TLB miss handler is attached to DAMR5.
These can be viewed with the _ptd_i and _ptd_d GDB macros:
(gdb) _ptd_d
$5 = {{pte = 0x0} <repeats 127 times>, {pte = 0x539b01}, {
pte = 0x0} <repeats 896 times>, {pte = 0x719303}, {pte = 0x6d5303}, {
pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {
pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {pte = 0x6a1303}, {
pte = 0x0} <repeats 12 times>, {pte = 0x709303}, {pte = 0x0}, {pte = 0x0},
{pte = 0x6fd303}, {pte = 0x6f9303}, {pte = 0x6f5303}, {pte = 0x0}, {
pte = 0x6ed303}, {pte = 0x531b01}, {pte = 0x50db01}, {
pte = 0x0} <repeats 13 times>, {pte = 0x5303}, {pte = 0x7f5303}, {
pte = 0x509b01}, {pte = 0x505b01}, {pte = 0x7c9303}, {pte = 0x7b9303}, {
pte = 0x7b5303}, {pte = 0x7b1303}, {pte = 0x7ad303}, {pte = 0x0}, {
pte = 0x0}, {pte = 0x7a1303}, {pte = 0x0}, {pte = 0x795303}, {pte = 0x0}, {
pte = 0x78d303}, {pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {pte = 0x0}, {
pte = 0x0}, {pte = 0x775303}, {pte = 0x771303}, {pte = 0x76d303}, {
pte = 0x0}, {pte = 0x765303}, {pte = 0x7c5303}, {pte = 0x501b01}, {
pte = 0x4f1b01}, {pte = 0x4edb01}, {pte = 0x0}, {pte = 0x4f9b01}, {
pte = 0x4fdb01}, {pte = 0x0} <repeats 2992 times>}
Documentation/ioctl/ioctl-number.txt
浏览文件 @ f5a8eb63
......@@ -305,7 +305,6 @@ Code Seq#(hex) Include File Comments
0xA0 all linux/sdp/sdp.h Industrial Device Project
<mailto:kenji@bitgate.com>
0xA1 0 linux/vtpm_proxy.h TPM Emulator Proxy Driver
0xA2 00-0F arch/tile/include/asm/hardwall.h
0xA3 80-8F Port ACL in development:
<mailto:tlewis@mindspring.com>
0xA3 90-9F linux/dtlk.h
......
Documentation/metag/00-INDEX 已删除 100644 → 0
浏览文件 @ c9297d28
00-INDEX
- this file
kernel-ABI.txt
- Documents metag ABI details
Documentation/metag/kernel-ABI.txt 已删除 100644 → 0
浏览文件 @ c9297d28
==========================
KERNEL ABIS FOR METAG ARCH
==========================
This document describes the Linux ABIs for the metag architecture, and has the
following sections:
(*) Outline of registers
(*) Userland registers
(*) Kernel registers
(*) System call ABI
(*) Calling conventions
====================
OUTLINE OF REGISTERS
====================
The main Meta core registers are arranged in units:
UNIT Type DESCRIPTION GP EXT PRIV GLOBAL
======= ======= =============== ======= ======= ======= =======
CT Special Control unit
D0 General Data unit 0 0-7 8-15 16-31 16-31
D1 General Data unit 1 0-7 8-15 16-31 16-31
A0 General Address unit 0 0-3 4-7 8-15 8-15
A1 General Address unit 1 0-3 4-7 8-15 8-15
PC Special PC unit 0 1
PORT Special Ports
TR Special Trigger unit 0-7
TT Special Trace unit 0-5
FX General FP unit 0-15
GP registers form part of the main context.
Extended context registers (EXT) may not be present on all hardware threads and
can be context switched if support is enabled and the appropriate bits are set
in e.g. the D0.8 register to indicate what extended state to preserve.
Global registers are shared between threads and are privilege protected.
See arch/metag/include/asm/metag_regs.h for definitions relating to core
registers and the fields and bits they contain. See the TRMs for further details
about special registers.
Several special registers are preserved in the main context, these are the
interesting ones:
REG (ALIAS) PURPOSE
======================= ===============================================
CT.1 (TXMODE) Processor mode bits (particularly for DSP)
CT.2 (TXSTATUS) Condition flags and LSM_STEP (MGET/MSET step)
CT.3 (TXRPT) Branch repeat counter
PC.0 (PC) Program counter
Some of the general registers have special purposes in the ABI and therefore
have aliases:
D0 REG (ALIAS) PURPOSE D1 REG (ALIAS) PURPOSE
=============== =============== =============== =======================
D0.0 (D0Re0) 32bit result D1.0 (D1Re0) Top half of 64bit result
D0.1 (D0Ar6) Argument 6 D1.1 (D1Ar5) Argument 5
D0.2 (D0Ar4) Argument 4 D1.2 (D1Ar3) Argument 3
D0.3 (D0Ar2) Argument 2 D1.3 (D1Ar1) Argument 1
D0.4 (D0FrT) Frame temp D1.4 (D1RtP) Return pointer
D0.5 Call preserved D1.5 Call preserved
D0.6 Call preserved D1.6 Call preserved
D0.7 Call preserved D1.7 Call preserved
A0 REG (ALIAS) PURPOSE A1 REG (ALIAS) PURPOSE
=============== =============== =============== =======================
A0.0 (A0StP) Stack pointer A1.0 (A1GbP) Global base pointer
A0.1 (A0FrP) Frame pointer A1.1 (A1LbP) Local base pointer
A0.2 A1.2
A0.3 A1.3
==================
USERLAND REGISTERS
==================
All the general purpose D0, D1, A0, A1 registers are preserved when entering the
kernel (including asynchronous events such as interrupts and timer ticks) except
the following which have special purposes in the ABI:
REGISTERS WHEN STATUS PURPOSE
=============== ======= =============== ===============================
D0.8 DSP Preserved ECH, determines what extended
DSP state to preserve.
A0.0 (A0StP) ALWAYS Preserved Stack >= A0StP may be clobbered
at any time by the creation of a
signal frame.
A1.0 (A1GbP) SMP Clobbered Used as temporary for loading
kernel stack pointer and saving
core context.
A0.15 !SMP Protected Stores kernel stack pointer.
A1.15 ALWAYS Protected Stores kernel base pointer.
On UP A0.15 is used to store the kernel stack pointer for storing the userland
context. A0.15 is global between hardware threads though which means it cannot
be used on SMP for this purpose. Since no protected local registers are
available A1GbP is reserved for use as a temporary to allow a percpu stack
pointer to be loaded for storing the rest of the context.
================
KERNEL REGISTERS
================
When in the kernel the following registers have special purposes in the ABI:
REGISTERS WHEN STATUS PURPOSE
=============== ======= =============== ===============================
A0.0 (A0StP) ALWAYS Preserved Stack >= A0StP may be clobbered
at any time by the creation of
an irq signal frame.
A1.0 (A1GbP) ALWAYS Preserved Reserved (kernel base pointer).
===============
SYSTEM CALL ABI
===============
When a system call is made, the following registers are effective:
REGISTERS CALL RETURN
=============== ======================= ===============================
D0.0 (D0Re0) Return value (or -errno)
D1.0 (D1Re0) System call number Clobbered
D0.1 (D0Ar6) Syscall arg #6 Preserved
D1.1 (D1Ar5) Syscall arg #5 Preserved
D0.2 (D0Ar4) Syscall arg #4 Preserved
D1.2 (D1Ar3) Syscall arg #3 Preserved
D0.3 (D0Ar2) Syscall arg #2 Preserved
D1.3 (D1Ar1) Syscall arg #1 Preserved
Due to the limited number of argument registers and some system calls with badly
aligned 64-bit arguments, 64-bit values are always packed in consecutive
arguments, even if this is contrary to the normal calling conventions (where the
two halves would go in a matching pair of data registers).
For example fadvise64_64 usually has the signature:
long sys_fadvise64_64(i32 fd, i64 offs, i64 len, i32 advice);
But for metag fadvise64_64 is wrapped so that the 64-bit arguments are packed:
long sys_fadvise64_64_metag(i32 fd, i32 offs_lo,
i32 offs_hi, i32 len_lo,
i32 len_hi, i32 advice)
So the arguments are packed in the registers like this:
D0 REG (ALIAS) VALUE D1 REG (ALIAS) VALUE
=============== =============== =============== =======================
D0.1 (D0Ar6) advice D1.1 (D1Ar5) hi(len)
D0.2 (D0Ar4) lo(len) D1.2 (D1Ar3) hi(offs)
D0.3 (D0Ar2) lo(offs) D1.3 (D1Ar1) fd
===================
CALLING CONVENTIONS
===================
These calling conventions apply to both user and kernel code. The stack grows
from low addresses to high addresses in the metag ABI. The stack pointer (A0StP)
should always point to the next free address on the stack and should at all
times be 64-bit aligned. The following registers are effective at the point of a
call:
REGISTERS CALL RETURN
=============== ======================= ===============================
D0.0 (D0Re0) 32bit return value
D1.0 (D1Re0) Upper half of 64bit return value
D0.1 (D0Ar6) 32bit argument #6 Clobbered
D1.1 (D1Ar5) 32bit argument #5 Clobbered
D0.2 (D0Ar4) 32bit argument #4 Clobbered
D1.2 (D1Ar3) 32bit argument #3 Clobbered
D0.3 (D0Ar2) 32bit argument #2 Clobbered
D1.3 (D1Ar1) 32bit argument #1 Clobbered
D0.4 (D0FrT) Clobbered
D1.4 (D1RtP) Return pointer Clobbered
D{0-1}.{5-7} Preserved
A0.0 (A0StP) Stack pointer Preserved
A1.0 (A0GbP) Preserved
A0.1 (A0FrP) Frame pointer Preserved
A1.1 (A0LbP) Preserved
A{0-1},{2-3} Clobbered
64-bit arguments are placed in matching pairs of registers (i.e. the same
register number in both D0 and D1 units), with the least significant half in D0
and the most significant half in D1, leaving a gap where necessary. Further
arguments are stored on the stack in reverse order (earlier arguments at higher
addresses):
ADDRESS 0 1 2 3 4 5 6 7
=============== ===== ===== ===== ===== ===== ===== ===== =====
A0StP -->
A0StP-0x08 32bit argument #8 32bit argument #7
A0StP-0x10 32bit argument #10 32bit argument #9
Function prologues tend to look a bit like this:
/* If frame pointer in use, move it to frame temp register so it can be
easily pushed onto stack */
MOV D0FrT,A0FrP
/* If frame pointer in use, set it to stack pointer */
ADD A0FrP,A0StP,#0
/* Preserve D0FrT, D1RtP, D{0-1}.{5-7} on stack, incrementing A0StP */
MSETL [A0StP++],D0FrT,D0.5,D0.6,D0.7
/* Allocate some stack space for local variables */
ADD A0StP,A0StP,#0x10
At this point the stack would look like this:
ADDRESS 0 1 2 3 4 5 6 7
=============== ===== ===== ===== ===== ===== ===== ===== =====
A0StP -->
A0StP-0x08
A0StP-0x10
A0StP-0x18 Old D0.7 Old D1.7
A0StP-0x20 Old D0.6 Old D1.6
A0StP-0x28 Old D0.5 Old D1.5
A0FrP --> Old A0FrP (frame ptr) Old D1RtP (return ptr)
A0FrP-0x08 32bit argument #8 32bit argument #7
A0FrP-0x10 32bit argument #10 32bit argument #9
Function epilogues tend to differ depending on the use of a frame pointer. An
example of a frame pointer epilogue:
/* Restore D0FrT, D1RtP, D{0-1}.{5-7} from stack, incrementing A0FrP */
MGETL D0FrT,D0.5,D0.6,D0.7,[A0FrP++]
/* Restore stack pointer to where frame pointer was before increment */
SUB A0StP,A0FrP,#0x20
/* Restore frame pointer from frame temp */
MOV A0FrP,D0FrT
/* Return to caller via restored return pointer */
MOV PC,D1RtP
If the function hasn't touched the frame pointer, MGETL cannot be safely used
with A0StP as it always increments and that would expose the stack to clobbering
by interrupts (kernel) or signals (user). Therefore it's common to see the MGETL
split into separate GETL instructions:
/* Restore D0FrT, D1RtP, D{0-1}.{5-7} from stack */
GETL D0FrT,D1RtP,[A0StP+#-0x30]
GETL D0.5,D1.5,[A0StP+#-0x28]
GETL D0.6,D1.6,[A0StP+#-0x20]
GETL D0.7,D1.7,[A0StP+#-0x18]
/* Restore stack pointer */
SUB A0StP,A0StP,#0x30
/* Return to caller via restored return pointer */
MOV PC,D1RtP
Documentation/mn10300/ABI.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=========================
MN10300 FUNCTION CALL ABI
=========================
=======
GENERAL
=======
The MN10300/AM33 kernel runs in little-endian mode; big-endian mode is not
supported.
The stack grows downwards, and should always be 32-bit aligned. There are
separate stack pointer registers for userspace and the kernel.
================
ARGUMENT PASSING
================
The first two arguments (assuming up to 32-bits per argument) to a function are
passed in the D0 and D1 registers respectively; all other arguments are passed
on the stack.
If 64-bit arguments are being passed, then they are never split between
registers and the stack. If the first argument is a 64-bit value, it will be
passed in D0:D1. If the first argument is not a 64-bit value, but the second
is, the second will be passed entirely on the stack and D1 will be unused.
Arguments smaller than 32-bits are not coalesced within a register or a stack
word. For example, two byte-sized arguments will always be passed in separate
registers or word-sized stack slots.
=================
CALLING FUNCTIONS
=================
The caller must allocate twelve bytes on the stack for the callee's use before
it inserts a CALL instruction. The CALL instruction will write into the TOS
word, but won't actually modify the stack pointer; similarly, the RET
instruction reads from the TOS word of the stack, but doesn't move the stack
pointer beyond it.
Stack:
| |
| |
|---------------| SP+20
| 4th Arg |
|---------------| SP+16
| 3rd Arg |
|---------------| SP+12
| D1 Save Slot |
|---------------| SP+8
| D0 Save Slot |
|---------------| SP+4
| Return Addr |
|---------------| SP
| |
| |
The caller must leave space on the stack (hence an allocation of twelve bytes)
in which the callee may store the first two arguments.
============
RETURN VALUE
============
The return value is passed in D0 for an integer (or D0:D1 for a 64-bit value),
or A0 for a pointer.
If the return value is a value larger than 64-bits, or is a structure or an
array, then a hidden first argument will be passed to the callee by the caller:
this will point to a piece of memory large enough to hold the result of the
function. In this case, the callee will return the value in that piece of
memory, and no value will be returned in D0 or A0.
===================
REGISTER CLOBBERING
===================
The values in certain registers may be clobbered by the callee, and other
values must be saved:
Clobber: D0-D1, A0-A1, E0-E3
Save: D2-D3, A2-A3, E4-E7, SP
All other non-supervisor-only registers are clobberable (such as MDR, MCRL,
MCRH).
=================
SPECIAL REGISTERS
=================
Certain ordinary registers may carry special usage for the compiler:
A3: Frame pointer
E2: TLS pointer
==========
KERNEL ABI
==========
The kernel may use a slightly different ABI internally.
(*) E2
If CONFIG_MN10300_CURRENT_IN_E2 is defined, then the current task pointer
will be kept in the E2 register, and that register will be marked
unavailable for the compiler to use as a scratch register.
Normally the kernel uses something like:
MOV SP,An
AND 0xFFFFE000,An
MOV (An),Rm // Rm holds current
MOV (yyy,Rm) // Access current->yyy
To find the address of current; but since this option permits current to
be carried globally in an register, it can use:
MOV (yyy,E2) // Access current->yyy
instead.
===============
SYSTEM CALL ABI
===============
System calls are called with the following convention:
REGISTER ENTRY EXIT
=============== ======================= =======================
D0 Syscall number Return value
A0 1st syscall argument Saved
D1 2nd syscall argument Saved
A3 3rd syscall argument Saved
A2 4th syscall argument Saved
D3 5th syscall argument Saved
D2 6th syscall argument Saved
All other registers are saved. The layout is a consequence of the way the MOVM
instruction stores registers onto the stack.
Documentation/mn10300/compartmentalisation.txt 已删除 100644 → 0
浏览文件 @ c9297d28
=========================================
PART-SPECIFIC SOURCE COMPARTMENTALISATION
=========================================
The sources for various parts are compartmentalised at two different levels:
(1) Processor level
The "processor level" is a CPU core plus the other on-silicon
peripherals.
Processor-specific header files are divided among directories in a similar
way to the CPU level:
(*) include/asm-mn10300/proc-mn103e010/
Support for the AM33v2 CPU core.
The appropriate processor is selected by a CONFIG_MN10300_PROC_YYYY option
from the "Processor support" choice menu in the arch/mn10300/Kconfig file.
(2) Unit level
The "unit level" is a processor plus all the external peripherals
controlled by that processor.
Unit-specific header files are divided among directories in a similar way
to the CPU level; not only that, but specific sources may also be
segregated into separate directories under the arch directory:
(*) include/asm-mn10300/unit-asb2303/
(*) arch/mn10300/unit-asb2303/
Support for the ASB2303 board with an ASB2308 daughter board.
(*) include/asm-mn10300/unit-asb2305/
(*) arch/mn10300/unit-asb2305/
Support for the ASB2305 board.
The appropriate processor is selected by a CONFIG_MN10300_UNIT_ZZZZ option
from the "Unit type" choice menu in the arch/mn10300/Kconfig file.
============
COMPILE TIME
============
When the kernel is compiled, symbolic links will be made in the asm header file
directory for this arch:
include/asm-mn10300/proc => include/asm-mn10300/proc-YYYY/
include/asm-mn10300/unit => include/asm-mn10300/unit-ZZZZ/
So that the header files contained in those directories can be accessed without
lots of #ifdef-age.
The appropriate arch/mn10300/unit-ZZZZ directory will also be entered by the
compilation process; all other unit-specific directories will be ignored.
Documentation/watchdog/watchdog-parameters.txt
浏览文件 @ f5a8eb63
......@@ -55,11 +55,6 @@ wdt_time: Watchdog time in seconds. (default=30)
nowayout: Watchdog cannot be stopped once started
(default=kernel config parameter)
-------------------------------------------------
bfin_wdt:
timeout: Watchdog timeout in seconds. (1<=timeout<=((2^32)/SCLK), default=20)
nowayout: Watchdog cannot be stopped once started
(default=kernel config parameter)
-------------------------------------------------
coh901327_wdt:
margin: Watchdog margin in seconds (default 60s)
-------------------------------------------------
......
MAINTAINERS
浏览文件 @ f5a8eb63
......@@ -868,7 +868,6 @@ F: drivers/iio/*/ad*
F: drivers/iio/adc/ltc2497*
X: drivers/iio/*/adjd*
F: drivers/staging/iio/*/ad*
F: drivers/staging/iio/trigger/iio-trig-bfin-timer.c
ANDES ARCHITECTURE
M: Greentime Hu <green.hu@gmail.com>
......@@ -2643,51 +2642,6 @@ F: Documentation/filesystems/bfs.txt
F: fs/bfs/
F: include/uapi/linux/bfs_fs.h
BLACKFIN ARCHITECTURE
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
T: git git://git.code.sf.net/p/adi-linux/code
W: http://blackfin.uclinux.org
S: Orphan
F: arch/blackfin/
BLACKFIN EMAC DRIVER
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
W: http://blackfin.uclinux.org
S: Orphan
F: drivers/net/ethernet/adi/
BLACKFIN MEDIA DRIVER
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
W: http://blackfin.uclinux.org/
S: Orphan
F: drivers/media/platform/blackfin/
F: drivers/media/i2c/adv7183*
F: drivers/media/i2c/vs6624*
BLACKFIN RTC DRIVER
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
W: http://blackfin.uclinux.org
S: Orphan
F: drivers/rtc/rtc-bfin.c
BLACKFIN SDH DRIVER
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
W: http://blackfin.uclinux.org
S: Orphan
F: drivers/mmc/host/bfin_sdh.c
BLACKFIN SERIAL DRIVER
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
W: http://blackfin.uclinux.org
S: Orphan
F: drivers/tty/serial/bfin_uart.c
BLACKFIN WATCHDOG DRIVER
L: adi-buildroot-devel@lists.sourceforge.net (moderated for non-subscribers)
W: http://blackfin.uclinux.org
S: Orphan
F: drivers/watchdog/bfin_wdt.c
BLINKM RGB LED DRIVER
M: Jan-Simon Moeller <jansimon.moeller@gmx.de>
S: Maintained
......@@ -3763,16 +3717,6 @@ S: Maintained
F: Documentation/filesystems/cramfs.txt
F: fs/cramfs/
CRIS PORT
M: Mikael Starvik <starvik@axis.com>
M: Jesper Nilsson <jesper.nilsson@axis.com>
L: linux-cris-kernel@axis.com
W: http://developer.axis.com
T: git git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris.git
S: Maintained
F: arch/cris/
F: drivers/tty/serial/crisv10.*
CRYPTO API
M: Herbert Xu <herbert@gondor.apana.org.au>
M: "David S. Miller" <davem@davemloft.net>
......@@ -5821,10 +5765,6 @@ F: fs/crypto/
F: include/linux/fscrypt*.h
F: Documentation/filesystems/fscrypt.rst
FUJITSU FR-V (FRV) PORT
S: Orphan
F: arch/frv/
FUJITSU LAPTOP EXTRAS
M: Jonathan Woithe <jwoithe@just42.net>
L: platform-driver-x86@vger.kernel.org
......@@ -8359,11 +8299,6 @@ W: http://linux-test-project.github.io/
T: git git://github.com/linux-test-project/ltp.git
S: Maintained
M32R ARCHITECTURE
W: http://www.linux-m32r.org/
S: Orphan
F: arch/m32r/
M68K ARCHITECTURE
M: Geert Uytterhoeven <geert@linux-m68k.org>
L: linux-m68k@lists.linux-m68k.org
......@@ -9131,20 +9066,6 @@ F: drivers/media/platform/meson/ao-cec.c
F: Documentation/devicetree/bindings/media/meson-ao-cec.txt
T: git git://linuxtv.org/media_tree.git
METAG ARCHITECTURE
M: James Hogan <jhogan@kernel.org>
L: linux-metag@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/metag.git
S: Odd Fixes
F: arch/metag/
F: Documentation/metag/
F: Documentation/devicetree/bindings/metag/
F: Documentation/devicetree/bindings/interrupt-controller/img,*
F: drivers/clocksource/metag_generic.c
F: drivers/irqchip/irq-metag.c
F: drivers/irqchip/irq-metag-ext.c
F: drivers/tty/metag_da.c
MICROBLAZE ARCHITECTURE
M: Michal Simek <monstr@monstr.eu>
W: http://www.monstr.eu/fdt/
......@@ -10462,14 +10383,6 @@ L: platform-driver-x86@vger.kernel.org
S: Maintained
F: drivers/platform/x86/panasonic-laptop.c
PANASONIC MN10300/AM33/AM34 PORT
M: David Howells <dhowells@redhat.com>
L: linux-am33-list@redhat.com (moderated for non-subscribers)
W: ftp://ftp.redhat.com/pub/redhat/gnupro/AM33/
S: Maintained
F: Documentation/mn10300/
F: arch/mn10300/
PARALLEL LCD/KEYPAD PANEL DRIVER
M: Willy Tarreau <willy@haproxy.com>
M: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
......@@ -11072,7 +10985,7 @@ F: include/linux/pktcdvd.h
F: include/uapi/linux/pktcdvd.h
PKUNITY SOC DRIVERS
M: Guan Xuetao <gxt@mprc.pku.edu.cn>
M: Guan Xuetao <gxt@pku.edu.cn>
W: http://mprc.pku.edu.cn/~guanxuetao/linux
S: Maintained
T: git git://github.com/gxt/linux.git
......@@ -12322,13 +12235,6 @@ F: include/linux/sched.h
F: include/uapi/linux/sched.h
F: include/linux/wait.h
SCORE ARCHITECTURE
M: Chen Liqin <liqin.linux@gmail.com>
M: Lennox Wu <lennox.wu@gmail.com>
W: http://www.sunplus.com
S: Supported
F: arch/score/
SCR24X CHIP CARD INTERFACE DRIVER
M: Lubomir Rintel <lkundrak@v3.sk>
S: Supported
......@@ -13993,19 +13899,6 @@ S: Orphan
F: drivers/net/wireless/ti/
F: include/linux/wl12xx.h
TILE ARCHITECTURE
W: http://www.mellanox.com/repository/solutions/tile-scm/
S: Orphan
F: arch/tile/
F: drivers/char/tile-srom.c
F: drivers/edac/tile_edac.c
F: drivers/net/ethernet/tile/
F: drivers/rtc/rtc-tile.c
F: drivers/tty/hvc/hvc_tile.c
F: drivers/tty/serial/tilegx.c
F: drivers/usb/host/*-tilegx.c
F: include/linux/usb/tilegx.h
TIMEKEEPING, CLOCKSOURCE CORE, NTP, ALARMTIMER
M: John Stultz <john.stultz@linaro.org>
M: Thomas Gleixner <tglx@linutronix.de>
......@@ -14331,7 +14224,7 @@ F: include/linux/uwb.h
F: include/linux/uwb/
UNICORE32 ARCHITECTURE:
M: Guan Xuetao <gxt@mprc.pku.edu.cn>
M: Guan Xuetao <gxt@pku.edu.cn>
W: http://mprc.pku.edu.cn/~guanxuetao/linux
S: Maintained
T: git git://github.com/gxt/linux.git
......
Makefile
浏览文件 @ f5a8eb63
......@@ -339,14 +339,6 @@ ifeq ($(ARCH),sh64)
SRCARCH := sh
endif
# Additional ARCH settings for tile
ifeq ($(ARCH),tilepro)
SRCARCH := tile
endif
ifeq ($(ARCH),tilegx)
SRCARCH := tile
endif
KCONFIG_CONFIG ?= .config
export KCONFIG_CONFIG
......
arch/blackfin/Clear_BSD.txt 已删除 100644 → 0
浏览文件 @ c9297d28
The Clear BSD license:
Copyright (c) 2012, Analog Devices, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted (subject to the limitations in the
disclaimer below) provided that the following conditions are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.
* Neither the name of Analog Devices, Inc. nor the names of its
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
NO EXPRESS OR IMPLIED LICENSES TO ANY PARTY'S PATENT RIGHTS ARE
GRANTED BY THIS LICENSE. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT
HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
arch/blackfin/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/Kconfig.debug 已删除 100644 → 0
浏览文件 @ c9297d28
# SPDX-License-Identifier: GPL-2.0
menu "Kernel hacking"
source "lib/Kconfig.debug"
config DEBUG_VERBOSE
bool "Verbose fault messages"
default y
select PRINTK
help
When a program crashes due to an exception, or the kernel detects
an internal error, the kernel can print a not so brief message
explaining what the problem was. This debugging information is
useful to developers and kernel hackers when tracking down problems,
but mostly meaningless to other people. This is always helpful for
debugging but serves no purpose on a production system.
Most people should say N here.
config DEBUG_MMRS
tristate "Generate Blackfin MMR tree"
depends on !PINCTRL
select DEBUG_FS
help
Create a tree of Blackfin MMRs via the debugfs tree. If
you enable this, you will find all MMRs laid out in the
/sys/kernel/debug/blackfin/ directory where you can read/write
MMRs directly from userspace. This is obviously just a debug
feature.
config DEBUG_HWERR
bool "Hardware error interrupt debugging"
depends on DEBUG_KERNEL
help
When enabled, the hardware error interrupt is never disabled, and
will happen immediately when an error condition occurs. This comes
at a slight cost in code size, but is necessary if you are getting
hardware error interrupts and need to know where they are coming
from.
config EXACT_HWERR
bool "Try to make Hardware errors exact"
depends on DEBUG_HWERR
help
By default, the Blackfin hardware errors are not exact - the error
be reported multiple cycles after the error happens. This delay
can cause the wrong application, or even the kernel to receive a
signal to be killed. If you are getting HW errors in your system,
try turning this on to ensure they are at least coming from the
proper thread.
On production systems, it is safe (and a small optimization) to say N.
config DEBUG_DOUBLEFAULT
bool "Debug Double Faults"
default n
help
If an exception is caused while executing code within the exception
handler, the NMI handler, the reset vector, or in emulator mode,
a double fault occurs. On the Blackfin, this is a unrecoverable
event. You have two options:
- RESET exactly when double fault occurs. The excepting
instruction address is stored in RETX, where the next kernel
boot will print it out.
- Print debug message. This is much more error prone, although
easier to handle. It is error prone since:
- The excepting instruction is not committed.
- All writebacks from the instruction are prevented.
- The generated exception is not taken.
- The EXCAUSE field is updated with an unrecoverable event
The only way to check this is to see if EXCAUSE contains the
unrecoverable event value at every exception return. By selecting
this option, you are skipping over the faulting instruction, and
hoping things stay together enough to print out a debug message.
This does add a little kernel code, but is the only method to debug
double faults - if unsure say "Y"
choice
prompt "Double Fault Failure Method"
default DEBUG_DOUBLEFAULT_PRINT
depends on DEBUG_DOUBLEFAULT
config DEBUG_DOUBLEFAULT_PRINT
bool "Print"
config DEBUG_DOUBLEFAULT_RESET
bool "Reset"
endchoice
config DEBUG_HUNT_FOR_ZERO
bool "Catch NULL pointer reads/writes"
default y
help
Say Y here to catch reads/writes to anywhere in the memory range
from 0x0000 - 0x0FFF (the first 4k) of memory. This is useful in
catching common programming errors such as NULL pointer dereferences.
Misbehaving applications will be killed (generate a SEGV) while the
kernel will trigger a panic.
Enabling this option will take up an extra entry in CPLB table.
Otherwise, there is no extra overhead.
config DEBUG_BFIN_HWTRACE_ON
bool "Turn on Blackfin's Hardware Trace"
default y
help
All Blackfins include a Trace Unit which stores a history of the last
16 changes in program flow taken by the program sequencer. The history
allows the user to recreate the program sequencer’s recent path. This
can be handy when an application dies - we print out the execution
path of how it got to the offending instruction.
By turning this off, you may save a tiny amount of power.
choice
prompt "Omit loop Tracing"
default DEBUG_BFIN_HWTRACE_COMPRESSION_OFF
depends on DEBUG_BFIN_HWTRACE_ON
help
The trace buffer can be configured to omit recording of changes in
program flow that match either the last entry or one of the last
two entries. Omitting one of these entries from the record prevents
the trace buffer from overflowing because of any sort of loop (for, do
while, etc) in the program.
Because zero-overhead Hardware loops are not recorded in the trace buffer,
this feature can be used to prevent trace overflow from loops that
are nested four deep.
config DEBUG_BFIN_HWTRACE_COMPRESSION_OFF
bool "Trace all Loops"
help
The trace buffer records all changes of flow
config DEBUG_BFIN_HWTRACE_COMPRESSION_ONE
bool "Compress single-level loops"
help
The trace buffer does not record single loops - helpful if trace
is spinning on a while or do loop.
config DEBUG_BFIN_HWTRACE_COMPRESSION_TWO
bool "Compress two-level loops"
help
The trace buffer does not record loops two levels deep. Helpful if
the trace is spinning in a nested loop
endchoice
config DEBUG_BFIN_HWTRACE_COMPRESSION
int
depends on DEBUG_BFIN_HWTRACE_ON
default 0 if DEBUG_BFIN_HWTRACE_COMPRESSION_OFF
default 1 if DEBUG_BFIN_HWTRACE_COMPRESSION_ONE
default 2 if DEBUG_BFIN_HWTRACE_COMPRESSION_TWO
config DEBUG_BFIN_HWTRACE_EXPAND
bool "Expand Trace Buffer greater than 16 entries"
depends on DEBUG_BFIN_HWTRACE_ON
default n
help
By selecting this option, every time the 16 hardware entries in
the Blackfin's HW Trace buffer are full, the kernel will move them
into a software buffer, for dumping when there is an issue. This
has a great impact on performance, (an interrupt every 16 change of
flows) and should normally be turned off, except in those nasty
debugging sessions
config DEBUG_BFIN_HWTRACE_EXPAND_LEN
int "Size of Trace buffer (in power of 2k)"
range 0 4
depends on DEBUG_BFIN_HWTRACE_EXPAND
default 1
help
This sets the size of the software buffer that the trace information
is kept in.
0 for (2^0) 1k, or 256 entries,
1 for (2^1) 2k, or 512 entries,
2 for (2^2) 4k, or 1024 entries,
3 for (2^3) 8k, or 2048 entries,
4 for (2^4) 16k, or 4096 entries
config DEBUG_BFIN_NO_KERN_HWTRACE
bool "Turn off hwtrace in CPLB handlers"
depends on DEBUG_BFIN_HWTRACE_ON
default y
help
The CPLB error handler contains a lot of flow changes which can
quickly fill up the hardware trace buffer. When debugging crashes,
the hardware trace may indicate that the problem lies in kernel
space when in reality an application is buggy.
Say Y here to disable hardware tracing in some known "jumpy" pieces
of code so that the trace buffer will extend further back.
config EARLY_PRINTK
bool "Early printk"
default n
select SERIAL_CORE_CONSOLE
help
This option enables special console drivers which allow the kernel
to print messages very early in the bootup process.
This is useful for kernel debugging when your machine crashes very
early before the console code is initialized. After enabling this
feature, you must add "earlyprintk=serial,uart0,57600" to the
command line (bootargs). It is safe to say Y here in all cases, as
all of this lives in the init section and is thrown away after the
kernel boots completely.
config NMI_WATCHDOG
bool "Enable NMI watchdog to help debugging lockup on SMP"
default n
depends on SMP
help
If any CPU in the system does not execute the period local timer
interrupt for more than 5 seconds, then the NMI handler dumps debug
information. This information can be used to debug the lockup.
config CPLB_INFO
bool "Display the CPLB information"
help
Display the CPLB information via /proc/cplbinfo.
config ACCESS_CHECK
bool "Check the user pointer address"
default y
help
Usually the pointer transfer from user space is checked to see if its
address is in the kernel space.
Say N here to disable that check to improve the performance.
config BFIN_ISRAM_SELF_TEST
bool "isram boot self tests"
default n
help
Run some self tests of the isram driver code at boot.
config BFIN_PSEUDODBG_INSNS
bool "Support pseudo debug instructions"
default n
help
This option allows the kernel to emulate some pseudo instructions which
allow simulator test cases to be run under Linux with no changes.
Most people should say N here.
config BFIN_PM_WAKEUP_TIME_BENCH
bool "Display the total time for kernel to resume from power saving mode"
default n
help
Display the total time when kernel resumes normal from standby or
suspend to mem mode.
endmenu
arch/blackfin/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
#
# arch/blackfin/Makefile
#
# This file is subject to the terms and conditions of the GNU General Public
# License. See the file "COPYING" in the main directory of this archive
# for more details.
#
ifeq ($(CROSS_COMPILE),)
CROSS_COMPILE := bfin-uclinux-
endif
LDFLAGS_vmlinux := -X
OBJCOPYFLAGS := -O binary -R .note -R .comment -S
GZFLAGS := -9
KBUILD_CFLAGS += $(call cc-option,-mno-fdpic)
ifeq ($(CONFIG_ROMKERNEL),y)
KBUILD_CFLAGS += -mlong-calls
endif
KBUILD_AFLAGS += $(call cc-option,-mno-fdpic)
KBUILD_CFLAGS_MODULE += -mlong-calls
LDFLAGS += -m elf32bfin
KBUILD_DEFCONFIG := BF537-STAMP_defconfig
# setup the machine name and the machine dependent settings
machine-$(CONFIG_BF512) := bf518
machine-$(CONFIG_BF514) := bf518
machine-$(CONFIG_BF516) := bf518
machine-$(CONFIG_BF518) := bf518
machine-$(CONFIG_BF522) := bf527
machine-$(CONFIG_BF523) := bf527
machine-$(CONFIG_BF524) := bf527
machine-$(CONFIG_BF525) := bf527
machine-$(CONFIG_BF526) := bf527
machine-$(CONFIG_BF527) := bf527
machine-$(CONFIG_BF531) := bf533
machine-$(CONFIG_BF532) := bf533
machine-$(CONFIG_BF533) := bf533
machine-$(CONFIG_BF534) := bf537
machine-$(CONFIG_BF536) := bf537
machine-$(CONFIG_BF537) := bf537
machine-$(CONFIG_BF538) := bf538
machine-$(CONFIG_BF539) := bf538
machine-$(CONFIG_BF542) := bf548
machine-$(CONFIG_BF542M) := bf548
machine-$(CONFIG_BF544) := bf548
machine-$(CONFIG_BF544M) := bf548
machine-$(CONFIG_BF547) := bf548
machine-$(CONFIG_BF547M) := bf548
machine-$(CONFIG_BF548) := bf548
machine-$(CONFIG_BF548M) := bf548
machine-$(CONFIG_BF549) := bf548
machine-$(CONFIG_BF549M) := bf548
machine-$(CONFIG_BF561) := bf561
machine-$(CONFIG_BF609) := bf609
MACHINE := $(machine-y)
export MACHINE
cpu-$(CONFIG_BF512) := bf512
cpu-$(CONFIG_BF514) := bf514
cpu-$(CONFIG_BF516) := bf516
cpu-$(CONFIG_BF518) := bf518
cpu-$(CONFIG_BF522) := bf522
cpu-$(CONFIG_BF523) := bf523
cpu-$(CONFIG_BF524) := bf524
cpu-$(CONFIG_BF525) := bf525
cpu-$(CONFIG_BF526) := bf526
cpu-$(CONFIG_BF527) := bf527
cpu-$(CONFIG_BF531) := bf531
cpu-$(CONFIG_BF532) := bf532
cpu-$(CONFIG_BF533) := bf533
cpu-$(CONFIG_BF534) := bf534
cpu-$(CONFIG_BF536) := bf536
cpu-$(CONFIG_BF537) := bf537
cpu-$(CONFIG_BF538) := bf538
cpu-$(CONFIG_BF539) := bf539
cpu-$(CONFIG_BF542) := bf542
cpu-$(CONFIG_BF542M) := bf542m
cpu-$(CONFIG_BF544) := bf544
cpu-$(CONFIG_BF544M) := bf544m
cpu-$(CONFIG_BF547) := bf547
cpu-$(CONFIG_BF547M) := bf547m
cpu-$(CONFIG_BF548) := bf548
cpu-$(CONFIG_BF548M) := bf548m
cpu-$(CONFIG_BF549) := bf549
cpu-$(CONFIG_BF549M) := bf549m
cpu-$(CONFIG_BF561) := bf561
cpu-$(CONFIG_BF609) := bf609
rev-$(CONFIG_BF_REV_0_0) := 0.0
rev-$(CONFIG_BF_REV_0_1) := 0.1
rev-$(CONFIG_BF_REV_0_2) := 0.2
rev-$(CONFIG_BF_REV_0_3) := 0.3
rev-$(CONFIG_BF_REV_0_4) := 0.4
rev-$(CONFIG_BF_REV_0_5) := 0.5
rev-$(CONFIG_BF_REV_0_6) := 0.6
rev-$(CONFIG_BF_REV_NONE) := none
rev-$(CONFIG_BF_REV_ANY) := any
CPU_REV := $(cpu-y)-$(rev-y)
export CPU_REV
KBUILD_CFLAGS += -mcpu=$(CPU_REV)
KBUILD_AFLAGS += -mcpu=$(CPU_REV)
# - we utilize the silicon rev from the toolchain, so move it over to the checkflags
CHECKFLAGS_SILICON = $(shell echo "" | $(CPP) $(KBUILD_CFLAGS) -dD - 2>/dev/null | awk '$$2 == "__SILICON_REVISION__" { print $$3 }')
CHECKFLAGS += -D__SILICON_REVISION__=$(CHECKFLAGS_SILICON) -D__bfin__
core-y += arch/$(ARCH)/kernel/ arch/$(ARCH)/mm/ arch/$(ARCH)/mach-common/
# If we have a machine-specific directory, then include it in the build.
ifneq ($(machine-y),)
core-y += arch/$(ARCH)/mach-$(MACHINE)/
core-y += arch/$(ARCH)/mach-$(MACHINE)/boards/
endif
ifeq ($(CONFIG_MPU),y)
core-y += arch/$(ARCH)/kernel/cplb-mpu/
else
core-y += arch/$(ARCH)/kernel/cplb-nompu/
endif
drivers-$(CONFIG_OPROFILE) += arch/$(ARCH)/oprofile/
libs-y += arch/$(ARCH)/lib/
machdirs := $(patsubst %,arch/blackfin/mach-%/, $(machine-y))
KBUILD_CFLAGS += -Iarch/$(ARCH)/include/
KBUILD_CFLAGS += -Iarch/$(ARCH)/mach-$(MACHINE)/include
KBUILD_CPPFLAGS += $(patsubst %,-I$(srctree)/%include,$(machdirs))
CLEAN_FILES += \
arch/$(ARCH)/kernel/asm-offsets.s \
archclean:
$(Q)$(MAKE) $(clean)=$(boot)
INSTALL_PATH ?= /tftpboot
boot := arch/$(ARCH)/boot
BOOT_TARGETS = uImage uImage.bin uImage.bz2 uImage.gz uImage.lzma uImage.lzo uImage.xip
PHONY += $(BOOT_TARGETS) install
KBUILD_IMAGE := $(boot)/uImage
all: uImage
$(BOOT_TARGETS): vmlinux
$(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
install:
$(Q)$(MAKE) $(build)=$(boot) BOOTIMAGE=$(KBUILD_IMAGE) install
define archhelp
echo '* vmImage - Alias to selected kernel format (vmImage.gz by default)'
echo ' vmImage.bin - Uncompressed Kernel-only image for U-Boot (arch/$(ARCH)/boot/vmImage.bin)'
echo ' vmImage.bz2 - Kernel-only image for U-Boot (arch/$(ARCH)/boot/vmImage.bz2)'
echo '* vmImage.gz - Kernel-only image for U-Boot (arch/$(ARCH)/boot/vmImage.gz)'
echo ' vmImage.lzma - Kernel-only image for U-Boot (arch/$(ARCH)/boot/vmImage.lzma)'
echo ' vmImage.lzo - Kernel-only image for U-Boot (arch/$(ARCH)/boot/vmImage.lzo)'
echo ' vmImage.xip - XIP Kernel-only image for U-Boot (arch/$(ARCH)/boot/vmImage.xip)'
echo ' install - Install kernel using'
echo ' (your) ~/bin/$(INSTALLKERNEL) or'
echo ' (distribution) PATH: $(INSTALLKERNEL) or'
echo ' install to $$(INSTALL_PATH)'
endef
arch/blackfin/boot/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
#
# arch/blackfin/boot/Makefile
#
# This file is subject to the terms and conditions of the GNU General Public
# License. See the file "COPYING" in the main directory of this archive
# for more details.
#
targets := uImage uImage.bin uImage.bz2 uImage.gz uImage.lzma uImage.lzo uImage.xip
extra-y += vmlinux.bin vmlinux.bin.gz vmlinux.bin.bz2 vmlinux.bin.lzma vmlinux.bin.lzo vmlinux.bin.xip
ifeq ($(CONFIG_RAMKERNEL),y)
UIMAGE_LOADADDR = $(CONFIG_BOOT_LOAD)
else # CONFIG_ROMKERNEL must be set
UIMAGE_LOADADDR = $(CONFIG_ROM_BASE)
endif
UIMAGE_ENTRYADDR = $(shell $(NM) vmlinux | awk '$$NF == "__start" {print $$1}')
UIMAGE_NAME = '$(CPU_REV)-$(KERNELRELEASE)'
UIMAGE_OPTS-$(CONFIG_ROMKERNEL) += -x
$(obj)/vmlinux.bin: vmlinux FORCE
$(call if_changed,objcopy)
$(obj)/vmlinux.bin.gz: $(obj)/vmlinux.bin FORCE
$(call if_changed,gzip)
$(obj)/vmlinux.bin.bz2: $(obj)/vmlinux.bin FORCE
$(call if_changed,bzip2)
$(obj)/vmlinux.bin.lzma: $(obj)/vmlinux.bin FORCE
$(call if_changed,lzma)
$(obj)/vmlinux.bin.lzo: $(obj)/vmlinux.bin FORCE
$(call if_changed,lzo)
# The mkimage tool wants 64bytes prepended to the image
quiet_cmd_mk_bin_xip = BIN $@
cmd_mk_bin_xip = ( printf '%64s' | tr ' ' '\377' ; cat $< ) > $@
$(obj)/vmlinux.bin.xip: $(obj)/vmlinux.bin FORCE
$(call if_changed,mk_bin_xip)
$(obj)/uImage.bin: $(obj)/vmlinux.bin
$(call if_changed,uimage,none)
$(obj)/uImage.bz2: $(obj)/vmlinux.bin.bz2
$(call if_changed,uimage,bzip2)
$(obj)/uImage.gz: $(obj)/vmlinux.bin.gz
$(call if_changed,uimage,gzip)
$(obj)/uImage.lzma: $(obj)/vmlinux.bin.lzma
$(call if_changed,uimage,lzma)
$(obj)/uImage.lzo: $(obj)/vmlinux.bin.lzo
$(call if_changed,uimage,lzo)
$(obj)/uImage.xip: $(obj)/vmlinux.bin.xip
$(call if_changed,uimage,none)
suffix-y := bin
suffix-$(CONFIG_KERNEL_GZIP) := gz
suffix-$(CONFIG_KERNEL_BZIP2) := bz2
suffix-$(CONFIG_KERNEL_LZMA) := lzma
suffix-$(CONFIG_KERNEL_LZO) := lzo
suffix-$(CONFIG_ROMKERNEL) := xip
$(obj)/uImage: $(obj)/uImage.$(suffix-y)
@ln -sf $(notdir $<) $@
install:
sh $(srctree)/$(src)/install.sh $(KERNELRELEASE) $(BOOTIMAGE) System.map "$(INSTALL_PATH)"
arch/blackfin/boot/install.sh 已删除 100644 → 0
浏览文件 @ c9297d28
#!/bin/sh
#
# arch/blackfin/boot/install.sh
#
# This file is subject to the terms and conditions of the GNU General Public
# License. See the file "COPYING" in the main directory of this archive
# for more details.
#
# Copyright (C) 1995 by Linus Torvalds
#
# Adapted from code in arch/i386/boot/Makefile by H. Peter Anvin
# Adapted from code in arch/i386/boot/install.sh by Mike Frysinger
#
# "make install" script for Blackfin architecture
#
# Arguments:
# $1 - kernel version
# $2 - kernel image file
# $3 - kernel map file
# $4 - default install path (blank if root directory)
#
verify () {
if [ ! -f "$1" ]; then
echo "" 1>&2
echo " *** Missing file: $1" 1>&2
echo ' *** You need to run "make" before "make install".' 1>&2
echo "" 1>&2
exit 1
fi
}
# Make sure the files actually exist
verify "$2"
verify "$3"
# User may have a custom install script
if [ -x ~/bin/${INSTALLKERNEL} ]; then exec ~/bin/${INSTALLKERNEL} "$@"; fi
if which ${INSTALLKERNEL} >/dev/null 2>&1; then
exec ${INSTALLKERNEL} "$@"
fi
# Default install - same as make zlilo
back_it_up() {
local file=$1
[ -f ${file} ] || return 0
local stamp=$(stat -c %Y ${file} 2>/dev/null)
mv ${file} ${file}.${stamp:-old}
}
back_it_up $4/uImage
back_it_up $4/System.map
cat $2 > $4/uImage
cp $3 $4/System.map
arch/blackfin/configs/BF518F-EZBRD_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
CONFIG_EXPERIMENTAL=y
CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_BLK_DEV_INITRD=y
CONFIG_EXPERT=y
# CONFIG_ELF_CORE is not set
# CONFIG_FUTEX is not set
# CONFIG_SIGNALFD is not set
# CONFIG_TIMERFD is not set
# CONFIG_EVENTFD is not set
# CONFIG_AIO is not set
CONFIG_SLAB=y
CONFIG_MMAP_ALLOW_UNINITIALIZED=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_LBDAF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
CONFIG_PREEMPT_VOLUNTARY=y
CONFIG_BF518=y
CONFIG_IRQ_TIMER0=12
# CONFIG_CYCLES_CLOCKSOURCE is not set
# CONFIG_SCHEDULE_L1 is not set
# CONFIG_MEMSET_L1 is not set
# CONFIG_MEMCPY_L1 is not set
# CONFIG_SYS_BFIN_SPINLOCK_L1 is not set
CONFIG_NOMMU_INITIAL_TRIM_EXCESS=0
CONFIG_BFIN_GPTIMERS=m
CONFIG_C_CDPRIO=y
CONFIG_BANK_3=0x99B2
CONFIG_BINFMT_FLAT=y
CONFIG_BINFMT_ZFLAT=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_PNP=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_IPV6 is not set
# CONFIG_WIRELESS is not set
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_FW_LOADER is not set
CONFIG_MTD=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=m
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_BLK_DEV_RAM=y
CONFIG_NETDEVICES=y
CONFIG_NET_BFIN=y
CONFIG_BFIN_MAC=y
# CONFIG_NET_VENDOR_BROADCOM is not set
# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_INTEL is not set
# CONFIG_NET_VENDOR_MARVELL is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
# CONFIG_NET_VENDOR_SEEQ is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_WLAN is not set
# CONFIG_INPUT is not set
# CONFIG_SERIO is not set
# CONFIG_VT is not set
# CONFIG_LEGACY_PTYS is not set
CONFIG_BFIN_JTAG_COMM=m
# CONFIG_DEVKMEM is not set
CONFIG_SERIAL_BFIN=y
CONFIG_SERIAL_BFIN_CONSOLE=y
CONFIG_SERIAL_BFIN_UART0=y
# CONFIG_HW_RANDOM is not set
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_BLACKFIN_TWI=y
CONFIG_I2C_BLACKFIN_TWI_CLK_KHZ=100
CONFIG_SPI=y
CONFIG_SPI_BFIN5XX=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_SYSFS=y
# CONFIG_HWMON is not set
CONFIG_WATCHDOG=y
CONFIG_BFIN_WDT=y
# CONFIG_USB_SUPPORT is not set
CONFIG_MMC=y
CONFIG_SDH_BFIN=y
CONFIG_SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_BFIN=y
CONFIG_EXT2_FS=m
# CONFIG_DNOTIFY is not set
CONFIG_VFAT_FS=m
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_UTF8=m
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEBUG_INFO=y
# CONFIG_FTRACE is not set
CONFIG_DEBUG_MMRS=y
CONFIG_DEBUG_HWERR=y
CONFIG_EXACT_HWERR=y
CONFIG_DEBUG_DOUBLEFAULT=y
CONFIG_DEBUG_BFIN_HWTRACE_COMPRESSION_ONE=y
CONFIG_EARLY_PRINTK=y
CONFIG_CPLB_INFO=y
CONFIG_BFIN_PSEUDODBG_INSNS=y
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRC_CCITT=m
arch/blackfin/configs/BF526-EZBRD_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
CONFIG_EXPERIMENTAL=y
CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_BLK_DEV_INITRD=y
CONFIG_EXPERT=y
# CONFIG_ELF_CORE is not set
# CONFIG_FUTEX is not set
# CONFIG_SIGNALFD is not set
# CONFIG_TIMERFD is not set
# CONFIG_EVENTFD is not set
# CONFIG_AIO is not set
CONFIG_SLAB=y
CONFIG_MMAP_ALLOW_UNINITIALIZED=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_LBDAF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
CONFIG_PREEMPT_VOLUNTARY=y
CONFIG_BF526=y
CONFIG_IRQ_TIMER0=12
CONFIG_BFIN526_EZBRD=y
CONFIG_IRQ_USB_INT0=11
CONFIG_IRQ_USB_INT1=11
CONFIG_IRQ_USB_INT2=11
CONFIG_IRQ_USB_DMA=11
# CONFIG_CYCLES_CLOCKSOURCE is not set
# CONFIG_SCHEDULE_L1 is not set
# CONFIG_MEMSET_L1 is not set
# CONFIG_MEMCPY_L1 is not set
# CONFIG_SYS_BFIN_SPINLOCK_L1 is not set
CONFIG_NOMMU_INITIAL_TRIM_EXCESS=0
CONFIG_BFIN_GPTIMERS=m
CONFIG_C_CDPRIO=y
CONFIG_BANK_3=0x99B2
CONFIG_BINFMT_FLAT=y
CONFIG_BINFMT_ZFLAT=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_PNP=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_IPV6 is not set
# CONFIG_WIRELESS is not set
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_FW_LOADER is not set
CONFIG_MTD=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_CFI=y
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=m
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_M25P80=y
CONFIG_MTD_NAND=m
CONFIG_MTD_SPI_NOR=y
CONFIG_BLK_DEV_RAM=y
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=m
# CONFIG_SCSI_LOWLEVEL is not set
CONFIG_NETDEVICES=y
CONFIG_NET_BFIN=y
CONFIG_BFIN_MAC=y
# CONFIG_NET_VENDOR_BROADCOM is not set
# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_INTEL is not set
# CONFIG_NET_VENDOR_MARVELL is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
# CONFIG_NET_VENDOR_SEEQ is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_WLAN is not set
CONFIG_INPUT_FF_MEMLESS=m
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
CONFIG_INPUT_MISC=y
# CONFIG_SERIO is not set
# CONFIG_LEGACY_PTYS is not set
CONFIG_BFIN_JTAG_COMM=m
# CONFIG_DEVKMEM is not set
CONFIG_SERIAL_BFIN=y
CONFIG_SERIAL_BFIN_CONSOLE=y
CONFIG_SERIAL_BFIN_UART1=y
# CONFIG_HW_RANDOM is not set
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_BLACKFIN_TWI=y
CONFIG_I2C_BLACKFIN_TWI_CLK_KHZ=100
CONFIG_SPI=y
CONFIG_SPI_BFIN5XX=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_SYSFS=y
CONFIG_WATCHDOG=y
CONFIG_BFIN_WDT=y
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_EZKEY=y
CONFIG_HID_GYRATION=y
CONFIG_HID_LOGITECH=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_PANTHERLORD=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
CONFIG_USB=y
# CONFIG_USB_DEVICE_CLASS is not set
CONFIG_USB_OTG_BLACKLIST_HUB=y
CONFIG_USB_MON=y
CONFIG_USB_STORAGE=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_BFIN=y
CONFIG_EXT2_FS=m
# CONFIG_DNOTIFY is not set
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_VFAT_FS=m
CONFIG_JFFS2_FS=m
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_UTF8=m
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEBUG_INFO=y
# CONFIG_FTRACE is not set
CONFIG_DEBUG_MMRS=y
CONFIG_DEBUG_HWERR=y
CONFIG_EXACT_HWERR=y
CONFIG_DEBUG_DOUBLEFAULT=y
CONFIG_DEBUG_BFIN_HWTRACE_COMPRESSION_ONE=y
CONFIG_EARLY_PRINTK=y
CONFIG_CPLB_INFO=y
CONFIG_BFIN_PSEUDODBG_INSNS=y
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRC_CCITT=m
arch/blackfin/configs/BF527-EZKIT_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF533-EZKIT_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF533-STAMP_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF537-STAMP_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF538-EZKIT_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF548-EZKIT_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF561-ACVILON_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF561-EZKIT_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BF609-EZKIT_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/BlackStamp_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/CM-BF527_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/CM-BF533_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/CM-BF537E_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/CM-BF537U_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/CM-BF548_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/CM-BF561_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/DNP5370_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/H8606_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/IP0X_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/PNAV-10_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/SRV1_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/TCM-BF518_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/configs/TCM-BF537_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/Kbuild 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/asm-offsets.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/atomic.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/barrier.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin-global.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin-lq035q1.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin5xx_spi.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_can.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_pfmon.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_ppi.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_sdh.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_serial.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_simple_timer.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_sport.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_sport3.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_twi.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfin_watchdog.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bfrom.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bitops.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/blackfin.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/bug.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cache.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cacheflush.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cdef_LPBlackfin.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/checksum.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/clocks.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cmpxchg.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/context.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cplb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cplbinit.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/cpu.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/def_LPBlackfin.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/delay.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/dma-mapping.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/dpmc.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/early_printk.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/elf.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/entry.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/exec.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/fixed_code.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/flat.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/ftrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/gptimers.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/hardirq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/io.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/ipipe.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/ipipe_base.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/irq_handler.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/irqflags.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/kgdb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/l1layout.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/linkage.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/mem_init.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/mem_map.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/mmu.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/mmu_context.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/module.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/nand.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/nmi.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/page.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/page_offset.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/pci.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/pda.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/perf_event.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/pgtable.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/pm.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/portmux.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/processor.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/ptrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/reboot.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/rwlock.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/scb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/sections.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/segment.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/smp.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/spinlock.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/spinlock_types.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/string.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/switch_to.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/syscall.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/thread_info.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/time.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/timex.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/tlb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/tlbflush.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/trace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/traps.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/uaccess.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/unistd.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/asm/vga.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-a.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-b.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-c.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-d.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-e.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-f.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-g.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-h.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-i.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/mach-common/ports-j.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/Kbuild 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/bfin_sport.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/byteorder.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/cachectl.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/fcntl.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/fixed_code.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/ioctls.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/poll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/posix_types.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/ptrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/sigcontext.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/siginfo.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/signal.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/stat.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/swab.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/include/uapi/asm/unistd.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/.gitignore 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/asm-offsets.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/bfin_dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/bfin_gpio.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/bfin_ksyms.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplb-mpu/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplb-mpu/cplbinit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplb-mpu/cplbmgr.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplb-nompu/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplb-nompu/cplbinit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplb-nompu/cplbmgr.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/cplbinfo.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/debug-mmrs.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/dma-mapping.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/dumpstack.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/early_printk.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/entry.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/exception.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/fixed_code.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/flat.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/ftrace-entry.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/ftrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/gptimers.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/ipipe.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/irqchip.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/kgdb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/kgdb_test.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/module.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/nmi.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/perf_event.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/process.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/pseudodbg.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/ptrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/reboot.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/setup.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/shadow_console.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/signal.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/stacktrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/sys_bfin.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/time-ts.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/time.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/trace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/traps.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/kernel/vmlinux.lds.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/ashldi3.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/ashrdi3.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/divsi3.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/gcclib.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/ins.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/lshrdi3.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/memchr.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/memcmp.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/memcpy.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/memmove.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/memset.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/modsi3.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/muldi3.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/outs.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/smulsi3_highpart.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/strcmp.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/strcpy.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/strncmp.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/strncpy.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/udivsi3.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/umodsi3.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/lib/umulsi3_highpart.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/boards/ezbrd.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/boards/tcm-bf518.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/include/mach/bf518.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf518/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/ad7160eval.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/cm_bf527.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/ezbrd.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/ezkit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/boards/tll6527m.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/include/mach/bf527.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf527/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/H8606.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/blackstamp.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/cm_bf533.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/ezkit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/ip0x.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/boards/stamp.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/include/mach/bf533.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf533/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/cm_bf537e.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/cm_bf537u.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/dnp5370.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/minotaur.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/pnav10.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/stamp.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/boards/tcm_bf537.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/include/mach/bf537.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf537/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/boards/ezkit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/ext-gpio.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/include/mach/bf538.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf538/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/boards/cm_bf548.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/boards/ezkit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/include/mach/bf548.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf548/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/atomic.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/boards/acvilon.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/boards/cm_bf561.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/boards/ezkit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/boards/tepla.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/coreb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/hotplug.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/include/mach/bf561.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/include/mach/smp.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/secondary.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf561/smp.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/boards/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/boards/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/boards/ezkit.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/clock.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/dpm.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/include/mach/bf609.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/include/mach/pll.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/include/mach/pm.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/pm.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-bf609/scb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/arch_checks.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/cache-c.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/cache.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/clock.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/clocks-init.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/dpmc.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/dpmc_modes.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/entry.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/head.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/interrupt.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/ints-priority.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/pm.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/scb-init.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mach-common/smp.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mm/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mm/blackfin_sram.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mm/init.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mm/isram-driver.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mm/maccess.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/mm/sram-alloc.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/oprofile/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/blackfin/oprofile/bfin_oprofile.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/Kconfig.debug 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/README.mm 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/axisflashmap.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/eeprom.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/gpio.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/i2c.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/i2c.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/drivers/sync_serial.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/crisksyms.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/debugport.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/entry.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/fasttimer.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/head.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/io_interface_mux.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/irq.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/kgdb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/process.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/ptrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/setup.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/shadows.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/signal.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/time.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/kernel/traps.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/checksum.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/checksumcopy.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/csumcpfruser.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/dram_init.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/hw_settings.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/memset.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/string.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/lib/usercopy.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/mm/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/mm/fault.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/mm/init.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/mm/tlb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v10/output_arch.ld 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/axisflashmap.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/cryptocop.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/iop_fw_load.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/mach-a3/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/mach-fs/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/pci/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/pci/bios.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/drivers/sync_serial.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/cache.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/cacheflush.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/crisksyms.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/debugport.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/entry.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/fasttimer.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/head.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/irq.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/kgdb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/kgdb_asm.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/process.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/ptrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/setup.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/signal.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/time.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/kernel/traps.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/checksum.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/checksumcopy.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/csumcpfruser.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/delay.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/memset.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/strcmp.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/string.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/lib/usercopy.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/arbiter.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/dram_init.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/hw_settings.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-a3/pinmux.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/arbiter.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/dma.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/dram_init.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/hw_settings.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mach-fs/pinmux.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mm/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mm/init.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mm/intmem.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mm/l2cache.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mm/mmu.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/mm/tlb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/arch-v32/output_arch.ld 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/.gitignore 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/README 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/decompress_v10.lds 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/decompress_v32.lds 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/head_v10.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/head_v32.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/compressed/misc.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/dts/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/dts/artpec3.dtsi 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/dts/dev88.dts 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/dts/etraxfs.dtsi 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/dts/p1343.dts 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/head_v10.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/head_v32.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/kimagerescue.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/rescue_v10.lds 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/rescue_v32.lds 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/rescue/testrescue.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/boot/tools/build.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/configs/artpec_3_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/configs/dev88_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/configs/etrax-100lx_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/configs/etrax-100lx_v2_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/configs/etraxfs_defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/bitops.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/bug.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/cache.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/checksum.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/delay.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/io.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/irqflags.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/memmap.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/mmu.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/offset.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/page.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/pgtable.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/processor.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/swab.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/system.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/thread_info.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/timex.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/tlb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/uaccess.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v10/arch/unistd.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/bitops.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/bug.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/cache.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/checksum.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/cryptocop.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/delay.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/hwregs/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/intmem.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/irqflags.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/memmap.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/mmu.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/offset.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/page.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/pgtable.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/processor.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/swab.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/system.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/thread_info.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/timex.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/tlb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/uaccess.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/arch/unistd.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/mach-a3/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/arch-v32/mach-fs/mach/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/Kbuild 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/asm-offsets.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/axisflashmap.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/bitops.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/bug.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/bugs.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/cache.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/cacheflush.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/checksum.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/delay.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/eshlibld.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/etraxi2c.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/fasttimer.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/fb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/ftrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/hw_irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/io.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/irqflags.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/mmu.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/mmu_context.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/page.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/pci.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/pgalloc.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/pgtable.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/processor.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/ptrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/segment.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/serial.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/shmparam.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/signal.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/stacktrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/string.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/swab.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/switch_to.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/termios.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/thread_info.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/timex.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/tlb.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/tlbflush.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/uaccess.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/ucontext.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/unaligned.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/unistd.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/asm/user.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/arch-v10/arch/svinto.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/arch-v10/arch/user.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/arch-v32/arch/user.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/Kbuild 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/byteorder.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/elf.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/elf_v10.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/elf_v32.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/ethernet.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/etraxgpio.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/ioctls.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/param.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/posix_types.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/ptrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/ptrace_v10.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/ptrace_v32.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/rs485.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/setup.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/sigcontext.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/signal.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/stat.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/swab.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/sync_serial.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/termbits.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/termios.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/include/uapi/asm/unistd.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/asm-offsets.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/crisksyms.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/irq.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/module.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/process.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/profile.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/ptrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/setup.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/stacktrace.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/sys_cris.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/time.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/traps.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/kernel/vmlinux.lds.S 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/mm/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/mm/fault.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/mm/init.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/mm/ioremap.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/cris/mm/tlb.c 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/Kconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/Kconfig.debug 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/boot/Makefile 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/defconfig 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/Kbuild 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/asm-offsets.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/atomic.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/atomic_defs.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/ax88796.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/barrier.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/bitops.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/bug.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/bugs.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/busctl-regs.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/cache.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/cacheflush.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/checksum.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/cmpxchg.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/cpu-irqs.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/current.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/delay.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/div64.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/dm9000.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/dma-mapping.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/dma.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/elf.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/emergency-restart.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/fpu.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/ftrace.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/futex.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/gdb-stub.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/gpio-regs.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/hardirq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/highmem.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
arch/frv/include/asm/hw_irq.h 已删除 100644 → 0
浏览文件 @ c9297d28
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或