Thanks for the patch! Unfortunately I'm using the tablet anymore and are not
able to test this.
This pressure level was chosen because the Linux driver uses it as well:
https://github.com/linuxwacom/input-wacom/blob/master/4.5/wacom_wac.c#L297
I have no technical knowledge on how this works, but
On Thu, Jun 03, 2021 at 09:23:16PM +0200, Stefan Hagen wrote:
> Peter J. Philipp wrote:
> > On Thu, Jun 03, 2021 at 08:06:06PM +0200, Stefan Hagen wrote:
> >> Which one?
> >
> > It didn't say in the dmesg if I recall correctly, luckily I found the
> > packaging. CTL-490 DW-S.
>
> Same model here.
On Fri, Jun 04, 2021 at 04:02:01AM +0200, Alessandro Pistocchi wrote:
>
> [...]
>
> My reasoning for not sending them is that the changes I made could create
> security
> issues for ordinary users, and I think that it would be a nightmare to
> maintain only
> to be able to play smoother games on
Hi all,
I have managed to create some exciting, gaming-specific extensions to the
OpenBSD kernel,
specifically for an arm64 raspberry pi 4.
I would like to turn this into a product that people enjoy if possible and
I would be happy to
make something that benefits the OpenBSD community as well som
Greg Steuck writes:
> vm_impl_init_vmx: uvm_share failed (22)
> failed to init arch-specific features for vm 0x0x8000237ace70
Thanks, will look into this one.
-dv
I happened to be looking at the console of one of the VMs getting abused
by syzkaller and caught what looked like assertions that people might
want to see.
pmap_unwire: wiring for pmap 0xfd807f009ae0 va 0x20001000 didn't change!
pmap_unwire: wiring for pmap 0xfd807f009ae0 va 0x20002000 did
On Wed, Jun 02 2021, Ingo Schwarze wrote:
> Hi,
>
> feeling hesitant to commit into ksh without at least one proper OK,
> i'm resending this patch here, sorry if i missed private feedback.
I found two mails in my drafts folder, sorry, you didn't miss any
feedback from me.
> What the existing cod
On 5/29/21 2:26 AM, Theo de Raadt wrote:
Why does anyone require this functionality?
Within OpenWrt we store keys based on fingerprint
(/etc/opkg/keys/). If you verify a signature the key is
selected based on the signatures public key fingerprint. This way we
support storing multiple publi
Peter J. Philipp wrote:
> On Thu, Jun 03, 2021 at 08:06:06PM +0200, Stefan Hagen wrote:
>> Which one?
>
> It didn't say in the dmesg if I recall correctly, luckily I found the
> packaging. CTL-490 DW-S.
Same model here. I just wanted to make sure that the driver is actually
used in your case. It
On Thu, Jun 03, 2021 at 08:06:06PM +0200, Stefan Hagen wrote:
> Peter J. Philipp wrote:
>
> > I have a Wacom Intuos.
>
> Which one?
It didn't say in the dmesg if I recall correctly, luckily I found the
packaging. CTL-490 DW-S.
> > I found that I could not write anything as good as with the pre
Peter J. Philipp wrote:
> I have a Wacom Intuos.
Which one?
> I found that I could not write anything as good as with the pressure
> having a higher threshold ie. the original driver.
Can you be more specific? Did you have false activations without
touching the tablet?
The pressure sensor is
I've taken a step back from my previous growing diff [1] to break it
down into something more reviewable, testable, and incremental.
This diff introduces better defined packet size limitations based on the
underlying tap(4) limits (TUNMRU=16384) and fully implements support for
device rx-side desc
On Thu, Jun 03, 2021 at 05:10:57PM +0200, Stefan Hagen wrote:
> Hi,
>
> I'm using a Wacom CTL-490 to draw on virtual whiteboards in online
> meetings.
Hi,
I tried your patch and got rejections, though I was able to fix it. I have
a Wacom Intuos. I found that I could not write anything as good
Hi,
I'm using a Wacom CTL-490 to draw on virtual whiteboards in online
meetings.
Compared to linux/windows, it needs a lot of pressure to draw something
on OpenBSD. This makes writing pretty hard.
In OpenBSD, a tip-pressure of >10 is required to activate button 0.
I'm not sure why this number w
On Thu, May 20, 2021 at 01:56:24PM +, Visa Hankala wrote:
> This patch adds a mutex that serializes access to a kqueue. As a result,
> most of kqueue's internals should become safe to run without the kernel
> lock. In principle, the patch should allow unlocking kevent(2).
>
> Some notes:
>
>
> This is also because communication with the device uses ASN.1-like
> structures, and that complexity should maybe not be part of the kernel.
I actually think this should all be in the driver. I think the wrong
decision was made of turning this into a /dev/ interface.
In the end, the object par
16 matches
Mail list logo