All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67681] Asus G75VW F key Not Working For Screen Brightness
Date: Wed, 14 May 2014 06:48:30 +0000	[thread overview]
Message-ID: <bug-67681-2300-DSR6Cx5f6D@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-67681-2300@https.bugzilla.kernel.org/>

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

--- Comment #27 from 3fdd1e5d@opayq.com ---
I thought I mentioned this before, but Nvidia uses a driver for Windows to
control this, it doesn't come from Nvidia. 

You can actually see that the F keys have an Asus ROG logo themed popup display
instead of the standard windows looking display.

So I REPEAT, this is not controlled by Nvidia... :)


thanks

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

  parent reply	other threads:[~2014-05-14  6:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-67681-2300@https.bugzilla.kernel.org/>
2014-05-14  2:18 ` [Bug 67681] Asus G75VW F key Not Working For Screen Brightness bugzilla-daemon
2014-05-14  6:45 ` bugzilla-daemon
2014-05-14  6:48 ` bugzilla-daemon [this message]
2014-05-14  6:49 ` bugzilla-daemon
2014-06-02  4:19 ` bugzilla-daemon
2014-06-30  0:56 ` bugzilla-daemon
2014-08-11  2:03 ` bugzilla-daemon
2014-12-05  3:10 ` bugzilla-daemon
2015-01-08  9:26 ` [Bug 67681] Asus G75VW F keys Not Working For WiFi & Brightness bugzilla-daemon
2015-01-08  9:29 ` bugzilla-daemon
2015-01-08  9:32 ` bugzilla-daemon
2015-01-08  9:45 ` bugzilla-daemon
2015-01-08  9:47 ` bugzilla-daemon
2015-01-08 11:48 ` bugzilla-daemon
2015-01-09  6:06 ` bugzilla-daemon
2015-05-06  7:45 ` bugzilla-daemon
2016-04-12  1:48 ` 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-67681-2300-DSR6Cx5f6D@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.