diff for duplicates of <4E35EC23.1010701@gmx.de> diff --git a/a/1.txt b/N1/1.txt index f7f6c99..3249c77 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -38,7 +38,8 @@ On 07/31/2011 11:28 PM, Laurent Pinchart wrote: >> - write raw FOURCC values in nonstd, enable FOURCC mode if upper byte != 0 >> - not having an explicit flag to enable FOURCC >> - in FOURCC mode drivers must set visual to FB_VISUAL_FOURCC ->> - making support of FOURCC visible to userspace by capabilites |>> FB_CAP_FOURCC +>> - making support of FOURCC visible to userspace by capabilites |= +>> FB_CAP_FOURCC >> >> The capabilities is not strictly necessary but I think it's very useful as >> - it allows applications to make sure the extension is supported (for @@ -52,7 +53,7 @@ On 07/31/2011 11:28 PM, Laurent Pinchart wrote: > Without a FOURCC capability applications will need to try FOURCCs blindly. > Drivers that are not FOURCC aware would then risk interpreting the FOURCC as > something else. As you mention below applications will need that check that -> visual = FB_VISUAL_FOURCC, so it's less of an issue than I initially thought, +> visual == FB_VISUAL_FOURCC, so it's less of an issue than I initially thought, > but it doesn't become a non-issue. The display might still show glitches. True. @@ -62,7 +63,8 @@ True. >> - the application may check capabilities to know whether FOURCC is >> supported - the application may write a raw FOURCC value in nonstd to >> request changing to FOURCC mode with this format ->> - when the driver switches to a FOURCC mode it must have visual >> FB_VISUAL_FOURCC and the current FOURCC format in nonstd +>> - when the driver switches to a FOURCC mode it must have visual = +>> FB_VISUAL_FOURCC and the current FOURCC format in nonstd >> - the application should check visual and nonstd to make sure it gets what >> it wanted >> diff --git a/a/content_digest b/N1/content_digest index 66945b9..bb758ec 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -54,7 +54,8 @@ ">> - write raw FOURCC values in nonstd, enable FOURCC mode if upper byte != 0\n" ">> - not having an explicit flag to enable FOURCC\n" ">> - in FOURCC mode drivers must set visual to FB_VISUAL_FOURCC\n" - ">> - making support of FOURCC visible to userspace by capabilites |>> FB_CAP_FOURCC\n" + ">> - making support of FOURCC visible to userspace by capabilites |=\n" + ">> FB_CAP_FOURCC\n" ">>\n" ">> The capabilities is not strictly necessary but I think it's very useful as\n" ">> - it allows applications to make sure the extension is supported (for\n" @@ -68,7 +69,7 @@ "> Without a FOURCC capability applications will need to try FOURCCs blindly.\n" "> Drivers that are not FOURCC aware would then risk interpreting the FOURCC as\n" "> something else. As you mention below applications will need that check that\n" - "> visual = FB_VISUAL_FOURCC, so it's less of an issue than I initially thought,\n" + "> visual == FB_VISUAL_FOURCC, so it's less of an issue than I initially thought,\n" "> but it doesn't become a non-issue. The display might still show glitches.\n" "\n" "True.\n" @@ -78,7 +79,8 @@ ">> - the application may check capabilities to know whether FOURCC is\n" ">> supported - the application may write a raw FOURCC value in nonstd to\n" ">> request changing to FOURCC mode with this format\n" - ">> - when the driver switches to a FOURCC mode it must have visual >> FB_VISUAL_FOURCC and the current FOURCC format in nonstd\n" + ">> - when the driver switches to a FOURCC mode it must have visual =\n" + ">> FB_VISUAL_FOURCC and the current FOURCC format in nonstd\n" ">> - the application should check visual and nonstd to make sure it gets what\n" ">> it wanted\n" ">>\n" @@ -113,4 +115,4 @@ "\n" Florian Tobias Schandinat -e9dc1b46f40f81f415816990ce5337e636c8c9a230fc6b5b7415c575849f2272 +ba5589a82ec644089cdf4e629c8c27f88c91c13ac5cdb53f88a99f257635c058
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.