Re: Thanks for All the Help

From: M. Warner Losh (imp_at_bsdimp.com)
Date: 05/29/04

  • Next message: Eitarou Kamo: "umass0: CBI......" 
    Date: Fri, 28 May 2004 19:37:47 -0600 (MDT)
To: joe@zircon.seattle.wa.us

    In message: <1085764038.485.71.camel@zircon>
                Joe Kelsey <joe@zircon.seattle.wa.us> writes:
    : On Fri, 2004-05-28 at 08:01, M. Warner Losh wrote:
    : > In message: <1085610184.3232.250.camel@zircon>
    : > Joe Kelsey <joe@zircon.seattle.wa.us> 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.

    OK. I'll write up some stuff this weekend.

    Warner
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Eitarou Kamo: "umass0: CBI......"

    Relevant Pages

    • Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.cif_iwi
      ... : Warner Losh wrote: ... :> on its name from the in-kernel loader. ... The in-kernel linker can only lookup things loaded ... :> safely and hand a reference to the file to the driver. ...
      (freebsd-arch)
    • Re: atheros frecuencies limited
      ... M. Warner Losh wrote: ... can get all the channels by using the same wireless card but a different OS. ... The other thing is that I thought atheros doesnt have firmware and the ... driver handles the regulatory domain settings. ...
      (freebsd-current)
    • Re: Problem with HP DL380
      ... : On Sat, 20 Nov 2004, M. Warner Losh wrote: ... hw.pci.do_powerstate puts a device into C3 state if no driver attaches. ... That iLO service processor of the DL380s ... kernel initializes its ACPI parts, and then the iLO console stops working. ...
      (freebsd-current)
    • Re: USB drivers
      ... :> From: M. Warner Losh ... :>: What I am trying to determine is why my multifunction ... mentioned that a pointer must be present for a driver to attach to a ... If there is only one pointer for a device, only one driver may ...
      (freebsd-current)
    • Re: Thanks for All the Help
      ... driver to the system and all of ZERO people chime in with help. ... I ran into the problem of how do I hook this into the kernel. ... problem arises since I just want to diddle I/O addresses and none of the ... base I/O address from the kernel config file. ...
      (freebsd-stable)