From: Robert Hancock <hancockr@shaw.ca>
To: Rick Niles <fniles@gnupooh.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help with rtc to hpet conversion of OSGPS driver
Date: Thu, 11 Oct 2007 22:20:18 -0600 [thread overview]
Message-ID: <470EF602.40404@shaw.ca> (raw)
In-Reply-To: <fa.nKddWg8u6TJNw86Rid83rey2q6Q@ifi.uio.no>
Rick Niles wrote:
> I'm the Linux maintainer for the OSGPS (open source GPS) project. Our
> last release version was based off Fedora 5 and since we have had some
> hardware issues with our on board interrupt line I was using the RTC
> interrupt to service the tracking loops. I've been trying to make the
> driver work with Fedora 7 and the 2.6.22 kernel, but the rtc_register()
> and other RTC functions seems to have been removed. I see they've been
> replaced by the corresponding HPET functions, which is great. However,
> hpet_register() always returns -16 (EBUSY). This could be because I
> lack the correct hardware (I'm running 32-bit Linux on a Athlon64 with
> an NVIDIA chipset) or some other reason.
>
> I'm looking for any help here. The RTC version of the code can be
> viewed at:
> http://osgps.cvs.sourceforge.net/osgps/osgps/linuxmod.c?revision=1.12&view=markup
>
>
> Can device drivers still use the real-time clock at all? Does the
> tickless kernel effect this at all?
>
> Thanks for any help you can lend,
> Rick Niles.
Am I missing why you can't just use a normal kernel timer for this? You
shouldn't have to mess with the RTC or HPET directly..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-10-12 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.nKddWg8u6TJNw86Rid83rey2q6Q@ifi.uio.no>
2007-10-12 4:20 ` Robert Hancock [this message]
2007-10-11 12:01 Help with rtc to hpet conversion of OSGPS driver Rick Niles
2007-10-11 12:37 ` Jan Engelhardt
2007-10-11 12:51 ` Rick Niles
2007-10-11 13:23 ` Jan Engelhardt
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=470EF602.40404@shaw.ca \
--to=hancockr@shaw.ca \
--cc=fniles@gnupooh.org \
--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.