Skip to content

display_driver leaves: pydevices ships it now - #24

Merged
bdbarnett merged 1 commit into
mainfrom
display-driver-move
Oct 7, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
display-driver-move

Conversation

@bdbarnett

Copy link
Copy Markdown
Collaborator

LVGL's PyDevices coordinator moved to PyDevices/pydevices lib/ (PyDevices/pydevices#129). A firmware gets it with pydevices: frozen by micropython-pydevices' --modules pydevices (or all), or from mip.install("pydevices"). That's where its appdev, events, keys and multimer already come from. This repo now freezes and syncs fs_driver.py only.

This replaces #23, the byte-identical copy of lvgl-bindings#24; that frame-hook change is in pydevices' file.

Merge after PyDevices/pydevices#129. Then move micropython-pydevices' modules.lock pins for pydevices and lvgl-micropython together in one change. With only the pydevices pin moved, an all build freezes two display_driver.py files. lvgl-micropython's comes first in that manifest and wins, and it's the older one, without the frame hook. Nothing reports it.

pytest tests/test_integration.py: 3 pass. bash -n on the sync script.

LVGL's PyDevices coordinator moved to PyDevices/pydevices lib/, beside the
appdev, events, keys and multimer it imports, and comes with the pydevices
mip package or micropython-pydevices' --modules pydevices. This repo now
freezes fs_driver only and syncs only that from lvgl-bindings.

Replaces #23, whose frame-hook change is in pydevices' copy (PyDevices/pydevices#129).
Merge after #129: on its own this leaves a firmware without pydevices with
no display_driver, which it could not import anyway (it needs appdev).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant