The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, linuxconsole-dev@lists.sourceforge.net
Subject: Re: 2.5 bk, input driver and dell i8100 nib+pad
Date: 10 Dec 2002 20:31:38 -0500	[thread overview]
Message-ID: <m3isy1mjd1.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <12249.1036665016@passion.cambridge.redhat.com>

>>>>> "|" == David Woodhouse <dwmw2@infradead.org> writes:

|> Weird. Does it come back to life if you suspend to RAM and resume?
|> Does the 'mouse' get detected as a Synaptics Touchpad by the
|> changed psmouse.c?

I've some more data on this.  I'd had been some time until I was able
to get a 2.5 to boot enough to run X....

Anyway, at 2.5.50 + a few csets, I had a spot where gpm could see the
nib iff /dev/mouse was symlinked to /dev/input/mice (c 13 63) but not
if it was linked to /dev/psaux (c 10 1) as it had been.

I hoped from that that X would also work, but I've not been able to
replicate that success even with gpm.  I don't know what magic insmod
made the difference (I wasn't trying to get it to work at the time,
just accidently hit the nib while at run level 3 and saw the gpm
cursor...).

As for a susend/resume cycle, this box has never been happy to do that.

-JimC


      parent reply	other threads:[~2002-12-11  1:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 15:29 2.5 bk, input driver and dell i8100 nib+pad James H. Cloos Jr.
2002-11-06 16:48 ` James H. Cloos Jr.
2002-11-06 17:04 ` David Woodhouse
2002-11-06 17:36   ` James H. Cloos Jr.
2002-11-07  4:18   ` James H. Cloos Jr.
2002-11-07  7:16     ` David Woodhouse
2002-11-07 10:11       ` James H. Cloos Jr.
2002-11-07 10:30         ` David Woodhouse
2002-11-07 13:48           ` James H. Cloos Jr.
2002-12-11  1:31           ` James H. Cloos Jr. [this message]

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=m3isy1mjd1.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    /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