On Tue, Oct 23, 2001 at 12:40:51PM -0500, John Goerzen wrote: > Daniel Jacobowitz <dan@debian.org> writes: > > > John, what kernel/machine do you have hwclock causing a hang? I'm not > > sure off the top of my head what the status is in 2.2, but 2.4 has a > > "proper" /dev/rtc driver. We should be using hwclock. Clock is an > > awful ADB-bit-bashing hack that needs to die. > > I'm using BenH's 2.4.x kernels. I observed this behavior in both > 2.4.13pre and 2.4.10 release. I had not installed hwclock when I was > using any previous version. you configured it wrong then. CONFIG_RTC=n CONFIG_PPC_RTC=y that is the correct config. yours is no doubt backwards. > The clock program works flawlessly. hwclock works perfectly under both 2.2.18 - .20 and 2.4.* so long as you configure them properly. i have several systems here to prove it. the clock program as Dan put it is a kludge that must die, and a couple users misconfiguring thier kernel is no reason to bring it back. now if benh just broke his latest kernel thats a kernel bug and still no reason to bring back kludges. -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgplmP_dTVII3.pgp
Description: PGP signature