archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <>
To: Andrey Borzenkov <>
Cc: Linux Kernel Development <>
Subject: Re: PATCH: mouse and keyboard by default if not embedded
Date: Sun, 10 Aug 2003 11:51:46 +0200 (MEST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, 10 Aug 2003, Andrey Borzenkov wrote:
> > Now INPUT_MOUSEDEV_PSAUX is always (on non-embedded machines) forced to 
> true,
> > even on machines without PS/2 keyboard/mouse hardware. Is that OK?
> > So far (compiling, not running 2.6.0-test3) I didn't notice any problems,
> > though
> there are problems. See
> mouse/atkbd depend on serio driver (i8042) so if i8042 is module and they are 
> forced to be builtin the whole story does not work.
> apparently there are people who build them as modules

I don't have CONFIG_SERIO_I8042 enabled at all, since I'm compiling for a m68k
box without i8042. But it does compile/link.



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2003-08-10  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  9:34 PATCH: mouse and keyboard by default if not embedded Andrey Borzenkov
2003-08-10  9:51 ` Geert Uytterhoeven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-12  9:21 "Andrey Borzenkov" 
2003-08-15 23:15 ` James Simmons
2003-08-10 10:17 Mikael Pettersson
2003-07-27 20:03 Alan Cox
2003-07-28  7:14 ` Christoph Hellwig
2003-08-08 10:27   ` Rob Landley
2003-08-10  8:42 ` Geert Uytterhoeven
2003-08-11 17:40   ` James Simmons

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).