Skip to content

gk7206v100: SC465SL image tuning and its AI noise reduction network - #2905

Merged
openipc-ai merged 3 commits into
masterfrom
gk7206v100-image-tuning
Nov 19, 2026
Merged

openipc-ai merged 3 commits into
masterfrom
gk7206v100-image-tuning

Conversation

@openipc-ai

Copy link
Copy Markdown
Collaborator

On a GK7206V11 + SC465SL every ISP block ran on the ISP library's generic
defaults -- the SDK publishes no tuning for this sensor -- and the picture
was far noisier and bluer than the stock Xiongmai firmware's on the same
camera. Two files close that:

  • /etc/sensors/iq/sc465sl.bin (goke-osdrv-gk7206v100): an SDK PQ bin, the
    ISP, AE and AWB parameter blocks xmedia_isp_import() loads, carrying the
    tuning the vendor firmware applies to this sensor (Xiongmai
    IPC_GK7206V11_K8, V1.10.T02.20261103): its per-ISO noise reduction,
    sharpening, demosaic, defect-pixel, gamma, DRC, dehaze, LCE and colour
    tables, AWB calibration and AE compensation curve, over the SDK's
    defaults. majestic reads /etc/sensors/iq/.bin by default
    (isp.iqProfile).
  • /usr/share/aiisp/sc465sl/ainr_2560x1440.xmm (hisilicon-opensdk, bumped to
    560559da, which adds the SDK's networks beside the sensor drivers): the
    AINR network the ISP runs on the NPU, byte-identical to the one the
    vendor firmware ships. Only SC465SL is installed, the sensor measured on
    a camera.

Tested on an XM IVG-K8 (GK7206V11 + SC465SL) beside a stock one, dark
storeroom: with both files at these paths, from a cold start, the same
picture as the stock camera (125 ms / 8 fps, ISO ~19500 vs ~21000, AINR
active). gk7206v100_lite builds: squashfs 4600K, firmware.bin 6656/7616K.

On a GK7206V11 + SC465SL every ISP block ran on the ISP library's generic
defaults -- the SDK publishes no tuning for this sensor -- and the picture
was far noisier and bluer than the stock Xiongmai firmware's on the same
camera. Two files close that:

- /etc/sensors/iq/sc465sl.bin (goke-osdrv-gk7206v100): an SDK PQ bin, the
  ISP, AE and AWB parameter blocks xmedia_isp_import() loads, carrying the
  tuning the vendor firmware applies to this sensor (Xiongmai
  IPC_GK7206V11_K8, V1.10.T02.20261103): its per-ISO noise reduction,
  sharpening, demosaic, defect-pixel, gamma, DRC, dehaze, LCE and colour
  tables, AWB calibration and AE compensation curve, over the SDK's
  defaults. majestic reads /etc/sensors/iq/<sensor>.bin by default
  (isp.iqProfile).
- /usr/share/aiisp/sc465sl/ainr_2560x1440.xmm (hisilicon-opensdk, bumped to
  560559da, which adds the SDK's networks beside the sensor drivers): the
  AINR network the ISP runs on the NPU, byte-identical to the one the
  vendor firmware ships. Only SC465SL is installed, the sensor measured on
  a camera.

Tested on an XM IVG-K8 (GK7206V11 + SC465SL) beside a stock one, dark
storeroom: with both files at these paths, from a cold start, the same
picture as the stock camera (125 ms / 8 fps, ISO ~19500 vs ~21000, AINR
active). gk7206v100_lite builds: squashfs 4600K, firmware.bin 6656/7616K.
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

PR Summary by Qodo

Add SC465SL image tuning and AI noise reduction for GK7206V100

✨ Enhancement ⚙️ Configuration changes 🕐 20-40 Minutes

Grey Divider

AI Description

• Install SC465SL ISP tuning to replace generic defaults and improve low-light color and noise.
• Install the matching AINR network from the updated OpenSDK for NPU noise reduction.
• Verify the tuning blob during the build with a pinned SHA-256 checksum.
Merge Risk 🟡 Medium

Blast radius 🔴 High 💥 2 capabilities

  • 2 affected capabilities span independent functional scopes: GK7206V100 SC465SL camera imaging, OpenIPC SDK-backed hardware media integration.
  • The IQ binary, SC465SL configuration, sensor driver and optional AINR model all participate in the single end-to-end outcome of producing the SC465SL camera image.
  • They are implementation hops within one bounded camera integration, not separate capabilities.
  • The version variable selects the source for the SDK package, whose built drivers, modules and libraries are consumed by the image's hardware media runtime.
  • These are coordinated parts of one bounded SDK integration; the available repository evidence does not justify splitting them into independent functional scopes or naming unrelated application capabilities.
Sources

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[707-710]

	$(foreach a,$(HISILICON_OPENSDK_AINR_gk7206v100), \
		$(INSTALL) -D -m 0644 $(@D)/libraries/sensor/gk7206v100/$(word 1,$(subst :, ,$(a)))/$(word 3,$(subst :, ,$(a))).xmm \
			$(TARGET_DIR)/usr/share/aiisp/$(word 2,$(subst :, ,$(a)))/$(word 3,$(subst :, ,$(a))).xmm ; \
	)

general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[97-99]

	cd $(GOKE_OSDRV_GK7206V100_PKGDIR)/files/iq && sha256sum -c --quiet SHA256SUMS
	$(INSTALL) -m 755 -d $(TARGET_DIR)/etc/sensors/iq
	$(INSTALL) -m 644 -t $(TARGET_DIR)/etc/sensors/iq $(GOKE_OSDRV_GK7206V100_PKGDIR)/files/iq/*.bin

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[7-8]

HISILICON_OPENSDK_SITE = $(call github,openipc,openhisilicon,$(HISILICON_OPENSDK_VERSION))
HISILICON_OPENSDK_VERSION = 560559da3e58814d841f0624cd421990bd0b69bb

general/package/goke-osdrv-gk7206v100/files/sensor/config/sc465sl_i2c_4M.ini[75-78]

op_type=MANUAL       ;MANUAL: pos_gain/gau_gain below; AUTO: per-ISO table
pos_gain=64
gau_gain=64
model=/usr/share/aiisp/sc465sl/ainr_2560x1440.xmm
Behavioral complexity 🟡 Medium 🧩 Compatibility cases

  • Before: the Buildroot integration selected the previous external SDK revision.
  • After: it selects a different revision while retaining the existing build/install contracts.
  • New correctness condition: the new producer revision must remain compatible with the repository's expected source layout, build interfaces, generated artifacts, ABI/module contracts and downstream runtime consumers.
  • This is a compatibility transition, not merely reuse of an unchanged mapping helper; the concrete mixed-version and artifact cases cannot be fully checked because the external source is unavailable.
Sources

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[7-8]

HISILICON_OPENSDK_SITE = $(call github,openipc,openhisilicon,$(HISILICON_OPENSDK_VERSION))
HISILICON_OPENSDK_VERSION = 560559da3e58814d841f0624cd421990bd0b69bb
Potential damage 🟡 Medium 🩹 Recoverable

  • A wrong tuning profile can visibly degrade camera output without implying persistent-state corruption or external side effects.
  • Reverting the image or replacing the IQ/profile assets restores the prior software behavior; no persistent camera state repair is shown as necessary.
  • If the optional AINR path is enabled and its model is unsuitable, disabling it or restoring the prior configuration is likewise a supported code/configuration recovery, subject to rebuilding and redeploying the image.
  • Recoverable through firmware/configuration rollback or replacement of the tuning assets.
  • The sources do not show automatic runtime repair, persistent state mutation, or compensation for external effects.
Sources

general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[97-99]

	cd $(GOKE_OSDRV_GK7206V100_PKGDIR)/files/iq && sha256sum -c --quiet SHA256SUMS
	$(INSTALL) -m 755 -d $(TARGET_DIR)/etc/sensors/iq
	$(INSTALL) -m 644 -t $(TARGET_DIR)/etc/sensors/iq $(GOKE_OSDRV_GK7206V100_PKGDIR)/files/iq/*.bin

general/package/goke-osdrv-gk7206v100/files/sensor/config/sc465sl_i2c_4M.ini[75-78]

op_type=MANUAL       ;MANUAL: pos_gain/gau_gain below; AUTO: per-ISO table
pos_gain=64
gau_gain=64
model=/usr/share/aiisp/sc465sl/ainr_2560x1440.xmm

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[320-326]

# gk7206v100's AI noise reduction networks, which the ISP runs on the NPU:
# the SDK's own, kept beside each sensor driver as ainr_<W>x<H>.xmm and
# installed as /usr/share/aiisp/<sensor>/ainr_<W>x<H>.xmm (about 190 KB each
# in the squashfs). Only the sensors measured on a camera; add one here once
# it has been.
HISILICON_OPENSDK_AINR_gk7206v100 = \
	smartsens_sc465sl:sc465sl:ainr_2560x1440
Assessed commit 1ead5b4
Diagram

graph TD
  Tuning["SC465SL tuning"] --> Goke["Goke package"] --> IQ["IQ profile"] --> Runtime["ISP and NPU"]
  Network["SDK network"] --> OpenSDK["OpenSDK package"] --> AINR["AINR model"] --> Runtime
Loading
High-Level Assessment

Keep the assets in their respective packages: the Goke package owns ISP tuning, and OpenSDK supplies the sensor network. Selecting only the measured sensor's network limits rootfs growth; duplicating that network in the Goke package would obscure its SDK provenance.

Files changed (3) +30 / -1

Enhancement (2) +29 / -1
goke-osdrv-gk7206v100.mkInstall verified SC465SL ISP tuning +16/-0

Install verified SC465SL ISP tuning

• Checks the IQ binary against SHA256SUMS and installs sensor tuning binaries under /etc/sensors/iq. Documents the SC465SL tuning's purpose and default runtime lookup path.

general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk

hisilicon-opensdk.mkPin OpenSDK revision and install the SC465SL AINR network +13/-1

Pin OpenSDK revision and install the SC465SL AINR network

• Advances the OpenSDK commit to one containing sensor networks. Selects the SC465SL 2560×1440 network and installs it under /usr/share/aiisp/sc465sl for GK7206V100 builds.

general/package/hisilicon-opensdk/hisilicon-opensdk.mk

Other (1) +1 / -0
SHA256SUMSPin the SC465SL IQ binary checksum +1/-0

Pin the SC465SL IQ binary checksum

• Adds a SHA-256 digest for sc465sl.bin so the package install can reject a changed or truncated tuning blob.

general/package/goke-osdrv-gk7206v100/files/iq/SHA256SUMS

@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (2) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Grey Divider


Action required

1. Ships a vendor-extracted tuning binary 📘 Rule violation ⚙ Maintainability
Description
The gk7206v100 install rule ships checked-in sc465sl.bin tuning taken from Xiongmai stock firmware
through its *.bin glob, without naming an SDK release or build step that produces it. Every
gk7206v100 image receives those bytes, but the tuning cannot be rebuilt or meaningfully reviewed and
maintained from a source; the SHA256 check only confirms that the committed bytes are unchanged.
Code

general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[R92-93]

+	$(INSTALL) -m 755 -d $(TARGET_DIR)/etc/sensors/iq
+	$(INSTALL) -m 644 -t $(TARGET_DIR)/etc/sensors/iq $(GOKE_OSDRV_GK7206V100_PKGDIR)/files/iq/*.bin
Evidence
The new comment attributes sc465sl.bin to Xiongmai stock firmware, while the package’s SDK
provenance statement applies to its existing libraries rather than this tuning. The install rule
includes the blob in every gk7206v100 image, and neither the package nor the hash file identifies an
SDK release or buildable source for it; the checksum verifies the committed file, not a way to
regenerate it.

Rule 6: No binaries without a buildable source
CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source: CLAUDE.md: Do Not Add Binary Blobs or Extracted Vendor Code Without Buildable Source
general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[79-93]
general/package/goke-osdrv-gk7206v100/files/iq/SHA256SUMS[1]
general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[21-25]
general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[83-93]
pr_compliance_checklist.yaml[23-35]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`sc465sl.bin` is tuning taken from Xiongmai stock firmware and shipped to every gk7206v100 image without a named SDK release or buildable source from which it can be reviewed, rebuilt, or maintained.
## Fix Focus Areas
- general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[79-93]
- general/package/goke-osdrv-gk7206v100/files/iq/SHA256SUMS[1]
## Recommended Fix
Remove the factory-derived binary from this PR and drop its `sha256sum -c` check and `*.bin` install until a maintainable source exists. Replace it with tuning traceable to a named vendor SDK release or a buildable source, such as SDK PQ tool output or a text table built into a bin by the package; alternatively, submit a small, reviewable delta over SDK defaults. Document the replacement’s provenance alongside the install rule.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

2. HiSilicon SDK pin loses full SHA length 📘 Rule violation ☼ Reliability
Description
HISILICON_OPENSDK_VERSION changes from the 40-character SHA
5a18160707292296866e5b047fb2d03f9f2ee9a5 to the 8-character 560559da, which is less specific. A
later clean build can resolve a different commit if the short prefix becomes ambiguous or is
rewritten.
Code

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[8]

+HISILICON_OPENSDK_VERSION = 560559da3e58814d841f0624cd421990bd0b69bb
Evidence
Rule 15 flags a *_VERSION with fewer hex characters than the value it replaces, and rule 26 names
a shortened new SHA. The removed value is a 40-character SHA and the new one is 8 characters, so
both criteria are met. The package's short-SHA convention does not excuse the change, because the
previous pin was already full length.

Rule 15: Version pins do not loosen, and help text agrees with SITE
CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources: CLAUDE.md: Use Trustworthy, Precisely Pinned Package Sources
general/package/hisilicon-opensdk/hisilicon-opensdk.mk[7-8]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
Issue description: `HISILICON_OPENSDK_VERSION` was bumped from a 40-character SHA to the 8-character `560559da`, which lowers the specificity of the pin.
Fix Focus Areas:
- general/package/hisilicon-opensdk/hisilicon-opensdk.mk[7-8]
Recommended Fix: Look up the full commit SHA for 560559da in OpenIPC/openhisilicon and set `HISILICON_OPENSDK_VERSION` to that 40-character value, leaving the rest of the line unchanged.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


3. The new noise reduction stays disabled 🐞 Bug ≡ Correctness
Description
The new AINR install rule adds a model but does not change the shipped SC465SL sensor
configuration's enable=FALSE setting. On the default configuration, adding the model alone does
not activate the noise-reduction block.
Code

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[R325-326]

+HISILICON_OPENSDK_AINR_gk7206v100 = \
+	smartsens_sc465sl:sc465sl:ainr_2560x1440
Evidence
The PR selects and installs an AINR model, but the SC465SL configuration installed in the same image
explicitly sets [isp_ainr] enable=FALSE.

general/package/hisilicon-opensdk/hisilicon-opensdk.mk[325-326]
general/package/goke-osdrv-gk7206v100/files/sensor/config/sc465sl_i2c_4M.ini[73-78]
general/package/goke-osdrv-gk7206v100/goke-osdrv-gk7206v100.mk[76-77]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new AINR model is shipped, but the SC465SL sensor configuration still disables AINR.
## Fix Focus Areas
- general/package/hisilicon-opensdk/hisilicon-opensdk.mk[325-326]
- general/package/goke-osdrv-gk7206v100/files/sensor/config/sc465sl_i2c_4M.ini[73-78]
## Recommended Fix
If this change is intended to make AINR active by default, enable it in the SC465SL configuration after validating its operating frame rate. Otherwise, state explicitly that the installed network is only for opt-in use.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


4. Enabling noise reduction misses its model ✓ Resolved
Description
The new install rule writes ainr_2560x1440.xmm under /usr/share/aiisp/sc465sl, but the SC465SL
sensor configuration names /usr/lib/sensors/sc465sl_ainr_2560x1440.xmm. If AINR is enabled using
that shipped configuration, its configured model path does not resolve to the installed file.

Grey Divider

Tip of the day
💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

…P state

The first export took the noise-reduction and sharpening tables from an
emulation of the vendor application's init path, which misses what it
rewrites at run time. Running the whole stock firmware in the
gk7206v11a QEMU twin and exporting there gives tables that, at a stock
camera's ISO, reproduce what that camera reports live (TNR thresholds,
chroma strength, sharpen texture and overshoot); the old ones did not.
On an IVG-K8 at ISO ~20000: visibly less grain, the stock look.
@openipc-ai

Copy link
Copy Markdown
Collaborator Author

Updated sc465sl.bin (f2e965d). The first version's noise-reduction and sharpening tables came from emulating only the vendor App's init path, which misses what the App rewrites while it runs. The new bin's ISP blocks are read from the stock firmware running in the qemu-bench gk7206v11a twin (OpenIPC/qemu-bench#344). Interpolated to a stock camera's ISO, those tables reproduce what that camera reports live in /proc/umap/isp (TNR motion thresholds 32/65, chroma strength 248, sharpen texture 16, overshoot 86). The old tables gave 22/43, 224, 13 and 113. On an IVG-K8 at ISO ~20000 the picture shows visibly less grain.

…rk; sc465sl.bin provenance

The [isp_ainr] model path pointed at /usr/lib/sensors, where nothing
installs a network; hisilicon-opensdk installs it under
/usr/share/aiisp/sc465sl. The comment on sc465sl.bin now names the tool
that regenerates it and records that it is interim, to be replaced by a
text profile built from source.
@openipc-ai

Copy link
Copy Markdown
Collaborator Author

Review follow-up (1ead5b4):

  1. sc465sl.bin without a buildable source. Acknowledged. The maintainers are landing it as an interim exception: no SDK release carries SC465SL tuning, and without it the camera runs the ISP library's generic defaults. The .mk comment now names what regenerates it (tools/xm-isp-tuning: a Xiongmai GK7206 camera's ISP tuning, as an SDK PQ bin qemu-bench#344, tools/xm-isp-tuning, from the stock dump) and records the commitment to replace it with a text profile built from source, once there are more boards in the lab to check one against the vendor's picture.
  2. Short SHA. Not the case: the new HISILICON_OPENSDK_VERSION is the full 560559da3e58814d841f0624cd421990bd0b69bb.
  3. AINR off in the .ini. Intended. That [isp_ainr] enable belongs to the .ini's consumer; majestic decides AINR from its own isp.aibnr, which is on, with the frame rate capped for the NPU (isp.aibnrFps, 20 at 2560x1440, measured with no dropped frames).
  4. Model path. Fixed: the SC465SL profile now names /usr/share/aiisp/sc465sl/ainr_2560x1440.xmm, where the network is installed.

openipc-ai added a commit to OpenIPC/qemu-bench that referenced this pull request Nov 19, 2026
… PQ bin (#344)

* tools: xm-isp-tuning -- a Xiongmai camera's ISP tuning out of a dump, as an SDK PQ bin

Xiongmai's firmware for GK7206V1 cameras tunes the ISP from per-sensor
tables compiled into its App; the XMedia SDK publishes no tuning for most
sensors, so firmware running the SDK alone gets the ISP library's generic
defaults -- on an IVG-K8 (GK7206V11 + SC465SL) a far noisier, bluer
picture than the stock firmware's on the same board.

xm-isp-capture.py runs the stock App's ISP monitor thread under Unicorn
(libc stubbed, the statically linked SDK returning 0, the SDK's attribute
setters and getters caught) and records what the App puts in force, block
by block, as the SDK's own structures. xm-isp-finish drops what the App
sets at run time instead of from tables; on the camera attrtool applies the
set, ae-ainr the AE curve and AINR switch points, and pqexport writes the
PQ bin xmedia_isp_import() loads. The addresses for one App build
(V1.10.T02.20261103) are a JSON profile.

Measured: applied to an OpenIPC IVG-K8 beside a stock one in low light
(ISO ~20000, 125 ms), the same picture; re-running the capture reproduces
the set behind the SC465SL profile in OpenIPC/firmware#2905 byte for byte;
the camera tools run on the board as built.

* tools/xm-isp-tuning: export the live ISP state from the stock firmware in the twin

Booting the stock GK7206V11 firmware in gk7206v11a and dumping the ISP
there gives the App's runtime tables, which the Unicorn capture misses
for STNR, BNR temporal, sharpen and LCE. Checked against a stock
camera's /proc/umap/isp at two ISOs.

* tools/xm-isp-tuning: review fixes

- attrtool: creates the dump directory, writes no block for a failed
  getter, checks its writes, exits non-zero on any failed get, set or
  missing file, and logs line by line (a crashing getter -- smart_info
  under the stock App -- no longer swallows the log).
- ae-ainr: reports the AE and AINR results separately and fails if
  either did; no uninitialised AINR fields on a failed read.
- xm-isp-finish: creates its output directory.
- build.sh: a failed compile fails the build instead of keeping an old
  binary; with SDK_STATIC it also builds the static tools the twin route
  types in (camera/sdkshim_static.c, the uClibc gaps of the SDK's static
  objects).
- xm-twin-export.py: writes <block>.bin as xm-isp-finish reads them;
  checks each command's exit status; verifies every file against
  hexout's length and checksum, re-requesting damaged ones (the App's
  log can cut a hex line); requires the PQ export and the NR/sharpen
  blocks; lists the dump with a shell loop (this busybox colours ls);
  sets xmuart=0 in a copy of the flash itself, keeping every other
  saved variable.

Two full twin runs give byte-identical ISP blocks, and the README's
route (export, AWB from the capture, finish) reproduces the shipped
sc465sl set exactly.

* tools/xm-isp-tuning: attrtool apply refuses a block name it does not know
@openipc-ai
openipc-ai merged commit c74ba39 into master Nov 19, 2026
82 checks passed
@openipc-ai
openipc-ai deleted the gk7206v100-image-tuning branch November 19, 2026 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant