diff options
Diffstat (limited to 'Documentation/powerpc')
-rw-r--r-- | Documentation/powerpc/00-INDEX | 4 | ||||
-rw-r--r-- | Documentation/powerpc/ptrace.txt | 1 | ||||
-rw-r--r-- | Documentation/powerpc/sound.txt | 81 | ||||
-rw-r--r-- | Documentation/powerpc/zImage_layout.txt | 47 |
4 files changed, 1 insertions, 132 deletions
diff --git a/Documentation/powerpc/00-INDEX b/Documentation/powerpc/00-INDEX index 5620fb5ac425..dd9e92802ec0 100644 --- a/Documentation/powerpc/00-INDEX +++ b/Documentation/powerpc/00-INDEX | |||
@@ -14,10 +14,6 @@ hvcs.txt | |||
14 | - IBM "Hypervisor Virtual Console Server" Installation Guide | 14 | - IBM "Hypervisor Virtual Console Server" Installation Guide |
15 | mpc52xx.txt | 15 | mpc52xx.txt |
16 | - Linux 2.6.x on MPC52xx family | 16 | - Linux 2.6.x on MPC52xx family |
17 | sound.txt | ||
18 | - info on sound support under Linux/PPC | ||
19 | zImage_layout.txt | ||
20 | - info on the kernel images for Linux/PPC | ||
21 | qe_firmware.txt | 17 | qe_firmware.txt |
22 | - describes the layout of firmware binaries for the Freescale QUICC | 18 | - describes the layout of firmware binaries for the Freescale QUICC |
23 | Engine and the code that parses and uploads the microcode therein. | 19 | Engine and the code that parses and uploads the microcode therein. |
diff --git a/Documentation/powerpc/ptrace.txt b/Documentation/powerpc/ptrace.txt index f2a7a3919772..99c5ce88d0fe 100644 --- a/Documentation/powerpc/ptrace.txt +++ b/Documentation/powerpc/ptrace.txt | |||
@@ -40,6 +40,7 @@ features will have bits indicating whether there is support for: | |||
40 | #define PPC_DEBUG_FEATURE_INSN_BP_MASK 0x2 | 40 | #define PPC_DEBUG_FEATURE_INSN_BP_MASK 0x2 |
41 | #define PPC_DEBUG_FEATURE_DATA_BP_RANGE 0x4 | 41 | #define PPC_DEBUG_FEATURE_DATA_BP_RANGE 0x4 |
42 | #define PPC_DEBUG_FEATURE_DATA_BP_MASK 0x8 | 42 | #define PPC_DEBUG_FEATURE_DATA_BP_MASK 0x8 |
43 | #define PPC_DEBUG_FEATURE_DATA_BP_DAWR 0x10 | ||
43 | 44 | ||
44 | 2. PTRACE_SETHWDEBUG | 45 | 2. PTRACE_SETHWDEBUG |
45 | 46 | ||
diff --git a/Documentation/powerpc/sound.txt b/Documentation/powerpc/sound.txt deleted file mode 100644 index df23d95e03a0..000000000000 --- a/Documentation/powerpc/sound.txt +++ /dev/null | |||
@@ -1,81 +0,0 @@ | |||
1 | Information about PowerPC Sound support | ||
2 | ===================================================================== | ||
3 | |||
4 | Please mail me (Cort Dougan, cort@fsmlabs.com) if you have questions, | ||
5 | comments or corrections. | ||
6 | |||
7 | Last Change: 6.16.99 | ||
8 | |||
9 | This just covers sound on the PReP and CHRP systems for now and later | ||
10 | will contain information on the PowerMac's. | ||
11 | |||
12 | Sound on PReP has been tested and is working with the PowerStack and IBM | ||
13 | Power Series onboard sound systems which are based on the cs4231(2) chip. | ||
14 | The sound options when doing the make config are a bit different from | ||
15 | the default, though. | ||
16 | |||
17 | The I/O base, irq and dma lines that you enter during the make config | ||
18 | are ignored and are set when booting according to the machine type. | ||
19 | This is so that one binary can be used for Motorola and IBM machines | ||
20 | which use different values and isn't allowed by the driver, so things | ||
21 | are hacked together in such a way as to allow this information to be | ||
22 | set automatically on boot. | ||
23 | |||
24 | 1. Motorola PowerStack PReP machines | ||
25 | |||
26 | Enable support for "Crystal CS4232 based (PnP) cards" and for the | ||
27 | Microsoft Sound System. The MSS isn't used, but some of the routines | ||
28 | that the CS4232 driver uses are in it. | ||
29 | |||
30 | Although the options you set are ignored and determined automatically | ||
31 | on boot these are included for information only: | ||
32 | |||
33 | (830) CS4232 audio I/O base 530, 604, E80 or F40 | ||
34 | (10) CS4232 audio IRQ 5, 7, 9, 11, 12 or 15 | ||
35 | (6) CS4232 audio DMA 0, 1 or 3 | ||
36 | (7) CS4232 second (duplex) DMA 0, 1 or 3 | ||
37 | |||
38 | This will allow simultaneous record and playback, as 2 different dma | ||
39 | channels are used. | ||
40 | |||
41 | The sound will be all left channel and very low volume since the | ||
42 | auxiliary input isn't muted by default. I had the changes necessary | ||
43 | for this in the kernel but the sound driver maintainer didn't want | ||
44 | to include them since it wasn't common in other machines. To fix this | ||
45 | you need to mute it using a mixer utility of some sort (if you find one | ||
46 | please let me know) or by patching the driver yourself and recompiling. | ||
47 | |||
48 | There is a problem on the PowerStack 2's (PowerStack Pro's) using a | ||
49 | different irq/drq than the kernel expects. Unfortunately, I don't know | ||
50 | which irq/drq it is so if anyone knows please email me. | ||
51 | |||
52 | Midi is not supported since the cs4232 driver doesn't support midi yet. | ||
53 | |||
54 | 2. IBM PowerPersonal PReP machines | ||
55 | |||
56 | I've only tested sound on the Power Personal Series of IBM workstations | ||
57 | so if you try it on others please let me know the result. I'm especially | ||
58 | interested in the 43p's sound system, which I know nothing about. | ||
59 | |||
60 | Enable support for "Crystal CS4232 based (PnP) cards" and for the | ||
61 | Microsoft Sound System. The MSS isn't used, but some of the routines | ||
62 | that the CS4232 driver uses are in it. | ||
63 | |||
64 | Although the options you set are ignored and determined automatically | ||
65 | on boot these are included for information only: | ||
66 | |||
67 | (530) CS4232 audio I/O base 530, 604, E80 or F40 | ||
68 | (5) CS4232 audio IRQ 5, 7, 9, 11, 12 or 15 | ||
69 | (1) CS4232 audio DMA 0, 1 or 3 | ||
70 | (7) CS4232 second (duplex) DMA 0, 1 or 3 | ||
71 | (330) CS4232 MIDI I/O base 330, 370, 3B0 or 3F0 | ||
72 | (9) CS4232 MIDI IRQ 5, 7, 9, 11, 12 or 15 | ||
73 | |||
74 | This setup does _NOT_ allow for recording yet. | ||
75 | |||
76 | Midi is not supported since the cs4232 driver doesn't support midi yet. | ||
77 | |||
78 | 2. IBM CHRP | ||
79 | |||
80 | I have only tested this on the 43P-150. Build the kernel with the cs4232 | ||
81 | set as a module and load the module with irq=9 dma=1 dma2=2 io=0x550 | ||
diff --git a/Documentation/powerpc/zImage_layout.txt b/Documentation/powerpc/zImage_layout.txt deleted file mode 100644 index 048e0150f571..000000000000 --- a/Documentation/powerpc/zImage_layout.txt +++ /dev/null | |||
@@ -1,47 +0,0 @@ | |||
1 | Information about the Linux/PPC kernel images | ||
2 | ===================================================================== | ||
3 | |||
4 | Please mail me (Cort Dougan, cort@fsmlabs.com) if you have questions, | ||
5 | comments or corrections. | ||
6 | |||
7 | This document is meant to answer several questions I've had about how | ||
8 | the PReP system boots and how Linux/PPC interacts with that mechanism. | ||
9 | It would be nice if we could have information on how other architectures | ||
10 | boot here as well. If you have anything to contribute, please | ||
11 | let me know. | ||
12 | |||
13 | |||
14 | 1. PReP boot file | ||
15 | |||
16 | This is the file necessary to boot PReP systems from floppy or | ||
17 | hard drive. The firmware reads the PReP partition table entry | ||
18 | and will load the image accordingly. | ||
19 | |||
20 | To boot the zImage, copy it onto a floppy with dd if=zImage of=/dev/fd0h1440 | ||
21 | or onto a PReP hard drive partition with dd if=zImage of=/dev/sda4 | ||
22 | assuming you've created a PReP partition (type 0x41) with fdisk on | ||
23 | /dev/sda4. | ||
24 | |||
25 | The layout of the image format is: | ||
26 | |||
27 | 0x0 +------------+ | ||
28 | | | PReP partition table entry | ||
29 | | | | ||
30 | 0x400 +------------+ | ||
31 | | | Bootstrap program code + data | ||
32 | | | | ||
33 | | | | ||
34 | +------------+ | ||
35 | | | compressed kernel, elf header removed | ||
36 | +------------+ | ||
37 | | | initrd (if loaded) | ||
38 | +------------+ | ||
39 | | | Elf section table for bootstrap program | ||
40 | +------------+ | ||
41 | |||
42 | |||
43 | 2. MBX boot file | ||
44 | |||
45 | The MBX boards can load an elf image, and relocate it to the | ||
46 | proper location in memory - it copies the image to the location it was | ||
47 | linked at. | ||