From: "Jon Dufresne" <jon.dufresne@gmail.com>
To: Scott Mcdermott <vaxerdec@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: intelfb crashes during modprobe
Date: Mon, 18 Aug 2008 11:32:41 -0700 [thread overview]
Message-ID: <376ea3380808181132v18ece4aby939e8feaf533e766@mail.gmail.com> (raw)
In-Reply-To: <20080818154126.GA3281@omnius.localdomain>
I gave the kernel modesetting option a shot. It actually appears to
get me to a framebuffer much smoother than the previous method. I have
a good looking 720p framebuffer on the CRT port that I can play videos
with. I am quite happy about that thanks.
I have a HDMI port attached to the same chip, using DVO port C. Using
this port has much different results than the CRT port. I looked
through the DMESG and the kernel code and it appears that all non-crt
ports do not support mode switching.
Is there a hardware limitation reason for this?
I commented out the line in the kernel intelfb driver that disables
mode switching for the non-CRT ports, I had no luck (thought I'd give
it a shot just in case).
Anyone have an idea what it would take to fix this? I would be willing
to give it a shot as this box will ideally hook up to a tv using HDMI,
not a CRT monitor. I just need an idea where to start.
Thanks,
Jon
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next prev parent reply other threads:[~2008-08-18 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 15:21 intelfb crashes during modprobe Jon Dufresne
2008-08-14 16:14 ` Scott Mcdermott
2008-08-18 15:03 ` Jon Dufresne
2008-08-18 15:41 ` Scott Mcdermott
2008-08-18 18:32 ` Jon Dufresne [this message]
2008-08-17 18:09 ` Krzysztof Helt
2008-08-18 15:00 ` Jon Dufresne
2008-08-18 15:09 ` Geert Uytterhoeven
2008-08-18 15:19 ` Jon Dufresne
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=376ea3380808181132v18ece4aby939e8feaf533e766@mail.gmail.com \
--to=jon.dufresne@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=vaxerdec@gmail.com \
/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