Loading Documentation/ABI/testing/ima_policy +6 −6 Original line number Diff line number Diff line Loading @@ -20,7 +20,7 @@ Description: lsm: [[subj_user=] [subj_role=] [subj_type=] [obj_user=] [obj_role=] [obj_type=]] base: func:= [BPRM_CHECK][FILE_MMAP][INODE_PERMISSION] base: func:= [BPRM_CHECK][FILE_MMAP][FILE_CHECK] mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC] fsmagic:= hex value uid:= decimal value Loading @@ -40,11 +40,11 @@ Description: measure func=BPRM_CHECK measure func=FILE_MMAP mask=MAY_EXEC measure func=INODE_PERM mask=MAY_READ uid=0 measure func=FILE_CHECK mask=MAY_READ uid=0 The default policy measures all executables in bprm_check, all files mmapped executable in file_mmap, and all files open for read by root in inode_permission. open for read by root in do_filp_open. Examples of LSM specific definitions: Loading @@ -54,8 +54,8 @@ Description: dont_measure obj_type=var_log_t dont_measure obj_type=auditd_log_t measure subj_user=system_u func=INODE_PERM mask=MAY_READ measure subj_role=system_r func=INODE_PERM mask=MAY_READ measure subj_user=system_u func=FILE_CHECK mask=MAY_READ measure subj_role=system_r func=FILE_CHECK mask=MAY_READ Smack: measure subj_user=_ func=INODE_PERM mask=MAY_READ measure subj_user=_ func=FILE_CHECK mask=MAY_READ Documentation/cpu-freq/governors.txt +2 −2 Original line number Diff line number Diff line Loading @@ -145,8 +145,8 @@ show_sampling_rate_max: THIS INTERFACE IS DEPRECATED, DON'T USE IT. up_threshold: defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then to its default value of '95' it means that between the checking intervals the CPU needs to be on average more than 95% in use to then decide that the CPU frequency needs to be increased. ignore_nice_load: this parameter takes a value of '0' or '1'. When Loading Documentation/fault-injection/fault-injection.txt +2 −2 Original line number Diff line number Diff line Loading @@ -143,8 +143,8 @@ o provide a way to configure fault attributes failslab, fail_page_alloc, and fail_make_request use this way. Helper functions: init_fault_attr_entries(entries, attr, name); void cleanup_fault_attr_entries(entries); init_fault_attr_dentries(entries, attr, name); void cleanup_fault_attr_dentries(entries); - module parameters Loading Documentation/feature-removal-schedule.txt +49 −0 Original line number Diff line number Diff line Loading @@ -493,3 +493,52 @@ Why: These two features use non-standard interfaces. There are the Who: Corentin Chary <corentin.chary@gmail.com> ---------------------------- What: usbvideo quickcam_messenger driver When: 2.6.35 Files: drivers/media/video/usbvideo/quickcam_messenger.[ch] Why: obsolete v4l1 driver replaced by gspca_stv06xx Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: ov511 v4l1 driver When: 2.6.35 Files: drivers/media/video/ov511.[ch] Why: obsolete v4l1 driver replaced by gspca_ov519 Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: w9968cf v4l1 driver When: 2.6.35 Files: drivers/media/video/w9968cf*.[ch] Why: obsolete v4l1 driver replaced by gspca_ov519 Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: ovcamchip sensor framework When: 2.6.35 Files: drivers/media/video/ovcamchip/* Why: Only used by obsoleted v4l1 drivers Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: stv680 v4l1 driver When: 2.6.35 Files: drivers/media/video/stv680.[ch] Why: obsolete v4l1 driver replaced by gspca_stv0680 Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: zc0301 v4l driver When: 2.6.35 Files: drivers/media/video/zc0301/* Why: Duplicate functionality with the gspca_zc3xx driver, zc0301 only supports 2 USB-ID's (because it only supports a limited set of sensors) wich are also supported by the gspca_zc3xx driver (which supports 53 USB-ID's in total) Who: Hans de Goede <hdegoede@redhat.com> Documentation/input/multi-touch-protocol.txt +40 −8 Original line number Diff line number Diff line Loading @@ -27,12 +27,30 @@ set of events/packets. A set of ABS_MT events with the desired properties is defined. The events are divided into categories, to allow for partial implementation. The minimum set consists of ABS_MT_TOUCH_MAJOR, ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which allows for multiple fingers to be tracked. If the device supports it, the ABS_MT_WIDTH_MAJOR may be used to provide the size of the approaching finger. Anisotropy and direction may be specified with ABS_MT_TOUCH_MINOR, ABS_MT_WIDTH_MINOR and ABS_MT_ORIENTATION. The ABS_MT_TOOL_TYPE may be used to specify whether the touching tool is a minimum set consists of ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which allows for multiple fingers to be tracked. If the device supports it, the ABS_MT_TOUCH_MAJOR and ABS_MT_WIDTH_MAJOR may be used to provide the size of the contact area and approaching finger, respectively. The TOUCH and WIDTH parameters have a geometrical interpretation; imagine looking through a window at someone gently holding a finger against the glass. You will see two regions, one inner region consisting of the part of the finger actually touching the glass, and one outer region formed by the perimeter of the finger. The diameter of the inner region is the ABS_MT_TOUCH_MAJOR, the diameter of the outer region is ABS_MT_WIDTH_MAJOR. Now imagine the person pressing the finger harder against the glass. The inner region will increase, and in general, the ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR, which is always smaller than unity, is related to the finger pressure. For pressure-based devices, ABS_MT_PRESSURE may be used to provide the pressure on the contact area instead. In addition to the MAJOR parameters, the oval shape of the finger can be described by adding the MINOR parameters, such that MAJOR and MINOR are the major and minor axis of an ellipse. Finally, the orientation of the oval shape can be describe with the ORIENTATION parameter. The ABS_MT_TOOL_TYPE may be used to specify whether the touching tool is a finger or a pen or something else. Devices with more granular information may specify general shapes as blobs, i.e., as a sequence of rectangular shapes grouped together by an ABS_MT_BLOB_ID. Finally, for the few devices Loading @@ -42,11 +60,9 @@ report finger tracking from hardware [5]. Here is what a minimal event sequence for a two-finger touch would look like: ABS_MT_TOUCH_MAJOR ABS_MT_POSITION_X ABS_MT_POSITION_Y SYN_MT_REPORT ABS_MT_TOUCH_MAJOR ABS_MT_POSITION_X ABS_MT_POSITION_Y SYN_MT_REPORT Loading Loading @@ -87,6 +103,12 @@ the contact. The ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR approximates the notion of pressure. The fingers of the hand and the palm all have different characteristic widths [1]. ABS_MT_PRESSURE The pressure, in arbitrary units, on the contact area. May be used instead of TOUCH and WIDTH for pressure-based devices or any device with a spatial signal intensity distribution. ABS_MT_ORIENTATION The orientation of the ellipse. The value should describe a signed quarter Loading Loading @@ -170,6 +192,16 @@ There are a few devices that support trackingID in hardware. User space can make use of these native identifiers to reduce bandwidth and cpu usage. Gestures -------- In the specific application of creating gesture events, the TOUCH and WIDTH parameters can be used to, e.g., approximate finger pressure or distinguish between index finger and thumb. With the addition of the MINOR parameters, one can also distinguish between a sweeping finger and a pointing finger, and with ORIENTATION, one can detect twisting of fingers. Notes ----- Loading Loading
Documentation/ABI/testing/ima_policy +6 −6 Original line number Diff line number Diff line Loading @@ -20,7 +20,7 @@ Description: lsm: [[subj_user=] [subj_role=] [subj_type=] [obj_user=] [obj_role=] [obj_type=]] base: func:= [BPRM_CHECK][FILE_MMAP][INODE_PERMISSION] base: func:= [BPRM_CHECK][FILE_MMAP][FILE_CHECK] mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC] fsmagic:= hex value uid:= decimal value Loading @@ -40,11 +40,11 @@ Description: measure func=BPRM_CHECK measure func=FILE_MMAP mask=MAY_EXEC measure func=INODE_PERM mask=MAY_READ uid=0 measure func=FILE_CHECK mask=MAY_READ uid=0 The default policy measures all executables in bprm_check, all files mmapped executable in file_mmap, and all files open for read by root in inode_permission. open for read by root in do_filp_open. Examples of LSM specific definitions: Loading @@ -54,8 +54,8 @@ Description: dont_measure obj_type=var_log_t dont_measure obj_type=auditd_log_t measure subj_user=system_u func=INODE_PERM mask=MAY_READ measure subj_role=system_r func=INODE_PERM mask=MAY_READ measure subj_user=system_u func=FILE_CHECK mask=MAY_READ measure subj_role=system_r func=FILE_CHECK mask=MAY_READ Smack: measure subj_user=_ func=INODE_PERM mask=MAY_READ measure subj_user=_ func=FILE_CHECK mask=MAY_READ
Documentation/cpu-freq/governors.txt +2 −2 Original line number Diff line number Diff line Loading @@ -145,8 +145,8 @@ show_sampling_rate_max: THIS INTERFACE IS DEPRECATED, DON'T USE IT. up_threshold: defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then to its default value of '95' it means that between the checking intervals the CPU needs to be on average more than 95% in use to then decide that the CPU frequency needs to be increased. ignore_nice_load: this parameter takes a value of '0' or '1'. When Loading
Documentation/fault-injection/fault-injection.txt +2 −2 Original line number Diff line number Diff line Loading @@ -143,8 +143,8 @@ o provide a way to configure fault attributes failslab, fail_page_alloc, and fail_make_request use this way. Helper functions: init_fault_attr_entries(entries, attr, name); void cleanup_fault_attr_entries(entries); init_fault_attr_dentries(entries, attr, name); void cleanup_fault_attr_dentries(entries); - module parameters Loading
Documentation/feature-removal-schedule.txt +49 −0 Original line number Diff line number Diff line Loading @@ -493,3 +493,52 @@ Why: These two features use non-standard interfaces. There are the Who: Corentin Chary <corentin.chary@gmail.com> ---------------------------- What: usbvideo quickcam_messenger driver When: 2.6.35 Files: drivers/media/video/usbvideo/quickcam_messenger.[ch] Why: obsolete v4l1 driver replaced by gspca_stv06xx Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: ov511 v4l1 driver When: 2.6.35 Files: drivers/media/video/ov511.[ch] Why: obsolete v4l1 driver replaced by gspca_ov519 Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: w9968cf v4l1 driver When: 2.6.35 Files: drivers/media/video/w9968cf*.[ch] Why: obsolete v4l1 driver replaced by gspca_ov519 Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: ovcamchip sensor framework When: 2.6.35 Files: drivers/media/video/ovcamchip/* Why: Only used by obsoleted v4l1 drivers Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: stv680 v4l1 driver When: 2.6.35 Files: drivers/media/video/stv680.[ch] Why: obsolete v4l1 driver replaced by gspca_stv0680 Who: Hans de Goede <hdegoede@redhat.com> ---------------------------- What: zc0301 v4l driver When: 2.6.35 Files: drivers/media/video/zc0301/* Why: Duplicate functionality with the gspca_zc3xx driver, zc0301 only supports 2 USB-ID's (because it only supports a limited set of sensors) wich are also supported by the gspca_zc3xx driver (which supports 53 USB-ID's in total) Who: Hans de Goede <hdegoede@redhat.com>
Documentation/input/multi-touch-protocol.txt +40 −8 Original line number Diff line number Diff line Loading @@ -27,12 +27,30 @@ set of events/packets. A set of ABS_MT events with the desired properties is defined. The events are divided into categories, to allow for partial implementation. The minimum set consists of ABS_MT_TOUCH_MAJOR, ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which allows for multiple fingers to be tracked. If the device supports it, the ABS_MT_WIDTH_MAJOR may be used to provide the size of the approaching finger. Anisotropy and direction may be specified with ABS_MT_TOUCH_MINOR, ABS_MT_WIDTH_MINOR and ABS_MT_ORIENTATION. The ABS_MT_TOOL_TYPE may be used to specify whether the touching tool is a minimum set consists of ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which allows for multiple fingers to be tracked. If the device supports it, the ABS_MT_TOUCH_MAJOR and ABS_MT_WIDTH_MAJOR may be used to provide the size of the contact area and approaching finger, respectively. The TOUCH and WIDTH parameters have a geometrical interpretation; imagine looking through a window at someone gently holding a finger against the glass. You will see two regions, one inner region consisting of the part of the finger actually touching the glass, and one outer region formed by the perimeter of the finger. The diameter of the inner region is the ABS_MT_TOUCH_MAJOR, the diameter of the outer region is ABS_MT_WIDTH_MAJOR. Now imagine the person pressing the finger harder against the glass. The inner region will increase, and in general, the ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR, which is always smaller than unity, is related to the finger pressure. For pressure-based devices, ABS_MT_PRESSURE may be used to provide the pressure on the contact area instead. In addition to the MAJOR parameters, the oval shape of the finger can be described by adding the MINOR parameters, such that MAJOR and MINOR are the major and minor axis of an ellipse. Finally, the orientation of the oval shape can be describe with the ORIENTATION parameter. The ABS_MT_TOOL_TYPE may be used to specify whether the touching tool is a finger or a pen or something else. Devices with more granular information may specify general shapes as blobs, i.e., as a sequence of rectangular shapes grouped together by an ABS_MT_BLOB_ID. Finally, for the few devices Loading @@ -42,11 +60,9 @@ report finger tracking from hardware [5]. Here is what a minimal event sequence for a two-finger touch would look like: ABS_MT_TOUCH_MAJOR ABS_MT_POSITION_X ABS_MT_POSITION_Y SYN_MT_REPORT ABS_MT_TOUCH_MAJOR ABS_MT_POSITION_X ABS_MT_POSITION_Y SYN_MT_REPORT Loading Loading @@ -87,6 +103,12 @@ the contact. The ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR approximates the notion of pressure. The fingers of the hand and the palm all have different characteristic widths [1]. ABS_MT_PRESSURE The pressure, in arbitrary units, on the contact area. May be used instead of TOUCH and WIDTH for pressure-based devices or any device with a spatial signal intensity distribution. ABS_MT_ORIENTATION The orientation of the ellipse. The value should describe a signed quarter Loading Loading @@ -170,6 +192,16 @@ There are a few devices that support trackingID in hardware. User space can make use of these native identifiers to reduce bandwidth and cpu usage. Gestures -------- In the specific application of creating gesture events, the TOUCH and WIDTH parameters can be used to, e.g., approximate finger pressure or distinguish between index finger and thumb. With the addition of the MINOR parameters, one can also distinguish between a sweeping finger and a pointing finger, and with ORIENTATION, one can detect twisting of fingers. Notes ----- Loading
Ingo Molnar <mingo@elte.hu>Ingo Molnar <mingo@elte.hu>