compute-runtime
kbct
Our great sponsors
compute-runtime | kbct | |
---|---|---|
58 | 6 | |
1,066 | 254 | |
3.7% | - | |
10.0 | 0.0 | |
4 days ago | over 1 year ago | |
C++ | Rust | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
compute-runtime
- Intel Graphics Compute Runtime for OneAPI Level Zero and OpenCL
-
Alder Lake HDR tone mapping
Well... Fuck! https://github.com/intel/compute-runtime/issues/643
-
Proxmox VE 8.0 released!
For what it's worth, I was able to get IOMMU enabled and iGPU passthrough working for Plex on an Ubuntu 22.04 LXC container with a fresh install of Proxmox 8.0.3 (kenrel 6.2.16-3-pve) on an Intel i5-13400, ASRock B760M Pro RS/D4, also using Intel drivers released early today. I largely followed this guide.
-
rocm-opencl (rocm-opencl-runtime) rx 6600 xt support
For this little project unless someone chimes in with experience or can point to regarding the RX 6600 XT / 6650 XT / perhaps 7600 I might go with https://github.com/intel/compute-runtime . (They don't have perfect documentation re supported gpus either, the readme table doesn't list DG2, you need to go to releases to see that) . Phoronix reported it as pretty stable when they tested it with kernel 6.2 in March.
-
Vladmandic Stable Diffusion added Intel ARC GPU support on Linux
Update: I was able to fix my issue. I'm using Ubuntu 22.04.2 LTS and have the newest available kernel, 6.3.1. Installing the drivers via apt does not work, instead I needed to use https://github.com/intel/compute-runtime/releases/
- Intel Arc Driver Overhead - Just a Myth?
- How do you allocate more than 4GB of memory for OpenCL in A770 16GB?
-
Proxmox iGPU passthrough to LXC not working
Drivers: https://github.com/intel/compute-runtime/releases
-
Stable Diffusion Web UI for Intel Arc
wget https://github.com/intel/compute-runtime/releases/download/22.43.24595.30/intel-level-zero-gpu-dbgsym_1.3.24595.30_amd64.ddeb
-
Current state of Intel Arc transcoding
For OpenCL HDR/DV tone-mapping, install the extra compute-runtime if running on host.
kbct
- Help - Key Remap
-
Show HN: I spent a year designing an low profile, minimal mechanical keyboard
I had a similar problem with the Tecurs KB510 I got at work. The only way I found to type F1-F12 keys on Linux was to set up a hack with kbct [0] and the Super key... until I tried the configuration described in the gist you linked. Thanks a lot for that !
[0] https://github.com/samvel1024/kbct
-
Linux utility to assign different keys to tap vs hold (like Karabiner does in macOS)
I use KBCT and encourage others to support it: https://github.com/samvel1024/kbct
-
me right now
kbct
-
Linux Touchpad Like MacBook Update: Touchpad Gestures Now Shipping
>Creating a "standardized experience" like Windows usually means that configurability goes right out the window. It's how you get abominations like dconf or the GNOME music player
I don't understand how you connected these dots and I'd suggest against calling things abominations. You don't have to use dconf or the GNOME music player, those aren't standardized. If someone does like them I think they're perfectly fine, they do exactly what they're advertised to do. It's also fine if you don't like them, they're just two options from the many configuration databases and media players that you can choose from.
>But why shouldn't I be able to run xbindkeys or sxhkd or whatever hotkey dameon I want?
In some ways you actually can but it depends on the hotkey daemon and how it's implemented. The reason for that is technical, those are implemented with X grabs which have a number of usability and security issues. There are a few key rebinding daemons that use evdev directly so they work with Wayland:
https://github.com/samvel1024/kbct
https://github.com/snyball/Hawck
But these also do have similar security issues to X key grabs, in that they effectively operate as keyloggers. If you're looking for an API that works purely within Wayland and lets unprivileged clients request key rebinding, that doesn't exist yet. Somebody would need to specify what that API looks like and figure out a good way to make it secure. What would the end goal of the API be, and how could the system (and by extension, the user) tell the difference between a legitimate hotkey daemon and a malicious keylogger? And would it actually be any better than the approach of snooping evdev? I don't know the answer to these questions but you may have more experience with this than I do.
- Keyboard customization tool for Linux
What are some alternatives?
jellyfin-ffmpeg - FFmpeg for Jellyfin
input-remapper - 🎮 ⌨ An easy to use tool to change the behaviour of your input devices.
docker-jellyfin
rkvm - Virtual KVM switch for Linux machines
PMS_Updater - Shell script for updating the Plex Media Server inside the FreeNAS Plex plugin
evsieve - A utility for mapping events from Linux event devices.
hawck - Key-rebinding daemon for Linux (Wayland/X11/Console)
kmonad - An advanced keyboard manager
intel-graphics-compiler
leddy - Linux LED controller for the Fnatic miniStreak.
docker-mods - Documentation and Examples of base container modifications
map2 - Linux input remapping for your keyboard, mouse and more!