Repository navigation
ingenic: a T41NQ that reports the T40 family's SoC ID - #285
Conversation
An owner's T41NQ reads 0x10040003 at 0x1300002c, the T40 family's ID, with grade code 0xAAAA at 0x13540250. The T40 branch had no name for 0xAAAA and the chip came out as unknown; it is a T41NQ (34), and the family is T41. The four T40 grades are unchanged. OpenIPC/majestic#376
PR Summary by QodoRecognize T41NQ devices that report a T40 SoC ID
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
Code Review by Qodo
1.
|
Review on #285: routing it to T41 takes away the T40 pad table it was given while it came out unknown. That table describes a T40's pins; with none, pad lookups refuse instead of muxing a T41 pin by a T40 function name.
|
On the Qodo finding T41NQ loses its T40 pad table: this is right about the mechanism, but the T40 table was never this chip's to keep. Before this PR, As a T41 it now has no table, so |
An owner's T41NQ (OpenIPC/majestic#376) reads
0x10040003at0x1300002c, the T40 family's ID, with grade code0xAAAAin the upper half of0x13540250.get_cpu_id()therefore takes its T40 branch, which has no0xAAAA, and the camera comes out asunknown.0xAAAAunder the T40 ID now maps to T41NQ, with the family set to t41. The four T40 grades (0x1111,0x8888,0x7777,0x4444) are unchanged, and no T40 grade uses0xAAAA. This is the mapping the owner had patched in locally, and it reportedt41nq/t41on their device.Tested on the qemu-bench T41NQ twin, which now reports that measured SoC ID: