| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The LFS "transitional extension" API is deprecated and is not available on FreeBSD.
Large file support (64 bit) is not required on the geode 32 bit only architecture.
There are some hints that the LFS transional extension API were not used
correclty. The variable holding the value is held in an unsigned long rather
than in off_t. The msr open call did not use the O_LARGEFILE flag and did not
check for EOVERFLOW.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
|
|
|
|
These changes have been done in all other video drivers.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
In this case "now" means a couple of years ago. All of Xorg is compiled
with AC_PROG_CC_C99. It shows up in config.log as CC='gcc -std=gnu99'.
The removed statement was resetting the compiler to C89 as it comes
after XORG_DEFAULT_OPTIONS.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
HAVE_XEXTPROTO_71 not used in Makefile.
AC_HEADER_STD is very obsolete.
AC_SUBST([XORG_CFLAGS]) is redundant.
DRIVER_NAME is correctly no longer used.
AC_SUBST([moduledir]) has just been moved up.
Any erroneously removed statements above would result
in a configuration failure.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Now we have a clean separation between CPP flags and C Flags
Only the C Flags apply to both geode and ztv driver, however
it is not worth doing a per target compilation.
Should some flags become mutually exclusive and if we want to have
both target in the same makefile, add the incompatible flag
on the appropriate target, example:
geode_drv_la_CFLAGS = $(AM_CFLAGS) -newCFlag
and/or
geode_drv_la_CPPFLAGS = $(AM_CPPFLAGS) -newCPPFlag
Note that both AM_CFLAGS and AM_CPPFLAGS are picked-up by both
geode and ztv driver target.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Clean-up what goes in AM_CFLAGS and AM_CPPFLAGS
Use more descriptive names such that comments are not needed.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
For gcc compiler only at the moment.
The configuration reports if support is found or not, e.g.:
checking if gcc supports the -m32 Intel/AMD option... yes
The configuration C test relies on #include unistd.h which includes
features.h which includes gnu/stubs.h which includes gnu/stubs-32.h
which is missing on 64 bit system without the 32 bit library support.
Tested on x86_64 AMD64 CPU with/without libc6-dev-i386 which provides
32 bit support. Remains to be tested on Geode and FreeBSD 32/64 bit.
The configuration does not attempt to decide if building should proceed
or be aborted. If no 32 bit support then the build will die in the
assembly code as it always did before.
The variable M32_CFLAGS provides the flag for the makefiles.
The variable names and organization is subject to change.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
No functional changes.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
The AM_CONDITIONAL I386ARCH is not used.
The AC_CHECK_DECLS is misleading as it suggests there could be some i*86
system with a 64 bit architecture which is incorrect.
It also provides false results on 64 bit computer.
The generated HAVE_DECL_XXX are not used anyway.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Only the gx driver provide such a panel.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Use already existing:
--enable-strict-compilation
Enable all warnings from compiler and make them
errors (default: disabled)
which, byt the way was broken as it was not implemented in geode.
Use already existing CWARNINGFLAGS variable, so there is no need
to define GCC_WARNINGS.
Both come from util-macros version 1.4 or later.
http://cgit.freedesktop.org/xorg/util/macros/tree/xorg-macros.m4.in
?id=03b04a6b5d61aafbd2705f7d29e58e0c92553a4a
If you configure with a later version of util-macros you may see new
warnings appear as additional flags have been added over the years.
You get better support for platforms/compiler differences.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Only the suffixes .s, .S, and .sx are recognized by automake
as being files containing assembly code.
http://www.gnu.org/software/automake/manual/automake.html#Assembly-Support
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
The makefile defines LINUX_2_6 so the "else" code is dead.
The port from kernel 2.4 is complete.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
This was added by commit f762b456 in 2007 and has been since implemented
in the server which returns it in XORG_CFLAGS
pkg-config --cflags xorg-server
The server also takes care of platforms and compilers being used.
Currently the visibility is set twice and even if you disable it,
it is still passed through XORG_CFLAGS.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
It is used in ztv but not geode driver.
In the wake of more platforms other than linux, might as well
remove any source of confusion.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
These macros are not used in z4l.c.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
This macro has been removed every where from source code.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Even when V4L2 is available there are always reasons why distros
may not want to build the driver.
This patch uses a common idiom in xorg.
When no configure option is specified ztv is built iff v4l2 is detected (auto).
When user issues --disable-ztv, the ztv driver is not built (no)
When user issues --enable-ztv, the ztv driver is built (yes) if v4l2 is detected
but the configuration fails if v4l2 is missing. Distros do not want silent
failures when a feature is explicitly requested but cannot be built.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
Detect the presence of Video4Linux V2 and do not build if missing.
The geode driver is no longer Linux only.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
The convention is to have the video driver (geode) in the src subdir
and any other targets (utils, apps, other drivers) in their own
directory. It makes it much simpler to right a correct makefile
and to set conditional compile.
This highlighted a few things to fix. For now, the directory includes
have not been copied as they are required. The AM_CCASFLAGS is not required
either as there is no assembler.
Other than that, the gcc command issued has no differences. Other unrequired
defines could be removed later.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
|
|
|
|
|
|
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Inverted two FAQ sections so as to bring the answer about WXGA
right below this new supported resolutions section.
|
|
b9a5a86a402832fe699e43b3030932b50ae821a0 restored code compatibility
with X server 1.4.
|
|
Changing GEODE_TRACE_FALL to 1 allows to easily find the unaccelerated
code paths in a given use case while working on driver performance.
Signed-off-by: Priit Laes <plaes@plaes.org>
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
|
|
First argument is the number of elements and second the size of one
element, not vice-versa.
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
|
|
|
|
V4L1 support was dropped as of Linux kernel 2.6.38
|
|
Commit 5e72a00ad2 caused packed video data to corrupt glyphs and other
parts of the screen, but it turns out that the commit actually at fault
was d681a844e, incorrectly changing the size of the allocated destination
memory from the number of bytes needed to the number of lines needed.
While fixing this, I noticed that LXAllocateSurface is probably making the
same mistake, and that the height is probably not calculated correctly for
some corner cases when calling LXCopyFromSys in the packed
video path (but I'm not sure about either).
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=33004
|
|
|
|
Signed-off-by: Priit Laes <plaes@plaes.org>
|
|
The LX is a bit odd in that the palette can be used for gamma correction
of graphics data, or video data, but not both at the same time.
Right now, during X startup, X sets gamma correction (but without any
actual correction) causing the Geode driver to start using the palette
for graphics gamma correction. (this is just momentary)
Later on during startup, vg_set_custom_mode() switches to using the
palette for video gamma correction, and this is the end result.
If you later use xrandr to change the gamma, the palette starts being used
for graphics again.
If you VT switch, vg_set_custom_mode (momentarily) starts using the palette
for video, but then X jumps in with a gamma callback causing it to be used
for graphics again.
End result: no user visible bug, but this is inconsistent.
As there is no exposed mechanism for changing video gamma I suggest
we just drop that bit from vg_set_custom_mode(). Then the inconsistency
goes away.
Downside: this now becomes dependent on X setting gamma during startup.
I don't know when this was introduced but I think it is recent.
Aditionally, I think I found a (harmless) bug in
df_set_video_palette_entry, it doesn't do what the comments say.
|
|
Signed-off-by: Priit Laes <plaes@plaes.org>
|
|
NOTE: the eCafe EC-800's panel doesn't support a higher refresh rate.
|
|
Signed-off-by: Frank Huang<frankr.huang@amd.com>
|
|
|
|
This reverts commit fab58e111b6655602b4f739260a01247ff478f35.
|
