From: Vojtech Pavlik <vojtech@suse.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New Input PS/2 driver
Date: Sat, 6 Oct 2001 01:07:25 +0200 [thread overview]
Message-ID: <20011006010725.A18843@suse.cz> (raw)
In-Reply-To: <20011006005006.A17152@suse.cz> <Pine.LNX.4.10.10110051558000.31239-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10110051558000.31239-100000@transvirtual.com>; from jsimmons@transvirtual.com on Fri, Oct 05, 2001 at 04:02:08PM -0700
On Fri, Oct 05, 2001 at 04:02:08PM -0700, James Simmons wrote:
>
> > > Not implemented yet.
> >
> > Quite the opposite: #undef was forgotten in the .h file after the .c
> > file converted to a runtime option instead of a compiletime one. I
> > removed it in the CVS now.
>
> Okay. Another thing is how to deal with IRQ's and the port regions. This
> can vary from platform to platform. We could have this as a command line
> option as well. In fact we might since it can be built as a module. Alot
> of platforms added things to the command line inside the kernel code.
> Or we can do lots of #ifdef in i8042.h or using the asm/keyboard method
> like now. Personally I don't like this method since even on mips the i8042
> port range varies on different machines. So we still end up with a bunch
> of messy #ifdef.
I'd prefer a bunch of #ifdefs in i8042.h with defaults and a command
line option to change that if needed. For some of the more differing
architectures (Sun Ultra AX) which have i8042-alike chips in them
complete separate drivers may make sense as well.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-10-05 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 13:34 New Input PS/2 driver Etienne Lorrain
2001-10-03 19:28 ` James Simmons
2001-10-05 22:50 ` Vojtech Pavlik
2001-10-05 23:02 ` James Simmons
2001-10-05 23:07 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 4:47 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:
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=20011006010725.A18843@suse.cz \
--to=vojtech@suse.cz \
--cc=etienne_lorrain@yahoo.fr \
--cc=jsimmons@transvirtual.com \
--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