public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Gerstung <heiko.gerstung@meinberg.de>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jesper Juhl <jesper.juhl@gmail.com>, 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 16:48:44 +0200	[thread overview]
Message-ID: <448595CC.8040607@meinberg.de> (raw)
In-Reply-To: <20060606144334.GA7859@csclub.uwaterloo.ca>

Hi, Lennart:

Lennart Sorensen wrote:
> On Tue, Jun 06, 2006 at 01:41:02PM +0200, Heiko Gerstung wrote:
>> 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.
> 
> Which part of PPS doesn't work on 2.6 if you have the PPS-kit-light
> installed?  There is a version for 2.6.15 around, which applies to
> 2.6.16 with minimal fixing.  Only problem I found so far with the code
> was that it breaks the serial console on my system, but that was easy to
> fix.  I still have to test it though since my serial port has the CD
> line stuck high at the moment until I can get the board fixed, so
> testing is a bit tricky.
> 
> I know I have run a gps receiver with PPS on the CD line under 2.6.8
> using PPS-kit-light, and it worked rather well.

It works but on my system it takes ~4 hours before I reach lower
microsecond offsets, where the 2.4 ppskit is below 10 microseconds after
four polling cycles. I already tried to fix that but the internal kernel
pps discipline is not working as good as  it did with the 2.4 ppskit
versions.

> 
> Len Sorensen

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 14:48 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
2006-06-06 14:43     ` Lennart Sorensen
2006-06-06 14:48       ` Heiko Gerstung [this message]
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=448595CC.8040607@meinberg.de \
    --to=heiko.gerstung@meinberg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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