I've just added hackish support for transparently installing PC
keymaps on RiscPC machines. I'm not sure whether this hack will work
in every case, or even work at all.
I'll need your feedback.
This will be in console-common 0.6, about to be released.
Relevant changelog items:
* Moved ps2-
On Fri, Apr 06, 2001 at 07:35:30PM +0200, Richard Atterer wrote:
> We're stuck with this mapping, changing it is no use: In practice,
> you'd end up maintaining duplicate maps to support both 2.4 and 2.5,
> not my idea of an improvement.
If we change it for 2.5, we may have to support the alternat
On Fri, Apr 06, 2001 at 12:12:14PM +0100, [EMAIL PROTECTED] wrote:
> Yann Dirson writes:
> > There is at least the option of running gpm with the "-S ''" option so that
> > you can reboot with your mouse - or even trigger reinitialisation of the
> > keyboard, with a bit more work.
>
> Yuck. I use
Richard Atterer:
> Hm, how about a version of loadkeys which ...
Why such strange complications?
One wants the new version to be the right one, free of kludges.
For people who go back and forth between old and new a test
case `uname -r` in ...
will suffice to load the right map a boot time
On Fri, Apr 06, 2001 at 12:12:14PM +0100, [EMAIL PROTECTED] wrote:
> All the above are bodges, not a fixes.
>
> Bodges will come back to fester later. Always fix problems properly
> so it never re-appears. Don't introduce new problems that can be
> easily worked around.
Just my thoughts - however
Yann Dirson writes:
> There is at least the option of running gpm with the "-S ''" option so that
> you can reboot with your mouse - or even trigger reinitialisation of the
> keyboard, with a bit more work.
Yuck. I use all three buttons on my mouse. I don't want the machine
randomly rebooting.
On Fri, Apr 06, 2001 at 10:50:08AM +0100, [EMAIL PROTECTED] wrote:
> And what happens when you accidentally (or even purposely) unplug the
> keyboard and plug it back in? You end up with a non-functioning keyboard.
>
> Since most of these machines are used where there isn't another machine
> to c
[EMAIL PROTECTED] writes:
> So, if we make the translation table act like the i8042
> the result will be PC scancodes and all PC keymaps will work.
Indeed.
> 2.5 will start soon I suppose.
> Would you object against now [until Vojtech's patches are applied]
> switching to PC keycodes here (in 2.5
Philip Blundell writes:
> It doesn't matter. So long as you configure the keyboard for scancode set 1,
> the PC keymap will work. If you remember, this is what we do for CLPS7500.
And what happens when you accidentally (or even purposely) unplug the
keyboard and plug it back in? You end up wit
Russell King ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] writes:
> You mean that the hardware is the same but the initialization
> sets one up in scancode set 1 and the other in scancode set 2?
The keyboard hardware is the same, but what is at the end of the
keyboard cable in
>The keyboard hardware is the same, but what is at the end of the
>keyboard cable in the machine is different.
It doesn't matter. So long as you configure the keyboard for scancode set 1,
the PC keymap will work. If you remember, this is what we do for CLPS7500.
/* ibm powerpc portable
[EMAIL PROTECTED] writes:
> You mean that the hardware is the same but the initialization
> sets one up in scancode set 1 and the other in scancode set 2?
The keyboard hardware is the same, but what is at the end of the
keyboard cable in the machine is different. On a PC, the i8042
does the conve
> To make it absolutely clear, ps2 keyboard codes != pc keyboard codes.
You mean that the hardware is the same but the initialization
sets one up in scancode set 1 and the other in scancode set 2?
Andries
[EMAIL PROTECTED] writes:
> OK - but that looks like it took the i386 code, and simplified
> it to the bones, and applied a transformation to turn PC codes
> into old Acorn codes.
Ah, but they're not PC codes - they're the bare bones codes that are sent
over the wire. We don't have a PC controlle
> drivers/acorn/char/keyb_ps2.c
OK - but that looks like it took the i386 code, and simplified
it to the bones, and applied a transformation to turn PC codes
into old Acorn codes.
Maybe the author was more familiar with Acorn codes, or maybe
this is useful for compatibility.
Let me cc Russell Kin
On Fri, Apr 06, 2001 at 01:16:07AM +0200, Yann Dirson wrote:
> On Thu, Apr 05, 2001 at 11:16:28PM +0200, [EMAIL PROTECTED] wrote:
[Why does the kernel remap the PS/2 codes?]
> > > I CC Andries, who may know the answer, or may be inderested in it.
> >
> > Yes, I am interested. No, I don't know the
On Thu, Apr 05, 2001 at 11:16:28PM +0200, [EMAIL PROTECTED] wrote:
> > I CC Andries, who may know the answer, or may be inderested in it.
>
> Yes, I am interested. No, I don't know the answer.
>
> > The RiscPC kernel does an internal remapping of
> > scancodes in the keyboard driver
>
> Where in
> I CC Andries, who may know the answer, or may be inderested in it.
Yes, I am interested. No, I don't know the answer.
> The RiscPC kernel does an internal remapping of
> scancodes in the keyboard driver
Where in the kernel tree? At first sight I didnt see this in 2.4.3.
Andries
On Wed, Apr 04, 2001 at 08:49:02PM +0100, Philip Blundell wrote:
> >I'm not sure what you mean here. If one plugs a PS/2 keyboard to a RiscPC,
> >one should be able to use the same keymaps as on a PC, isn't it ? Or did I
> >miss some specificity ?
>
> No, unfortunately not. The RiscPC kernel do
I'm not CC'ing the BTS - I'm not sure what it'd do to the
attachment...
The tarball contains a "kmap-to-riscpc" script which converts the
keymaps, and a German, a UK and a US keymap. Please try them out -
after syncing! ;-) In particular, the US one is completely untested,
but I don't expect it to
In message <[EMAIL PROTECTED]>
Yann Dirson <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 04, 2001 at 02:06:36AM +0200, Richard Atterer wrote:
> > Phil wrote:
> > IMHO, the best solution would be to use the i386 keymaps, but convert
> > them to RiscPC maps (on the fly or while building the pa
>I'm not sure what you mean here. If one plugs a PS/2 keyboard to a RiscPC,
>one should be able to use the same keymaps as on a PC, isn't it ? Or did I
>miss some specificity ?
No, unfortunately not. The RiscPC kernel does an internal remapping of
scancodes in the keyboard driver, so although
On Wed, Apr 04, 2001 at 02:06:36AM +0200, Richard Atterer wrote:
> Phil wrote:
> > Yann wrote:
> > >A detailed description of the keymap will be necessary anyway; see
> > >/usr/share/debhelper/dh-consoledata/templates/keymaps for the
> > >definition of the console-data/keymap/* questions.
> >
> >
Richard Atterer wrote:
>IMHO, the best solution would be to use the i386 keymaps, but convert
>them to RiscPC maps (on the fly or while building the package) using
>just one fixed lowlevel-to-lowlevel key code map.
This does seem like a good solution. Can you supply the technology to
implement i
[Bcc'd to [EMAIL PROTECTED]
Hello,
Phil wrote:
> Yann wrote:
> >A detailed description of the keymap will be necessary anyway; see
> >/usr/share/debhelper/dh-consoledata/templates/keymaps for the
> >definition of the console-data/keymap/* questions.
>
> I don't personally have any information be
Could somebody with knowledge of RiscPCs take a look at bug #85629 and try to
supply some of the information that Yann asks for?
p.
26 matches
Mail list logo
