public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>
Subject: Re: Backport of a 2.6.x USB driver to 2.4.32 - help needed
Date: Tue, 06 Jun 2006 18:16:46 -0600	[thread overview]
Message-ID: <44861AEE.3020109@shaw.ca> (raw)
In-Reply-To: <6kHVe-3Hs-45@gated-at.bofh.it>

Jesper Juhl wrote:
> On 06/06/06, Heiko Gerstung <heiko.gerstung@meinberg.de> wrote:
>> Hi!
>>
>> Short Version (tm): I try to backport a USB driver (rtl8150.c) from
>> 2.6.15.x to 2.4.32 and have no idea how to substitue two functions:
>> in_atomic() and schedule_timeout_uninterruptible() ... I really would
>> appreciate any help, because I am no kernel hacker at all ...
>>
> in_atomic() is used to test if the kernel is in a state where sleeping
> is allowed or not. The 2.4.x kernel is not preemptive and has quite
> coarse grained SMP support (the BKL "Big Kernel Lock"), it didin't
> need in_atomic() in the same way as 2.6.x does.

There's little difference in the need for it, 2.4 just doesn't have it. 
I don't see a call to that function in that driver's code though?

> 
> schedule_timeout_uninterruptible() is used to sleep on a wait-queue,
> which 2.4.x does not have.

Huh? 2.4 did have wait queues, but that call has nothing to do with 
them. You should be able to replace it with:

set_current_state( TASK_UNINTERRUPTIBLE );
schedule_timeout( timeout );

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-06-07  0:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6kGwd-1tt-23@gated-at.bofh.it>
     [not found] ` <6kHVe-3Hs-45@gated-at.bofh.it>
2006-06-07  0:16   ` Robert Hancock [this message]
2006-06-07  6:56     ` Backport of a 2.6.x USB driver to 2.4.32 - help needed Heiko Gerstung
     [not found] <mailman.1149588721.11795.linux-kernel2news@redhat.com>
2006-06-09 23:26 ` Pete Zaitcev
2006-06-14 13:56   ` Heiko Gerstung
2006-06-06  9:48 Heiko Gerstung
2006-06-06 11:23 ` Jesper Juhl
2006-06-06 11:41   ` Heiko Gerstung
2006-06-06 14:43     ` Lennart Sorensen
2006-06-06 14:48       ` Heiko Gerstung
2006-06-06 14:58         ` Lennart Sorensen
2006-06-06 18:30   ` Nish Aravamudan
2006-06-07  8:04     ` Jesper Juhl

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=44861AEE.3020109@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=jesper.juhl@gmail.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