Serial can be disabled by a simple change:
diff -r 2e5d4e459c1c buildconfigs/linux-defconfig_xen_ia64
--- a/buildconfigs/linux-defconfig_xen_ia64 Sun May 21 07:31:02 2006 -0600
+++ b/buildconfigs/linux-defconfig_xen_ia64 Mon May 22 15:06:00 2006 +0800
@@ -98,6 +98,7 @@ CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
+CONFIG_XEN_DISABLE_SERIAL=y
CONFIG_XEN_SYSFS=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_DMA_IS_DMA32=y
@@ -1544,4 +1545,3 @@ CONFIG_CRYPTO_DES=y
# XEN
#
# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
-# CONFIG_XEN_DISABLE_SERIAL is not set
But I'm not sure why I have to set option to be 'yes' explicitly:
config XEN_DISABLE_SERIAL
bool "Disable serial port drivers"
default y
So after making oldconfig, this option should be enabled automatically.
Does I misunderstand the logic behind? :-(
Thanks,
Kevin
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of
>Tian, Kevin
>Sent: 2006年5月22日 14:53
>To: Isaku Yamahata
>Cc: xen-ia64-devel@lists.xensource.com
>Subject: RE: [Xen-ia64-devel] [PATCH 0/6] Add full evtchn mechanism
>forxen/ia64
>
>>From: Isaku Yamahata [mailto:[EMAIL PROTECTED]
>>Sent: 2006年5月22日 13:43
>>On Mon, May 22, 2006 at 12:53:11PM +0800, Tian, Kevin wrote:
>>
>>> Why is serial
>>> required to be disabled in dom0? What's policy to choose which serial
>>> to be disabled, if there're multiple serial ports with different type?
>>
>>In fact I'm not sure about the policy.
>>Since xenLinux/x86 defines CONFIG_XEN_DISABLE_SERIAL=y, I
>>thought
>>it was the xen's policy. However I'm not sure whether it's right.
>>It seemed that you used serial port from dom0, I wanted to confirm it.
>>
>>It is bad that xen and dom0 accesse to the same UART.
>>This is only what I'm sure about.
>
>Yes, that's bad which may be the reason why xen/x86 disables serial
>directly. Ideally that should also apply to xen/ia64 since that option is
>common in drivers/xen. So I'm not sure why that option doesn't work
>for ia64. Alex should know more about this area, and it may simply
>come from a mis-configuration case...
>
>Thanks,
>Kevin
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@lists.xensource.com
>http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
