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

Issue 729846 link

Starred by 0 users
Status: WontFix
Owner:
█ tutankhamen@chromium.org
Last visit 27 days ago
Closed: Jun 2017
Cc:
vapier@chromium.org
█ h...@chromium.org
█ marc...@chromium.org
█ dbehr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

tegra freon kernel options not properly disabled

Project Member Reported by vapier@chromium.org, Jun 6 2017 
this commit attempted to disable framebuffer related options:
  https://chromium-review.googlesource.com/399619

but it doesn't actually work ... the "=n" syntax is not valid, so the config generation step ignores it and picks the defaults which turns things back on.

you need to use the form:
# CONFIG_FOO is not set

i tried to do that, but there's a bunch more config options that toggle and i don't know their implications.

Comment 1 by marc...@chromium.org, Jun 6 2017

Cc: h...@chromium.org
Owner: tutankhamen@chromium.org
Robert, do you have cycles to look at this?

Comment 2 by tutankhamen@chromium.org, Jun 26 2017 

Looking into it.

Comment 3 Deleted

Comment 4 by tutankhamen@chromium.org, Jun 27 2017 

vapier@chromium.org, I just tested it with nyan_big and I don't see frambuffer devices there.

Comment 5 by tutankhamen@chromium.org, Jun 27 2017

Status: WontFix (was: Available)
"CONFIG=n" syntax also should be valid because it means "don't compile this module". "# CONFIG is not set" isn't the same as "CONFIG=n" because it doesn't set any value for "CONFIG" and forces it to use the default value.
►

Sign in to add a comment