From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: "Heiko Gerstung" <heiko.gerstung@meinberg.de>,
linux-kernel@vger.kernel.org
Subject: Re: Backport of a 2.6.x USB driver to 2.4.32 - help needed
Date: Tue, 6 Jun 2006 11:30:51 -0700 [thread overview]
Message-ID: <29495f1d0606061130s5451db8r102c7e1e75981994@mail.gmail.com> (raw)
In-Reply-To: <9a8748490606060423t102384f4m626b4366898ce9cd@mail.gmail.com>
On 6/6/06, Jesper Juhl <jesper.juhl@gmail.com> 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.
>
> schedule_timeout_uninterruptible() is used to sleep on a wait-queue,
> which 2.4.x does not have.
schedule_timeout_uninterruptible(timeout_value) is just a wrapper for
set_current_state(TASK_UNINTERRUPTIBLE);
schedule_timeout(timeout_value);
Maybe you were thinking of sleep_on*()?
Thanks,
Nish
next prev parent reply other threads:[~2006-06-06 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-06-07 8:04 ` Jesper Juhl
[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
2006-06-07 6:56 ` 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
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=29495f1d0606061130s5451db8r102c7e1e75981994@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=heiko.gerstung@meinberg.de \
--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
all inboxes | Powered by JetHome®