A few days ago I branched drm-next-4.6 in to drm-next and synced it with
Torvalds' tree as of the v4.6 tag. I then integrated the ~800 commits to drm /
i915 / radeon / amdgpu , testing periodically along the way and updating the
linuxkpi as needed. I've just tagged the drm-next branch with drm-
On 12 Aug 2016, at 00:18, Lundberg, Johannes
wrote:
>
> Currently by default evdev create /dev/input/eventX devices with 600
> permission. These need to be accessible for non-root users. What is the
> best solution? Should we create a "input" group similar to "video" group is
> being used for ri
On 8/10/2016 4:20 PM, Bryan Drewery wrote:
> On 8/7/16 5:44 PM, Don Lewis wrote:
>> Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on
>> HEAD. When I do that I get this failure:
>>
>> ===> Ports module emulators/virtualbox-ose-kmod (all)
>> cd ${PORTSDIR:-/usr/ports}/emulators/v
Hi,
On 12.08.16 01:18, Lundberg, Johannes wrote:
x11/libinput (removed udev-stubs and linked to libudev-devd)
If you feel adventurous, you can try out the current state of the
libinput port here (1.4.0):
https://github.com/jiixyj/libinput
I haven't yet tested the port with the evdev kernel
On 12 Aug, Bryan Drewery wrote:
> On 8/10/2016 4:20 PM, Bryan Drewery wrote:
>> On 8/7/16 5:44 PM, Don Lewis wrote:
>>> Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on
>>> HEAD. When I do that I get this failure:
>>>
>>> ===> Ports module emulators/virtualbox-ose-kmod (all)
>>
> There is a similar problem for the drm devices (by default, users can’t
> use 3D acceleration). A devfs.conf policy can change the permissions. I’d
> suggest that we create a default group called something like console or
> local, put new users there by default, and make drm and evdev devices
>
>
> If you feel adventurous, you can try out the current state of the libinput
> port here (1.4.0):
> https://github.com/jiixyj/libinput
>
>
Great! Will check it out.
> I haven't yet tested the port with the evdev kernel work, though. I've
> been using my evdev implementation in userspace whic
Hi,
On 12.08.16 19:22, Lundberg, Johannes wrote:
Where can I find xf86-input-libinput for FreeBSD? Will the original
source build?
Yes, the original source
(https://cgit.freedesktop.org/xorg/driver/xf86-input-libinput/) will
build unmodified.
I've copied libinput_drv.so to
/usr/local/lib
Hi
I followed the instructions for evdev enabled kernel here
https://github.com/wulf7/libudev-devd and it works fine!
I needed to update libinput to latest version since it was required by
xf86-input-libinput so I'm using latest version from
https://github.com/jiixyj/libinput.
As for the wsp driv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first RC build of the 11.0-RELEASE release cycle is now available.
Installation images are available for:
o 11.0-RC1 amd64 GENERIC
o 11.0-RC1 i386 GENERIC
o 11.0-RC1 powerpc GENERIC
o 11.0-RC1 powerpc64 GENERIC64
o 11.0-RC1 sparc64 GENERIC
o 11
On Sat, Aug 13, 2016 at 01:30:56AM +, Glen Barber wrote:
> o OpenSSH DSA keys have been disabled by default. Users upgrading from
> prior FreeBSD versions are urged to update their SSH keys to DSA or
> ECDSA keys before upgrading to 11.0-RC1.
>
Note, this should have suggested to update
11 matches
Mail list logo
