From: Egbert Eich <eich@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Egbert Eich <eich@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: vgacon fixes to help font restauration in X11
Date: Mon, 17 Jan 2005 10:07:51 +0100 [thread overview]
Message-ID: <16875.32871.47983.655764@xf14.local> (raw)
In-Reply-To: alan@lxorguk.ukuu.org.uk wrote on Saturday, 15 January 2005 at 00:33:44 +0000
[Please leave me in Cc: as I'm not subscribed to this list]
Alan Cox writes:
> On Maw, 2005-01-11 at 14:28, Egbert Eich wrote:
> > I'm fully aware that in the long run we will need to look into a new
> > driver model for graphics where no two instances fight over who gets
> > register access. However such a model won't be created nor will we get
> > the majority of the drivers ported over night.
> > Therefore we need to find an interim solution for the most pressing
> > problems.
>
> This doesn't appear to work as a solution because the functionality
> changes won't be in all the existing kernel, and also because the kernel
> font save has a couple of bugs reported against it with regards to
> saving the right data that might need looking at anyway.
Can you point me to these reports?
I tested with a couple chipsets here and didn't find any problems.
Maybe we can compare the code in X with the code in the kernel
for the amount of data to save.
However we don't know if the X font code is completely without
problems. I remeber fixing a problem in X years ago - a case
where the kernel got it right ;-)
X VGA font code involves a lot of magic. Also things might differ
slightly form HW vendor to vendor and it will be extremely hard
to get it right for all chipset models therefore I would not even
talk about 'bugs' ;-)
>
> It seems it would be neccessary for X to have a way to know whether the
> feature is present.
>
We could check for the kernel version. This could be done during build
time - assuming we don't ship generic binaries or during run time if we
want to provide binaries that work everywhere.
In reality the former would be sufficient for a lot of cases - especially
for vendor supplied binaries.
Once X.Org starts shipping binaries it should definitely provide a version
that fits everywhere.
But maybe you have a better suggestion.
Anyway, would my patch be acceptable for the kernel?
Cheers,
Egbert.
next prev parent reply other threads:[~2005-01-17 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 14:28 vgacon fixes to help font restauration in X11 Egbert Eich
2005-01-15 0:33 ` Alan Cox
2005-01-17 9:07 ` Egbert Eich [this message]
2005-01-17 12:23 ` Alan Cox
2005-01-17 14:29 ` Egbert Eich
2005-01-17 16:30 ` Alan Cox
2005-01-18 8:31 ` Egbert Eich
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=16875.32871.47983.655764@xf14.local \
--to=eich@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).