I am trying to get an x86 SBC booting from a DiskOnChip device, but have
discovered that the devb-doc that comes with the 6.1 RTOS needs to link with
the libraries from 6.0.
Where can I get the DiskOnChip drivers for 6.1?
Thanks
Larry
This driver is written by M-System, if they haven’t made a 6.1 version
there isn’t much you can do. Try contacting them.
“Larry Holding” <larryh@ansys.co.za> wrote in message
news:9ko627$jrh$1@inn.qnx.com…
I am trying to get an x86 SBC booting from a DiskOnChip device, but have
discovered that the devb-doc that comes with the 6.1 RTOS needs to link
with
the libraries from 6.0.Where can I get the DiskOnChip drivers for 6.1?
Thanks
Larry
“Larry Holding” <larryh@ansys.co.za> wrote in message
news:9ko627$jrh$1@inn.qnx.com…
I am trying to get an x86 SBC booting from a DiskOnChip device, but have
discovered that the devb-doc that comes with the 6.1 RTOS needs to link
with
the libraries from 6.0.Where can I get the DiskOnChip drivers for 6.1?
Did you manage to get that 6.1 driver ?
Pavol Kycina
“Pavol Kycina” <kycina@microstep-hdo.sk> wrote in message
news:3b723a38@asrpx.mshdo…
“Larry Holding” <> larryh@ansys.co.za> > wrote in message
news:9ko627$jrh$> 1@inn.qnx.com> …
I am trying to get an x86 SBC booting from a DiskOnChip device, but have
discovered that the devb-doc that comes with the 6.1 RTOS needs to link
with
the libraries from 6.0.Where can I get the DiskOnChip drivers for 6.1?
Did you manage to get that 6.1 driver ?
I queried M-Systems about the driver, and they replied that they are working
on a new driver for QNXRTP together with QNX, and that it will be out soon.
For now I have created a boot image with both the new libraries (libc.so.2,
libcam.so.2), the old libraries (libc.so.1, libcam.so.1) and links from
/usr/lib for ldqnx.so.2 and ldqnx.so.1 in it.
Realy this is not soo much an impact on the system, since the devb-doc
application itself chews up 1.5Mb of my RAM so the saving of a couple of kb
is not so critical. Also devb-fdc is a hog for RAM.
Pavol Kycina
Enjoy,
Larry
“Larry Holding” <l_holding@icon.co.za> wrote in message
news:9kuquq$njf$1@inn.qnx.com…
[snip]
I queried M-Systems about the driver, and they replied that they are
working
on a new driver for QNXRTP together with QNX, and that it will be out
soon.For now I have created a boot image with both the new libraries
(libc.so.2,
libcam.so.2), the old libraries (libc.so.1, libcam.so.1) and links from
/usr/lib for ldqnx.so.2 and ldqnx.so.1 in it.
Thanks for the idea with both libraries.
Realy this is not soo much an impact on the system, since the devb-doc
application itself chews up 1.5Mb of my RAM so the saving of a couple of
kb
is not so critical. Also devb-fdc is a hog for RAM.
I used cache=5% option of devb-doc to cut down RAM usage.
Pavol Kycina
Enjoy,
Larry
Pavol Kycina
Larry Holding <l_holding@icon.co.za> wrote:
: “Pavol Kycina” <kycina@microstep-hdo.sk> wrote in message
: news:3b723a38@asrpx.mshdo…
:> “Larry Holding” <larryh@ansys.co.za> wrote in message
:> news:9ko627$jrh$1@inn.qnx.com…
:> > I am trying to get an x86 SBC booting from a DiskOnChip device, but have
:> > discovered that the devb-doc that comes with the 6.1 RTOS needs to link
:> with
:> > the libraries from 6.0.
:> >
:> > Where can I get the DiskOnChip drivers for 6.1?
:>
:> Did you manage to get that 6.1 driver ?
: I queried M-Systems about the driver, and they replied that they are working
: on a new driver for QNXRTP together with QNX, and that it will be out soon.
: For now I have created a boot image with both the new libraries (libc.so.2,
: libcam.so.2), the old libraries (libc.so.1, libcam.so.1) and links from
: /usr/lib for ldqnx.so.2 and ldqnx.so.1 in it.
: Realy this is not soo much an impact on the system, since the devb-doc
: application itself chews up 1.5Mb of my RAM so the saving of a couple of kb
: is not so critical. Also devb-fdc is a hog for RAM.
If you start devb-fdc with no options it will use the default for caching
that disk do (its a devb device after all). This is currently set to be
15% of the system ram. You can reduce it by passing it the blk cache=
option. Look at the docs on io-blk.so for full details.
Peter
:> Pavol Kycina
: Enjoy,
: Larry