From: James Simmons <jsimmons@transvirtual.com>
To: Modular Forms Boy <eger@cc.gatech.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
FrameBuffer List <linux-fbdev@vuser.vu.union.edu>
Subject: Re: New Linux Drivers - Configure question
Date: Mon, 18 Jun 2001 14:56:47 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10106181451060.3113-100000@transvirtual.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0106180852480.16027-100000@oscar.cc.gatech.edu>
> I am working on a new framebuffer driver for an LCD controller that's
> custom to the PowerPC embedded world. As such, it's architecture
> dependent. Where should I place the driver in the tree, and how should I
> set up the proper Configure options? Where do I put checks for #ifdef
> CONFIGURE_blah_blah_blah?
Hi!
You would place it in drivers/video. If you look at the Config.in
file in the linux/drivers/video directory you will see
if [ "$CONFIG_PPC" = "y" ]; then
bool ' Open Firmware frame buffer device support' CONFIG_FB_OF
...
fi
Just add you driver in that section. Also you have to alter fbmem.c. You
need to add something like
extern int xxxmydriverfb_init(void);
extern int xxxmydriverfb_setup(char*);
and further down in the file.
#ifdef CONFIG_FB_MYDRIVER
{ "myfbdriver", xxxmydriverfb_init, xxxmydriverfb_setup },
#endif
When you look at this file you will see what I mean. If you have any
further questions just go to http://www.linux-fbdev.org. In this email you
will see the address for our mailing list. On our web site it gives you
info about joining the mailing list.
next prev parent reply other threads:[~2001-06-18 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 13:00 Modular Forms Boy
2001-06-18 13:20 ` Chakir Ettayebi
2001-06-18 21:56 ` James Simmons [this message]
2001-07-03 0:22 ` readl() / writel() on PowerPC David T Eger
2001-07-03 0:54 ` David Schleef
2001-07-03 2:39 ` James Simmons
2001-07-04 7:50 ` Paul Mackerras
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=Pine.LNX.4.10.10106181451060.3113-100000@transvirtual.com \
--to=jsimmons@transvirtual.com \
--cc=eger@cc.gatech.edu \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®