All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: akpm@osdl.org
Cc: apw@shadowen.org, linux-kernel@vger.kernel.org
Subject: [PATCH] tidy AMD 768MPX fix
Date: Fri, 03 Sep 2004 17:13:57 +0100	[thread overview]
Message-ID: <E1C3GhJ-0001YB-7N@localhost.localdomain> (raw)

Convert the AMD 768MPX errata #56 fix to use PAGE_SIZE instead of using
4096 in line with other declarations in this file.  Also take the
oppotunity to match indentation.

Revision: $Rev: 612 $

Signed-off-by: Andy Whitcroft <apw@shadowen.org>

diffstat 020-tidy-AMD-768MPX-fix
---
 setup.c |   10 ++++++----
 1 files changed, 6 insertions(+), 4 deletions(-)

diff -X /home/apw/brief/lib/vdiff.excl -rupN reference/arch/i386/kernel/setup.c current/arch/i386/kernel/setup.c
--- reference/arch/i386/kernel/setup.c	2004-09-02 18:05:57.000000000 +0100
+++ current/arch/i386/kernel/setup.c	2004-09-03 16:59:45.000000000 +0100
@@ -1052,12 +1052,14 @@ static unsigned long __init setup_memory
 	/* reserve EBDA region, it's a 4K region */
 	reserve_ebda_region();
 
-    /* could be an AMD 768MPX chipset. Reserve a page  before VGA to prevent
-       PCI prefetch into it (errata #56). Usually the page is reserved anyways,
-       unless you have no PS/2 mouse plugged in. */
+	/*
+	 * could be an AMD 768MPX chipset. Reserve a page before VGA to
+	 * prevent PCI prefetch into it (errata #56). Usually the page is
+	 * reserved anyways, unless you have no PS/2 mouse plugged in.
+	 */
 	if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD &&
 	    boot_cpu_data.x86 == 6)
-	     reserve_bootmem(0xa0000 - 4096, 4096);
+		reserve_bootmem(0xa0000 - PAGE_SIZE, PAGE_SIZE);
 
 #ifdef CONFIG_SMP
 	/*

             reply	other threads:[~2004-09-03 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 16:13 Andy Whitcroft [this message]
2004-09-03 15:27 ` [PATCH] tidy AMD 768MPX fix Alan Cox
2004-09-03 16:46   ` Andy Whitcroft
2004-09-06 12:34     ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1C3GhJ-0001YB-7N@localhost.localdomain \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.