From: "Pattrick Hüper" <pattyh@gmx.net>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] notify fbcon if framebuffer registered
Date: Tue, 02 Mar 2004 21:42:58 +0100 [thread overview]
Message-ID: <4044F1D2.3050609@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0403021720240.18264-100000@phoenix.infradead.org>
Hi,
thanks for your reply!
>Is your driver built as a module? That is the only way that could happen
>that I know of. The new behavior is that the fbdev device doesn't not
>automatically take over the console. You use the app con2fb to do that.
>The reason was so developers could debug there drivers easily. Alot of
>times there is a bug in the xxfb_init code and you end up with a blank
>display. Very hard to work with. Also some fbdev drivers can work with
>vgacon. So you could run a fbdev app on vgacon!!! In this case you don't
>want the fbdev device changing the hardware.
> Actually you don't really need fbcon for embedded devices except for
>debugging output. If your device is embedded and without fbcon you can
>call fb_set_var before you register the device.
>
>
>
The driver is not compiled as a module, but still fb_console_init runs
before mq11xxfb_init, originally i just called fb_console_init from
within my probe function which worked but was a very ugly way to go, so
i came up with the framebuffer_register notification, and since i saw
that you added event_notifications in kernel 2.6.3, i adapted my
notification and thought i could send you the patch.
It works perfectly for me, sicne my main problem is, that i dont have a
serial cable and can only login to my device thru infrared serial port
which only starts when linuxrc of initrd is running, thus i needed a way
to see kernel messages and the fb seemed an easy way to do that. Thats
what i needed the patch for, and it works perfectly for me, i dont need
to call any applications, just as soon as my (statically compiled) fb is
registered, the fbcon comes up and shows me the boot messages.
I agree that it is only needed for debugging output, thats all i
currently need it for.
>>This patch could come in handy for hotplug events :-) We would also need a
>>unregister event. The only thing is you have to do some filtering here.
>>Say you have a multi-head system. If question you have is do you want to
>>register this device to the fbcon system. The second question is to which
>>VCs do you map this device. In fbcon you have a map for that. I have to
>>think about how to do that. Your patch is a great start. I just need to
>>go over the different possible cases we can have.
>>
>>
>>
I'm very glad if you can use the patch, actually i am not very deep into
the internals of the fbcon, i just saw, that by calling
take_over_console, i can reach my goal, i did not think about any
complications or problems, since i dont know enough about the fbcon.
Regards, Patty
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
prev parent reply other threads:[~2004-03-02 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 11:38 [PATCH] notify fbcon if framebuffer registered Pattrick Hueper
2004-03-02 17:41 ` James Simmons
2004-03-02 20:42 ` Pattrick Hüper [this message]
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=4044F1D2.3050609@gmx.net \
--to=pattyh@gmx.net \
--cc=jsimmons@infradead.org \
--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.