-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CEA608 changes to pass Sarnoff tests #4900
Conversation
1. NTSC parity and validity bit check added 2. process_cc_data_flag check added 3. PAINT ON mode support added 4. Fixed line alignment issues for multi-line text 5. Fixed issue of dropping too many duplicate control commands 6. Fix for showing CC1 even if other channels are selected 7. Filtering out TEXT and XDS content 8. Fix for missing whitespaces when italic or other mid-row formatting is used 9. Fix for NTSC Deleted tests of sarnoff 10. Log illegal control codes instead of throwing exception
As noted on previous pull requests, if you can describe the change in the form of 10 bullet points, it should really be split into 10 pull requests, or at least 10 commits within a single pull request so the changes can be looked at in isolation. It's really hard to review changes where everything is just squashed together like this. |
okie :-) |
Splitting this change into smaller change sets: |
Second pull request: |
Is this an accurate reflection of the current state for merging these changes:
(2) and (6) sound relatively trivial to get merged next (although I didn't look at which code changes those correspond to). Possibly (7) and (10) as well? |
Yes, that state seems to be correct. I have a list of all commits with comments what changes can be squashed in what order, so the next ones on my list are:
|
Handling channel bit: #5390 |
Is it just (9) and (10) from the original list at the top of this pull request that are still outstanding? Are we close enough that this pull request can be closed? Thanks! |
Closing this since most of it has landed elsewhere. If there are pending changes (e.g. for (9) and (10)), I would assume they will come as separate pull requests). Thanks for your help! |
is used