lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f08669ec112d6ab2f62e35c0c96d1f06@oscillator.se>
Date: Sat, 13 Sep 2025 15:11:16 +0200
From: Staffan Melin <staffan.melin@...illator.se>
To: Salvatore Bonaccorso <carnil@...ian.org>
Cc: zhangheng <zhangheng@...inos.cn>, Jiri Kosina <jkosina@...e.com>,
 Benjamin Tissoires <bentiss@...nel.org>, linux-input@...r.kernel.org,
 linux-kernel@...r.kernel.org, regressions@...ts.linux.dev,
 stable@...r.kernel.org, 1114557@...s.debian.org
Subject: Re: [regression] 1a8953f4f774 ("HID: Add IGNORE quirk for
 SMARTLINKTECHNOLOGY") causes issue with ID 4c4a:4155 Jieli Technology USB
 Composite Device

Ah, thanks, I get it now :)

So I got 6.16.7, and the patch applied without problems.

But no luck, the same results as before: touchscreen not working, xinput 
--list not showing the Jieli touchscreen. dmesg shows the same as 
before, too.

Best regards,

Staffan


On 2025-09-13 10:55, Salvatore Bonaccorso wrote:
> Hi Staffan,
> 
> chiming in hopefully it is of help.
> 
> Now really with the patch ...
> 
> On Fri, Sep 12, 2025 at 09:57:04PM +0200, Staffan Melin wrote:
>> Thank you,
>> 
>> I tried to apply this patch to 6.12.39, the first problematic kernel, 
>> as
>> well as 6.12.41, the first bad I tried, and on both I got an error 
>> message:
>> 
>> Applying: HID: quirks: Add device descriptor for 4c4a:4155
>> error: patch failed: drivers/hid/hid-quirks.c:1068
>> error: drivers/hid/hid-quirks.c: patch does not apply
>> Patch failed at 0001 HID: quirks: Add device descriptor for 4c4a:4155
>> 
>> To which kernel version should I apply the patch?
> 
> As the deveopment goes from mainline then down to stable series, the
> fix needs to be developed first for mainline. So the patch is targeted
> there.
> 
> But please find attached an updated patch which hopefully should work
> which resolved the context changes on top of 6.12.47.
> 
> But ideally you can provide a Tested-by on zhangheng's mainline patch
> to get things rolling as needed.
> 
> Regards,
> Salvatore

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ