From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 11 Apr 2013 16:10:09 +0000 Subject: Re: [PATCH V2] video: implement a simple framebuffer driver Message-Id: <5166E061.1050008@wwwdotorg.org> List-Id: References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-arm-kernel@lists.infradead.org On 04/11/2013 04:42 AM, Geert Uytterhoeven wrote: > On Thu, Apr 4, 2013 at 4:39 AM, Stephen Warren wrote: >> + { "r5g6b5", 16, {11, 5}, {5, 6}, {0, 5}, {0, 0} }, > > Why "r5g6b5" instead of "rgb565", which is what's commonly used? Both representations appear commonly used. I mentioned my rationale in response to V1: "r5g6b5" is a much more well-defined structure. It's directly algorithmically parse-able if required, whereas you'd need somewhat more complex heuristics to determine exactly what rgb565 or argb2101010 mean, since all the numbers are run together without delimiters. From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Thu, 11 Apr 2013 10:10:09 -0600 Subject: [PATCH V2] video: implement a simple framebuffer driver In-Reply-To: References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> Message-ID: <5166E061.1050008@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/11/2013 04:42 AM, Geert Uytterhoeven wrote: > On Thu, Apr 4, 2013 at 4:39 AM, Stephen Warren wrote: >> + { "r5g6b5", 16, {11, 5}, {5, 6}, {0, 5}, {0, 0} }, > > Why "r5g6b5" instead of "rgb565", which is what's commonly used? Both representations appear commonly used. I mentioned my rationale in response to V1: "r5g6b5" is a much more well-defined structure. It's directly algorithmically parse-able if required, whereas you'd need somewhat more complex heuristics to determine exactly what rgb565 or argb2101010 mean, since all the numbers are run together without delimiters. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH V2] video: implement a simple framebuffer driver Date: Thu, 11 Apr 2013 10:10:09 -0600 Message-ID: <5166E061.1050008@wwwdotorg.org> References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Geert Uytterhoeven Cc: Linux Fbdev development list , Arnd Bergmann , devicetree-discuss@lists.ozlabs.org, Rob Clark , linux-rpi-kernel@lists.infradead.org, Olof Johansson , Andrew Morton , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org On 04/11/2013 04:42 AM, Geert Uytterhoeven wrote: > On Thu, Apr 4, 2013 at 4:39 AM, Stephen Warren wrote: >> + { "r5g6b5", 16, {11, 5}, {5, 6}, {0, 5}, {0, 0} }, > > Why "r5g6b5" instead of "rgb565", which is what's commonly used? Both representations appear commonly used. I mentioned my rationale in response to V1: "r5g6b5" is a much more well-defined structure. It's directly algorithmically parse-able if required, whereas you'd need somewhat more complex heuristics to determine exactly what rgb565 or argb2101010 mean, since all the numbers are run together without delimiters.