All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ling, Xiaofeng" <xiaofeng.ling@intel.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH]Fix the issue of on x86_64, rhel4 can not get into runlevel 5.
Date: Fri, 25 Nov 2005 15:55:29 +0800	[thread overview]
Message-ID: <4386C371.4000805@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

Fix the issue of on x86_64, rhel4 can not get into runlevel 5.
Xserver will scan pci and the cirrus VGA driver will register
mmio each time, cause mmio array out of space.

Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>




[-- Attachment #2: xwinmmiofix.patch --]
[-- Type: text/x-patch, Size: 1080 bytes --]

# HG changeset patch
# User Xiaofeng Ling <xiaofeng.ling@intel.com>
# Node ID 43babde5b5096f3b9a9ef0f73779927ac8f08c97
# Parent  dc250958aebbe72d603f0e1584b12a0525f570e3
Fix the issue of on x86_64, rhel4 can not get into runlevel 5.
Xserver will scan pci and the cirrus VGA driver will register
mmio each time, cause mmio array out of space.

Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>

diff -r dc250958aebb -r 43babde5b509 tools/ioemu/exec.c
--- a/tools/ioemu/exec.c	Fri Nov 25 15:04:57 2005 +0800
+++ b/tools/ioemu/exec.c	Fri Nov 25 15:42:16 2005 +0800
@@ -262,6 +262,15 @@
                                   unsigned long size,
                                   unsigned long phys_offset)
 {
+        int i;
+
+        for (i = 0; i < mmio_cnt; i++) { 
+            if(mmio[i].start == start_addr) {
+                mmio[i].io_index = phys_offset;
+                mmio[i].size = size;
+                return;
+            }
+        }
         if (mmio_cnt == MAX_MMIO) {
                 fprintf(logfile, "too many mmio regions\n");
                 exit(-1);

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2005-11-25  7:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4386C371.4000805@intel.com \
    --to=xiaofeng.ling@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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.