This moves the timers to SHL and removes the old static_misc header and
source. They are no longer needed.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
The ring implementation is only used in one place so move it into SHL to
avoid linking it into all other libraries and applications.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This moves the whole hashtable implementation into the SHL library. Now we
can link it only to the applications that really use it.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Shl (Static helper library) is the new name of all static helpers in
kmscon that might be shared between different applications.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
There is really no need to use these helper functions. Just directly call
the pthread locks.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Update all the introduction and documentation comments. Also remove an old
TODO item regarding glib.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
A short comment on how the UTF8 state machine works and why it does not do
any sophisticated error recovery.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Four helpers that define maximum UCS4 values, invalid values and a
replacement character for unknown values.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
All terminal-emulation code is moved into a new library called "TSM -
Terminal State Machine". So we rename everything to have a separate
namespace.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Instead of requiring to use uterm_screen objects we now add a
fake_blendv() request directly to the display object. We rename it to
"fake_blend" instead of just "blend" so we can later implement real
blending.
This reuses the existing infrastructure. But the fake_blendv is the way to
go so we rename the existing functions to "fake_*" either.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Instead of requiring to use a uterm_screen object we now also add these
helpers to the display directly. This allows to use libuterm without any
screens, which is often useful if no virtual screen are needed.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
The user should be notified what went wrong when DRM properties couldn't
been read. There are also pending patches on the dri-devel ML that fix
reading properties without DRM-master.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This call may fail with recent kernel versions as DRM_MASTER is required.
Therefore, print more information so we know what went wrong.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
We need a copy of xkbcommon-keysyms.h as long as xkbcommon is not included
in all major distributions. We _need_ this build-time dependency,
otherwise, we cannot build the other keyboard backends.
However, requiring xkbcommon as build-time dependency is not a solution as
no major distribution includes it.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
uterm_internal.h contains only input related content so we can rename it
and remove all the inclusions where it is not needed.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This splits off all video related helpers of the big internal
uterm_internal.h header into uterm_video.h.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
The fakevt tool is no longer used. The same functionality was integrated
into kmscon with the fake-VT uterm_vt backend.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
There is no need to make genshader being generated by configure, anymore.
We used to use @srcdir@ but this was not embedded into Makefile.am. Hence,
we can avoid this and make it build normally.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
libkms doesn't link to libdrm so our current check for gbm_bo_get_stride()
fails. This has been fixed upstream but distributions still need to pick
it up. Therefore, we simply add the drm libs to our checks. They are
available at this point, anyway.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
We intend to make libuterm independent of kmscon so it can be used by
other projects. Therefore, add a pkg-config file for easier integration
into other build systems.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
If libxkbcommon is not available on the current platform, we still want to
be able to use the keysyms. We currently do this by depending on xproto
but this is ugly and we want to avoid this.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
The pkg-config file allows other users of libeloop to more easily
configure build-time options for eloop.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
pre-cbs are similar to post-cbs but they are called _before_ the actual
dispatching takes place. It can be used to perform any actions before
going to sleep.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
If the dispatch files or is skipped for whatever reason, we should
nevertheless call the post-cbs to avoid any integration errors.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Instead of using an ev_counter object internally, we now directly create a
new eventfd object. This avoids adding/removing the fd from the epoll-set
constantly when adding/removing idle sources. This should increase
idle-source speed considerably.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
The "d" variants of the log functions take a direct pointer to the llog
helper instead of the parent. This is sometimes used when we have no
parent but still want to log errors.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
When integrating other event-sources or event-loops into eloop which do
not provide FD-abstractions, we often want to check for specific
conditions before returning from the dispatch-callback or going to sleep.
Therefore, you can now register a post-dispatch-cb and check whether your
alien event source is firing. If it is, simply push an idle-source into
the event-loop and it will fire during the next dispatch without going to
sleep.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This new helper allows retrieving a single file descriptor which
represents the whole event loop. This is very useful if you want to use
your own event loop in combination with libeloop.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This is the first public release. Most major features are implemented and
kmscon works reliably. I use it for real work since several weeks now so I
consider it stable.
Anyway, there is still much to do. The TODO list is long...
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This never really worked and was horrible to maintain. We need to find
something else for documentation, but we will probably have to do it with
a separate XML file without any generator.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
We need to include everything in the distribution and fix the
include-path, otherwise, we might get "distcheck" errors.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Instead of doing nothing we now pass everything to log_dummyf() if a
logging macro is not enabled. This silences all the "unused variable"
warnings which are really annoying.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
"10" is really small and not really suited as default value. We currently
do debugging a lot and hence using bigger fonts makes that task a lot more
easy. Furthermore, as a "first impression" people get from kmscon, we want
the font to be at a proper size.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
We have added a lot of more xterm functionality so "xterm-256color" should
be the better default value now. It also makes most applications behave
better as they can use improved control sequences.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
We need to know whether a current attribute was created with a specific
RGB value or whether a vt-color-code was used. This is, because several
affects have to be applied when color-codes are used. For instance, bold
colors are always brightened to simulate "bold".
Therefore, two new fields are added which contain the color-code or -1 if
an RGB value is used. All of this is always applied internally of the VTE
layer so other layers (like the console layer) can be sure, that the RGB
value is always correct and use it.
But the VTE layer needs to keep track of the color-codes so we put them
into the attribute structure.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Remove the last reference to uterm structures so we can put the vte layer
into a separate library without any dependency to rendering
infrastructure.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
We finally want to get rid of any dependencies in the vte/console layer so
we can split it out into a separate library.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
