Skip to content
Snippets Groups Projects
Select Git revision
  • android-7.1.2_r28_klist
  • master default protected
  • pie-cts-release
  • pie-vts-release
  • pie-cts-dev
  • oreo-mr1-iot-release
  • sdk-release
  • oreo-m6-s4-release
  • oreo-m4-s12-release
  • pie-release
  • pie-r2-release
  • pie-r2-s1-release
  • oreo-vts-release
  • oreo-cts-release
  • oreo-dev
  • oreo-mr1-dev
  • pie-gsi
  • pie-platform-release
  • pie-dev
  • oreo-cts-dev
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
  • android-9.0.0_r3
40 results

file_contexts

  • Greg Hackmann's avatar
    7004789d
    Add policies for Atomic Display Framework · 7004789d
    Greg Hackmann authored
    
    ADF is a modern replacement for fbdev.
    
    ADF's device nodes (/dev/adf[X]), interface nodes
    (/dev/adf-interface[X].[Y]), and overlay engine nodes
    (/dev/adf-overlay-engine[X].[Y]) are collectively used in similar
    contexts as fbdev nodes.  Vendor HW composers (via SurfaceFlinger) and
    healthd will need to send R/W ioctls to these nodes to prepare and
    update the display.
    
    Ordinary apps should not talk to ADF directly.
    
    Change-Id: Ic0a76b1e82c0cc1e8f240f219928af1783e79343
    Signed-off-by: default avatarGreg Hackmann <ghackmann@google.com>
    7004789d
    History
    Add policies for Atomic Display Framework
    Greg Hackmann authored
    
    ADF is a modern replacement for fbdev.
    
    ADF's device nodes (/dev/adf[X]), interface nodes
    (/dev/adf-interface[X].[Y]), and overlay engine nodes
    (/dev/adf-overlay-engine[X].[Y]) are collectively used in similar
    contexts as fbdev nodes.  Vendor HW composers (via SurfaceFlinger) and
    healthd will need to send R/W ioctls to these nodes to prepare and
    update the display.
    
    Ordinary apps should not talk to ADF directly.
    
    Change-Id: Ic0a76b1e82c0cc1e8f240f219928af1783e79343
    Signed-off-by: default avatarGreg Hackmann <ghackmann@google.com>