linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linuxppc-dev@lists.linuxppc.org,
	linux-apus-devel@lists.sourceforge.net
Subject: Re: newer xfree86 4.0.1 patches
Date: Fri, 08 Sep 2000 03:23:08 +0200	[thread overview]
Message-ID: <39B83F7C.EA7B41FF@student.ethz.ch> (raw)
In-Reply-To: 00090723415902.31531@enzo.bigblue.local


Franz Sirl wrote:

> > > - what's the keycode situation in XF3/4 for Apus?
> >
> > AFAIK it isn't very clean with either, the best bet is still to disable
> > Xkb.
>
> On PPC we can switch the keycodes between ADB and Linux with a sysctl. Linux
> keycodes are ~95% compatible with AT keycodes, so XKB will work.

That would be great IMHO.


> > > - if your developer repository for 2.4 is different from BK
> > > linuxppc_2_3, did you integrate your input layer drivers in your trees
> > > and plan to submit them for 2.4?
> >
> > We have a CVS repository at SourceForge. Roman Zippel integrates bitkeeper
> > into it, but unfortunately we don't have anyone for the reverse direction.
> > How could that be done?
>
> Via Linus probably, but in this special case we could arrange something.

Please post to linux-apus-devel@lists.sourceforge.net what we'd have to do.


> > > If you want to keep the current state of affairs I can see in the
> > > linuxppc_2_3 tree, there's not much point in using machid.c, AFAICS. On
> > > the other hand, if you plan to integrate your input drivers into 2.4, it
> > > makes perfect sense.
> >
> > I think it would be nice, but to be honest I don't fully understand what
> > would be involved.
>
> Actually not much, given the Apus input drivers in the linuxconsole
> repository ("ruby") on sourceforge are already functional,

I don't know, so I assume not :(

> it's simply a matter of copying the files and modifying the configuration
> scripts. If you want to continue to support Apus keycodes, you need some
> translation code in input/keybdev.c too.

Thanks.


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-09-08  1:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-06 19:32 newer xfree86 4.0.1 patches Olaf Hering
2000-09-07  9:53 ` Geert Uytterhoeven
2000-09-07 12:09   ` Olaf Hering
2000-09-07 12:42   ` Franz Sirl
2000-09-07 12:54     ` Michel Dänzer
2000-09-07 15:03       ` Franz Sirl
2000-09-07 15:09         ` Michel Dänzer
2000-09-07 16:59           ` Geert Uytterhoeven
2000-09-07 21:43             ` Michael Schmitz
2000-09-07 21:55             ` Franz Sirl
2000-09-08  9:57               ` Kostas Gewrgiou
2000-09-08 10:33                 ` Franz Sirl
2000-09-07 21:41           ` Franz Sirl
2000-09-08  1:23             ` Michel Dänzer [this message]
2000-09-08 14:31               ` Franz Sirl
2000-09-08 16:16                 ` Michel Dänzer
2000-09-09 10:16             ` Roman Zippel

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=39B83F7C.EA7B41FF@student.ethz.ch \
    --to=daenzerm@student.ethz.ch \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-apus-devel@lists.sourceforge.net \
    --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).