From: Arun Sharma <arun.sharma@intel.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: x86-64 xen broken with May4th xen-unstable build
Date: Thu, 05 May 2005 17:45:47 -0700 [thread overview]
Message-ID: <427ABE3B.4070606@intel.com> (raw)
In-Reply-To: <mailman.1115245832.5358@unix-os.sc.intel.com>
Jerone Young wrote:
> There are two things that happened in the May 4th build.
>
> 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> This can easily be resolved by commenting out "c-xen-obj-
> $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> removed from i386 and no one told x86-64 about it ...that's why he
> always misses the party :-)
>
This might be a better fix?
--- 1.2/linux-2.6.11-xen-sparse/arch/xen/x86_64/pci/Makefile
2005-04-02 12:27:09 -08:00
+++ edited/linux-2.6.11-xen-sparse/arch/xen/x86_64/pci/Makefile
2005-05-05 15:43:11 -07:00
@@ -12,7 +12,7 @@
c-obj-y += fixup.o
c-obj-$(CONFIG_ACPI_PCI) += acpi.o
c-obj-y += legacy.o common.o
-c-xen-obj-$(CONFIG_PCI_DIRECT)+= direct.o
+c-obj-$(CONFIG_PCI_DIRECT)+= direct.o
c-xen-obj-y += irq.o
# mmconfig has a 64bit special
c-obj-$(CONFIG_PCI_MMCONFIG) += mmconfig.o
-Arun
next parent reply other threads:[~2005-05-06 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1115245832.5358@unix-os.sc.intel.com>
2005-05-06 0:45 ` Arun Sharma [this message]
2005-05-06 17:04 ` x86-64 xen broken with May4th xen-unstable build Jerone Young
2005-05-10 2:14 Nakajima, Jun
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 23:11 Nakajima, Jun
2005-05-06 16:47 ` Jerone Young
2005-05-04 22:29 Jerone Young
2005-05-06 21:57 ` David F Barrera
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=427ABE3B.4070606@intel.com \
--to=arun.sharma@intel.com \
--cc=jyoung5@us.ibm.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.