diff for duplicates of <3150258.gEx8mFWcM9@avalon> diff --git a/a/1.txt b/N1/1.txt index e530c56..fba2726 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -25,7 +25,7 @@ On Wednesday 19 September 2012 14:45:29 Tomi Valkeinen wrote: Thank you for working on this proposal. > OMAP SoC -> ==== +> ======== > > So here's first the SoC specific display nodes. OMAP has a DSS (display > subsystem) block, which contains the following elements: @@ -132,7 +132,7 @@ around. > > > Simple DPI panel -> ======== +> ================ > > Here a board has a DPI panel, which is controlled via i2c. Panel nodes > are children of the control bus, so in this case we define the panel @@ -147,7 +147,7 @@ around. > > > HDMI -> == +> ==== > > OMAP has a HDMI output, but it cannot be connected directly to an HDMI > cable. TI uses tpd12s015 chip in its board, which provides ESD, @@ -179,7 +179,8 @@ board) Should we then have a driver for the HDMI monitor ? > DSI bridge chip -> =======> +> =============== +> > In this board we have a DSI bridge chip that is controlled via DSI, and > gets the pixel data via DSI video mode stream. The chip converts this to > LVDS. We then have an LVDS panel connected to this bridge chip, which is @@ -200,7 +201,8 @@ Should we then have a driver for the HDMI monitor ? > > > High res dual-DSI panel -> ===========> +> ======================= +> > Here we have a DSI video mode panel that gets its data from two DSI > buses. This allows it to get the combined bandwidth of the DSI buses, > achieving higher resolution than with single DSI bus. The panel is @@ -216,7 +218,7 @@ Should we then have a driver for the HDMI monitor ? > > > DSI buffer chip with two outputs -> ================ +> ================================ > > This board has a DSI command mode buffer chip, that contains its own > framebuffer. The buffer chip has two DPI outputs, which get the pixels diff --git a/a/content_digest b/N1/content_digest index 421d7a5..38203fb 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,7 +2,7 @@ "ref\01348055129.2565.54.camel@deskari\0" "From\0Laurent Pinchart <laurent.pinchart@ideasonboard.com>\0" "Subject\0Re: [RFC 0/5] Generic panel framework\0" - "Date\0Wed, 31 Oct 2012 13:13:43 +0000\0" + "Date\0Wed, 31 Oct 2012 14:13:43 +0100\0" "To\0Tomi Valkeinen <tomi.valkeinen@ti.com>" " Richard Purdie <rpurdie@rpsys.net>\0" "Cc\0linux-fbdev@vger.kernel.org" @@ -46,7 +46,7 @@ "Thank you for working on this proposal.\n" "\n" "> OMAP SoC\n" - "> ====\n" + "> ========\n" "> \n" "> So here's first the SoC specific display nodes. OMAP has a DSS (display\n" "> subsystem) block, which contains the following elements:\n" @@ -153,7 +153,7 @@ "> \n" "> \n" "> Simple DPI panel\n" - "> ========\n" + "> ================\n" "> \n" "> Here a board has a DPI panel, which is controlled via i2c. Panel nodes\n" "> are children of the control bus, so in this case we define the panel\n" @@ -168,7 +168,7 @@ "> \n" "> \n" "> HDMI\n" - "> ==\n" + "> ====\n" "> \n" "> OMAP has a HDMI output, but it cannot be connected directly to an HDMI\n" "> cable. TI uses tpd12s015 chip in its board, which provides ESD,\n" @@ -200,7 +200,8 @@ "Should we then have a driver for the HDMI monitor ?\n" "\n" "> DSI bridge chip\n" - "> =======> \n" + "> ===============\n" + "> \n" "> In this board we have a DSI bridge chip that is controlled via DSI, and\n" "> gets the pixel data via DSI video mode stream. The chip converts this to\n" "> LVDS. We then have an LVDS panel connected to this bridge chip, which is\n" @@ -221,7 +222,8 @@ "> \n" "> \n" "> High res dual-DSI panel\n" - "> ===========> \n" + "> =======================\n" + "> \n" "> Here we have a DSI video mode panel that gets its data from two DSI\n" "> buses. This allows it to get the combined bandwidth of the DSI buses,\n" "> achieving higher resolution than with single DSI bus. The panel is\n" @@ -237,7 +239,7 @@ "> \n" "> \n" "> DSI buffer chip with two outputs\n" - "> ================\n" + "> ================================\n" "> \n" "> This board has a DSI command mode buffer chip, that contains its own\n" "> framebuffer. The buffer chip has two DPI outputs, which get the pixels\n" @@ -274,4 +276,4 @@ "\n" Laurent Pinchart -7a9f69740eddfb78afe319ee819a7f200499b51f2796e611db46321a2635f830 +ecd38f79ca4202b490280aa6f0bd66f1799abcb75d7852a82e3c3941cfd62be9
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.