From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Antonino Daplas <adaplas@pol.net>
Cc: Sven Luther <luther@dpt-info.u-strasbg.fr>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: request_mem_region problem ...
Date: Thu, 31 Oct 2002 12:31:22 +0100 [thread overview]
Message-ID: <20021031113122.GA2692@iliana> (raw)
In-Reply-To: <1036062270.638.25.camel@daplas>
On Thu, Oct 31, 2002 at 07:05:13PM +0800, Antonino Daplas wrote:
> On Thu, 2002-10-31 at 16:10, Sven Luther wrote:
> > On Thu, Oct 31, 2002 at 08:34:05AM +0800, Antonino Daplas wrote:
> [...]
> >
> > I already solutioned this problem.
> >
> > BTW, i don't understand how the tdfxfb does not have this problem, as it
> > is from there that i tried to sole this.
> >
> > The problem was that i did :
> >
> > /* Find the mmio register area */
> > pm3_fix.mmio_start = pci_resource_start(pdev, 0);
> > pm3_fix.mmio_len = pci_resource_len(pdev, 0);
> >
> > And later :
> >
> > if (!request_mem_region(pci_resource_start(pdev, 0), pci_resource_len(pdev, 0), ...
> >
> > Changing this to :
> >
> > if (!request_mem_region(pm3_fix.mmio_start, pm3_fix.mmio_len, ...
> >
> > Solved the problem, so it seems that the pci_resource_ functions can be
> > called only one time. Is this true ?
> >
> Strange. pci_resource_* are just macros, so they should be usable as
> long as the pci_dev pointer is valid.
Yes, thought so also, but then i may have been another problem, will
look into this more tomorrow.
> > Now, i seem to have everything fine, but it still hangs in
> > register_framebuffer, a bit of searching has it that it is when
> > register_framebuffer calls take_over_console. I didn't have time for
> > looking into it more yesterday.
> >
> > Still the screen is black, and i see a small (underscore) blinking
> > cursor at the bottom left of the screen. The machine was dead though :
> >
> > Oct 30 23:15:53 iliana kernel: printing eip:
> > Oct 30 23:15:53 iliana kernel: c023affc
> > Oct 30 23:15:53 iliana kernel: Oops: 0000
> > Oct 30 23:15:53 iliana kernel: pm3fb nls_iso8859-15 nls_cp437 sym53c8xx
> > Oct 30 23:15:53 iliana kernel: CPU: 0
> > Oct 30 23:15:53 iliana kernel: EIP: 0060:[fbcon_cursor+108/480] Not tainted
> > Oct 30 23:15:53 iliana kernel: EFLAGS: 00010246
> > Oct 30 23:15:53 iliana kernel: eax: 00000000 ebx: 00000000 ecx: 00000000 edx: c1143240
> > Oct 30 23:15:53 iliana kernel: esi: c042d280 edi: 00000002 ebp: 00000018 esp: c4dcbc10
> > Oct 30 23:15:53 iliana kernel: ds: 0068 es: 0068 ss: 0068
> > Oct 30 23:15:53 iliana kernel: Process modprobe (pid: 495, threadinfo=c4dca000 task=c6bec040)
> > Oct 30 23:15:53 iliana kernel: Stack: 00000000 c04156c0 00000000 00000000 c01f21f8 c1143240 00000002 00000000
> > Oct 30 23:15:53 iliana kernel: c04156c0 c01f5435 00000000 c039ef20 c03dfe9f 0000339f 000033cf c0414a30
> > Oct 30 23:15:53 iliana kernel: 00002adf c01275e1 00000000 c0119439 c039ef20 c03dfe9f 00000030 000033cf
> >
> Running ksymoops on that might help. The source can be found at
> ftp.kernel.org.
Yes, ... (altoug i do old style debuging (with printk) takes more time,
but work also.
> If you define FBCON_HAS_ACCEL, then fb_imageblit, fb_copyarea and
> fb_fillrect in info->fbops must not be null. Otherwise, you'll always
> get an oops. If you don't define FBCON_HAS_ACCEL, you'll end up with
> fbcon_dummy, which is totally safe but will not show anything at all.
Mmm, ok,
> This is all assuming you use gen_set_var.
Yes, i use this one.
> 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)
>
> Your oops tracing points to fbcon_cursor as the culprit. If
> dispsw->cursor is NULL, then you must have a valid dispsw->revc.
Ok, but will look more at it, tomorrow.
> > How, well, maybe i should wait for the new patches from James to be
> > accepted into the linus tree.
> >
> > Notice, maybe this is due to me not having defined yet any of the
> > check_var, set_par, blank, ... functions, but my idea, for the howto
> > afterward, was to write first the most minimal working fbdev.
> >
> > BTW, should i work on james BK tree directly ? Is there an howto on how
> > to do that ? Or could it be possible to get a patch against 2.5.44 ?
> >
> Try Documentation/BK-usage. You will need a very fat pipe, then for a
> start,
>
> bk clone bk://fbdev.bkbits.net/fbdev-2.5
Ok, ...
i have ADSL 512K, i suppose it will have to be enough, anyway, the other
solution would be to just be patient, isn't it ?
> > when i try to use the cfb_xxx functions, it does not work. i copied the
> > neofb line in the Makefile so that pm3fb should have added the 3 cfbxxx
> > objects, but it does not work. When loading the cfbxxx.o object files as
> > modules, insmod complains about lack of version in them, so i guess they
> > are not modules. Still, they don't get linked with the pm3fb.o (and
> > neither with the neofb.o when i tried it), and when loading pm3fb.o, i
> > get a message about missing symbols cfb_xxx.
> >
> > So, does the cfb_xxx generic accel stuff get linked correctly when
> > building as modules or am i missing something ?
> >
> You're correct, the neofb line in the Makefile is for static building
> only. The cfb_xxx will not compile as modules, yet. If your driver has
> its own Makefile, just add cfb_xxx.o objects to directly link to them.
It is just one file, i think i will just copy the cfb_xxx functions into
my file for now, it should work as well, anyway, i plan to add my own
accel functions later on.
Friendly,
Sven Luther
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
next prev parent reply other threads:[~2002-10-31 11:31 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 [this message]
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
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=20021031113122.GA2692@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=adaplas@pol.net \
--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).