mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
	Pavel Machek <pavel@ucw.cz>,
	dtor_core@ameritech.net, "Martin J. Bligh" <mbligh@mbligh.org>
Subject: Re: Remove silly messages from input layer.
Date: Tue, 09 May 2006 08:54:24 +0200	[thread overview]
Message-ID: <44603CA0.2050304@aitel.hist.no> (raw)
In-Reply-To: <200605081725.29977.kernel@kolivas.org>

Con Kolivas wrote:

>On Monday 08 May 2006 16:43, Helge Hafting wrote:
>  
>
>>Dave Jones wrote:
>>    
>>
>>>On Fri, May 05, 2006 at 12:31:23PM +0200, Pavel Machek wrote:
>>>      
>>>
>>>>If you only pressed single key -- your keyboard is crap or there's
>>>>some problem in the driver.
>>>>
>>>>If you never pressed any key -- your keyboard is crap or there's
>>>>some problem in the driver.
>>>>        
>>>>
>>>That's hardly a constructive answer when the keyboard is a part of
>>>a laptop.  Crap hardware exists, get used to it.
>>>      
>>>
>>If some laptop comes with a bad keyboard, please blacklist
>>it so future linux users can avoid the brand when shopping
>>for hardware.
>>    
>>
>
>This is great in theory but if we end up blacklisting half of the hardware out 
>there we're stuffed. The truth is most hardware out there is cheap and nasty 
>and sells in vast quantities. We have workarounds for timer code being buggy 
>on virtually half the motherboards out there on amd64 for example...
>  
>
Well, it depends on how broken they are then.
These keyboards actually work, so it is not so much a case
of being broken, more a case of  "too cheap to follow the spec,
but we can still get the keypresses"? 

I should have been more clear.  With blacklisting, I didn't mean
to make the driver refuse them.  I was thinking about
http://www.tldp.org/HOWTO/Hardware-HOWTO/index.html
and similiar sites, where a buyer can go and look for any linux issues
with the hardware he plans to buy.  There is no problem if 50%
of all hardware ends up here - one can then read about the issues
and decide if they matter enough to get a different brand instead.

Helge Hafting

  reply	other threads:[~2006-05-09  6:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04  2:44 Dave Jones
2006-05-04  7:13 ` Pavel Machek
2006-05-04  7:17 ` Pavel Machek
2006-05-04 15:08   ` Martin J. Bligh
2006-05-04 18:34     ` Dmitry Torokhov
2006-05-04 18:38       ` Dave Jones
2006-05-05 10:31         ` Pavel Machek
2006-05-05 10:39           ` Sergei Organov
2006-05-05 10:51             ` Valdis.Kletnieks
2006-05-05 15:27           ` Dave Jones
2006-05-05 15:37             ` Martin Mares
2006-05-05 15:46               ` Dave Jones
2006-05-05 15:54                 ` Martin Mares
2006-05-05 16:00                   ` Dave Jones
2006-05-05 16:12                     ` Martin Mares
2006-05-05 19:59                     ` Nuri Jawad
2006-05-05 20:06                       ` Martin Bligh
2006-05-05 20:30                         ` Nuri Jawad
2006-05-07  8:07                           ` Joseph Fannin
2006-05-08  6:43             ` Helge Hafting
2006-05-08  7:25               ` Con Kolivas
2006-05-09  6:54                 ` Helge Hafting [this message]
2006-05-04 19:14       ` Hugh Dickins
2006-05-04 15:45   ` David Greaves
2006-05-06 18:51     ` Jindrich Makovicka
2006-05-04 14:59 ` Nuri Jawad
2006-05-04 19:24   ` Hua Zhong

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=44603CA0.2050304@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=davej@redhat.com \
    --cc=dtor_core@ameritech.net \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®