An error occurred fetching the project authors.
- 26 May, 2006 1 commit
-
-
Mark Underwood authored
This is an updated version of my patch that adds support for RGB444 mode for the internal LCD controller which now applies against linux-2.6.16 with the patch-2.6.16-omap2 applied. Jonathan McDowell posted a slightly modified version of my original patch to this list previously: http://Linux.omap.com/pipermail/linux-omap-open-source/2006-April/006839.html This patch is used by the Amstrad Delta (E3). Signed-off-by: Mark Underwood <basicmark@yahoo.com> Acked-by: Jonathan McDowell <noodles@earth.li> Signed-off-by: Imre Deak <imre.deak@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 04 Apr, 2006 1 commit
-
-
Tony Lindgren authored
-
- 28 Mar, 2006 1 commit
-
-
Komal Shah authored
sem2mutex conversion Signed-off-by: Komal Shah <komal_shah802003@yahoo.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 21 Feb, 2006 1 commit
-
-
Juha Yrjola authored
If an external LCD controller is in manual update mode, the DSP must let the FB driver know when a frame should be send over the remote framebuffer interface. Original code by Toshihiro, FB parts by Imre. Signed-off-by: Imre Deak <imre.deak@nokia.com> Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>
-
- 09 Feb, 2006 1 commit
-
-
Imre Deak authored
- Support for the Philips LPH8923 LCD panel - Support for the Epson HWA742 LCD controller - Support for frame buffer located in SRAM and/or SDRAM - Support for boot loader initialized LCD controller / frame buffer content. - LCD panels will now register a device in the relevant board-* files instead of specifying the LCD type as an OMAP_TAG_LCD. The controller type is still specified in OMAP_TAG_LCD. - A new ATAG OMAP_TAG_FBMEM is used to describe the frame buffer memory configuration (SRAM and SDRAM regions) - Changed the OMAP1 LCD controller driver to export its functions through the lcd_ctrl object. - OMAP1 pixel clock divider will now round up in lcdc.c - Changed the OMAP1 SoSSI driver to export its functions through the lcd_ctrl_extif object. - OMAP1 SoSSI clock calculation goes through all possible clock dividers. Rounding of clock tick values now takes places at each timing parameter. - OMAP2 RFBI clock calculation goes through all possible clock dividers. Rounding of clock tick values now takes places at each timing parameter. - OMAP2 pixel clock divider will now round up in dispc.c Signed-off-by: Imre Deak <imre.deak@nokia.com> Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>
-
- 25 Jan, 2006 1 commit
-
-
Kyungmin Park authored
default enabled features as following UART ethernet LCD sound + (needs spi patch:) OneNAND
-
- 20 Jan, 2006 1 commit
-
-
Dirk Behme authored
drivers/video/omap/omapfb_main.c:877: warning: initialization from incompatible pointer type Signed-off-by: Dirk Behme <dirk.behme_at_de.bosch.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 03 Jan, 2006 1 commit
-
-
Todd Poynor authored
Fix fb driver miscompile
-
- 20 Dec, 2005 1 commit
-
-
Brian Swetland authored
Some LCD panels require the pixel clock to be active before being able to enable them. Signed-off-by: Brian Swetland <swetland@google.com> Signed-off-by: Juha Yrjl <juha.yrjola@nokia.com>
-
- 29 Nov, 2005 1 commit
-
-
Komal Shah authored
omapfb: Use struct platform_driver Signed-off-by: Komal Shah <komal_shah802003@yahoo.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 10 Nov, 2005 1 commit
-
-
Tony Lindgren authored
Misc changes to compile after sync with mainline
-
- 27 Oct, 2005 1 commit
-
-
Imre Deak authored
I forgot that the fbconsole code is using a palette even though we are in true color mode, so we have to handle that case separately.
-
- 19 Oct, 2005 1 commit
-
-
Imre Deak authored
included in this FB patch: - OMAP2 support with overlay, colorkey handling - the palmte patch posted by Romain Goyet. The palette loading is changed a bit, so that it works ok with other platforms as well. - registering the FB device through plat-omap/devices.c instead of doing it from the driver itself. Boards have to specify the OMAP_TAG_LCD config in the related board-*.c with in order to have FB support. - pixel clock divider calculation based on the panel->pixel_clock instead of the wired panel->pcd - support for external controllers both on SOSSI (OMAP1) and RFBI (OMAP2), kudos to Juha for this - removal of the OMAP1 2D gfx stuff, it didn't really improve the performance:( - double buffering IOCTL API, as this can be done in a more standard way through FBIOPUT_VSCREENINFO - update of the affected omap_*_defconfigs - minor formatting changes and typo fixes Still TODO: - OMAP2 Rotation, scaling of video planes - OMAP2 digit-out (aka tv-out) - moving the frame buffer to an alternative locating (onchip SRAM) I tested it with H2 and H4 but it might break on other OMAP1 boards as there were changes also in the old parts.
-
- 14 Sep, 2005 2 commits
-
-
Tony Lindgren authored
Search and replace of CONFIG_ARCH_OMAP1510 with CONFIG_ARCH_OMAP15XX
-
Dirk Behme authored
CC drivers/video/omap/omapfb_main.o drivers/video/omap/omapfb_main.c: In function omapfb_suspend' drivers/video/omap/omapfb_main.c: At top level: drivers/video/omap/omapfb_main.c:1645: warning: initialization from incompatible pointer type drivers/video/omap/omapfb_main.c:1646: warning: initialization from incompatible pointer type drivers/video/omap/omapfb_main.c:1702: warning: initialization from incompatible pointer type drivers/video/omap/omapfb_main.c:1704: warning: initialization from incompatible pointer type drivers/video/omap/omapfb_main.c:1704: warning: initialization from incompatible pointer type drivers/video/omap/omapfb_main.c:1705: warning: initialization from incompatible pointer type drivers/video/omap/omapfb_main.c:1728: warning: initialization from incompatible pointer type Signed-off-by: Dirk Behme <dirk.behme_at_de.bosch.com>
-
- 09 May, 2005 1 commit
-
-
Imre Deak authored
Adds support for OMAP framebuffer. Signed-off-by: Imre Deak <imre.deak@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-