From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: S3 suspend and serial console
Date: Mon, 07 Feb 2005 18:14:57 +0100 [thread overview]
Message-ID: <4207A211.3000305@gmx.net> (raw)
In-Reply-To: <20050207143242.GE8040-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
Pavel Machek schrieb:
> Hi!
>
>
>>>>Erm... is it intentional that serial powermanagement code is never
>>>>called on entering/leaving S3? When I added debugging statements
>>
>>>Probably noone was yet trying to use serial during suspend....
>>
>>You mean noone uses the serial console while testing suspend?
>>What is the new way to debug suspend problems not requiring a
>>serial console?
>
> Well, when video works, you debug using video. I used hardware
> debugger, too...
Will there be any patch to actually use the powermanagement code
in the serial core?
Regarding the original problem:
It seems the following call is sufficient to make the console work
again. However, I haven't found a function which would give me
the parameters needed to call ->set_termios.
serial/8250.c: serial8250_set_termios
Do you have any idea how to obtain the termios and tty structures
for a given port, e.g. ttyS0?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-07 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 14:09 S3 suspend and serial console Carl-Daniel Hailfinger
[not found] ` <42023083.8030508-hi6Y0CQ0nG0@public.gmane.org>
2005-02-05 13:29 ` Carl-Daniel Hailfinger
[not found] ` <4204CA50.8090906-hi6Y0CQ0nG0@public.gmane.org>
2005-02-05 15:58 ` Karol Kozimor
[not found] ` <20050205155845.GA20131-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-02-05 22:06 ` Stefan Seyfried
[not found] ` <20050205220619.GA30739-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-02-07 2:16 ` Carl-Daniel Hailfinger
[not found] ` <4206CF63.2090600-hi6Y0CQ0nG0@public.gmane.org>
2005-02-07 14:16 ` Pavel Machek
[not found] ` <20050207141655.GB8040-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-02-07 14:28 ` Carl-Daniel Hailfinger
[not found] ` <42077B07.5090606-hi6Y0CQ0nG0@public.gmane.org>
2005-02-07 14:32 ` Pavel Machek
[not found] ` <20050207143242.GE8040-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-02-07 17:14 ` Carl-Daniel Hailfinger [this message]
[not found] ` <4207A211.3000305-hi6Y0CQ0nG0@public.gmane.org>
2005-02-07 22:04 ` Nigel Cunningham
2005-02-08 12:54 ` Pavel Machek
[not found] ` <20050208125453.GA1622-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-02-08 14:02 ` Carl-Daniel Hailfinger
[not found] ` <4208C674.1000002-hi6Y0CQ0nG0@public.gmane.org>
2005-02-08 16:31 ` Pavel Machek
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=4207A211.3000305@gmx.net \
--to=c-d.hailfinger.devel.2005-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.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