omap(4)

💖 omap(4): OMAP SoC graphics 💖

okay so welcome to omap(4), straight outta the Kernel Interfaces Manual — this is the page for the OMAP SoC graphics life, and I’m gonna walk you through it like we’re texting in the group chat 💅✨

---

✨ NAME ✨

omap — OMAP SoC graphics

🎀 SYNOPSIS 🎀

Section "Device"
  Identifier "devname"
  Driver "omap"
  ...
EndSection

🦋 DESCRIPTION 🦋

omap is an Xorg driver for OMAP SoCs. That’s the whole vibe of this page, bestie — it’s giving “specialized Xorg driver,” no cap.

🌸 SUPPORTED HARDWARE 🌸

omap supports these exact chips, okay?

• OMAP3430
• OMAP3630
• OMAP4430
• OMAP4460

💜 CONFIGURATION DETAILS 💜

Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.

TODO — yes, literally, that’s what the page says 👀 no cap.

The following driver Options are supported, and every single one is here:

• Option "Debug" "boolean" — Enable debug logging. Default: Disabled
• Option "DRI" "boolean" — Enable DRI2. Default: Enabled
• Option "NoAccel" "boolean" — Disable hw acceleration. Default: Disabled
• Option "HWcursor" "boolean" — Enable HW mouse cursor. Default: Enabled

🌈 OUTPUT CONFIGURATION 🌈

The driver supports runtime configuration of detected outputs. You can use the xrandr tool to control outputs on the command line as follows:

xrandr --output output --set property value

Note that you may need to quote property and value arguments that contain spaces. Each output listed below may have one or more properties associated with it (like a binary EDID block if one is found). Some outputs have unique properties which are described below. See the MULTIHEAD CONFIGURATIONS section below for additional information.

TODO — again, yes, it’s in the source, bestie 🫶

See xorg.conf(5) for information on associating Monitor sections with these outputs for configuration. Associating Monitor sections with each output can be helpful if you need to ignore a specific output, for example, or statically configure an extended desktop monitor layout.

🧚 MULTIHEAD CONFIGURATIONS 🧚

The number of independent outputs is dictated by the number of CRTCs (in X parlance) a given chip supports. OMAP3xxx supports up to two, while OMAP4xxx supports up to three displays. The actual number of displays supported will depend on the board. But a built-in LCD and external HDMI are a common configuration.

You can use the "xrandr" tool, or various desktop utilities, to change your output configuration at runtime. To statically configure your outputs, you can use the "Monitor-<type>" options along with additional monitor sections in your xorg.conf to create your screen topology. The example below puts the VGA output to the right of the builtin laptop screen, both running at 1024x768.

Section "Monitor"
  Identifier "Laptop FooBar Internal Display"
  Option "Position" "0 0"
EndSection

Section "Monitor"
  Identifier "Some Random CRT"
  Option "Position" "1024 0"
  Option "RightOf" "Laptop FoodBar Internal Display"
EndSection

Section "Device"
  Driver "omap"
  Option "monitor-LVDS" "Laptop FooBar Internal Display"
  Option "monitor-VGA" "Some Random CRT"
EndSection

bestie, copy that example exactly — yes, Laptop FoodBar Internal Display is right there in the source, typo and all 😭💅 do not “fix” it, okay?

🍓 REPORTING BUGS 🍓

The xf86-video-omap driver is part of the X.Org and Freedesktop.org umbrella projects. Report bugs at https://bugs.freedesktop.org/enter_bug.cgi?product=xorg. Mailing lists are also commonly used to report experiences and ask questions about configuration and other topics. See lists.freedesktop.org for more information (the xorg@lists.freedesktop.org mailing list is the most appropriate place to ask X.Org and driver related questions).

👑 SEE ALSO 👑

Xorg(1), xorg.conf(5), Xserver(1), X(7)

💖 AUTHORS 💖

Authors include: Ian Elliott, Rob Clark.

---

X Version 11 • xf86-video-omap 0.4.5 • omap(4) — that’s the footer sign-off, bestie, no separate date line in sight 💅✨