public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Wyatt <josh.wyatt@hcssystems.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "'Kernel-Mailingliste'" <linux-kernel@vger.kernel.org>
Subject: Re: Softdog support on non-x86
Date: Tue, 15 Jan 2002 09:19:34 -0500	[thread overview]
Message-ID: <3C443A76.BDCB4454@hcssystems.com> (raw)
In-Reply-To: <E16K6eS-0002HR-00@the-village.bc.nu> <3C3DA9DC.D00C3C72@hcssystems.com> <20020111103423.A30436@flint.arm.linux.org.uk>

Russell King wrote:
> 
> On Thu, Jan 10, 2002 at 09:49:00AM -0500, Josh Wyatt wrote:
> > I'd like to use the software watchdog timer, softdog.c, on the Sparc
> > architecture, using kernel 2.2.17.  I used this to build the module:
> > cd /usr/src/linux-2.2.17/drivers/char
> > gcc -c -DMODVERSIONS -D__KERNEL__ -DMODULE -Wall -Wstrict-prototypes
> > softdog.c
> 
> Why are you building it manually?  It'd be better to turn it on
> using the configuration tools, and build it in the normal way?

Please CC: me as I am not on the list.

I built the module manually precisely because I did not want to rebuild
the entire kernel and module set just to get this one module.

Perhaps I do not understand the correct approach to building individual
modules, on an existing tree.

What's the documented, correct approach to only building a single
module, starting with menuconfig, such that it will happily fit in with
the currently running kernel and modules?  I notice that many
drivers/modules happily include the correct gcc incantation (in comment)
for doing exactly this, and many do not.

And finally, back to my original question, is it a mute point?  Is the
softdog an Intel-only thing?

Thanks,
josh


> 
> --
> Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
>              http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2002-01-15 14:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 19:44 Linux 2.4.18-pre1 Andreas Hartmann
2001-12-28 21:10 ` Troels Walsted Hansen
2001-12-28 21:41   ` Andreas Hartmann
2001-12-28 23:43   ` Alan Cox
2002-01-10 14:49     ` Softdog support on non-x86 Josh Wyatt
2002-01-11 10:34       ` Russell King
2002-01-15 14:19         ` Josh Wyatt [this message]
2001-12-28 23:26 ` Linux 2.4.18-pre1 Alan Cox
2002-01-03 11:51 ` Tim Waugh

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=3C443A76.BDCB4454@hcssystems.com \
    --to=josh.wyatt@hcssystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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