From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: (no subject)
Date: Sat, 15 Apr 2006 07:47:24 +0200 [thread overview]
Message-ID: <444088EC.9020808@t-online.de> (raw)
In-Reply-To: <200604141502.k3EF2u4C031951@falbala.ti.uam.es>
>intelfb: Framebuffer driver for Intel(R)
>830M/845G/852GM/855GM/865G/915G/915GM chipsets
>intelfb: Version 0.9.2
>intelfb: 00:02.0: Intel(R) 855GME, aperture size 128MB, stolen memory 892kB
>intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching.
>intelfb: Video mode must be programmed at boot time.
>
>
>the driver (*) is inside kernel.
>
>
Yes - of course, why not? It should be possible to compile a framebuffer
driver into the kernel without problems, and it should be possible to
load it as a module ... even from within xterm ;-)
Why do you believe that this is related to any of the problems?
cu,
knut
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-15 5:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 15:02 (no subject) Javier Ruano
2006-04-14 15:28 ` Jan-Benedict Glaw
2006-04-15 5:47 ` Knut Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 9:31
2007-08-17 16:47 Krzysztof Helt
2004-05-26 9:00 xuhaoz
2004-05-28 7:42 ` Antonino A. Daplas
2004-05-22 1:48 xuhaoz
2003-07-17 12:25 Nitin Mahajan
2003-07-07 23:37 Lia Maggioni
2003-02-06 15:27 p.gilardetti
2003-02-06 21:55 ` Antonino Daplas
2002-12-10 10:59 Vincent Ivens
2002-12-10 18:31 ` James Simmons
2002-12-10 21:05 ` vivens
2002-12-13 6:33 ` Antonino Daplas
2002-08-19 9:02 Geert Uytterhoeven
2002-08-22 18:48 ` James Simmons
2002-08-06 17:37 Adam K Kirchhoff
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=444088EC.9020808@t-online.de \
--to=knut_petersen@t-online.de \
--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).