Repository navigation
ingenic: T41 eFuse code 0x6666 is T41ZX, and 0x4444 is T41A - #287
Merged
Merged
Conversation
The T41 SDK 1.2.0's own SPL (u-boot common/spl/spl.c) prints SUBSOCTYPE2 0x6666 as T41ZX and 0x4444 as T41A, and OpenIPC/u-boot's openipc-ingenic SPL, which builds the T41 bootloaders OpenIPC ships, copies that table. ipctool called 0x6666 "T41X", a grade the SDK has no name for, and did not know 0x4444, so a T41A came out "unknown". The SDK gives the T41XQ no code of its own: its U-Boot is the T41ZX's with another DDR skew. Checked on the qemu-bench T41 twin (OpenIPC/qemu-bench#331), ipcinfo -c from master against this branch: t41zx (0x6666) t41x -> t41zx t41a (0x4444) unknown -> t41a t41nq, t41n unchanged
PR Summary by QodoCorrect Ingenic T41ZX and T41A eFuse identification
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR |
openipc-ai
added a commit
to OpenIPC/qemu-bench
that referenced
this pull request
Nov 17, 2026
…IPC/ipctool#287 (#332) * ingenic: ipctool names the T41ZX and T41A as the SPL does, since OpenIPC/ipctool#287 The T41 grade notes said ipctool calls 0x6666 "T41X" and does not know 0x4444. OpenIPC/ipctool#287 names them T41ZX and T41A, as the T41 SDK's SPL does; checked on this twin then (t41x -> t41zx, unknown -> t41a). Comment and docs only. * ingenic: state the T41 ipctool names as they are, and which ipctool still says T41X
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The T41 SDK 1.2.0's own SPL (u-boot common/spl/spl.c) prints SUBSOCTYPE2
0x6666 as T41ZX and 0x4444 as T41A, and OpenIPC/u-boot's openipc-ingenic
SPL, which builds the T41 bootloaders OpenIPC ships, copies that table.
ipctool called 0x6666 "T41X", a grade the SDK has no name for, and did
not know 0x4444, so a T41A came out "unknown".
The SDK gives the T41XQ no code of its own: its U-Boot is the T41ZX's
with another DDR skew.
Checked on the qemu-bench T41 twin (OpenIPC/qemu-bench#331), ipcinfo -c
from master against this branch:
t41zx (0x6666) t41x -> t41zx
t41a (0x4444) unknown -> t41a
t41nq, t41n unchanged