-
Notifications
You must be signed in to change notification settings - Fork 349
Remove legacy Intel platforms #7000
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we also remove hsw please? It was never supported...
scripts/qemu-check.sh
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and remove bdw as well btw.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
skl kbl are also questionable now that I read the whole line
|
@plbossart this is just the first step, more to come |
|
Thank you for the update. Yesterday I updated SOF Docker image, every platform has 15-20min build time. It will save the build time a lot. |
You're talking about the toolchains, right?
|
|
There are some scripts / tests that don't contain Intel platforms newer than cAVS2.0, i.e. after we complete legacy clean up they won't contain any Intel hardware. Do we need those scripts or are they deprecated? Those that I've found are:
Then there's the tone generator, the test for which is configured for Baytrail
And one more test set is using an Apollo Lake configuration
|
4f3e69f to
f200b67
Compare
|
some statistics: |
|
"merge commit" only to resolve a conflict to run CI jobs, will be rebased properly before upstreaming of course |
67280b1 to
05f0dda
Compare
kv2019i
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, that is a thorough job (and a lot to review). A few minor notes. As a generic comment, I'd like to see a "supported in stable-v2.2" series comment in all the commits to give some more hints on what this is about.
src/platform/Kconfig
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to add a mention that these platforms will be supported in the stable-v2.2 branch.
installer/GNUmakefile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could start with one platform and get the merged. This is getting bewildering to review. Here it seems we are adding back support in middle of the series.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a comment. It's true, I wanted to move it back to not remove them in the first place, but forgot. It has a comment in line 26 that these are the platforms kept in 2.3, so no reason to remove them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see why you are doing this, but this is bumping up the review effort. I'm mentally scanning for changes that only cover platforms, so this kind of stuff jumps out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is related to this patch - it removes "sue" ;-) Obviously, that's why I hit this and other typos fixed in this PR, personally I'd keep these changes - they are tiny and obvious comments, but can trivially be extracted too...
.travis.yml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After whole series applied, "icl" is still left here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't touch .travis.yml, it has not been used since we moved to Github Actions. There's another PR to finalize the transfer to Github Actions and remove it.
Agree 200%, it's hard to merely scroll up and down. Focus on one or two platforms to set a template, ease the review pain and give all various CIs time to adjust: they should be able to remove all deprecated platforms with a small number of changed lines. Most of this has been done already. After the first removal is merged and CI back to normal then removing all the other ones should be easy and require barely any review. |
we can merge them individually, sure, but that won't make them or the review effort smaller. To avoid redundant reviewing, if after reviewing one of them you notice something that you think is likely to repeat in other patches you can just comment that and stop reviewing. But really, there isn't much to review here. Most of these changes are removing complete files and directories. |
Not each platform individually. Just one platform first, properly reviewed thanks to a reasonable size and nothing off-topic, then well tested in all CIs over a few days after merge. Then mass duplication to all the other platforms at once in a giant PR that is barely looked at and rubber-stamped. |
|
@lyakh can we make this PR byt/cht only as we can see impact of the merge on CI and adjust one by one. |
@lgirdwood sure, I'll update it |
|
@lyakh its probably a lot easier to split this PR up into one PR per patch above for review and merging and do one by one. |
|
Remove all support for Sue Creek platforms, it isn't supported any more. Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
No description provided.