From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Re: xorg-server-1.5.2 doesn't work because of missing sysfs pci resource files
Date: Tue, 9 Dec 2008 17:57:02 +0000 [thread overview]
Message-ID: <20081209175701.GA22661@linux-mips.org> (raw)
In-Reply-To: <20081209173907.GB2741@adriano.hkcable.com.hk>
On Wed, Dec 10, 2008 at 01:39:08AM +0800, Zhang Le wrote:
> > I have build a new kernel with this patch.
> > Now I have the resource{0,1} file with permission 600.
> > However, X is not working yet, since there is an undefined reference in sis's
> > X driver.
>
> It is working now! Just forget to load "vbe" module.
> Thanks!
Wonderful, thanks for testing!
Now, my patch doesn't try to handle all the caching modes. Any mapping
will be uncached which is guaranteed to deliver the lowest possible
performance. Registers should be mapped uncached but a framebuffer
will usually work best if mapped in uncached accelerated mode. On
most MIPS implementations the effect of mapping something multiple times
in different caching modes is undefined so that needs to be avoided
which will require some bookkeeping etc. Too much for 2.6.28 but this
simple solution seems harmless enough to be pushed for 2.6.28 and
-stable.
Ralf
next prev parent reply other threads:[~2008-12-09 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 15:43 xorg-server-1.5.2 doesn't work because of missing sysfs pci resource files Zhang Le
2008-12-05 17:59 ` Arnaud Patard
2008-12-05 18:08 ` Ralf Baechle
2008-12-06 10:20 ` Ralf Baechle
2008-12-06 16:47 ` Zhang Le
2008-12-09 17:22 ` Zhang Le
2008-12-09 17:39 ` Zhang Le
2008-12-09 17:57 ` Ralf Baechle [this message]
2008-12-09 18:17 ` Arnaud Patard
2008-12-09 18:36 ` Ralf Baechle
2008-12-09 19:01 ` Arnaud Patard
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=20081209175701.GA22661@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.