From: Sven Luther <luther@lambda.u-strasbg.fr>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: board with broken vga ...
Date: Thu, 18 Jul 2002 09:51:46 +0200 [thread overview]
Message-ID: <20020718075146.GA6020@lambda.u-strasbg.fr> (raw)
Hello, ...
i am looking again at pm3fb (still old style one though).
Permedia3 (and probably permedia2 also) has a problem with accessing vga
stuff in mmio mode, which makes it not work correctly when the text from
the vga console mode is copied over to the fbcon at the switch.
I have the understanding that you moved this stuff over to some other
place and not the pm3fb driver itself (but where ?)
I now know how to get this data by looking at the framebuffer directly
(it is found starting at framebuffer addr + 0 in 8 byte steps.), but
need to know how i can hook it in, to write it back.
Also, the size of this text is somewhat of a mistery for me still.
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 ?
Friendly,
Sven Luther
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-07-18 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 7:51 Sven Luther [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 9:42 board with broken vga Petr Vandrovec
2002-07-18 11:36 ` Sven Luther
2002-07-18 16:16 ` Sven Luther
2002-07-22 17:23 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=20020718075146.GA6020@lambda.u-strasbg.fr \
--to=luther@lambda.u-strasbg.fr \
--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).