On Fri, 2004-05-28 at 08:01, M. Warner Losh wrote:
> In message: <1085610184.3232.250.camel@zircon>
> Joe Kelsey <firstname.lastname@example.org> writes:
> : Gee, I ask a seemingly simple question about connecting a very simple
> : driver to the system and all of ZERO people chime in with help.
> : The only thing anyone had to say involved something like "Read and
> : update isa_compat.h" and I can take it from there! However, noone said
> : that or anything else for that matter.
> : It really upsets me because it seems that absolutely *no* documentation
> : exists for how to connect a driver to FreeBSD 4.x. Documentation exists
> : for 3.x and 5.x, but none for 4.x.
> : This mailing list just seems useless to me.
> stable tends to be more user oriented, and less developer oriented. I
> read it less often than I do the other lists.
> Maybe if you could send me your driver, I can point out the problems
> in it. Since you didn't provide any code, it really is hard to guess
> what might be going wrong. isa_compat.h almost certainly isn't the
> answer, since that's only for drivers in a transition period from the
> old APIs to the new ones.
Thank you very much for the offer to help. In fact, I "randomly" choose
gpib.c and labpc.c as the structural models for my device driver, and so
I ran into the problem of how do I hook this into the kernel. The basic
problem arises since I just want to diddle I/O addresses and none of the
devices have interrupts associated with them, so it really does not need
all of that horrid module stuff. I just wanted to hook up a choice of
base I/O address from the kernel config file.