From: Sven Luther <luther@lambda.u-strasbg.fr>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: board with broken vga ...
Date: Thu, 18 Jul 2002 13:36:42 +0200 [thread overview]
Message-ID: <20020718113642.GA6719@lambda.u-strasbg.fr> (raw)
In-Reply-To: <B3CC4836A3C@vcnet.vc.cvut.cz>
On Thu, Jul 18, 2002 at 11:42:57AM +0200, Petr Vandrovec wrote:
> On 18 Jul 02 at 9:51, Sven Luther wrote:
> >
> > Ok, that said, i suppose ours are the only boards with such problems,
> > but since there is so much taken out of the drivers in your new setup
> > and put in a common place, would it not solve this problem if there were
> > an additional function which driver could provide (or fill in NULL if
> > there was no proble), for retrieving this data, which fbcon can write
> > back later on ?
>
> Unfortunately there is no such hook. Fortunately call sequence is:
Yes, i know, but would such a hook be a good addition for the new API or
something ?
Altough, it is true that maybe only pm2fb and pm3fb will make use of it,
it would be cleaner than patching vgacon code for it.
> your drivers's init
> --> look and init devices
> --> call register_framebuffer
> --> VGACON reads contents of VGA buffer
So vgacon is responsible for (wrongly) reading the text data from the
board.
> --> call to fbdev setvar
> --> upper layer restores screen
> ...
> With matroxfb I moved all initialization which changes framebuffer layout
> to the setvar call, and so VGACON finds hardware in VGA, and not MMIO,
> state.
Mmm, that may be an idea, provided the normal VGA stuff is not broken.
> You can look at drivers/char/console.c: take_over_console calls
> save_screen, which in turn calls con_save_screen method of vgacon.
> So you can try directly overwritting vgacon's savescreen procedure
>
> extern struct consw vga_con;
> vga_con.con_save_screen = myOwnSaveScreen;
>
> if you find that your fbdev is primary VGA device. Of course it is
> not tested, and I cannot recommend doing that...
Ok, i will look at it, thanks.
Friendly,
Sven Luther
> Petr
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-18 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 9:42 board with broken vga Petr Vandrovec
2002-07-18 11:36 ` Sven Luther [this message]
2002-07-18 16:16 ` Sven Luther
-- strict thread matches above, loose matches on Subject: below --
2002-07-22 17:23 Sven LUTHER
2002-07-18 7:51 Sven Luther
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=20020718113642.GA6719@lambda.u-strasbg.fr \
--to=luther@lambda.u-strasbg.fr \
--cc=VANDROVE@vc.cvut.cz \
--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.