qbit/xenocara
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
369cc172f4
xenocara/driver/xf86-video-openchrome
History
oga 90bf659960 openchrome doesn't build if you have an xserver with DRI compiled in, 
but you disable dri on in the driver build and don't have the via_drm.h
it wants in dri mode. Work around this by changing the #define used to
an openchrome only one, instead of overloading the XF86DRI identifier.

Also disable the DRI build unconditionally.

This is needed here since we don't provide the via DRM module, and i'm
moving libdrm over to using the kernel headers (instead of libdrms own
private copy of same... This is why kernel modules should be developed
in kernel). We won't provide a via drm driver until it is re-written,
since it is full of linuxisms (like futex).

ok matthieu@, discussed with a few. tested by grange@ to prove it was a
no-op functionality wise.
2009-01-08 20:28:57 +00:00
..
libxvmc regen 2008-07-12 12:59:51 +00:00
man openchrome doesn't build if you have an xserver with DRI compiled in, 2009-01-08 20:28:57 +00:00
src openchrome doesn't build if you have an xserver with DRI compiled in, 2009-01-08 20:28:57 +00:00
acinclude.m4 Import the openchrome video driver, version 0.2.902. Discussed with 2008-07-12 12:48:04 +00:00
aclocal.m4 regen 2008-07-12 12:59:51 +00:00
ChangeLog Import the openchrome video driver, version 0.2.902. Discussed with 2008-07-12 12:48:04 +00:00
config.guess regen 2008-07-12 12:59:51 +00:00
config.h.in openchrome doesn't build if you have an xserver with DRI compiled in, 2009-01-08 20:28:57 +00:00
config.sub regen 2008-07-12 12:59:51 +00:00
configure openchrome doesn't build if you have an xserver with DRI compiled in, 2009-01-08 20:28:57 +00:00
configure.ac openchrome doesn't build if you have an xserver with DRI compiled in, 2009-01-08 20:28:57 +00:00
COPYING Import the openchrome video driver, version 0.2.902. Discussed with 2008-07-12 12:48:04 +00:00
depcomp regen 2008-07-12 12:59:51 +00:00
install-sh regen 2008-07-12 12:59:51 +00:00
ltmain.sh regen 2008-07-12 12:59:51 +00:00
Makefile.am Import the openchrome video driver, version 0.2.902. Discussed with 2008-07-12 12:48:04 +00:00
Makefile.bsd-wrapper openchrome doesn't build if you have an xserver with DRI compiled in, 2009-01-08 20:28:57 +00:00
Makefile.in regen 2008-07-12 12:59:51 +00:00
missing regen 2008-07-12 12:59:51 +00:00
NEWS xf86-video-openchrome 0.2.903 2008-11-03 20:37:24 +00:00
README Import the openchrome video driver, version 0.2.902. Discussed with 2008-07-12 12:48:04 +00:00

README 

xf86-video-openchrome
---------------------
(http://www.openchrome.org)

SUPPORTED CHIPSETS :
--------------------
- CLE266 (VT3122)
- KM400/P4M800 (VT3205)
- K8M800 (VT3204)
- PM800/PM880/CN400 (VT3259)
- VM800/CN700/P4M800Pro (VT3314)
- CX700 (VT3324)
- P4M890 (VT3327)
- K8M890 (VT3336)
- P4M900/VN896 (VT3364)


SUPPORTED FEATURES :
--------------------
- Free modesetting for Unichrome and Unichrome Pro chipset.
- VBE modesetting for everything not natively supported.
- TV-out support.
- EXA acceleration.
- Hardware MPEG2 acceleration.


IMPORTANT NOTE :
----------------
- The driver name is now 'openchrome', and this is what you need to use in
  your xorg.conf now (instead of 'via'). The XvMC libraries have also been
  renamed, to 'libchromeXvMC.so' and 'libchromeXvMCPro.so'.


KNOWN BUGS/LIMITATIONS :
------------------------
* Laptop panel
- Laptop displays for anything other than CLE266 and KM400/P4M800 are only
  supported thru VBE calls.
- Virtual terminal is broken on some laptop displays. Use a vesa framebuffer to
  work around that (append vga=791 to your kernel command line, for example).

* XvMC
- The hardware MPEG4 acceleration that is present on some chipsets is not
  implemented.
- No XvMC support for CX700 (new, unsupported engine).
- No XvMC support for K8M890, P4M890 and P4M900/VN896 (need to get dri working
  for them first).

* TV output
- TV modes are hardcoded and must be choosen inside a list depending on the TV
  encoder.
- Outputs are dependent on each other and will use the least common
  denominator. If you're using both VGA/LCD output and TV output, the VGA/LCD
  output will be limited by the TV encoder (720x576@50Hz for example).
  In other words, there is no dual screen support.

* Misc.
- Add-on and integrated TMDS encoders are not supported, except thru VBE.

* Chrome9
- Chrome9 chipsets' family (P4M900 and K8M890) currently doesn't
  support neither AGP DMA nor 3D acceleration. 


Please note that 3D acceleration is provided by Mesa (http://mesa3d.org) and is
not directly related to openchrome.