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 06:22:49 +0800	[thread overview]
Message-ID: <1036189404.621.7.camel@daplas> (raw)
In-Reply-To: <20021101212353.GA2163@iliana>

On Sat, 2002-11-02 at 05:23, Sven Luther wrote:
> On Sat, Nov 02, 2002 at 04:29:32AM +0800, Antonino Daplas wrote:
> > It's an irritating bug in the new kernel configurator.  Try make -k if
> > it complains about the QT libs.
> 
> Ok, it worked some, but debian's kernel-package command did not like it,
> o well, i will have to build it by hand until it is fixed.
> 
> BTW, in the old pm3fb driver (which i did not write) a pm3fb_info
> structure contained the driver local stuff. I suppose, from reading
> skeletonfb.c, that it is now in the xxx_par (that is pm3fb_par) that
> private driver info will be found ?
> 
Yes, you can stuff all your driver private data in info->par. (fb_info
can be stuffed in pci_device during pci_probe, I think).
  
> Also, since pm3fb_par is placed in include/video/pm3.h, this data will
> be shared with other entities, like the drm module for example.
> 
Yes, but it's optional.

> ...
> 
> Mmm, it does not compile :((((
> 
> drivers/video/console/vgacon.c: In function `vgacon_adjust_height':
> drivers/video/console/vgacon.c:890: `i' undeclared (first use in this function)
> drivers/video/console/vgacon.c:890: (Each undeclared identifier is reported only once
> drivers/video/console/vgacon.c:890: for each function it appears in.)
> make[3]: *** [drivers/video/console/vgacon.o] Erreur 1
> 
> O, well, i think i will wait another week or so that the new stuff has
> stabilized a bit more before continuing working on this.
> 
Just declare 'int i' and it should work.

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

  parent reply	other threads:[~2002-11-01 22:24 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
     [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 [this message]
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=1036189404.621.7.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).