To make it clear: 1) This was bug in openChrome driver 2) We were touching reserved bits of 0x2A register (bug) 3) Bug didn't exist in last release 0.2.903 and we belive it doesn't exist in current trunk (actually from revision 746 == 25.04.2009)
Great explaination was provided in openChrome's ticket's comment: http://www.openchrome.org/trac/ticket/288#comment:24
To make it clear:
1) This was bug in openChrome driver
2) We were touching reserved bits of 0x2A register (bug)
3) Bug didn't exist in last release 0.2.903 and we belive it doesn't exist in current trunk (actually from revision 746 == 25.04.2009)
Great explaination was provided in openChrome's ticket's comment: http:// www.openchrome. org/trac/ ticket/ 288#comment: 24