RE: Porting USB stack -- questions on ioconf.c

Hello Hubert, I've actually solved the problem today working with Jared
McNeill from this list.  It turns out the implementation of malloc() in
my code did not honor the M_ZERO flag, didn't fill the allocated block
with zeros, and thus caused quite a bit of downstream-from-malloc
confusion.

Thanks for your response, though!  I will be sure and post more
questions as I continue on this porting adventure.  I'm sure there's
more crocodiles in the pond.  

As for the operating system I'm porting to:
http://www.ddci.com/products_deos.php

-----Original Message-----
From: Hubert Feyrer [mailto:[email protected]] 
Sent: Friday, August 26, 2011 3:18 PM
To: Pow, Christopher (SWCOE)
Cc: [email protected]
Subject: Re: Porting USB stack -- questions on ioconf.c


On Fri, 26 Aug 2011, Pow, Christopher (SWCOE) wrote:
> Hopefully someone out there can give me some pointers as to how the 
> tables in ioconf.c relate and how they should be set up differently
than 
> what I've got...?

I can't, but maybe a few hints:
  * ioconf.c is created by running "config KERNELNAME" in NetBSD,
    and it's created in the kernel compile directory (besides ioconf.h)
  * from that, digging into the config(8) program may help
  * also, NetBSD's autoconf system may be useful - see
    http://www.netbsd.org/docs/kernel/programming.html#autoconf and
    http://nixdoc.net/man-pages/NetBSD/autoconf.9.html for a start.
  * Other documentation that may be useful if you haven't found it
    already:
     - http://www.netbsd.org/docs/kernel/ddwg.html
     - http://www.netbsd.org/docs/kernel/pseudo/
     - http://www.netbsd.org/docs/internals/en/

Good luck!


  - Hubert

P.S.: What OS are you porting the USB stack to?