public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@drugphish.ch>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Leonard Milcin Jr." <leonard.milcin@post.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: keyboard driver of 2.6 kernel
Date: Thu, 05 Jan 2006 13:43:23 +0100	[thread overview]
Message-ID: <43BD146B.2010308@drugphish.ch> (raw)
In-Reply-To: <Pine.LNX.4.61.0601051249030.21555@yvahk01.tjqt.qr>

>>But http://ttyrpld.sourceforge.net/ looks indeed interesting, however no 2.4.x
>>support from what I can see.
>  
> Do you really need 2.4 support?

Well, 90% of our managed Linux servers run 2.4.x kernels. Granted, 
that's only a couple of hundred nodes scattered all over the world; but 
the question is more, if I really want to integrate ttypld into our 
kernel/distro.

> Well, after all, I can add it back, it's 
> not too much #defines and stuff.

I'll let you know if I need it; I reckon it might not be too difficult 
to backport it anyway, so I can also do it myself ;).

Thanks and best regards,
Roberto Nibali, ratz
-- 
echo 
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc

  reply	other threads:[~2006-01-05 12:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  8:32 keyboard driver of 2.6 kernel P.Manohar
2006-01-04  8:33 ` Arjan van de Ven
2006-01-04  9:07   ` Leonard Milcin Jr.
2006-01-04  9:23     ` Jan Engelhardt
2006-01-05 10:08       ` [OT] " Roberto Nibali
2006-01-05 11:51         ` Jan Engelhardt
2006-01-05 12:43           ` Roberto Nibali [this message]
2006-01-05 21:07             ` Nuno Monteiro
2006-01-05 23:28               ` Roberto Nibali
2006-01-06  7:01                 ` Jan Engelhardt
2006-01-06 10:28                   ` Nuno Monteiro
2006-01-05 11:58         ` Leonard Milcin Jr.
2006-01-05 12:47           ` Roberto Nibali
2006-01-04 16:25   ` 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=43BD146B.2010308@drugphish.ch \
    --to=ratz@drugphish.ch \
    --cc=jengelh@linux01.gwdg.de \
    --cc=leonard.milcin@post.pl \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox