All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Gerstung <heiko.gerstung@meinberg.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Backport of a 2.6.x USB driver to 2.4.32 - help needed
Date: Tue, 06 Jun 2006 13:41:02 +0200	[thread overview]
Message-ID: <448569CE.1020906@meinberg.de> (raw)
In-Reply-To: <9a8748490606060423t102384f4m626b4366898ce9cd@mail.gmail.com>

Jesper Juhl wrote:
> 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.
OK, so I guess I can safely ommit this.

> schedule_timeout_uninterruptible() is used to sleep on a wait-queue,
> which 2.4.x does not have.
Is there any similiar functionality in a 2.4 kernel environment? A
pointer to a 2.4 kernel driver using such a mechanism would be a good
starter...

> [snip]
> 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 ???
Yes, but unfortunately I have no chance to do this and therefore I rely
on others to do this. Well, the same applies to [me] and [kernel
drivers], but I hoped that it might be easier to try and backport one
driver instead of trying to improve other people's code (maybe that is
what OPC stands for :-)), especially when this code has a much larger
impact on several parts of the kernel.

> [snip]
> 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...
OK, I will try to do so, but I am afraid that I will run out of time in
the meantime.

Thank you very much for your help and your fast response.

Kind regards,
Heiko




-- 
------------------------------------------------------------------------

*MEINBERG Funkuhren GmbH & Co. KG*
Auf der Landwehr 22
D-31812 Bad Pyrmont, Germany
Tel.: ++49 (0)5281 9309-25
Fax: ++49 (0)5281 9309-30
eMail: heiko.gerstung@meinberg.de <mailto:heiko.gerstung@meinberg.de>
Internet: www.meinberg.de <http://www.meinberg.de/>

------------------------------------------------------------------------

Meinberg radio clocks: 25 years of accurate time worldwide


  reply	other threads:[~2006-06-06 11:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  9:48 Backport of a 2.6.x USB driver to 2.4.32 - help needed Heiko Gerstung
2006-06-06 11:23 ` Jesper Juhl
2006-06-06 11:41   ` Heiko Gerstung [this message]
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=448569CE.1020906@meinberg.de \
    --to=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 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.