From: Ron Arts <ron.arts@netland.nl>
To: xen-devel@lists.sourceforge.net
Subject: isa_bus_to_virt_needs_PRIVILEGED_BUILD
Date: Thu, 30 Dec 2004 09:38:58 +0100 [thread overview]
Message-ID: <41D3BEA2.7000109@netland.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi,
What does this mean? Having read the FAQ I can guess what
it means, but will this be solved eventually?
(I am trying to enable i2c in a -xenU domain)
CC arch/xen/i386/mm/ioremap.o
arch/xen/i386/mm/ioremap.c: In function `__ioremap':
arch/xen/i386/mm/ioremap.c:144: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
arch/xen/i386/mm/ioremap.c:144: error: (Each undeclared identifier is
reported only once
arch/xen/i386/mm/ioremap.c:144: error: for each function it appears in.)
arch/xen/i386/mm/ioremap.c: In function `bt_ioremap':
arch/xen/i386/mm/ioremap.c:280: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
make[4]: *** [arch/xen/i386/mm/ioremap.o] Error 1
make[3]: *** [arch/xen/i386/mm] Error 2
make[3]: Leaving directory `/root/xen-2.0/linux-2.6.9-xenU'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/root/xen-2.0'
make[1]: *** [linux-2.6-xenU-build] Error 2
make[1]: Leaving directory `/root/xen-2.0'
make: *** [kernels] Error 2
Thanks,
Ron
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3228 bytes --]
next reply other threads:[~2004-12-30 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 8:38 Ron Arts [this message]
2004-12-30 9:15 ` isa_bus_to_virt_needs_PRIVILEGED_BUILD Keir Fraser
2004-12-30 11:44 ` isa_bus_to_virt_needs_PRIVILEGED_BUILD Ron Arts
2004-12-30 14:33 ` isa_bus_to_virt_needs_PRIVILEGED_BUILD M.A. Williamson
2004-12-31 9:27 ` isa_bus_to_virt_needs_PRIVILEGED_BUILD Ron Arts
2004-12-31 15:34 ` isa_bus_to_virt_needs_PRIVILEGED_BUILD M.A. Williamson
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=41D3BEA2.7000109@netland.nl \
--to=ron.arts@netland.nl \
--cc=xen-devel@lists.sourceforge.net \
/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.