- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
05219 | Misc. | Minor | Always | Jun 25, 2013, 17:39 | Jul 4, 2013, 21:02 |
Tester | hap | View Status | Public | Platform | |
Assigned To | hap | Resolution | Fixed | OS | |
Status [?] | Resolved | Driver | |||
Version | 0.149 | Fixed in Version | 0.149u1 | Build | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 05219: tetrisp2: Priority RAM test fails. | ||||
Description | Priority RAM test fails. | ||||
Steps To Reproduce | Go to testmode and do the memory test. | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | 0.135u1 | ||||
Affected Sets / Systems | tetrisp2 | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
4
No.09615
Tafoid Administrator
Jun 25, 2013, 21:05
|
Source states: - Priority RAM is not taken into account. In TODO. This isn't a regression. |
---|---|
No.09617
Haze Senior Tester
Jun 26, 2013, 13:50
|
actually unrelated.. that just means the video code isn't properly using priority RAM yet (same for ms32.c) the real culprit is AM_RANGE(0x200000, 0x23ffff) AM_READWRITE8(tetrisp2_priority_r, tetrisp2_priority_w, 0x00ff) which sets the RAM up as 8-bit access only. the RAM test expects to be able to access 16-bits. chances are it's 16-bit ram and the video only gets hooked up to the lower 8-bits or something. |
No.09618
Tafoid Administrator
Jun 26, 2013, 14:14
|
I did some regression testing and it is indeed a regression. Noted at 0.135u1. |
No.09619
NekoEd Senior Tester
Jun 26, 2013, 14:44
|
Tafoid notes it's a regression, so that makes it a bug. Confirming. |