New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 845611 link

Starred by 2 users
Status: WontFix
Owner:
smbar...@chromium.org
Closed: Nov 2
Cc:
chirantan@chromium.org
za...@chromium.org
█ dbehr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

kidd: bring up amdgpu

Project Member Reported by smbar...@chromium.org, May 22 2018 
Bring up amdgpu on kidd.

Need, at the very least, the Vega M kernel patch series and latest firmware blobs from linux-firmware.

WIP backports: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1067196/1

Unknowns: do we need to build in the firmware? USE=builtin_fw_amdgpu which version of the polaris firmware needs to be built in if so?

Comment 1 by za...@chromium.org, May 22 2018

Cc: dbehr@chromium.org
+dbehr, who had a lot to say during the graphics meeting when I brought this up. There is a lot of existing work in backporting amdgpu to our kernels, and I would hate to have the work repeated.

Additionally, we will likely need to bring in the vga_switcheroo kernel module, which handles muxing displays for the two GPUs.

Comment 2 by dbehr@chromium.org, May 22 2018 

we should add vga_switcheroo module to our kernel to enable switching between both integrated and discrete gpus

and maybe look at bumbleebee project which is used to integrate both https://github.com/Bumblebee-Project/Bumblebee

Comment 3 by zalcorn@chromium.org, Sep 28 

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Comment 4 by smbar...@chromium.org, Nov 2

Status: WontFix (was: Assigned)
►

Sign in to add a comment