From: "Buttchereit, Axel (XLsigned)" <XL@XLsigned.net>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
Sylvain Meyer <sylvain.meyer@worldonline.fr>
Subject: Re: Re: Added 915G to intelfb of 2.6.10-kernel-sources
Date: Fri, 28 Jan 2005 23:41:45 +0100 [thread overview]
Message-ID: <41FABFA9.7050709@XLsigned.net> (raw)
In-Reply-To: <200501290554.24649.adaplas@hotpop.com>
Antonino A. Daplas wrote:
> Can you resend the patch that touches only intelfb? Also, there are a lot
> of XLSigned with the printk's, what is that?
Yes, I will do so.
I've marked all the places where I added/changed something with a
comment that contains my domainname (for finding them easier
during editing). I'll remove this before resending.
> Because the modedb array is marked __init. You can however pass
> the vesa_modes array instead to fb_find_mode().
Ah, yes!
At the moment "intelfb" does not pass any "modedb" in its call(s) to
"fb_find_mode()" which results in using the "__init modedb" in case
of "static link" and using no modedb (actually using a not-initialized one)
at all, otherwise.
Passing "vesa_modes" would make things better when loading
"intelfb" as a module, but would change "well known behaviour",
when linked statically, though I could perfectly live with an "initfb"
that is always using "vesa_modedb".
Any suggestions?
Bumping into driver development for the first time it's quite
clear that I do not know many important things that I should know.
So please be "forgiving", if I ask stupid questions like this one:
How do I detect, if something (intelfb) is loaded as a module or
statically linked into the kernel?
>>>ByTheWay: Why isn't the framebuffer module (intelfb) automatically
>>>loaded, if
>>>"video=intelfb:..." is specified as kernel-parameter?
>
>
> If you want it loaded automatically, compile the driver statically. If you don't
> want to load a compiled-in driver, use:
>
> video=intelfb:off
This is not exactly what I was asking for. :-)
It would be nice, if the module would automatically be loaded in
"early boot stage", when specified as a kernel-parameter. But this is
not really important (for me), because using "udev" and "hotplug/coldplug"
(on gentoo) finally loads it anyway.
Thanks
--Axel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-28 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41F9BEA6.2030300@XLsigned.net>
2005-01-28 16:42 ` Added 915G to intelfb of 2.6.10-kernel-sources Sylvain Meyer
2005-01-28 21:54 ` Antonino A. Daplas
2005-01-28 22:41 ` Buttchereit, Axel (XLsigned) [this message]
2005-01-29 0:19 ` Antonino A. Daplas
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=41FABFA9.7050709@XLsigned.net \
--to=xl@xlsigned.net \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sylvain.meyer@worldonline.fr \
/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).