From: Juan Quintela <quintela@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: cfergeau@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] ps2: migrate ledstate
Date: Mon, 17 Oct 2011 17:21:31 +0200 [thread overview]
Message-ID: <m3botfskxw.fsf@trasno.mitica> (raw)
In-Reply-To: <4E9C4691.2080405@redhat.com> (Gerd Hoffmann's message of "Mon, 17 Oct 2011 17:15:29 +0200")
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi,
>
>>> We only need to migrate the state when it is different of the default
>>> one (0).
>>
>> Er, isn't it going to be different from the default in like 99% of
>> circumstances?
>
> Why? caps lock and scroll lock are off usually. numlock depends on
> what the user prefers. In case he cares in the first place of
> course. I expect most users don't and just go with the default.
>
> On my physical machines numlock is off by default. Likewise in my
> virtual machines: SeaBIOS keeps it off by default, and Linux+Windows
> guests don't muck with it at boot.
>
> I remember physical machines used to have numlock on by default in the
> 90ies. They even had a BIOS Setup option to pick the initial numlock
> state. That seems to be out-fashioned these days though, I havn't
> seen that for quite a while now ...
I have nothing else to add. This is exactly my point. I think that I
have _never_ setup NumLock by default in any of my machines. And
capslock use is very, very sporadic. In my case, it would be 0 about
99.9% of the time.
Later, Juan.
next prev parent reply other threads:[~2011-10-17 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 11:37 [Qemu-devel] [PATCH v4] ps2: migrate ledstate Juan Quintela
2011-10-17 13:35 ` Christophe Fergeau
2011-10-17 13:37 ` Anthony Liguori
2011-10-17 15:15 ` Gerd Hoffmann
2011-10-17 15:21 ` Juan Quintela [this message]
2011-10-17 15:24 ` Anthony Liguori
2011-11-01 22:21 ` Anthony Liguori
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=m3botfskxw.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=cfergeau@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).