linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Huber <huber@mclx.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: gpm and XF401 (Re: ADB-Mouse)
Date: Mon, 23 Oct 2000 12:27:16 -0400	[thread overview]
Message-ID: <20001023122716.D426@missioncriticallinux.com> (raw)
In-Reply-To: <20001023150002.A3112@suse.de>; from olh@suse.de on Mon, Oct 23, 2000 at 03:00:02PM +0200

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

On Mon, Oct 23, 2000 at 03:00:02PM +0200, Olaf Hering wrote:
> You mean you mark some text at console with gpm and all you get in the
> selected area is garbage, even with a non psaux device?
> I tried it here on a chrp machine and got the same effect, could be a
> framebuffer bug. Anyone else with that problem?
> 
> I have XF4 here with kernel 2.4 and no problems at all (fbdev driver).

I have the same problem on a g4 (r128 fb driver) when using 2.4.

I haven't had the time to look into it, but selecting text in console
mode is definately broken.  It looks like it's somehow using the wrong
characters for the highlighted versions of the text.

Anyone have any ideas,

-- 
Josh
| huber@mclx.com |
1024D/6B21489A 61F0 6138 BE7B FEBF A223  E9D1 BFE1 2065 6B21 489A

[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

  parent reply	other threads:[~2000-10-23 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200010210500.AAA23065@lists.linuxppc.org>
2000-10-23 11:39 ` COPTS for Makefile LinuxPPC 2000 Derek Homeier
2000-10-23 15:35   ` William Blew
2000-10-23 17:38   ` gpm and XF401 (Re: ADB-Mouse) Derek Homeier
2000-10-23 12:55 ` Henning Lvser
2000-10-23 13:00   ` Olaf Hering
2000-10-23 13:06     ` Henning Lvser
2000-10-23 15:40     ` William Blew
2000-10-23 16:27     ` Josh Huber [this message]
2000-10-23 18:03       ` Geert Uytterhoeven

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=20001023122716.D426@missioncriticallinux.com \
    --to=huber@mclx.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).