OpenPrinting / OpenPrinting/splix
RFC: Reverse engineered Samsung CMS tested on CLP-310N
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 48
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
This is a request for comments as I have used a Cursor AI to reverse engineer the proprietary bits of the CMS out of the ULD.
https://github.com/HeyMeco/splix/commit/73a1b6eba6e096734932fe0c1841eaaf7bb59894
In my testing comparing the prints from both the linked commit produces identical results. Is this something that can be upstreamed to splix?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked splix commit 73a1b6eba6e096734932fe0c1841eaaf7bb59894 and the CMS-related driver changes it contains. Compare its behavior with the current driver and the reported CLP-310N print results; done means the upstream suitability and required scope are clearly decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100