From: "Paolo Scaffardi" <arsenio@tin.it>
To: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: FrameBuffer support on PPC Kernels
Date: Mon, 31 Jul 2000 11:24:45 +0200 [thread overview]
Message-ID: <00c301bffad2$fbb85120$640a0a0a@server> (raw)
I'm writing a framebuffer device for my 8xx PPC platform (a loadable
module). To do this i must enable the framebuffer support on the kernel, to
resolve the calls to "register_framebuffer" of the device.
The problem is that by enabling the framebuffer support on the kernel
(without any other fb driver inside) the kernel doesn't compiles and reports
that "video_init" doesn't exists (called from main.c).
I am using MPC8xx-2.2.13 kernel. With the mvista kernel 2.2.13-7 i have the
same problem and another one when i try to enable "loadable module support".
It can be done because of "init_modules" and other functions that cannot be
referenced by "main.c". Why that? How can i enable the framebuffer support?
Please help me!
- MAY THE PINGUIN B WITH U -
Best regards,
Paolo Scaffardi
AIRVENT SAM s.p.a - RIMINI (ITALY)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-07-31 9:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='00c301bffad2$fbb85120$640a0a0a@server' \
--to=arsenio@tin.it \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).