My recollection is that the problem relates to calling make_dev() from the
attach routine, and attach from the open call, and of course you can't
open before you make_dev with devfs. Someone needs to restructure the
driver to match some our other pseudo-device drivers where the device is
properly created as part of module initialization. If fixed this and
other things locally at one point on my notebook, but eventually got
sufficiently sick of always fixing the kernel module for the latest
-CURRENT change that I gave up on updating it. I have since lost the
changes, but they shouldn't be too hard to reproduce.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Thu, 15 Aug 2002, dmk wrote:
> Is anybody successfully using the port emulators/rtc with vmware2 on
> While the port builds and installs fine, a /dev/rtc device never appears.
> ISTM that the rtc device does a make_dev as part of the device open()
> rather than at module load and that vmware doesn't work like that.
> Having no kernel (module) hacking experience, I come to the list for
> pointers. I am trying to wrap my head around rtc enough to try make_dev()
> at module load time, but maybe someone can give me a hint as to what's
> going on.
> I'm breaking the rules and running an old -CURRENT from Feb 4, 2002, so
> I'll humbly swallow suggestions that I upgrade.
> Thanks loads,
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message