linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: david@lang.hm
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, Bastien Nocera <hadess@hadess.net>
Subject: Re: [git pull] Input updates for 2.6.34-rc6
Date: Fri, 14 May 2010 11:55:43 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.01.1005141151570.8603@asgard.lang.hm> (raw)
In-Reply-To: <20100514184931.GA10113@srcf.ucam.org>

On Fri, 14 May 2010, Matthew Garrett wrote:

> On Fri, May 14, 2010 at 11:47:43AM -0700, david@lang.hm wrote:
>
>> yes, everything has USB ports, so they could use USB keyboards, but it's
>> actually pretty common to still use PS/2 keyboards (and while the systems
>> all support USB, it's not uncommon to have KVM systems, including pretty
>> expensive 'enterprise' KVM systems that still require PS/2 keyboards be
>> used to plug into the KVM, so those are the keyboards that are in the
>> datacenter that someone will grab to plug into a problem machine)
>
> The server hardware I've looked at will all declare the ports regardless
> of whether or not there's something plugged in.

remember that many people use systems in datacenters that are not 'server 
hardware'.

when a desktop PC can have 4-6 cores with 8G+ of ram and a couple TB of 
storage, a lot of people will end up using those systems for production.

As they grow into bigger companies they will shift to 'server class' 
hardware, but startups tend to use whatever they can scrounge (or buy 
_really_ cheap)

David Lang

  reply	other threads:[~2010-05-14 18:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  7:57 [git pull] Input updates for 2.6.34-rc6 Dmitry Torokhov
2010-05-13 14:35 ` Linus Torvalds
2010-05-13 14:47   ` Bastien Nocera
2010-05-13 15:04     ` Linus Torvalds
2010-05-13 15:19       ` Linus Torvalds
2010-05-13 15:50       ` Dmitry Torokhov
2010-05-13 16:16         ` Linus Torvalds
2010-05-13 16:38           ` Randy Dunlap
2010-05-13 20:15         ` Matthew Garrett
2010-05-13 16:01   ` Dmitry Torokhov
2010-05-13 16:54     ` Linus Torvalds
2010-05-13 16:58       ` Linus Torvalds
2010-05-13 17:16       ` Dmitry Torokhov
2010-05-13 17:30         ` Linus Torvalds
2010-05-13 18:10           ` Dmitry Torokhov
2010-05-13 19:55             ` Linus Torvalds
2010-05-14  7:56               ` Eric W. Biederman
2010-05-14 14:54                 ` Linus Torvalds
2010-05-14 15:38                   ` Matthew Garrett
2010-05-14 15:42                     ` Linus Torvalds
2010-05-14 15:49                       ` Matthew Garrett
2010-05-20  4:53                         ` Len Brown
2010-05-27  6:22       ` Robert Hancock
2010-05-27  6:43         ` Dmitry Torokhov
2010-05-27 17:06         ` Linus Torvalds
2010-05-27 23:03           ` Robert Hancock
2010-05-28  0:46             ` Linus Torvalds
2010-05-28  1:03               ` Dmitry Torokhov
2010-05-28  4:05                 ` Robert Hancock
2010-05-28  5:10                   ` Dmitry Torokhov
2010-05-14 14:55   ` Matthew Garrett
2010-05-14 15:16     ` Linus Torvalds
2010-05-14 16:28       ` Dmitry Torokhov
2010-05-14 18:47       ` david
2010-05-14 18:49         ` Matthew Garrett
2010-05-14 18:55           ` david [this message]
2010-05-14 18:59             ` Matthew Garrett
2010-05-14 19:05             ` david
2010-05-28  2:38       ` Mike Frysinger
2010-08-04  6:20       ` Dmitry Torokhov
2010-08-04  6:29         ` Dmitry Torokhov
2010-05-14 16:29     ` Dmitry Torokhov
2010-05-14 16:35       ` Matthew Garrett
  -- strict thread matches above, loose matches on Subject: below --
2010-05-05  6:41 Dmitry Torokhov

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=alpine.DEB.2.01.1005141151570.8603@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=torvalds@linux-foundation.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).