linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: request_mem_region problem ...
Date: 02 Nov 2002 04:06:59 +0800	[thread overview]
Message-ID: <1036181217.572.5.camel@daplas> (raw)
In-Reply-To: <20021101195207.GA931@iliana>

On Sat, 2002-11-02 at 03:52, Sven Luther wrote:

[...]
> > > Ok, i did copy the cfb_ functions to the driver, it works better (the
> > > box does not hang anymore), the console apprently works (the cursor
> > > blinks in the right place, and it could type stuff, switch VT and
> > > shutdown the box) but there is nothing else written.
> > > 
> > > BTW, what is the difference between the full cursor and the underline
> > > one ?
> > The block cursor most probably comes from fbcon's software cursor, the
> > underline is probably your hardware's?
> 
> Mmm, maybe the other way around ? i get block cursor with the old
> accelerated pm3fb, and since i did enter no acceleration whatsoever yet
> in the new driver, i don't believe it can be using the hardware cursor.
> 
The fbcon software cursor is always a block cursor, well at least before
the latest patch James posted.  The newest patch should give you an
underline cursor by default.

> > > Anyway, here are the two Oops :
> > > 
> > > 
> > [...]
> > > I don't believe the result of running ksymoops on these are valid, i
> > > will have to reboot in the 2.5.44 kernel for it.
> > > 
> > > > If you did not define fb_set_var at all, then info->disp.dispsw must
> > > > point to valid console drawing hooks before you register the
> > > > framebuffer.  (Actually, all fields in struct display must be valid
> > > > before you register the framebuffer)
> > > 
> > > Mmm, still need to check those.
> > > 
> > > > Your oops tracing points to fbcon_cursor as the culprit.  If
> > > > dispsw->cursor is NULL, then you must have a valid dispsw->revc.
> > > 
> > > There where two oops, the first in fbcon_setup, and the second in
> > > fbcon_cursor, i think i will be looking in the first oops first.
> > > 
> > Might as well try to port your driver using the latest fbdev patch
> > posted by James, hopefully, this is the last major change.  This should
> > give you less things to worry about.
> 
> Well, yes, i was going to donwload the BK tree, but james was speaking
> about a 2.5.45 diff, which was finally not the right one.
> 
I downloaded the patch 12 hours ago and actually ported a driver to
that.  So unless James changed it again, it should be the right one.

Tony



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en

  reply	other threads:[~2002-11-01 20:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 13:00 request_mem_region problem Sven Luther
2002-10-31  0:34 ` Antonino Daplas
2002-10-31  8:10   ` Sven Luther
2002-10-31 11:05     ` Antonino Daplas
2002-10-31 11:31       ` Sven Luther
2002-11-01 10:52       ` Sven Luther
2002-11-01 19:42         ` Antonino Daplas
2002-11-01 19:52           ` Sven Luther
2002-11-01 20:06             ` Antonino Daplas [this message]
     [not found]               ` <20021101202246.GA2026@iliana>
2002-11-01 20:40                 ` Antonino Daplas
     [not found]                 ` <1036182603.622.8.camel@daplas>
     [not found]                   ` <20021101212353.GA2163@iliana>
2002-11-01 22:22                     ` Antonino Daplas
2002-11-08  0:04                       ` James Simmons
2002-11-01 17:35       ` James Simmons
2002-11-01 18:43         ` Sven Luther
2002-11-01 23:23           ` James Simmons
2002-11-09  7:52       ` 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=1036181217.572.5.camel@daplas \
    --to=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=luther@dpt-info.u-strasbg.fr \
    /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).