diff options
Diffstat (limited to 'Documentation/arm')
-rw-r--r-- | Documentation/arm/IXP2000 | 2 | ||||
-rw-r--r-- | Documentation/arm/IXP4xx | 14 | ||||
-rw-r--r-- | Documentation/arm/README | 4 | ||||
-rw-r--r-- | Documentation/arm/SA1100/Assabet | 5 | ||||
-rw-r--r-- | Documentation/arm/SA1100/Brutus | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/FreeBird | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/GraphicsClient | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/GraphicsMaster | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/Itsy | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/PLEB | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/Victor | 2 | ||||
-rw-r--r-- | Documentation/arm/SA1100/nanoEngine | 2 | ||||
-rw-r--r-- | Documentation/arm/memory.txt | 8 | ||||
-rw-r--r-- | Documentation/arm/tcm.txt | 30 |
14 files changed, 45 insertions, 34 deletions
diff --git a/Documentation/arm/IXP2000 b/Documentation/arm/IXP2000 index e0148b6b2c40..68d21d92a30b 100644 --- a/Documentation/arm/IXP2000 +++ b/Documentation/arm/IXP2000 | |||
@@ -14,7 +14,7 @@ telecom systems. In addition to an XScale core, it contains up to 8 | |||
14 | interfaces (UTOPIA, SPI, etc), a PCI host bridge, one serial port, | 14 | interfaces (UTOPIA, SPI, etc), a PCI host bridge, one serial port, |
15 | flash interface, and some other odds and ends. For more information, see: | 15 | flash interface, and some other odds and ends. For more information, see: |
16 | 16 | ||
17 | http://developer.intel.com/design/network/products/npfamily/ixp2xxx.htm | 17 | http://developer.intel.com |
18 | 18 | ||
19 | 2. Linux Support | 19 | 2. Linux Support |
20 | 20 | ||
diff --git a/Documentation/arm/IXP4xx b/Documentation/arm/IXP4xx index 72fbcc4fcab0..133c5fa6c7a1 100644 --- a/Documentation/arm/IXP4xx +++ b/Documentation/arm/IXP4xx | |||
@@ -45,7 +45,7 @@ require the use of Intel's propietary CSR softare: | |||
45 | If you need to use any of the above, you need to download Intel's | 45 | If you need to use any of the above, you need to download Intel's |
46 | software from: | 46 | software from: |
47 | 47 | ||
48 | http://developer.intel.com/design/network/products/npfamily/ixp425swr1.htm | 48 | http://developer.intel.com/design/network/products/npfamily/ixp425.htm |
49 | 49 | ||
50 | DO NOT POST QUESTIONS TO THE LINUX MAILING LISTS REGARDING THE PROPIETARY | 50 | DO NOT POST QUESTIONS TO THE LINUX MAILING LISTS REGARDING THE PROPIETARY |
51 | SOFTWARE. | 51 | SOFTWARE. |
@@ -53,7 +53,7 @@ SOFTWARE. | |||
53 | There are several websites that provide directions/pointers on using | 53 | There are several websites that provide directions/pointers on using |
54 | Intel's software: | 54 | Intel's software: |
55 | 55 | ||
56 | http://ixp4xx-osdg.sourceforge.net/ | 56 | http://sourceforge.net/projects/ixp4xx-osdg/ |
57 | Open Source Developer's Guide for using uClinux and the Intel libraries | 57 | Open Source Developer's Guide for using uClinux and the Intel libraries |
58 | 58 | ||
59 | http://gatewaymaker.sourceforge.net/ | 59 | http://gatewaymaker.sourceforge.net/ |
@@ -112,21 +112,21 @@ http://www.adiengineering.com/productsCoyote.html | |||
112 | Finally, there is an IDE port hanging off the expansion bus. | 112 | Finally, there is an IDE port hanging off the expansion bus. |
113 | 113 | ||
114 | Gateworks Avila Network Platform | 114 | Gateworks Avila Network Platform |
115 | http://www.gateworks.com/avila_sbc.htm | 115 | http://www.gateworks.com/support/overview.php |
116 | 116 | ||
117 | The Avila platform is basically and IXDP425 with the 4 PCI slots | 117 | The Avila platform is basically and IXDP425 with the 4 PCI slots |
118 | replaced with mini-PCI slots and a CF IDE interface hanging off | 118 | replaced with mini-PCI slots and a CF IDE interface hanging off |
119 | the expansion bus. | 119 | the expansion bus. |
120 | 120 | ||
121 | Intel IXDP425 Development Platform | 121 | Intel IXDP425 Development Platform |
122 | http://developer.intel.com/design/network/products/npfamily/ixdp425.htm | 122 | http://www.intel.com/design/network/products/npfamily/ixdpg425.htm |
123 | 123 | ||
124 | This is Intel's standard reference platform for the IXDP425 and is | 124 | This is Intel's standard reference platform for the IXDP425 and is |
125 | also known as the Richfield board. It contains 4 PCI slots, 16MB | 125 | also known as the Richfield board. It contains 4 PCI slots, 16MB |
126 | of flash, two 10/100 ports and one ADSL port. | 126 | of flash, two 10/100 ports and one ADSL port. |
127 | 127 | ||
128 | Intel IXDP465 Development Platform | 128 | Intel IXDP465 Development Platform |
129 | http://developer.intel.com/design/network/products/npfamily/ixdp465.htm | 129 | http://www.intel.com/design/network/products/npfamily/ixdp465.htm |
130 | 130 | ||
131 | This is basically an IXDP425 with an IXP465 and 32M of flash instead | 131 | This is basically an IXDP425 with an IXP465 and 32M of flash instead |
132 | of just 16. | 132 | of just 16. |
@@ -141,15 +141,13 @@ Intel IXDPG425 Development Platform | |||
141 | a pivot_root to NFS. | 141 | a pivot_root to NFS. |
142 | 142 | ||
143 | Motorola PrPMC1100 Processor Mezanine Card | 143 | Motorola PrPMC1100 Processor Mezanine Card |
144 | http://www.fountainsys.com/datasheet/PrPMC1100.pdf | 144 | http://www.fountainsys.com |
145 | 145 | ||
146 | The PrPMC1100 is based on the IXCP1100 and is meant to plug into | 146 | The PrPMC1100 is based on the IXCP1100 and is meant to plug into |
147 | and IXP2400/2800 system to act as the system controller. It simply | 147 | and IXP2400/2800 system to act as the system controller. It simply |
148 | contains a CPU and 16MB of flash on the board and needs to be | 148 | contains a CPU and 16MB of flash on the board and needs to be |
149 | plugged into a carrier board to function. Currently Linux only | 149 | plugged into a carrier board to function. Currently Linux only |
150 | supports the Motorola PrPMC carrier board for this platform. | 150 | supports the Motorola PrPMC carrier board for this platform. |
151 | See https://mcg.motorola.com/us/ds/pdf/ds0144.pdf for info | ||
152 | on the carrier board. | ||
153 | 151 | ||
154 | 5. TODO LIST | 152 | 5. TODO LIST |
155 | 153 | ||
diff --git a/Documentation/arm/README b/Documentation/arm/README index d98783fbe0c7..aea34095cdcf 100644 --- a/Documentation/arm/README +++ b/Documentation/arm/README | |||
@@ -41,12 +41,12 @@ Bug reports etc | |||
41 | --------------- | 41 | --------------- |
42 | 42 | ||
43 | Please send patches to the patch system. For more information, see | 43 | Please send patches to the patch system. For more information, see |
44 | http://www.arm.linux.org.uk/patches/info.html Always include some | 44 | http://www.arm.linux.org.uk/developer/patches/info.php Always include some |
45 | explanation as to what the patch does and why it is needed. | 45 | explanation as to what the patch does and why it is needed. |
46 | 46 | ||
47 | Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk, | 47 | Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk, |
48 | or submitted through the web form at | 48 | or submitted through the web form at |
49 | http://www.arm.linux.org.uk/forms/solution.shtml | 49 | http://www.arm.linux.org.uk/developer/ |
50 | 50 | ||
51 | When sending bug reports, please ensure that they contain all relevant | 51 | When sending bug reports, please ensure that they contain all relevant |
52 | information, eg. the kernel messages that were printed before/during | 52 | information, eg. the kernel messages that were printed before/during |
diff --git a/Documentation/arm/SA1100/Assabet b/Documentation/arm/SA1100/Assabet index 91f7ce7ba426..08b885d35674 100644 --- a/Documentation/arm/SA1100/Assabet +++ b/Documentation/arm/SA1100/Assabet | |||
@@ -2,8 +2,7 @@ The Intel Assabet (SA-1110 evaluation) board | |||
2 | ============================================ | 2 | ============================================ |
3 | 3 | ||
4 | Please see: | 4 | Please see: |
5 | http://developer.intel.com/design/strong/quicklist/eval-plat/sa-1110.htm | 5 | http://developer.intel.com |
6 | http://developer.intel.com/design/strong/guides/278278.htm | ||
7 | 6 | ||
8 | Also some notes from John G Dorsey <jd5q@andrew.cmu.edu>: | 7 | Also some notes from John G Dorsey <jd5q@andrew.cmu.edu>: |
9 | http://www.cs.cmu.edu/~wearable/software/assabet.html | 8 | http://www.cs.cmu.edu/~wearable/software/assabet.html |
@@ -64,7 +63,7 @@ Initial RedBoot configuration | |||
64 | ----------------------------- | 63 | ----------------------------- |
65 | 64 | ||
66 | The commands used here are explained in The RedBoot User's Guide available | 65 | The commands used here are explained in The RedBoot User's Guide available |
67 | on-line at http://sources.redhat.com/ecos/docs-latest/redboot/redboot.html. | 66 | on-line at http://sources.redhat.com/ecos/docs.html. |
68 | Please refer to it for explanations. | 67 | Please refer to it for explanations. |
69 | 68 | ||
70 | If you have a CF network card (my Assabet kit contained a CF+ LP-E from | 69 | If you have a CF network card (my Assabet kit contained a CF+ LP-E from |
diff --git a/Documentation/arm/SA1100/Brutus b/Documentation/arm/SA1100/Brutus index b1cfd405dccc..6a3aa95e9bfd 100644 --- a/Documentation/arm/SA1100/Brutus +++ b/Documentation/arm/SA1100/Brutus | |||
@@ -1,7 +1,7 @@ | |||
1 | Brutus is an evaluation platform for the SA1100 manufactured by Intel. | 1 | Brutus is an evaluation platform for the SA1100 manufactured by Intel. |
2 | For more details, see: | 2 | For more details, see: |
3 | 3 | ||
4 | http://developer.intel.com/design/strong/applnots/sa1100lx/getstart.htm | 4 | http://developer.intel.com |
5 | 5 | ||
6 | To compile for Brutus, you must issue the following commands: | 6 | To compile for Brutus, you must issue the following commands: |
7 | 7 | ||
diff --git a/Documentation/arm/SA1100/FreeBird b/Documentation/arm/SA1100/FreeBird index eda28b3232e7..fb23b770aaf4 100644 --- a/Documentation/arm/SA1100/FreeBird +++ b/Documentation/arm/SA1100/FreeBird | |||
@@ -1,5 +1,5 @@ | |||
1 | Freebird-1.1 is produced by Legned(C) ,Inc. | 1 | Freebird-1.1 is produced by Legned(C) ,Inc. |
2 | (http://www.legend.com.cn) | 2 | http://web.archive.org/web/*/http://www.legend.com.cn |
3 | and software/linux mainatined by Coventive(C),Inc. | 3 | and software/linux mainatined by Coventive(C),Inc. |
4 | (http://www.coventive.com) | 4 | (http://www.coventive.com) |
5 | 5 | ||
diff --git a/Documentation/arm/SA1100/GraphicsClient b/Documentation/arm/SA1100/GraphicsClient index 6c9c4f5a36e1..867bb35943af 100644 --- a/Documentation/arm/SA1100/GraphicsClient +++ b/Documentation/arm/SA1100/GraphicsClient | |||
@@ -71,7 +71,7 @@ Supported peripherals: | |||
71 | - serial ports (ttyS[0-2]) | 71 | - serial ports (ttyS[0-2]) |
72 | - ttyS0 is default for serial console | 72 | - ttyS0 is default for serial console |
73 | - Smart I/O (ADC, keypad, digital inputs, etc) | 73 | - Smart I/O (ADC, keypad, digital inputs, etc) |
74 | See http://www.applieddata.com/developers/linux for IOCTL documentation | 74 | See http://www.eurotech-inc.com/linux-sbc.asp for IOCTL documentation |
75 | and example user space code. ps/2 keybd is multiplexed through this driver | 75 | and example user space code. ps/2 keybd is multiplexed through this driver |
76 | 76 | ||
77 | To do: | 77 | To do: |
diff --git a/Documentation/arm/SA1100/GraphicsMaster b/Documentation/arm/SA1100/GraphicsMaster index ee7c6595f23f..9145088a0ba2 100644 --- a/Documentation/arm/SA1100/GraphicsMaster +++ b/Documentation/arm/SA1100/GraphicsMaster | |||
@@ -28,7 +28,7 @@ Supported peripherals: | |||
28 | - serial ports (ttyS[0-2]) | 28 | - serial ports (ttyS[0-2]) |
29 | - ttyS0 is default for serial console | 29 | - ttyS0 is default for serial console |
30 | - Smart I/O (ADC, keypad, digital inputs, etc) | 30 | - Smart I/O (ADC, keypad, digital inputs, etc) |
31 | See http://www.applieddata.com/developers/linux for IOCTL documentation | 31 | See http://www.eurotech-inc.com/linux-sbc.asp for IOCTL documentation |
32 | and example user space code. ps/2 keybd is multiplexed through this driver | 32 | and example user space code. ps/2 keybd is multiplexed through this driver |
33 | 33 | ||
34 | To do: | 34 | To do: |
diff --git a/Documentation/arm/SA1100/Itsy b/Documentation/arm/SA1100/Itsy index 3b594534323b..44b94997fa0d 100644 --- a/Documentation/arm/SA1100/Itsy +++ b/Documentation/arm/SA1100/Itsy | |||
@@ -4,7 +4,7 @@ research projects at Compaq that are related to pocket computing. | |||
4 | 4 | ||
5 | For more information, see: | 5 | For more information, see: |
6 | 6 | ||
7 | http://www.research.digital.com/wrl/itsy/index.html | 7 | http://www.hpl.hp.com/downloads/crl/itsy/ |
8 | 8 | ||
9 | Notes on initial 2.4 Itsy support (8/27/2000) : | 9 | Notes on initial 2.4 Itsy support (8/27/2000) : |
10 | The port was done on an Itsy version 1.5 machine with a daughtercard with | 10 | The port was done on an Itsy version 1.5 machine with a daughtercard with |
diff --git a/Documentation/arm/SA1100/PLEB b/Documentation/arm/SA1100/PLEB index 92cae066908d..b9c8a631a351 100644 --- a/Documentation/arm/SA1100/PLEB +++ b/Documentation/arm/SA1100/PLEB | |||
@@ -6,6 +6,6 @@ PLEB support has yet to be fully integrated. | |||
6 | 6 | ||
7 | For more information, see: | 7 | For more information, see: |
8 | 8 | ||
9 | http://www.cse.unsw.edu.au/~pleb/ | 9 | http://www.cse.unsw.edu.au |
10 | 10 | ||
11 | 11 | ||
diff --git a/Documentation/arm/SA1100/Victor b/Documentation/arm/SA1100/Victor index f938a29fdc20..9cff415da5a7 100644 --- a/Documentation/arm/SA1100/Victor +++ b/Documentation/arm/SA1100/Victor | |||
@@ -3,7 +3,7 @@ VisuAide, Inc. to be used by blind people. | |||
3 | 3 | ||
4 | For more information related to Victor, see: | 4 | For more information related to Victor, see: |
5 | 5 | ||
6 | http://www.visuaide.com/victor | 6 | http://www.humanware.com/en-usa/products |
7 | 7 | ||
8 | Of course Victor is using Linux as its main operating system. | 8 | Of course Victor is using Linux as its main operating system. |
9 | The Victor implementation for Linux is maintained by Nicolas Pitre: | 9 | The Victor implementation for Linux is maintained by Nicolas Pitre: |
diff --git a/Documentation/arm/SA1100/nanoEngine b/Documentation/arm/SA1100/nanoEngine index fc431cbfefc2..48a7934f95f6 100644 --- a/Documentation/arm/SA1100/nanoEngine +++ b/Documentation/arm/SA1100/nanoEngine | |||
@@ -7,5 +7,5 @@ for more info. | |||
7 | (Ref: Stuart Adams <sja@brightstareng.com>) | 7 | (Ref: Stuart Adams <sja@brightstareng.com>) |
8 | 8 | ||
9 | Also visit Larry Doolittle's "Linux for the nanoEngine" site: | 9 | Also visit Larry Doolittle's "Linux for the nanoEngine" site: |
10 | http://recycle.lbl.gov/~ldoolitt/bse/ | 10 | http://www.brightstareng.com/arm/nanoeng.htm |
11 | 11 | ||
diff --git a/Documentation/arm/memory.txt b/Documentation/arm/memory.txt index eb0fae18ffb1..771d48d3b335 100644 --- a/Documentation/arm/memory.txt +++ b/Documentation/arm/memory.txt | |||
@@ -33,7 +33,13 @@ ffff0000 ffff0fff CPU vector page. | |||
33 | 33 | ||
34 | fffe0000 fffeffff XScale cache flush area. This is used | 34 | fffe0000 fffeffff XScale cache flush area. This is used |
35 | in proc-xscale.S to flush the whole data | 35 | in proc-xscale.S to flush the whole data |
36 | cache. Free for other usage on non-XScale. | 36 | cache. (XScale does not have TCM.) |
37 | |||
38 | fffe8000 fffeffff DTCM mapping area for platforms with | ||
39 | DTCM mounted inside the CPU. | ||
40 | |||
41 | fffe0000 fffe7fff ITCM mapping area for platforms with | ||
42 | ITCM mounted inside the CPU. | ||
37 | 43 | ||
38 | fff00000 fffdffff Fixmap mapping region. Addresses provided | 44 | fff00000 fffdffff Fixmap mapping region. Addresses provided |
39 | by fix_to_virt() will be located here. | 45 | by fix_to_virt() will be located here. |
diff --git a/Documentation/arm/tcm.txt b/Documentation/arm/tcm.txt index 77fd9376e6d7..7c15871c1885 100644 --- a/Documentation/arm/tcm.txt +++ b/Documentation/arm/tcm.txt | |||
@@ -19,8 +19,8 @@ defines a CPUID_TCM register that you can read out from the | |||
19 | system control coprocessor. Documentation from ARM can be found | 19 | system control coprocessor. Documentation from ARM can be found |
20 | at http://infocenter.arm.com, search for "TCM Status Register" | 20 | at http://infocenter.arm.com, search for "TCM Status Register" |
21 | to see documents for all CPUs. Reading this register you can | 21 | to see documents for all CPUs. Reading this register you can |
22 | determine if ITCM (bit 0) and/or DTCM (bit 16) is present in the | 22 | determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present |
23 | machine. | 23 | in the machine. |
24 | 24 | ||
25 | There is further a TCM region register (search for "TCM Region | 25 | There is further a TCM region register (search for "TCM Region |
26 | Registers" at the ARM site) that can report and modify the location | 26 | Registers" at the ARM site) that can report and modify the location |
@@ -35,7 +35,15 @@ The TCM memory can then be remapped to another address again using | |||
35 | the MMU, but notice that the TCM if often used in situations where | 35 | the MMU, but notice that the TCM if often used in situations where |
36 | the MMU is turned off. To avoid confusion the current Linux | 36 | the MMU is turned off. To avoid confusion the current Linux |
37 | implementation will map the TCM 1 to 1 from physical to virtual | 37 | implementation will map the TCM 1 to 1 from physical to virtual |
38 | memory in the location specified by the machine. | 38 | memory in the location specified by the kernel. Currently Linux |
39 | will map ITCM to 0xfffe0000 and on, and DTCM to 0xfffe8000 and | ||
40 | on, supporting a maximum of 32KiB of ITCM and 32KiB of DTCM. | ||
41 | |||
42 | Newer versions of the region registers also support dividing these | ||
43 | TCMs in two separate banks, so for example an 8KiB ITCM is divided | ||
44 | into two 4KiB banks with its own control registers. The idea is to | ||
45 | be able to lock and hide one of the banks for use by the secure | ||
46 | world (TrustZone). | ||
39 | 47 | ||
40 | TCM is used for a few things: | 48 | TCM is used for a few things: |
41 | 49 | ||
@@ -65,18 +73,18 @@ in <asm/tcm.h>. Using this interface it is possible to: | |||
65 | memory. Such a heap is great for things like saving | 73 | memory. Such a heap is great for things like saving |
66 | device state when shutting off device power domains. | 74 | device state when shutting off device power domains. |
67 | 75 | ||
68 | A machine that has TCM memory shall select HAVE_TCM in | 76 | A machine that has TCM memory shall select HAVE_TCM from |
69 | arch/arm/Kconfig for itself, and then the | 77 | arch/arm/Kconfig for itself. Code that needs to use TCM shall |
70 | rest of the functionality will depend on the physical | 78 | #include <asm/tcm.h> |
71 | location and size of ITCM and DTCM to be defined in | ||
72 | mach/memory.h for the machine. Code that needs to use | ||
73 | TCM shall #include <asm/tcm.h> If the TCM is not located | ||
74 | at the place given in memory.h it will be moved using | ||
75 | the TCM Region registers. | ||
76 | 79 | ||
77 | Functions to go into itcm can be tagged like this: | 80 | Functions to go into itcm can be tagged like this: |
78 | int __tcmfunc foo(int bar); | 81 | int __tcmfunc foo(int bar); |
79 | 82 | ||
83 | Since these are marked to become long_calls and you may want | ||
84 | to have functions called locally inside the TCM without | ||
85 | wasting space, there is also the __tcmlocalfunc prefix that | ||
86 | will make the call relative. | ||
87 | |||
80 | Variables to go into dtcm can be tagged like this: | 88 | Variables to go into dtcm can be tagged like this: |
81 | int __tcmdata foo; | 89 | int __tcmdata foo; |
82 | 90 | ||