linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paolo Pisati <p.pisati@gmail.com>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Amiga, serial and SYSRQ
Date: Mon, 20 May 2024 07:22:34 +1200	[thread overview]
Message-ID: <6321b7d3-ee31-45eb-bb5f-28a2c74cb7fa@gmail.com> (raw)
In-Reply-To: <CAMuHMdWL2S1OMS5ikKgQj2uohoiL6_a5FLwdCphUEBVtMOSFcA@mail.gmail.com>

Hi Geert,

On 19/05/24 21:17, Geert Uytterhoeven wrote:
> Hi Michael,
>
> On Sun, May 19, 2024 at 9:37 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> On a serial console, SysRq is BREAK:
> s/serial console/virtual console/
I meant to write 'serial console' there. You will note that I carefully 
avoided the topic of sysrq on the virtual consoles because I could find 
no information on the key combo,
> Amiga keyboards do not have a SysRq key.  We used to implement it
> using SHIFT+ALTGR+HELP in the old drivers/char/amikeyb.c, but that
> feature was lost with the transition to drivers/input/keyboard/amikbd.c

Thanks - same problem in atakbd.c. What key is 'KEY_102ND'? Does it even 
exists on our keyboards?

Cheers,

     Michael


> For enabling it, you can s/KEY_HELP/KEY_SYRQ/ in
> drivers/input/keyboard/amikbd.c.
>
>> On the serial console (PC style standard serial ports only)
> drivers/tty/amiserial.c does support break, so that should work, too.
>
> Gr{oetje,eeting}s,
>
>                          Geert
>

  reply	other threads:[~2024-05-19 19:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 18:17 Amiga, serial and SYSRQ Paolo Pisati
2024-05-19  7:36 ` Michael Schmitz
2024-05-19  9:17   ` Geert Uytterhoeven
2024-05-19 19:22     ` Michael Schmitz [this message]
2024-05-19 20:09       ` Geert Uytterhoeven
2024-05-20 21:03         ` Michael Schmitz
2024-05-19 13:24   ` Paolo Pisati
2024-05-19 13:31     ` Geert Uytterhoeven
2024-05-19 13:54       ` Paolo Pisati
2024-05-19 19:12         ` Michael Schmitz
2024-05-20 17:08           ` Paolo Pisati
2024-05-19 14:58 ` Geert Uytterhoeven
2024-05-20 17:17   ` Paolo Pisati
2024-05-20 21:01     ` Michael Schmitz
2024-05-20 21:15       ` Andreas Schwab
2024-05-20 22:01         ` Michael Schmitz
2024-05-21  7:07       ` Geert Uytterhoeven
2024-05-21 17:56         ` Paolo Pisati
2024-05-21 21:11         ` Michael Schmitz

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=6321b7d3-ee31-45eb-bb5f-28a2c74cb7fa@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=p.pisati@gmail.com \
    /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).