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

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

> 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.

I tried  changing all the config options in that category
from =y to =n and make oldconfig just returns them to =y.
Does removing the lines altogether have a different result?

> 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?

I've been thinking that linux/arch/ia64/defconfig might
work for both HP and tiger4, but since it uses many modules,
I have been waiting to try it until the boot-dom0-with-initrd
works (RHEL4).

Perhaps just changing all the =m to =y in linux/arch/ia64/defconfig
will work for a xen0_defconfig_ia64 for both HP and tiger4?

Dan

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