[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: OK, now domU can boot on tip. ;-)


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 10 Nov 2005 13:42:54 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 10 Nov 2005 05:42:54 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXlIo7CfukUD0Q/QLaqMp6BH/+whQAVOmOgAAH04wAADmbhIA==
  • Thread-topic: [Xen-ia64-devel] RE: OK, now domU can boot on tip. ;-)

>From: Magenheimer, Dan (HP Labs Fort Collins) [mailto:dan.magenheimer@xxxxxx]
>Sent: 2005年11月10日 7:10
>
>We should probably have a sparse/arch/xen/configs/xenU_defconfig_ia64
>(as opposed to xen0_defconfig_ia64) that turns off CONFIG_VT.
>However, it doesn't seem possible to turn off CONFIG_VT "permanently"
>without changing driver/char/Kconfig.  (make oldconfig will just
>turn it back on.)  Anybody know a workaround for this?
>
>Dan

Just made a comparison between xenU_defconfig_x86_32 and xen0_defconfig_x86_32. 
It seems that whole "Character devices" category is de-selected, which should 
have the effect to disable CONFIG_VT for xenU.

Actually what confusing me is how to support different configuration file 
copied to xen0_defconfig_ia64 automatically when build. Current 
xen0_defconfig_ia64 is based on zx box configuration, and I have to copy one 
for tiger manually to override that file before build. However I didn't find 
easy way to pass into such machvec information and let it automate. Can anyone 
help with an idea?

Thanks,
Kevin

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.