public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias Rittweiler <inkognito.anonym@uni.de>
To: Antonino Daplas <adaplas@pol.net>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re[2]: [STATUS] fbdev api.
Date: Fri, 6 Dec 2002 23:59:40 +0100	[thread overview]
Message-ID: <15835232027.20021206235940@uni.de> (raw)
In-Reply-To: <1039218931.989.24.camel@localhost.localdomain>

Hello Antonino,

Saturday, December 7, 2002, 12:55:34 AM, you wrote:

>> a) Although your patch fixes the FB oddness for me, it makes booting
>>    without using framebuffer fail, IOW the kernel hangs:
>> 
>>    Video mode to be used for restore is f00
>>    BIOS-provided physical RAM map:
>>     BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
>> 
AD> Do you have framebuffer console enabled but with no framebuffer device
AD> enabled at boot time?  This will always fail with James' current patch.

AD> The diff I submitted in one of my replies in this thread (fbcon.diff)
AD> might fix that (not sure).

Thanks, that patches fixes it.


>> b) After returning from blanking mode (via APM) to normal mode, no
>>    character is drawn. Let's assume I'm using VIM when that happens:
>>    After putting any character to return from blank mode, the screen stays
>>    blanked apart from the cursor that _is_ shown. Now I'm able to move
>>    the cursor, and when the cursor encounters a character, this char
>>    is drawn (and keeps drawn). Though when I press Ctrl-L or when I go one line
>>    above to the current top-line (i.e. by forcing a redrawn), the
>>    whole screen is drawn properly.
>> 
AD> Can you try this?
AD> [..diff..]

Yes, it fixes the problem, thanks.


>> c) instruction:          | produces:
>>    ======================|==================
>>    1. typing abc def     | $ abc def
>>                          |          ^ (<- cursor)
>>    2. going three chars  | $ abc def
>>       ro the left        |       ^
>>    3. pressing backspace | $ abcddef
>>                          |      ^
>>    4. pressing enter     | -bash: abcdef: command not found
>>                          |

AD> I get this also. Seems to occur only with colored terms.  When I do 

AD> set TERM=vt100

AD> the problem disappears, so I thought this was an isolated case with my
AD> setup :-). Similar glitches happen also in emacs with syntax
AD> highlighting turned on.

Still there.


AD> Tony
-- 
cheers,
 Tobias


  reply	other threads:[~2002-12-06 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 19:42 [STATUS] fbdev api Tobias Rittweiler
2002-12-06 23:55 ` Antonino Daplas
2002-12-06 22:59   ` Tobias Rittweiler [this message]
2002-12-06 23:51     ` Re[2]: " James Simmons
2002-12-07 10:22     ` Antonino Daplas
2002-12-07 10:15       ` Re[4]: " Tobias Rittweiler
2002-12-07 19:05       ` Re[2]: " James Simmons
2002-12-07 21:43         ` Antonino Daplas
2002-12-07  0:49   ` James Simmons

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=15835232027.20021206235940@uni.de \
    --to=inkognito.anonym@uni.de \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@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