From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Ben Collins <bcollins@swissdisk.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VT: Restore VT fonts on switch
Date: Fri, 8 Aug 2008 09:49:17 +0200 [thread overview]
Message-ID: <20080808074916.GB10657@ucw.cz> (raw)
In-Reply-To: <20080721222428.20395240@lxorguk.ukuu.org.uk>
Hi!
> > > > > do you have a list of which ones don't ?
> > > >
> > > > I don't, but perhaps Matthew does.
> > >
> > > Perhaps Matthew would care to file X bugs against those that get it wrong
> > > then.
> >
> > It's hardly limited to X. Fonts are set through the kernel - why
> > shouldn't it be the kernel's responsibility to ensure that they're
> > restored?
>
> Why should it be the kernels problem to clean up after buggy X drivers ?
>
> There are cases the kernel probably should handle font restore: the
> obvious one being suspend/resume. X is not one of those cases and wasting
> memory on fonts on embedded boxes that will never be seen anyway seems
> silly.
>
> For suspend/resume it might be far better to do it in user space,
> although I'm not sure what the interface would look like.
This does not parse. 'kernel should handle font restore' .... 'but it
might be better to do that in userspace'.
Actually I'd prefer to do this in kernel, so it works in cases like
suspend self-test (done from kernel), from single user mode, etc...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-08-08 7:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 19:39 [PATCH] VT: Restore VT fonts on switch Matthew Garrett
2008-07-21 20:40 ` Alan Cox
2008-08-08 9:32 ` Benjamin Herrenschmidt
2008-07-21 20:43 ` Arjan van de Ven
2008-07-21 20:53 ` Ben Collins
2008-07-21 21:12 ` Alan Cox
2008-07-21 21:37 ` Matthew Garrett
2008-07-21 21:24 ` Alan Cox
2008-08-08 7:49 ` Pavel Machek [this message]
2008-07-21 21:23 ` Arjan van de Ven
2008-07-21 21:40 ` Ben Collins
2008-07-21 22:18 ` Arjan van de Ven
2008-07-21 22:29 ` Ben Collins
2008-07-21 20:54 ` Jan Engelhardt
2008-07-22 7:59 ` Arkadiusz Miskiewicz
2008-08-08 7:44 ` 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=20080808074916.GB10657@ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=bcollins@swissdisk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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