linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <470E1C42.1040600@gnupooh.org>
Date:	Thu, 11 Oct 2007 08:51:14 -0400
From:	Rick Niles <fniles@...pooh.org>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Help with rtc to hpet conversion of OSGPS driver

Maybe I'm way off here, but that seems to be the function to register a 
RTC hardware chip with the kernel.  I want to use a real-time clock 
interrupt to wake up my driver and service the GPS correlator, about 
every 500ms.  Please let me know if I'm misunderstanding.

Jan Engelhardt wrote:
> On Oct 11 2007 08:01, Rick Niles wrote:
>   
>> 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.
>>     
>
> grep -r rtc_device_register drivers/rtc/
>
> Does that help?
>
>   
>> 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.
>>     

-
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/