All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Buttchereit, Axel (XL)" <xl@xlsigned.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: intelfb does not work with i915
Date: Fri, 22 Jul 2005 05:01:40 +0200	[thread overview]
Message-ID: <42E06194.9030100@xlsigned.net> (raw)
In-Reply-To: <6d86e88105072010252790b42d@mail.gmail.com>

Hi,

this weekend I'm going to switch the kernel version on the computer
that I used to develop the patch from 2.6.10 (+ original patch)
to 2.6.12(-gentoo-r4) and give (you) a feedback.

ByTheWay:
  16 Bits per Pixel does not work on my computer, too.
  Have you tried a 32 Bit mode, e. g. 1024x768-32@70?
  (This should be the default mode.)

Cheers,
Axel


Dave Kavanagh wrote:
> I have been having no luck getting the intelfb driver working
> with an i915 chipset. I've been searching and reading message
> boards and mail lists for days and haven't found anything.
> It seems that the driver is not setting the proper video timings.
> 
> I have tried using the vesafb driver and my hardware works fine.
> 
> If I try to use the intelfb driver my monitor either complains
> and shuts off or I get text and graphics that is horizontally
> squiggly (if that makes sense).
> 
> I tried initializing the driver in several modes with parameters
> such as:
> 
>       video=intelfb
>       video=intelfb:640x480-16@60
> 
> 
> fbset -i reports the following:
> 
> mode "1024x768-70"
>     # D: 75.002 MHz, H: 56.477 kHz, V: 70.071 Hz
>     geometry 1024 768 1024 768 32
>     timings 13333 144 24 29 3 136 6
>     accel true
>     rgba 8/16,8/8,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : Intel(R) 915G
>     Address     : 0xd0000000
>     Size        : 8253440
>     Type        : PACKED PIXELS
>     Visual      : TRUECOLOR
>     XPanStep    : 8
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 4096
>     MMIO Address: 0xcfd80000
>     MMIO Size   : 524288
>     Accelerator : Unknown (42)
> 
> 
> I am using kernel 2.6.12. Any help or ideas would be appreciated.
> 
> Thanks,
> Dave Kavanagh
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
> 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

  reply	other threads:[~2005-07-22  3:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 17:25 intelfb does not work with i915 Dave Kavanagh
2005-07-22  3:01 ` Buttchereit, Axel (XL) [this message]
2005-07-22  3:40   ` Buttchereit, Axel (XL)

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=42E06194.9030100@xlsigned.net \
    --to=xl@xlsigned.net \
    --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 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.