'bump to latest version, removed buggy acpi patch, removed included

patch'

2 files changed, 0 insertions, 87 deletions

diff --git a/patches/acpi-buggy-bios.patch b/patches/acpi-buggy-bios.patch
deleted file mode 100644
index 3e1ac43..0000000
--- a/patches/acpi-buggy-bios.patch
+++ /dev/null
@@ -1,36 +0,0 @@
----
- drivers/acpi/processor_perflib.c |   11 +++++++++++
- 1 files changed, 11 insertions(+)
-
-http://bugzilla.kernel.org/attachment.cgi?id=9798&action=view
-
-Index: linux-2.6.19/drivers/acpi/processor_perflib.c
-===================================================================
---- linux-2.6.19.orig/drivers/acpi/processor_perflib.c	2006-12-25 15:40:47.000000000 +0800
-+++ linux-2.6.19/drivers/acpi/processor_perflib.c	2006-12-26 09:20:14.000000000 +0800
-@@ -258,6 +258,7 @@ static int acpi_processor_get_performanc
- 	for (i = 0; i < pr->performance->state_count; i++) {
- 
- 		struct acpi_processor_px *px = &(pr->performance->states[i]);
-+		int j;
- 
- 		state.length = sizeof(struct acpi_processor_px);
- 		state.pointer = px;
-@@ -273,6 +274,16 @@ static int acpi_processor_get_performanc
- 			goto end;
- 		}
- 
-+		/*
-+		 * Fixme: Duplicated core frequency is allowed, if they have the same control and status
-+		 */
-+		if (px->core_frequency == 1992)
-+			for (j = 0; j < i; j++) {
-+				if (pr->performance->states[j].control == px->control && pr->performance->states[j].core_frequency > 1992)
-+					ACPI_DEBUG_PRINT((ACPI_DB_WARN, "States [%d] :Wrong processor core frequency %u, set it to 1992\n", j, (u32)pr->performance->states[j].core_frequency));
-+					pr->performance->states[j].core_frequency = 1992;
-+			}
-+
- 		ACPI_DEBUG_PRINT((ACPI_DB_INFO,
- 				  "State [%d]: core_frequency[%d] power[%d] transition_latency[%d] bus_master_latency[%d] control[0x%x] status[0x%x]\n",
- 				  i,
- 
diff --git a/patches/pat_fix_reserve_mem_type_for_1mb.patch b/patches/pat_fix_reserve_mem_type_for_1mb.patch
deleted file mode 100644
index 120f99e..0000000
--- a/patches/pat_fix_reserve_mem_type_for_1mb.patch
+++ /dev/null
@@ -1,51 +0,0 @@
-[patch] x86, pat: fix reserve_memtype() for legacy 1MB range
-
-Thierry Vignaud reported:
-> On P4 with an SiS motherboard (video card is a SiS 651)
-> X server fails to start with error:
-> xf86MapVidMem: Could not mmap framebuffer (0x00000000,0x2000) (Invalid
-> argument)
-
-Here X is trying to map first 8KB of memory using /dev/mem. Existing
-code treats first 0-4KB of memory as non-RAM and 4KB-8KB as RAM. Recent
-code changes don't allow to map memory with different attributes
-at the same time.
-
-Fix this by treating the first 1MB legacy region as special and always
-track the attribute requests with in this region using linear linked
-list (and don't bother if the range is RAM or non-RAM or mixed)
-
-Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
-Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
----
-
-diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
-index 85cbd3c..c959a4d 100644
---- a/arch/x86/mm/pat.c
-+++ b/arch/x86/mm/pat.c
-@@ -333,11 +333,20 @@ int reserve_memtype(u64 start, u64 end, unsigned long req_type,
- 					      req_type & _PAGE_CACHE_MASK);
- 	}
- 
--	is_range_ram = pagerange_is_ram(start, end);
--	if (is_range_ram == 1)
--		return reserve_ram_pages_type(start, end, req_type, new_type);
--	else if (is_range_ram < 0)
--		return -EINVAL;
-+	/*
-+	 * For legacy reasons, some parts of the physical address range in the
-+	 * legacy 1MB region is treated as non-RAM (even when listed as RAM in
-+	 * the e820 tables).  So we will track the memory attributes of this
-+	 * legacy 1MB region using the linear memtype_list always.
-+	 */
-+	if (end >= ISA_END_ADDRESS) {
-+		is_range_ram = pagerange_is_ram(start, end);
-+		if (is_range_ram == 1)
-+			return reserve_ram_pages_type(start, end, req_type,
-+						      new_type);
-+		else if (is_range_ram < 0)
-+			return -EINVAL;
-+	}
- 
- 	new  = kmalloc(sizeof(struct memtype), GFP_KERNEL);
- 	if (!new)