linux-kernel - Help with rtc to hpet conversion of OSGPS driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <470E109C.6020903@gnupooh.org>
Date:	Thu, 11 Oct 2007 08:01:32 -0400
From:	Rick Niles <fniles@...pooh.org>
To:	linux-kernel@...r.kernel.org
Subject: Help with rtc to hpet conversion of OSGPS driver

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/