From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Heiko Gerstung" <heiko.gerstung@meinberg.de>
Cc: 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 13:23:12 +0200 [thread overview]
Message-ID: <9a8748490606060423t102384f4m626b4366898ce9cd@mail.gmail.com> (raw)
In-Reply-To: <44854F74.50406@meinberg.de>
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.
[snip]
>
> Under 2.4.32 this driver crashes (kernel panic) when I try to enslave a
> network interface handled by it, with a 2.6 kernel there is no such
> problem. Unfortunately I cannot go ahead with a 2.6 kernel at the
> moment, because it lacks a properly running PPS support.
>
Wouldn't it make more sense to work on improving PPS (I assume you are
refering to NTP "pulse per second" btw) support in 2.6.x rather than
backporting an USB driver to 2.4.x ???
[snip]
>
> Now I would need help in finding a way to substitute the two missing
> functions in a 2.4 kernel environment and I desperately hope that
> someone sees my dilemma and can help me somehow...
>
The book "Linux Device Drivers" third edition is available for free
online and describes 2.6.x USB drivers in a fair bit of detail.
Earlier editions of the book describe the 2.4.x kernel (don't know if
those are available for free, but it should be possible to get them
from a bookstore in any case).
Getting hold of the second & third editions of LDD and comparing the
USB info from both should give you some idea of where to start...
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-06-06 11:23 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 [this message]
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
[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=9a8748490606060423t102384f4m626b4366898ce9cd@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=heiko.gerstung@meinberg.de \
--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®