From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@uni-koblenz.de>,
Harald Koerfgen <Harald.Koerfgen@home.ivm.de>,
Craig P Prescott <prescott@phys.ufl.edu>,
linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: BREAK and magic SysRq handling for Z8530
Date: Wed, 09 Aug 2000 12:08:51 +0400 [thread overview]
Message-ID: <39911193.672C7E59@niisi.msk.ru> (raw)
In-Reply-To: Pine.GSO.3.96.1000807174812.3044E-100000@delta.ds2.pg.gda.pl
Maciej,
"Maciej W. Rozycki" wrote:
>
> Hi,
>
> It appears our current Z8530 driver lacks BREAK support. It also has the
> unfortunate side effect magic SysRq wouldn't work either, if we had it.
> Not anymore! The following patch adds both features to our Z8530 driver.
> It also allows the magic SysRq hack to be compiled-in (i.e. no more
> linking errors) even if no virtual terminal driver is build, which is
> suitable for certain configurations, including mine.
>
Have you tested the patch? The problem isn't in the patch itself, but as
I see the zs driver is broken for a long time. At least, I used to patch
heavily this driver for my Baget taht has 2 zs chips on board. Harald
has the plans to implement new version of the driver, but I guess he is
busy all the time. Or have I missed a cleanup of the driver ?
Also, changes in sunkbd.c, keyboard.c, and serial.c isn't a good idea.
:-)
Regards,
Gleb.
next prev parent reply other threads:[~2000-08-09 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-07 15:56 BREAK and magic SysRq handling for Z8530 Maciej W. Rozycki
2000-08-09 8:08 ` Gleb O. Raiko [this message]
2000-08-09 9:38 ` Maciej W. Rozycki
2000-08-09 16:13 ` Ralf Baechle
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=39911193.672C7E59@niisi.msk.ru \
--to=raiko@niisi.msk.ru \
--cc=Harald.Koerfgen@home.ivm.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=prescott@phys.ufl.edu \
--cc=ralf@uni-koblenz.de \
/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