From: Florian Fainelli <florian.fainelli@telecomint.eu>
To: kaka <share.kt@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Error opening framebuffer device
Date: Tue, 9 Oct 2007 11:07:49 +0200 [thread overview]
Message-ID: <200710091107.49453.florian.fainelli@telecomint.eu> (raw)
In-Reply-To: <eea8a9c90710090145mb65a89dr4244050b58a0eea7@mail.gmail.com>
Hi,
On Tuesday 09 October 2007 10:45:43 kaka wrote:
> *Hi All,*
>
> *While running the cross compiled directFB example on MIPS chip,*
>
> *
> We tried to install the framebuffer driver(command given at the
> bottom) and we have already created the node fb0.*
Looking at the insmod below, I think the framebuffer did not register
correctly, so creating the device will not help if the driver is not
registered.
> # insmod brcmstfb.ko
> brcmstfb: Unknown symbol unregister_framebuffer
> brcmstfb: Unknown symbol BKNI_EnterCriticalSection_tagged
> brcmstfb: Unknown symbol printf
> brcmstfb: Unknown symbol BKNI_DestroyEventGroup
> brcmstfb: Unknown symbol BKNI_WaitForEvent_tagged
> brcmstfb: Unknown symbol BKNI_Printf
> brcmstfb: Unknown symbol __divsf3
> brcmstfb: Unknown symbol BKNI_Vprintf
> brcmstfb: Unknown symbol BKNI_Memset
> brcmstfb: Unknown symbol bnetif_dma_data
> brcmstfb: Unknown symbol bnetif_dma_delete_filter
> brcmstfb: Unknown symbol cleanup_bnetif_dma
> brcmstfb: Unknown symbol BKNI_AcquireMutex_tagged
> brcmstfb: Unknown symbol malloc
> brcmstfb: Unknown symbol BKNI_DestroyMutex
> brcmstfb: Unknown symbol framebuffer_alloc
> brcmstfb: Unknown symbol BKNI_RemoveEventGroup
> brcmstfb: Unknown symbol BKNI_Malloc_tagged
> brcmstfb: Unknown symbol BKNI_CreateEventGroup
> brcmstfb: Unknown symbol BKNI_WaitForGroup
> brcmstfb: Unknown symbol __extendsfdf2
> brcmstfb: Unknown symbol BKNI_SetEvent_tagged
> brcmstfb: Unknown symbol BKNI_Memcpy
> brcmstfb: Unknown symbol BKNI_LinuxKernel_SetIsrTasklet
> brcmstfb: Unknown symbol BKNI_Memcmp
> brcmstfb: Unknown symbol fb_find_mode
> brcmstfb: Unknown symbol fb_dealloc_cmap
> brcmstfb: Unknown symbol bnetif_dma_stop
> brcmstfb: Unknown symbol BKNI_ResetEvent_tagged
> brcmstfb: Unknown symbol BKNI_CreateMutex
> brcmstfb: Unknown symbol BKNI_CreateEvent_tagged
> brcmstfb: Unknown symbol __floatsisf
> brcmstfb: Unknown symbol brcm_dir_entry
> brcmstfb: Unknown symbol register_framebuffer
> brcmstfb: Unknown symbol BKNI_Fail
> brcmstfb: Unknown symbol fb_alloc_cmap
> brcmstfb: Unknown symbol BKNI_Snprintf
> brcmstfb: Unknown symbol BKNI_Delay_tagged
> brcmstfb: Unknown symbol BKNI_LeaveCriticalSection_tagged
> brcmstfb: Unknown symbol BKNI_Sleep_tagged
> brcmstfb: Unknown symbol bnetif_dma_add_filter
> brcmstfb: Unknown symbol BKNI_Free_tagged
> brcmstfb: Unknown symbol BKNI_DestroyEvent_tagged
> brcmstfb: Unknown symbol init_bnetif_dma
> brcmstfb: Unknown symbol framebuffer_release
> brcmstfb: Unknown symbol BKNI_AddEventGroup
> brcmstfb: Unknown symbol BKNI_ReleaseMutex_tagged
> brcmstfb: Unknown symbol __addsf3
> brcmstfb: Unknown symbol free
> insmod: cannot insert `brcmstfb.ko': Unknown symbol in module (2): No
> such file or directory
> #
Did you compile framebuffer support for your kernel ? Because if yes, most
symbols (I did not check all) used by your drivers seems to be exported with
EXPORT_SYMBOL, and not EXPORT_SYMBOL_GPL, so your driver, even with a
proprietary license should be able to access them.
I would recommend you mention your linux version, and the relevant kernel
configuration parts.
prev parent reply other threads:[~2007-10-09 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eea8a9c90710082258y5bbfc987h83f00d2b48d96fc6@mail.gmail.com>
2007-10-09 6:44 ` Fwd: Error opening framebuffer device kaka
2007-10-09 9:18 ` Geert Uytterhoeven
2007-10-09 11:00 ` Ralf Baechle
2007-10-09 8:45 ` kaka
2007-10-09 9:07 ` Florian Fainelli [this message]
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=200710091107.49453.florian.fainelli@telecomint.eu \
--to=florian.fainelli@telecomint.eu \
--cc=linux-mips@linux-mips.org \
--cc=share.kt@gmail.com \
/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