Hi,
On 02/22/2017 02:11 PM, Julien Grall wrote:
On 22/02/17 13:19, Ian Jackson wrote:
Julien Grall writes ("Re: [Xen-devel] [linux-linus test] 104684:
regressions - FAIL"):
On 14/02/17 17:42, Wei Liu wrote:
(test-lab)liuw@osstest:~/testing.git$ ./mg-hosts showprops | grep
DTUART | grep arndale
arndale-bluewater XenDTUARTPath /serial@12C20000
arndale-lakeside XenDTUARTPath /serial@12C20000
arndale-metrocentre XenDTUARTPath /serial@12C20000
arndale-westfield XenDTUARTPath /serial@12C20000
That's a property of this kind of hosts in osstest. It needs to be
updated by the administrator (Ian).
Ian, could you change the XenDTUARTPath property for the arndale from
"/serial@12C20000" to "serial0"?
Done.
This should hopefully fix boot of Linux upstream on the board and keep
compatibility with the previous version of Linux.
Let's hope it doesn't break anything :-).
Thank you! I will watch next flights on osstest.
Sounds like this trick didn't work ([1]) and we also lost xen log for
the other the flights (see xen-unstable-smoke [2]) thought they are
still passing.
Looking at the device-tree again, I thought the serial aliases were
existing in 3.16.7-ctk one but it seems that I looked at the wrong DT.
Sorry for that.
This means that the path to the serial is different between 3.16 and
4.10 and we have no common one. For now, I would revert it.
A per-flight override sounds quite ugly, so I am not sure how to solve
this in the future. Any opinions?
Regardless that I gave the wrong alias on the previous e-mail for 4.10.
Below the list of serial alias:
serial0 = "/soc/serial@12C00000";
serial1 = "/soc/serial@12C10000";
serial2 = "/soc/serial@12C20000";
serial3 = "/soc/serial@12C30000";
So for the alias should be serial2.
Cheers,
[1] http://logs.test-lab.xenproject.org/osstest/logs/106009/test-armhf-
armhf-xl/info.html
[2]
http://logs.test-lab.xenproject.org/osstest/logs/106021/test-armhf-armhf-xl/info.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
