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

Issue 920477 link

Starred by 0 users
Status: Untriaged
Owner: ----
Cc:
█ pgeorgi@chromium.org
vapier@chromium.org
groeck@chromium.org
sonnyrao@chromium.org
█ vbendeb@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 3
Type: Feature



Sign in to add a comment

move away from /dev/mem

Project Member Reported by vapier@chromium.org, Jan 10 
can we figure out why we have /dev/mem enabled still ?

based on the history, seems like it came in via the large squash in 40ac8f67cd8aac6c6789327619e90f4148c769a7 for linux-3.2.  i don't see the knob in linux-3.0.

i see references in chameleon (video test suite), mosys, coreboot, and flashrom.

Comment 1 by sonny...@google.com, Jan 10 

I tried stracing flashrom on my caroline -- it looks like it's reading some coreboot tables from /dev/mem.

If I remove /dev/mem then flashrom is unable to read the main firmware image.
►

Sign in to add a comment