From: Anand Gadiyar <gadiyar@ti.com>
To: Manjunath Kondaiah G <manjugk@ti.com>,
Govindraj <govindraj.ti@gmail.com>
Cc: Thomas Weber <weber@corscience.de>,
linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Govindraj Raja <govindraj.raja@ti.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Andrei Emeltchenko <andrei.emeltchenko@nokia.com>,
linux-kernel@vger.kernel.org
Subject: RE: [PATCHv2] OMAP: Enable Magic SysRq on serial console ttyOx
Date: Thu, 20 Jan 2011 17:49:42 +0530 [thread overview]
Message-ID: <38f2b3af600ce3dfea1e73edec7c81fa@mail.gmail.com> (raw)
In-Reply-To: <20110120114855.GD1987@m-desktop>
> > >>>> Magic SysRq key is not working for OMAP on new serial
> > >>>> console ttyOx because SUPPORT_SYSRQ is not defined
> > >>>> for omap-serial.
> > >>>>
> > >>>> This patch defines SUPPORT_SYSRQ in omap-serial and
> > >>>> enables handling of Magic SysRq character.
> > >>>>
> > >>>> Signed-off-by: Thomas Weber <weber@corscience.de>
> > >>>
> > >>> Looks fine to me.
> > >>>
> > >>> Acked-by: Govindraj.R <govindraj.raja@ti.com>
> > >> I tried to use SysRq key on minicom after applying this patch, it
looks
> > >> like it is not triggering sysrq event.
> > >>
> > >> Am I missing anything?
> > >>
> > >> -Manjunath
> > >> --
> > > Hello Manjunath,
> > >
> > > Do you have CONFIG_MAGIC_SYSRQ enabled?
> > > Magic SysRq key in Kernel Hacking
> > >
> > > I tested it on Devkit8000 (beagle board clone).
> > >
> >
> > re-setting lsr_break_flag to 0 in receive chars is causing issues
> > in getting sysrq key break sequence on omap-serial.c
> >
> > Manju,
> >
> > can you try this change on your environment.
> > With below change works for me on 3430SDP/4430SDP.
> > key sequence I checked.
> > [alt + b + t] => shows trace of tasks running.
> > [alt + b + b] => system reboot.
>
> With below patch, it works fine on TeraTerm. However, I am not able to
> perform the same on minicom.
>
> Tested-by: Manjunath G Kondaiah <manjugk@ti.com>
>
> -Manjunath
>
Not sure what you guys are trying out, but I am able to use sysrq
just fine in minicom (using only Thomas' original patch) - you need
to send a break sequence, and the way to do this in minicom is to
do Ctrl-A followed by F.
Works for me, without the "resetting lsr_break_flag to 0" part.
@Govind,
What are the issues you see in getting sysrq key break sequence
without your change? And how is your change fixing this?
- Anand
next prev parent reply other threads:[~2011-01-20 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 8:41 [PATCHv2] OMAP: Enable Magic SysRq on serial console ttyOx Thomas Weber
2011-01-19 9:31 ` Govindraj
2011-01-19 13:00 ` G, Manjunath Kondaiah
2011-01-19 13:31 ` Thomas Weber
2011-01-19 13:58 ` Govindraj
2011-01-20 6:58 ` Thomas Weber
2011-01-20 11:48 ` G, Manjunath Kondaiah
2011-01-20 12:19 ` Anand Gadiyar [this message]
2011-01-21 7:24 ` Govindraj
2011-01-21 7:45 ` G, Manjunath Kondaiah
2011-01-21 9:08 ` Govindraj
2011-01-22 1:03 ` Kevin Hilman
2011-01-22 17:13 ` Govindraj
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=38f2b3af600ce3dfea1e73edec7c81fa@mail.gmail.com \
--to=gadiyar@ti.com \
--cc=andrei.emeltchenko@nokia.com \
--cc=govindraj.raja@ti.com \
--cc=govindraj.ti@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=tony@atomide.com \
--cc=weber@corscience.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;
as well as URLs for NNTP newsgroup(s).