[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Xen on new Arndale 5250
Greetings, all. Last year I asked about an ARM development board, and Stefano kindly pointed me at the Arndale. I ordered one once they were available, and finally took some time to attempt to get it working. I crawled through _many_ threaded websites including the arndale wiki, linaro releases, and the various xenprojects for arndale. I'm at the point where I think I have most of a "cookbook recipe." So, instead of following a nested, multi-path journey through web pages, I captured one straight-through process with the intent that someone completely new to building Xen, Linux, and the Arndale could follow it in a long afternoon (believe me, it took me a LOT longer than that to get to this point). Of course it references all the real web pages for the sources of the instructions.
At the moment it seems like getting Xen itself compiled and running was the most straightforward part of the whole exercise, due to the clear documentation and rock solid makefiles. It's all the stuff around Xen that has been the battle...
One thing that is different is that on my first several attempts, I installed the cross-compiler environment, and built Xen that way. However, it was faster (less work, many fewer chances for me to mess something up) in my experiments to build Xen natively on the Arndale, under linaro 14.03. Even on the uSD, it was whippy fast. With that approach, Xen boots, seems happy, and launches dom0: ARNDALE5250 # bootm $xen_addr - $dtb_addr Startinllllllllllllllll- UART enabled - ... **********************************************
What's the etiquette for doing so? At the moment it is a 5-page Google Doc. Anyone interested if I clipped it and posted it directly to the list as text, or is there a better way to share it? -TC _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |