linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: asm/*.h files missing for ppc arch.
Date: Sat, 9 Sep 2006 22:17:04 +0200	[thread overview]
Message-ID: <200609092217.04623.arnd@arndb.de> (raw)
In-Reply-To: <BAY110-F38603E88776B0F5A2D966FB2340@phx.gbl>

Am Saturday 09 September 2006 21:28 schrieb Ming Liu:
> Dear Arnd,
>
> >It's usually easier if you add your module to your copy of the kernel
> >sources and build it along with all the other modules.
>
> How can I do that? I don't know how can I configure my driver and compile
> it as a module. Which option shall I choose to configure my driver as a
> module in menuconfig? Sorry that I am new to linux and I am anxious for
> your helpful telling...

You need to at least the following steps:

1. Add your module to an appropriate location in the source tree, e.g.
drivers/net/ or drivers/char/, or whereever it fits best depending on
what it does.

2. Edit the Makefile in that directory so your driver gets built, e.g.
by adding a line 'obj-m += your-driver.o'.

The optional but recommended steps are:

3. Add the driver to an appropriate Kconfig file, typically in the same
directory as your driver, and change your Makefile to 
use 'obj-$(CONFIG_YOUR_DRIVER) += your-driver.o'.

4. Learn to use 'quilt', or a similar tool, to manage your patch against
the kernel.

5. If you ask questions on the mailing list, make sure everyone has access
to your patch, e.g. by uploading it to a web site.

	Arnd <><

  reply	other threads:[~2006-09-09 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 15:05 asm/*.h files missing for ppc arch Ming Liu
2006-09-09 15:14 ` Ming Liu
2006-09-09 17:42   ` Josh Boyer
2006-09-09 18:34     ` Ming Liu
2006-09-09 19:21       ` Arnd Bergmann
2006-09-09 19:28         ` Ming Liu
2006-09-09 20:17           ` Arnd Bergmann [this message]
2006-09-09 20:37             ` Ming Liu

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=200609092217.04623.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-embedded@ozlabs.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).