| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
Re: [Xen-ia64-devel] serial console settings on Tiger4
Hi Simon,
On Wed, 2007-02-14 at 18:42 +0900, Horms wrote:
>
> Being greeted by a lovely not-working console this afternoon
Sorry about that, thanks for testing.
> I have set about testing this on Tiger2. Here are the results:
>
> Current tree (8bdbe88e422f): Broken
> Current tree - 7efb3a06c56a: Ok
> Current tree + Alex's first patch: Ok
> Current tree + Alex's first patch
> + Alex's second patch: Ok
> Current tree + Alex's first patch
> + Alex's second patch
> + Kawamura-san's patch: Ok
>
> So in short, while the current tree is broken, it
> seems pretty easy to make Tiger2 work.
>
> All of these tests were made with the following settings
> (ignore the irrelevant ones :)
>
> append="maxcpus=1 phys_efi com2=115200,8n1,0x2f8,0 console=com2
^^^^^^^^^^^^^^^^^^^^^^^
This should be unnecessary with all the patches applied. For a Tiger2,
com1 and com2 should be installed as 0x3f8 and 0x2f8 respectively. The
ns16550 driver _should_ be able to read the baud rate out of the UART.
> conswitch=bb sync_console dom0_max_vcpus=2 dom0_mem=1G
> crashkernel=256M
> -- clock=pit ip=on apm=power-off console=tty0 console=ttyS0,115200"
unnecessary -> ^^^^^^^
It's interesting that even on the Tiger2 you're using 0x2f8 as your
console. Is that typical? I'm wondering if we should handle both
Tiger2 and Tiger4 the same way and only setup com1 as 0x2f8. Then you
wouldn't even need the console=com2 option. Is 0x3f8 usable as a
console on either box? My impression from Kawamura-san was that Tiger4
didn't have a physical connection for 0x3f8, but Tiger2 might. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home