All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222002] [BUG] alienware-wmi: Missing support for Alienware 16 Area-51 (AA16250) lighting controller (AW-ELC 187c:0551)
Date: Wed, 16 Sep 2026 06:03:11 +0000	[thread overview]
Message-ID: <bug-222002-215701-nOjSPEYFtg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222002-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222002

--- Comment #4 from adrienpantovich@gmail.com (adrienpantovich@gmail.com) ---
Here is the output you requested. I am working on reverse engineering
a way to send information to the controller manually from dual-booting
windows and monitoring USBHID events that AWCC sends and receives to
the LED components. OpenRGB hasn't worked for me at all when I tried
installing it either, which is why I'm trying to do it myself lol.

On Tue, Sep 15, 2026 at 2:16 PM <bugzilla-daemon@kernel.org> wrote:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=222002
>
> --- Comment #3 from Armin Wolf (W_Armin@gmx.de) ---
> Can you share the output of "acpidump"?
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You reported the bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-09-16  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  8:09 [Bug 222002] New: [BUG] alienware-wmi: Missing support for Alienware 16 Area-51 (AA16250) lighting controller (AW-ELC 187c:0551) bugzilla-daemon
2026-09-11 20:55 ` [Bug 222002] " bugzilla-daemon
2026-09-15 10:49 ` bugzilla-daemon
2026-09-15 19:16 ` bugzilla-daemon
2026-09-16  6:03 ` bugzilla-daemon [this message]
2026-09-22 20:44 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-222002-215701-nOjSPEYFtg@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.