From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] what change of vesa...
Date: Sun, 7 Jun 2015 22:49:23 +0200 [thread overview]
Message-ID: <90445d4090491ca8ef71805b109ea8d4@felloff.net> (raw)
In-Reply-To: <59CBA0461FDA4C33A403BE5428B85959@jitaku.localdomain>
> What were the changes on this vesa related timing things
> cinap reported before. Can I see the difference of old and
> new codes. As I mentioned above, I crushed my file server,
> and cannot see them by myself.
vesa shouldnt be affected by that at all. the timings are required
for native drivers. what went in new is that nvidiascale stuff,
maybe that screws up on your card. have you tried commenting it
out?
--
cinap
next prev parent reply other threads:[~2015-06-07 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 5:43 Kenji Okamoto
2015-06-05 5:47 ` [9front] " Kurt H Maier
2015-06-07 20:49 ` cinap_lenrek [this message]
2015-06-08 0:21 ` Kenji Okamoto
2015-06-07 15:34 ` kokamoto
2015-06-08 0:43 ` cinap_lenrek
2015-06-08 0:30 ` cinap_lenrek
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=90445d4090491ca8ef71805b109ea8d4@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).