All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christer Weinigel <christer@weinigel.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: NatSemi SCx200 patches for Linux-2.5
Date: 30 Sep 2002 14:39:33 +0200	[thread overview]
Message-ID: <87u1k7wt16.fsf@zoo.weinigel.se> (raw)
In-Reply-To: <1033388216.16266.1.camel@irongate.swansea.linux.org.uk>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> On Mon, 2002-09-30 at 12:23, Christer Weinigel wrote:
> > How can I guarantee that the driver scx200.c is initialized before any
> > other drivers that use the scx200_gpio functions (e.g. scx200_i2c.c)?
> > I have put scx200.c in in arch/i386/kernel in the hope that this
> > directory will always be initialized before anything else, but is this
> > really true?
> 
> There are two ways. For built in code you can use the link order to
> force ordering. In 2.4 thats your only real choice. For modules you need
> to ensure there is a dependancy so modprobe loads the supporting module
> first

I'll just assume that it works then.  With the current link order in
2.5 it works when compiled into the kernel and for the module case
there is an explicit dependency.

Now I just have to merge back a few things to the 2.4 code; I found a
few uglies and want to see if the link order trick works with 2.4.

  /Christer

-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer@weinigel.se>  http://www.weinigel.se

  reply	other threads:[~2002-09-30 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 11:23 NatSemi SCx200 patches for Linux-2.5 Christer Weinigel
2002-09-30 12:16 ` Alan Cox
2002-09-30 12:39   ` Christer Weinigel [this message]
2002-09-30 13:16     ` Alan Cox

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=87u1k7wt16.fsf@zoo.weinigel.se \
    --to=christer@weinigel.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.