linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: intelfb driver on 945GM chipset
Date: Tue, 2 Jan 2007 14:11:10 +0300	[thread overview]
Message-ID: <20070102111110.GA7689@procyon.home> (raw)
In-Reply-To: <21d7e9970701011827q714656belf91904fa9ebd63c6@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 831 bytes --]

On Tue, Jan 02, 2007 at 01:27:57PM +1100, Dave Airlie wrote:
> On 12/29/06, rami jiossy <sramij@yahoo.com> wrote:
> > here is my dmesg output.
> > as you can see below intelfb claims no video mode configured at boot time
> > inspit is does.
> 
> Intelfb doesn't support mode switching on non-CRT devices, I've
> contemplated doing the work, but I really don't have a requirement for
> it and it is a lot of work..

I have seen a board (Kontron CP306 3U CompactPCI) with which intelfb
always claims that there is a non-CRT device connected - but the board
has only a VGA output.  Probably this is just another broken BIOS...

> I'm not sure how you can get the mode set to 1024x768 before intelfb runs..

Building intelfb into the kernel and using the vga=... parameter like
with vesafb used to work in this case.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

  reply	other threads:[~2007-01-02 11:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 13:53 intelfb driver on 945GM chipset rami jiossy
2007-01-02  2:27 ` Dave Airlie
2007-01-02 11:11   ` Sergey Vlasov [this message]
2007-01-02 21:21   ` Dennis Munsie
  -- strict thread matches above, loose matches on Subject: below --
2007-01-02 11:33 rami jiossy
2007-01-02 11:31 rami jiossy
2006-12-27 20:41 rami jiossy
2006-12-27 20:46 ` James Simmons
2006-12-27 14:23 rami jiossy
2006-12-27 15:47 ` Dennis Munsie

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=20070102111110.GA7689@procyon.home \
    --to=vsu@altlinux.ru \
    --cc=airlied@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).