Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Aug 2000 19:32:56 -0700
From:      Mike Smith <msmith@freebsd.org>
To:        "Isaac Waldron" <waldroni@lr.net>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Size limits for kld's? 
Message-ID:  <200008250232.TAA00847@mass.osd.bsdi.com>
In-Reply-To: Your message of "Sun, 13 Aug 2000 12:10:23 EDT." <003e01c00540$fecf05c0$0100000a@waldron.house> 

next in thread | previous in thread | raw e-mail | index | archive | help
> Unfortunately, while the open and close functions I wrote are called
> correctly, the ioctl function is never called.  A call to ioctl(filehdl,
> PLEX86_IOCTL, int) returns an error, and a perror("ioctl") prints
> "ioctl: Bad Address."  I know that the ioctl number is correct, and it
> was defined with the proper _IO* macro.  The file handle also opens just
> fine, as the printf's in my open function are executed and show on the
> console.  AFAIK, that error would be caused by an EFAULT being returned
> somewhere in the chain.
> 
> What I'm asking is, what would cause some of the functions referenced by
> my driver's cdevsw to not be able to be called?  Are there size limits
> on functions in a kld?  Or a limit on the total size of a kld?

Nope.  But the third argument to ioctl() is typically the *address* of 
your integer parameter.



-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008250232.TAA00847>