Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/340/?format=api
{ "id": 340, "url": "http://patchwork.ozlabs.org/api/patches/340/?format=api", "web_url": "http://patchwork.ozlabs.org/project/linuxppc-dev/patch/1221590682.12463.46.camel@pasglop/", "project": { "id": 2, "url": "http://patchwork.ozlabs.org/api/projects/2/?format=api", "name": "Linux PPC development", "link_name": "linuxppc-dev", "list_id": "linuxppc-dev.lists.ozlabs.org", "list_email": "linuxppc-dev@lists.ozlabs.org", "web_url": "https://github.com/linuxppc/wiki/wiki", "scm_url": "https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git", "webscm_url": "https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/", "list_archive_url": "https://lore.kernel.org/linuxppc-dev/", "list_archive_url_format": "https://lore.kernel.org/linuxppc-dev/{}/", "commit_url_format": "https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id={}" }, "msgid": "<1221590682.12463.46.camel@pasglop>", "list_archive_url": "https://lore.kernel.org/linuxppc-dev/1221590682.12463.46.camel@pasglop/", "date": "2008-09-16T18:44:42", "name": "powerpc: Remove obsolete junk in Documentation/powerpc", "commit_ref": null, "pull_url": null, "state": "changes-requested", "archived": true, "hash": "253be5081aeb3c1ad39b0e738ecc1155734985e6", "submitter": { "id": 38, "url": "http://patchwork.ozlabs.org/api/people/38/?format=api", "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org" }, "delegate": null, "mbox": "http://patchwork.ozlabs.org/project/linuxppc-dev/patch/1221590682.12463.46.camel@pasglop/mbox/", "series": [], "comments": "http://patchwork.ozlabs.org/api/patches/340/comments/", "check": "pending", "checks": "http://patchwork.ozlabs.org/api/patches/340/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<linuxppc-dev-bounces+patchwork=ozlabs.org@ozlabs.org>", "X-Original-To": [ "patchwork@ozlabs.org", "linuxppc-dev@ozlabs.org" ], "Delivered-To": [ "patchwork@ozlabs.org", "linuxppc-dev@ozlabs.org" ], "Received": [ "from ozlabs.org (localhost [127.0.0.1])\n\tby ozlabs.org (Postfix) with ESMTP id F197CDE945\n\tfor <patchwork@ozlabs.org>; Wed, 17 Sep 2008 04:45:08 +1000 (EST)", "from gate.crashing.org (gate.crashing.org [63.228.1.57])\n\t(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\n\t(Client did not present a certificate)\n\tby ozlabs.org (Postfix) with ESMTPS id 422C9DDDD8\n\tfor <linuxppc-dev@ozlabs.org>; Wed, 17 Sep 2008 04:44:49 +1000 (EST)", "from [127.0.0.1] (localhost.localdomain [127.0.0.1])\n\tby gate.crashing.org (8.14.1/8.13.8) with ESMTP id m8GIig1M006996;\n\tTue, 16 Sep 2008 13:44:43 -0500" ], "Subject": "[PATCH] powerpc: Remove obsolete junk in Documentation/powerpc", "From": "Benjamin Herrenschmidt <benh@kernel.crashing.org>", "To": "Paul Mackerras <paulus@samba.org>", "Date": "Tue, 16 Sep 2008 11:44:42 -0700", "Message-Id": "<1221590682.12463.46.camel@pasglop>", "Mime-Version": "1.0", "X-Mailer": "Evolution 2.22.3.1 ", "Cc": "linuxppc-dev list <linuxppc-dev@ozlabs.org>", "X-BeenThere": "linuxppc-dev@ozlabs.org", "X-Mailman-Version": "2.1.11", "Precedence": "list", "Reply-To": "benh@kernel.crashing.org", "List-Id": "Linux on PowerPC Developers Mail List <linuxppc-dev.ozlabs.org>", "List-Unsubscribe": "<https://ozlabs.org/mailman/options/linuxppc-dev>,\n\t<mailto:linuxppc-dev-request@ozlabs.org?subject=unsubscribe>", "List-Archive": "<http://ozlabs.org/pipermail/linuxppc-dev>", "List-Post": "<mailto:linuxppc-dev@ozlabs.org>", "List-Help": "<mailto:linuxppc-dev-request@ozlabs.org?subject=help>", "List-Subscribe": "<https://ozlabs.org/mailman/listinfo/linuxppc-dev>,\n\t<mailto:linuxppc-dev-request@ozlabs.org?subject=subscribe>", "Content-Type": "text/plain; charset=\"us-ascii\"", "Content-Transfer-Encoding": "7bit", "Sender": "linuxppc-dev-bounces+patchwork=ozlabs.org@ozlabs.org", "Errors-To": "linuxppc-dev-bounces+patchwork=ozlabs.org@ozlabs.org" }, "content": "We have all sort of totally rotten pieces of documentation\nin there, let's get rid of them\n\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>", "diff": "Index: linux-work/Documentation/powerpc/ppc_htab.txt\n===================================================================\n--- linux-work.orig/Documentation/powerpc/ppc_htab.txt\t2008-09-16 11:38:42.000000000 -0700\n+++ /dev/null\t1970-01-01 00:00:00.000000000 +0000\n@@ -1,118 +0,0 @@\n- Information about /proc/ppc_htab\n-=====================================================================\n-\n-This document and the related code was written by me (Cort Dougan), please\n-email me (cort@fsmlabs.com) if you have questions, comments or corrections.\n-\n-Last Change: 2.16.98\n-\n-This entry in the proc directory is readable by all users but only\n-writable by root.\n-\n-The ppc_htab interface is a user level way of accessing the\n-performance monitoring registers as well as providing information\n-about the PTE hash table.\n-\n-1. Reading\n-\n- Reading this file will give you information about the memory management\n- hash table that serves as an extended tlb for page translation on the\n- powerpc. It will also give you information about performance measurement\n- specific to the cpu that you are using.\n-\n- Explanation of the 604 Performance Monitoring Fields:\n- MMCR0 - the current value of the MMCR0 register\n- PMC1\n- PMC2 - the value of the performance counters and a\n- description of what events they are counting\n- which are based on MMCR0 bit settings.\n- Explanation of the PTE Hash Table fields:\n-\n- Size - hash table size in Kb.\n- Buckets - number of buckets in the table.\n- Address - the virtual kernel address of the hash table base.\n- Entries - the number of ptes that can be stored in the hash table.\n- User/Kernel - how many pte's are in use by the kernel or user at that time.\n- Overflows - How many of the entries are in their secondary hash location.\n- Percent full - ratio of free pte entries to in use entries.\n- Reloads - Count of how many hash table misses have occurred\n- that were fixed with a reload from the linux tables.\n- Should always be 0 on 603 based machines.\n- Non-error Misses - Count of how many hash table misses have occurred\n- that were completed with the creation of a pte in the linux\n- tables with a call to do_page_fault().\n- Error Misses - Number of misses due to errors such as bad address\n- and permission violations. This includes kernel access of\n- bad user addresses that are fixed up by the trap handler.\n-\n- Note that calculation of the data displayed from /proc/ppc_htab takes\n- a long time and spends a great deal of time in the kernel. It would\n- be quite hard on performance to read this file constantly. In time\n- there may be a counter in the kernel that allows successive reads from\n- this file only after a given amount of time has passed to reduce the\n- possibility of a user slowing the system by reading this file.\n-\n-2. Writing\n-\n- Writing to the ppc_htab allows you to change the characteristics of\n- the powerpc PTE hash table and setup performance monitoring.\n-\n- Resizing the PTE hash table is not enabled right now due to many\n- complications with moving the hash table, rehashing the entries\n- and many many SMP issues that would have to be dealt with.\n-\n- Write options to ppc_htab:\n- \n- - To set the size of the hash table to 64Kb:\n-\n- echo 'size 64' > /proc/ppc_htab\n-\n- The size must be a multiple of 64 and must be greater than or equal to\n- 64.\n-\n- - To turn off performance monitoring:\n-\n- echo 'off' > /proc/ppc_htab\n-\n- - To reset the counters without changing what they're counting:\n-\n- echo 'reset' > /proc/ppc_htab\n-\n- Note that counting will continue after the reset if it is enabled.\n-\n- - To count only events in user mode or only in kernel mode:\n-\n- echo 'user' > /proc/ppc_htab\n- ...or...\n- echo 'kernel' > /proc/ppc_htab\n-\n- Note that these two options are exclusive of one another and the\n- lack of either of these options counts user and kernel.\n- Using 'reset' and 'off' reset these flags.\n-\n- - The 604 has 2 performance counters which can each count events from\n- a specific set of events. These sets are disjoint so it is not\n- possible to count _any_ combination of 2 events. One event can\n- be counted by PMC1 and one by PMC2.\n-\n- To start counting a particular event use:\n-\n- echo 'event' > /proc/ppc_htab\n-\n- and choose from these events:\n-\n- PMC1\n- ----\n- 'ic miss' - instruction cache misses\n- 'dtlb' - data tlb misses (not hash table misses)\n-\n- PMC2\n- ----\n- 'dc miss' - data cache misses\n- 'itlb' - instruction tlb misses (not hash table misses)\n- 'load miss time' - cycles to complete a load miss\n-\n-3. Bugs\n-\n- The PMC1 and PMC2 counters can overflow and give no indication of that\n- in /proc/ppc_htab.\nIndex: linux-work/Documentation/powerpc/smp.txt\n===================================================================\n--- linux-work.orig/Documentation/powerpc/smp.txt\t2008-09-16 11:38:42.000000000 -0700\n+++ /dev/null\t1970-01-01 00:00:00.000000000 +0000\n@@ -1,34 +0,0 @@\n- Information about Linux/PPC SMP mode\n-=====================================================================\n-\n-This document and the related code was written by me\n-(Cort Dougan, cort@fsmlabs.com) please email me if you have questions,\n-comments or corrections.\n-\n-Last Change: 3.31.99\n-\n-If you want to help by writing code or testing different hardware please\n-email me!\n-\n-1. State of Supported Hardware\n-\n- PowerSurge Architecture - tested on UMAX s900, Apple 9600\n- The second processor on this machine boots up just fine and\n- enters its idle loop. Hopefully a completely working SMP kernel\n- on this machine will be done shortly.\n-\n- The code makes the assumption of only two processors. The changes\n- necessary to work with any number would not be overly difficult but\n- I don't have any machines with >2 processors so it's not high on my\n- list of priorities. If anyone else would like do to the work email\n- me and I can point out the places that need changed. If you have >2\n- processors and don't want to add support yourself let me know and I\n- can take a look into it.\n-\n- BeBox\n- BeBox support hasn't been added to the 2.1.X kernels from 2.0.X\n- but work is being done and SMP support for BeBox is in the works.\n-\n- CHRP\n- CHRP SMP works and is fairly solid. It's been tested on the IBM F50\n- with 4 processors for quite some time now.\nIndex: linux-work/Documentation/powerpc/sound.txt\n===================================================================\n--- linux-work.orig/Documentation/powerpc/sound.txt\t2008-09-16 11:38:42.000000000 -0700\n+++ /dev/null\t1970-01-01 00:00:00.000000000 +0000\n@@ -1,81 +0,0 @@\n- Information about PowerPC Sound support\n-=====================================================================\n-\n-Please mail me (Cort Dougan, cort@fsmlabs.com) if you have questions,\n-comments or corrections.\n-\n-Last Change: 6.16.99\n-\n-This just covers sound on the PReP and CHRP systems for now and later\n-will contain information on the PowerMac's.\n-\n-Sound on PReP has been tested and is working with the PowerStack and IBM\n-Power Series onboard sound systems which are based on the cs4231(2) chip.\n-The sound options when doing the make config are a bit different from\n-the default, though.\n-\n-The I/O base, irq and dma lines that you enter during the make config\n-are ignored and are set when booting according to the machine type.\n-This is so that one binary can be used for Motorola and IBM machines\n-which use different values and isn't allowed by the driver, so things\n-are hacked together in such a way as to allow this information to be\n-set automatically on boot.\n-\n-1. Motorola PowerStack PReP machines\n-\n- Enable support for \"Crystal CS4232 based (PnP) cards\" and for the\n- Microsoft Sound System. The MSS isn't used, but some of the routines\n- that the CS4232 driver uses are in it.\n-\n- Although the options you set are ignored and determined automatically\n- on boot these are included for information only:\n-\n- (830) CS4232 audio I/O base 530, 604, E80 or F40\n- (10) CS4232 audio IRQ 5, 7, 9, 11, 12 or 15\n- (6) CS4232 audio DMA 0, 1 or 3\n- (7) CS4232 second (duplex) DMA 0, 1 or 3\n-\n- This will allow simultaneous record and playback, as 2 different dma\n- channels are used.\n-\n- The sound will be all left channel and very low volume since the\n- auxiliary input isn't muted by default. I had the changes necessary\n- for this in the kernel but the sound driver maintainer didn't want\n- to include them since it wasn't common in other machines. To fix this\n- you need to mute it using a mixer utility of some sort (if you find one\n- please let me know) or by patching the driver yourself and recompiling.\n-\n- There is a problem on the PowerStack 2's (PowerStack Pro's) using a\n- different irq/drq than the kernel expects. Unfortunately, I don't know\n- which irq/drq it is so if anyone knows please email me.\n-\n- Midi is not supported since the cs4232 driver doesn't support midi yet.\n-\n-2. IBM PowerPersonal PReP machines\n-\n- I've only tested sound on the Power Personal Series of IBM workstations\n- so if you try it on others please let me know the result. I'm especially\n- interested in the 43p's sound system, which I know nothing about.\n-\n- Enable support for \"Crystal CS4232 based (PnP) cards\" and for the\n- Microsoft Sound System. The MSS isn't used, but some of the routines\n- that the CS4232 driver uses are in it.\n-\n- Although the options you set are ignored and determined automatically\n- on boot these are included for information only:\n-\n- (530) CS4232 audio I/O base 530, 604, E80 or F40\n- (5) CS4232 audio IRQ 5, 7, 9, 11, 12 or 15\n- (1) CS4232 audio DMA 0, 1 or 3\n- (7) CS4232 second (duplex) DMA 0, 1 or 3\n- (330) CS4232 MIDI I/O base 330, 370, 3B0 or 3F0\n- (9) CS4232 MIDI IRQ 5, 7, 9, 11, 12 or 15\n-\n- This setup does _NOT_ allow for recording yet.\n-\n- Midi is not supported since the cs4232 driver doesn't support midi yet.\n-\n-2. IBM CHRP\n-\n- I have only tested this on the 43P-150. Build the kernel with the cs4232\n- set as a module and load the module with irq=9 dma=1 dma2=2 io=0x550\nIndex: linux-work/Documentation/powerpc/zImage_layout.txt\n===================================================================\n--- linux-work.orig/Documentation/powerpc/zImage_layout.txt\t2008-09-16 11:38:42.000000000 -0700\n+++ /dev/null\t1970-01-01 00:00:00.000000000 +0000\n@@ -1,47 +0,0 @@\n- Information about the Linux/PPC kernel images\n-=====================================================================\n-\n-Please mail me (Cort Dougan, cort@fsmlabs.com) if you have questions,\n-comments or corrections.\n-\n-This document is meant to answer several questions I've had about how\n-the PReP system boots and how Linux/PPC interacts with that mechanism.\n-It would be nice if we could have information on how other architectures\n-boot here as well. If you have anything to contribute, please\n-let me know.\n-\n-\n-1. PReP boot file\n-\n- This is the file necessary to boot PReP systems from floppy or\n- hard drive. The firmware reads the PReP partition table entry\n- and will load the image accordingly.\n-\n- To boot the zImage, copy it onto a floppy with dd if=zImage of=/dev/fd0h1440\n- or onto a PReP hard drive partition with dd if=zImage of=/dev/sda4\n- assuming you've created a PReP partition (type 0x41) with fdisk on\n- /dev/sda4.\n-\n- The layout of the image format is:\n-\n- 0x0 +------------+\n- | | PReP partition table entry\n- | |\n- 0x400 +------------+\n- | | Bootstrap program code + data\n- | |\n- | |\n- +------------+\n- | | compressed kernel, elf header removed\n- +------------+\n- | | initrd (if loaded)\n- +------------+\n- | | Elf section table for bootstrap program\n- +------------+\n-\n-\n-2. MBX boot file\n-\n- The MBX boards can load an elf image, and relocate it to the\n- proper location in memory - it copies the image to the location it was\n- linked at.\n", "prefixes": [] }