public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Wyatt <josh.wyatt@hcssystems.com>
To: "'Kernel-Mailingliste'" <linux-kernel@vger.kernel.org>
Cc: josh.wyatt@hcssystems.com
Subject: Softdog support on non-x86
Date: Thu, 10 Jan 2002 09:49:00 -0500	[thread overview]
Message-ID: <3C3DA9DC.D00C3C72@hcssystems.com> (raw)
In-Reply-To: <E16K6eS-0002HR-00@the-village.bc.nu>

Hi All,

I've researched this question and haven't been able to find a suitable
answer.  The answer may be "it's painless as-is, just go for it".  It
might also be "give up now while you still have your pants".

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

The module builds fine with some warnings.  After copying it over to
/lib/modules/2.2.17/misc/softdog.o and running depmod -a, I get
modprobe: ELF file not for this architecture

I haven't tried modprobe'ing the module yet, the above message frightens
me.

Is this driver safe for the sparc architecture?  If not, what would it
take?  Or did I screw up somwehere along the way?

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

Thanks in advance,
Josh Wyatt

  reply	other threads:[~2002-01-10 14:43 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     ` Josh Wyatt [this message]
2002-01-11 10:34       ` Softdog support on non-x86 Russell King
2002-01-15 14:19         ` Josh Wyatt
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=3C3DA9DC.D00C3C72@hcssystems.com \
    --to=josh.wyatt@hcssystems.com \
    --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