From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Jonathan Sambrook <swsusp@hmmn.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Swsusp mailing list <swsusp-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]
Date: Tue, 23 Mar 2004 23:17:56 +0100 [thread overview]
Message-ID: <20040323221756.GF364@elf.ucw.cz> (raw)
In-Reply-To: <1080076132.12965.18.camel@calvin.wpcb.org.au>
Hi!
> if/when its needed. I'm also of a mind to not include the original
> text-mode 'nice display' and just use the Bootsplash support.
Yes, that would be great. [Bootsplash is in mainline but is in vendor
kernels => great, vendor kernels get splashscreen with progress bar
and vanilla kernel just plain old dots].
> Of course there's also the point that you're assuming I'm going to
> disappear into the wild blue yonder after it's merged. That assumption
> has no basis from my perspective.
Ok, sorry about that one.
> > Oh and it is enough confusing that it confuses me. Some messages end
> > in dmesg, some do not. User feedback can be done with much less code,
> > and also slightly less confusing for the user, see swsusp1. [We have
> > to switch to another console, anyway; and printing dots is easy.]
>
> As I said above, much of the code was from debugging and can be removed.
> Nevertheless, the interface is not that confusing:
If it slims down a lot, great. If debugging code is gone, and progress
bar depends on bootsplash, we are left with something that looks like
output from swsusp1, right? And there should be little need to
configure it. Good.
> > Okay, we should probably make suspend more quiet, I can see users
> > badly confused by those hdX: spinning down (etc) messages.
>
> That's fine, but those messages aren't related to my code.
Yes, thats _my_ todo.
> > Also, in your model, where do messages printk()-ed from drivers during
> > suspend/resume end up? Corrupting screen? Lost from sight and only
> > accessible from dmesg? I believe driver messages *are* important, and
> > do not see how they could coexist with eye-candy.
>
> They do go in the logs. An important exception though (which applies to
> all implementations): messages displayed after the atomic copy is made
> (while suspending) or before the kernel is copied back (resuming) as
> lost because the printk buffer is overwritten,
Yes, but with eye candy its a bit more of a problem because progress
bar updating could obscure them.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-23 22:18 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1079659165.15559.34.camel@calvin.wpcb.org.au>
[not found] ` <20040318193703.4c02f7f5.akpm@osdl.org>
[not found] ` <1079661410.15557.38.camel@calvin.wpcb.org.au>
[not found] ` <20040318200513.287ebcf0.akpm@osdl.org>
[not found] ` <1079664318.15559.41.camel@calvin.wpcb.org.au>
2004-03-21 22:00 ` swsusp problems [was Re: Your opinion on the merge?] Pavel Machek
2004-03-22 0:29 ` Pavel Machek
2004-03-22 20:55 ` Nigel Cunningham
2004-03-22 23:17 ` Pavel Machek
2004-03-23 9:53 ` [Swsusp-devel] " Jonathan Sambrook
2004-03-23 15:25 ` Micha Feigin
2004-03-23 21:47 ` Pavel Machek
2004-03-23 21:08 ` Nigel Cunningham
2004-03-23 22:17 ` Pavel Machek [this message]
2004-03-23 22:38 ` Nigel Cunningham
2004-03-23 23:07 ` Michael Frank
2004-03-23 23:17 ` Pavel Machek
2004-03-23 22:36 ` Nigel Cunningham
2004-03-23 23:45 ` Dumitru Ciobarcianu
2004-03-23 22:52 ` Nigel Cunningham
2004-03-24 0:05 ` Joel Jaeggli
2004-03-23 23:10 ` Nigel Cunningham
2004-03-23 22:43 ` Dmitry Torokhov
2004-03-23 23:32 ` Pavel Machek
2004-03-23 22:40 ` Nigel Cunningham
2004-03-23 23:44 ` Pavel Machek
2004-03-24 3:12 ` Michael Frank
2004-03-24 10:17 ` Pavel Machek
2004-03-24 22:46 ` Michael Frank
2004-03-24 23:23 ` Pavel Machek
2004-03-24 23:56 ` Michael Frank
2004-03-25 0:23 ` -nice tree [was Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]] Pavel Machek
2004-03-25 0:50 ` Michael Frank
2004-03-25 1:41 ` Pavel Machek
[not found] ` <200403250857.08920.matthias.wieser@hiasl.net>
2004-03-25 20:39 ` Nigel Cunningham
2004-03-25 22:27 ` Pavel Machek
2004-03-25 21:38 ` Nigel Cunningham
2004-03-25 22:54 ` Pavel Machek
2004-03-26 5:59 ` Michael Frank
2004-03-26 10:50 ` Pavel Machek
2004-03-26 13:17 ` Michael Frank
2004-03-27 14:49 ` Jamie Lokier
2004-03-29 12:10 ` fast compressed fs (was Re: -nice tree) Pavel Machek
2004-03-26 5:59 ` -nice tree [was Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]] Michael Frank
2004-03-26 10:22 ` Pavel Machek
2004-03-26 20:30 ` Nigel Cunningham
2004-03-26 22:22 ` Pavel Machek
2004-03-27 2:08 ` Nigel Cunningham
2004-03-27 3:37 ` Luke-Jr
2004-03-27 4:28 ` Micha Feigin
2004-03-27 4:40 ` Luke-Jr
2004-03-27 19:50 ` Micha Feigin
2004-03-27 20:03 ` Luke-Jr
2004-03-27 21:01 ` Paranoia is fun [Was Re: -nice tree [was Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]]] Michael Frank
2004-03-27 21:40 ` Luke-Jr
2004-03-27 21:29 ` -nice tree [was Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]] Pavel Machek
2004-03-28 0:27 ` Micha Feigin
2004-03-27 2:21 ` Micha Feigin
2004-03-29 12:13 ` Pavel Machek
2004-03-24 4:52 ` [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?] Dmitry Torokhov
2004-03-24 5:04 ` Nigel Cunningham
2004-03-24 6:22 ` Michael Frank
2004-03-24 5:46 ` Nigel Cunningham
2004-03-24 7:31 ` Michael Frank
2004-03-24 10:26 ` Pavel Machek
2004-03-25 0:06 ` Jonathan Sambrook
2004-03-24 9:32 ` Karol Kozimor
2004-03-24 14:15 ` Michael Frank
2004-03-25 0:35 ` Karol Kozimor
2004-03-24 5:06 ` sleeping in request function mohanlal jangir
[not found] ` <20040324083313.GG3377@suse.de>
2004-03-25 3:45 ` mohanlal jangir
2004-03-24 10:22 ` [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?] Pavel Machek
2004-03-24 12:48 ` Dmitry Torokhov
2004-03-24 15:18 ` Pavel Machek
2004-03-24 20:22 ` Jonathan Sambrook
2004-03-24 21:06 ` Michael Frank
2004-03-25 22:13 ` swsusp is not reliable. Face it. [was Re: [Swsusp-devel] Re: swsusp problems] Pavel Machek
2004-03-25 21:33 ` Nigel Cunningham
2004-03-25 22:52 ` Pavel Machek
2004-03-26 5:59 ` Michael Frank
2004-03-26 9:59 ` Pavel Machek
2004-03-26 10:21 ` Michael Frank
2004-03-25 22:08 ` [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?] Pavel Machek
2004-03-24 22:05 ` Markus Gaugusch
2004-03-24 21:25 ` Nigel Cunningham
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=20040323221756.GF364@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=swsusp@hmmn.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