Andrew Boyd(deleted)
|
RE: help with custom io-pkt driver design / debug
|
Andrew Boyd(deleted)
07/19/2010 10:17 AM
post59799
|
RE: help with custom io-pkt driver design / debug
Whenever I have mutexing problems (with a new driver)
with io-pkt, I do this:
dumper -p <pid>
where pid is io-pkt's from pidin.
It will create a core file, as if io-pkt had sigsegv'd,
and you can easily bt with gdb to figure out what went
wrong. Sounds like you have a window somewhere.
PS I had to write an identical (emulated ethernet) driver
to talk to the bluetooth server for BNEP. We just put a
BNEP resmgr in the bluetooth server, and the driver does
read() and write() for packet rx and tx.
I put the driver in the nda section - generally anything
involving wireless involves more legal wrangling than my
first divorce, which was nuclear capable - but it turns
out there is absolutely nothing NDA in the driver - I
wrote it all from scratch, and it includes a sample resmgr
to integrate into your server that actually talks to the
hardware. It looks just like an ethernet driver to
io-pkt so tcp/ip and qnet work over it just fine.
If you want the source to the bt driver, ask Bert, or
whatever other connection you might have.
--
aboyd www.pittspecials.com/movies/tumble.wmv
|
|
|