Skip to content

Remove HP X677 quirks#125

Open
fabled wants to merge 1 commit intoOpenPrinting:masterfrom
fabled:remove-x677-quirk
Open

Remove HP X677 quirks#125
fabled wants to merge 1 commit intoOpenPrinting:masterfrom
fabled:remove-x677-quirk

Conversation

@fabled
Copy link
Copy Markdown
Contributor

@fabled fabled commented Mar 15, 2026

The firmware 5.9.0.2 (Aug 27, 2025) contains a proper fix.

The firmware 5.9.0.2 (Aug 27, 2025) contains a proper fix.
@alexpevzner
Copy link
Copy Markdown
Member

Looks like I've missed this PR...

One question. If this quirk doesn't conflict with new firmware, may be it is better not to remove this quirk, for users, who didn't upgrade their firmware?

@fabled
Copy link
Copy Markdown
Contributor Author

fabled commented May 7, 2026

The quirk does not reliable fix it - even if it improves situation. The downside of the quirk is that it has negative impact to performance.

Also the current X677 firmware has another issue that crashes the printer occasionally. HP is fixing this to the next release.

Would it then instead make sense to add a quirk for minimum required firmware version?

@alexpevzner
Copy link
Copy Markdown
Member

Would it then instead make sense to add a quirk for minimum required firmware version?

Quirks are applied, based on the information available from USB,

Does bcdDevice contain the reliable information regarding firmware version?

@fabled
Copy link
Copy Markdown
Contributor Author

fabled commented May 7, 2026

Does bcdDevice contain the reliable information regarding firmware version?

Sadly no. Seems this is fixed to 1.0.

Perhaps quirk can then just check firmware version and compare it against IPP level reported version and print error/refuse to work if it's older then quirk mandates as minimum?

@alexpevzner
Copy link
Copy Markdown
Member

Perhaps quirk can then just check firmware version and compare it against IPP level reported version and print error/refuse to work if it's older then quirk mandates as minimum?

This is very difficult to implement. Many quirks are applied before the IPP conversation has been started (and some of them are required to be applied early). Implementing a 2-phase quirks processing overcomplicates things too much...

OK. Lets remove these quirks. I've occasionally created a merge conflict by adding a section to HP.conf. Could you please resolve it at your side? It should be pretty simple...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants