From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Giuseppe Bilotta <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modular i810fb broken, partial fix
Date: Sat, 08 Oct 2005 21:03:15 +0800 [thread overview]
Message-ID: <4347C393.5090304@gmail.com> (raw)
In-Reply-To: <1308gutgj0dx4$.1ie66adezdlua$.dlg@40tude.net>
Giuseppe Bilotta wrote:
> On Sat, 08 Oct 2005 18:39:35 +0800, Antonino A. Daplas wrote:
>
>> Bernhard Rosenkraenzer wrote:
>>> Hi,
>>> i810fb as a module is broken (checked with 2.6.13-mm3 and 2.6.14-rc2-mm1).
>>> It compiles, but the module doesn't actually load because the kernel doesn't
>>> recognize the hardware (the MODULE_DEVICE_TABLE statement is missing).
>>> The attached patch fixes this.
>>>
>>> However, the resulting module still doesn't work.
>>> It loads, and then garbles the display (black screen with a couple of yellow
>>> lines, no matter what is written into the framebuffer device).
>> Did you compile CONFIG_FRAMEBUFFER_CONSOLE statically, or did a modprobe fbcon?
>> Does i810fb work if compiled statically?
>
> Since this is *really* coming out often: is there a specific reason
> why the fb modules do not depend on fbcon?
>
Some need fbdev only, without fbcon, ie, embedded.
Tony
next prev parent reply other threads:[~2005-10-08 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 13:47 Modular i810fb broken, partial fix Bernhard Rosenkraenzer
2005-10-08 10:39 ` Antonino A. Daplas
2005-10-08 11:02 ` Bernhard Rosenkraenzer
2005-10-08 11:31 ` Giuseppe Bilotta
2005-10-08 13:03 ` Antonino A. Daplas [this message]
2005-10-08 14:51 ` Giuseppe Bilotta
2005-10-08 21:22 ` Antonino A. Daplas
2005-10-08 11:56 ` Manuel Lauss
2005-10-08 13:03 ` Antonino A. Daplas
2005-10-08 15:30 ` Manuel Lauss
2005-10-09 16:48 ` Bernhard Rosenkraenzer
2005-10-09 17:13 ` Manuel Lauss
2005-10-09 17:21 ` Manuel Lauss
2005-10-10 8:06 ` 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=4347C393.5090304@gmail.com \
--to=adaplas@gmail.com \
--cc=bilotta78@hotpop.com \
--cc=linux-kernel@vger.kernel.org \
/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