(doh ! I posted this on Friday in qdn.public.devtools - #$#^%$ Mozilla -
anyway this should be the right place this time)
What is Reswrap.
Reswrap is a C++ resource manager framework for QNX6.
The goal of Reswrap is to allow those developing resource managers
in C++ under QNX 6 to provide full filesystem functionality to
their “non-filesystem” (i.e. resource managers that do not
manage hard disks per-se) resource managers.
The Reswrap library provides 2 classes which (when used together)
allow a ramdisk to be created in only a few lines of code; however
a ramdisk is not the goal of Reswrap (only a demonstration of how
it provides full file-system like functionality). By using the
primary class (Resmgr) in composition, and by deriving from one
or more of the other three classes (Device,Node,Ocb), the
programmer, can express application specific resource manager
semantics.
Currently Reswrap is beta software (version 0.90). The intention
is to obtain feedback, and produce a 1.0 version in Q1 2003.
Other notes:
o Reswrap requires libsigc++ version 1.2.1. (I’ll be posting
a .qpr for this shortly on my website, and I believe it’ll
be on the 3rd party CD).
o Reswrap is being made available under the LGPL license (details
presented prior to installation).
o Reswrap is currently available at http://home.attbi.com/~rgallen
(as a one-click .qpr).
o Reswrap source is available at the same site, as a tarball.
o Reswrap is being developed in my (limited) spare time, so
any help is welcomed.
o I’ll be working on tutorial documentation as time permits
reference documentation is available by running doxygen on
the headers.
o Any problems/comments to rgallen@attbi.com.
Happy Holidays,
Rennie
Hmm. Would this be helpful in porting the Linux
IEEE-1394 driver stack over to QNX? I’m interested
in interfacing cameras, but others may be interested
in interfacing external FireWire drives.
John Nagle
Animats
Rennie Allen wrote:
(doh ! I posted this on Friday in qdn.public.devtools - #$#^%$ Mozilla -
anyway this should be the right place this time)
What is Reswrap.
Reswrap is a C++ resource manager framework for QNX6.
The goal of Reswrap is to allow those developing resource managers
in C++ under QNX 6 to provide full filesystem functionality to
their “non-filesystem” (i.e. resource managers that do not
manage hard disks per-se) resource managers.
The Reswrap library provides 2 classes which (when used together)
allow a ramdisk to be created in only a few lines of code; however
a ramdisk is not the goal of Reswrap (only a demonstration of how
it provides full file-system like functionality). By using the
primary class (Resmgr) in composition, and by deriving from one
or more of the other three classes (Device,Node,Ocb), the
programmer, can express application specific resource manager
semantics.
Currently Reswrap is beta software (version 0.90). The intention
is to obtain feedback, and produce a 1.0 version in Q1 2003.
Other notes:
o Reswrap requires libsigc++ version 1.2.1. (I’ll be posting
a .qpr for this shortly on my website, and I believe it’ll
be on the 3rd party CD).
o Reswrap is being made available under the LGPL license (details
presented prior to installation).
o Reswrap is currently available at > http://home.attbi.com/~rgallen
(as a one-click .qpr).
o Reswrap source is available at the same site, as a tarball.
o Reswrap is being developed in my (limited) spare time, so
any help is welcomed.
o I’ll be working on tutorial documentation as time permits
reference documentation is available by running doxygen on
the headers.
o Any problems/comments to > rgallen@attbi.com> .
Happy Holidays,
Rennie
John Nagle wrote:
Hmm. Would this be helpful in porting the Linux
IEEE-1394 driver stack over to QNX? I’m interested
in interfacing cameras, but others may be interested
in interfacing external FireWire drives.
How helpful it would be is dependant on the structure
of the Linux code. Certainly, all other things being
equal it will be easier than doing it from scratch.
Linux drivers (being kernel based) are typically non-
trivial ports to QNX. I am going to be using the kit
to produce a compatible version of the Linux health
driver (compatible meaning that drivers for new
health chips will be able to be mechanically ported
to QNX - i.e. 5 minutes), I definately anticipate it
making my life easier in this endeavor (having already
done a proof-of-concept in ‘C’ with the “standard” kit).
Any performance bottlenecks introduced in the framework
should not be significant wrt a 1394 drive (the efficiency
of the caching code will be the biggest determinant of
performance for what is essentially a networked drive).
To get an idea of performance penalty for using the kit,
run the ramdisk test program that comes with the source
tarball (you could compare it to Rob Krten’s - done
in ‘C’ straight on top of the standard resmgr api).
Bottom line: the best recommendation I can give you is
download it and see 