From: Dan Malek <dan@netx4.com>
To: Ralf HECKHAUSEN <RHeckhau@frequentis.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kernel configuration problem
Date: Thu, 09 Dec 1999 13:20:27 -0500 [thread overview]
Message-ID: <384FF2EB.DB671513@netx4.com> (raw)
In-Reply-To: s84fbf1f.064@mail.frequentis.com
Ralf HECKHAUSEN wrote:
> When I select the frame buffer option, I get an unresolved reference error (video_setup) in main.o. The only thing to get arround this is to chose the Virtual Terminal option. But then I get an unresolved reference error (request_irq) in pc_keyb.o. Im am using the kernel 2.2.5. Isn't there a way just to use the frambuffer without console and keyboard?
No....You have to include lots of this stuff, and then go into
the initialization files and make sure the initialization functions
for things like the keyboard are not called. Not very embedded
friendly and something that needs attention.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-12-09 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 13:38 kernel configuration problem Ralf HECKHAUSEN
1999-12-09 18:20 ` Dan Malek [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=384FF2EB.DB671513@netx4.com \
--to=dan@netx4.com \
--cc=RHeckhau@frequentis.com \
--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).