mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Trying to convert old modules to newer kernels
Date: Sat, 29 Dec 2007 09:19:11 -0500	[thread overview]
Message-ID: <1198937951.9453.22.camel@perihelion> (raw)
In-Reply-To: <20071220162700.GF2308@csclub.uwaterloo.ca>


On Thu, 2007-12-20 at 11:27 -0500, Lennart Sorensen wrote:
> On Thu, Dec 20, 2007 at 11:13:19AM -0500, linux-os (Dick Johnson) wrote:
> > It never gets to the printk(). You were right about the
> > compilation. Somebody changed the kernel to compile with
> > parameter passing in REGISTERS! This means that EVERYTHING
> > needs to be compiled the same way, 'C' calling conventions
> > were not good enough!
> > 
> > FYI, it has been previously shown that passing parameters
> > in registers on register-starved ix86 machines is always
> > a loss, because the registers need to be freed up, either
> > by saving them on the stack or as dummy memory variables.
> > 
> > Now, they've done it to the entire kernel!
> 
> It's a config option.  I think redhat was the first to actually start
> using it on their distributions.  Many distributions don't use it.
> Debian does not use it on their kernels.

And anyway, what's wrong with having the kernel build scripts build the
module for you? ;-)

Jon.



  parent reply	other threads:[~2007-12-29 14:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 20:10 linux-os (Dick Johnson)
2007-12-19 20:23 ` Lennart Sorensen
2007-12-19 20:56   ` linux-os (Dick Johnson)
2007-12-20 15:02     ` Lennart Sorensen
2007-12-20 16:13       ` linux-os (Dick Johnson)
2007-12-20 16:27         ` Lennart Sorensen
2007-12-20 21:23           ` linux-os (Dick Johnson)
2007-12-20 21:40             ` Roland Dreier
2007-12-20 22:56               ` linux-os (Dick Johnson)
2007-12-21 14:39                 ` Lennart Sorensen
2007-12-21 16:37                   ` linux-os (Dick Johnson)
2007-12-29 14:19           ` Jon Masters [this message]
2007-12-20 18:28         ` Sam Ravnborg
2007-12-20 21:27           ` linux-os (Dick Johnson)
2007-12-20 22:05             ` Sam Ravnborg
2007-12-20 23:05               ` linux-os (Dick Johnson)
2007-12-20 23:53                 ` J.A. Magallón
2007-12-21 12:08                   ` James Courtier-Dutton
2007-12-21 12:43                     ` Jan Engelhardt
2007-12-27  0:17                     ` Bill Davidsen
2007-12-21 14:43             ` Lennart Sorensen
2007-12-21 16:39               ` linux-os (Dick Johnson)
2007-12-27  0:19               ` Bill Davidsen
2007-12-19 20:47 ` Jan Engelhardt
2007-12-19 21:10   ` linux-os (Dick Johnson)
2007-12-19 21:16     ` Jan Engelhardt
2007-12-19 20:52 ` Sam Ravnborg
     [not found] <9CdyE-1A6-7@gated-at.bofh.it>
     [not found] ` <9CdIw-1Op-29@gated-at.bofh.it>
     [not found]   ` <9Cebz-2sz-29@gated-at.bofh.it>
     [not found]     ` <9Cvcw-5mu-15@gated-at.bofh.it>
     [not found]       ` <9CwhY-76J-11@gated-at.bofh.it>
     [not found]         ` <9Cyk3-1Zc-29@gated-at.bofh.it>
     [not found]           ` <9CB8a-6zV-13@gated-at.bofh.it>
2007-12-21  0:16             ` Bodo Eggert
2007-12-21 13:11               ` linux-os (Dick Johnson)

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=1198937951.9453.22.camel@perihelion \
    --to=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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®