From 69acc5f3928f0578438cefdd69b39bc05bb0769b Mon Sep 17 00:00:00 2001 From: duerpei Date: Thu, 14 Apr 2022 10:01:20 +0800 Subject: [PATCH] Readme: Correct some spelling mistakes Bug-AGL:SPEC-4325 Signed-off-by: duerpei Change-Id: I3a315c9c17a1745554b08f277399564104f37fac --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 84af0a7..aa6cc2d 100644 --- a/README.md +++ b/README.md @@ -47,18 +47,18 @@ So, for example, a DRM lease for the first LVDS device on the device `/dev/dri/c ### Dynamic lease transfer When `drm-lease-manager` is started with the `-t` option, the -ownership of a leases resourses can be transfered from +ownership of a leases resources can be transferred from one client to another. This allows the ownership of the leased resources to be transferred without the display being closed and the screen blanking. -`drm-lease-manager` handles the timing of the tranfser and manages the +`drm-lease-manager` handles the timing of the transfer and manages the references to the DRM device, so that the last framebuffer of the old client stays on screen until the new client presents its first frame. The transition can be completed without direct communication between the old and new client applications, however, the client that the lease will be -transitioned *from* must be able to handle unexpected lease revokation. +transitioned *from* must be able to handle unexpected lease revocation. Once the lease is revoked, all DRM API calls referring to the DRM resources managed by the lease will fail with -ENOENT. The client should be able to gracefully handle this condition by, for example, -- 2.16.6