Upcoming patch

QNX Newsgroups (Archives) qdn.public.qnxrtp.installation
#1

It’s a little difficult deciding where to post this one, so I’ll take a
guess at this newsgroup being close.

There have been several references to an NTO patch that will be coming
at some point in the future. At this time, has QSSL got a release date
selected, and a list of fixes/enhancements that will be included in it?

#2

take a wild guess :slight_smile:
given the fact that there are still some glitches (read those
“leaked” information from other posts :slight_smile: and traditional slowness
in December (holiday season), we may get the patch A in January.
Or if we are lucky, we may get it as a Christmas present :slight_smile:
Anyway, the first non beta release of RTP will probably follow patch A
and it will most likely in Q1 2001 as I joked with Mario several
moths ago.
frank

On Sat, 25 Nov 2000, David Woodhouse wrote:

It’s a little difficult deciding where to post this one, so I’ll take a
guess at this newsgroup being close.

There have been several references to an NTO patch that will be coming
at some point in the future. At this time, has QSSL got a release date
selected, and a list of fixes/enhancements that will be included in it?

#3

For those of you who have access to patch A, any comments on
my posts some weeks ago (see below)? My guess is some of them
may be addressed while others may end up in patch B.

frank

========================================

  1. support of ext2 new features.
  2. install on linux ext2 partition.
  3. UDS support in tcpip full stack,
    or maybe de-couple it from tcpip and provide a special/separate driver?
  4. allow users to add .so object load directory (like linux’s /etc/ld.so.conf)
  5. mousetrap/inputtrap be more friendly to non Photon apps.
  6. autodetect modem as a 3rd serial port.
  7. boot/install on SCSI support.
    :sunglasses: ATA 66 ATA 100 support.
  8. package manager be firewall/proxy friendly.
  9. net driver support of promiscous mode.
#4

It is being tested by selected sites. List of changes was posted in one of newsgroups. It is also on qnxstart page.

Previously, David Woodhouse wrote in qdn.public.qnxrtp.installation:

It’s a little difficult deciding where to post this one, so I’ll take a
guess at this newsgroup being close.

There have been several references to an NTO patch that will be coming
at some point in the future. At this time, has QSSL got a release date
selected, and a list of fixes/enhancements that will be included in it?

#5

Frank Liu <liug@mama.indstate.edu> wrote:

  1. mousetrap/inputtrap be more friendly to non Photon apps.

This will have to wait until a redesigned input driver architecture is
in place.

I don’t think it will make it into the release version of Photon 2.0

#6

I liked the 25M .exe and 91M .iso options
If new ISO’s are going to be produced:

if the 91M one grows, as long as it stays under
Zip100 size (100,431,872 Bytes?)

A big one (650M) with contrib
diff CPU optimizations (qcc -Wc,-march=i[3-6]86 -or- K6)

–

I can’t find the reply to - Process Specific Code Gen
news:8vc474$66r$1@inn.qnx.com
Is there a way to pass (append) those $CCFLAGS through make?

David Woodhouse <David.Woodhouse@cnpl.enbridge.com> wrote in message
news:3A1FF3EB.5392E39F@cnpl.enbridge.com…

It’s a little difficult deciding where to post this one, so I’ll take a
guess at this newsgroup being close.

There have been several references to an NTO patch that will be coming
at some point in the future. At this time, has QSSL got a release date
selected, and a list of fixes/enhancements that will be included in it?

#7

Or is procnto, in QSSL tradition, hand-crafted in assembler?

I <n2kra@orn.com> wrote in message news:8vudt5$it7$1@inn.qnx.com…

I liked the 25M .exe and 91M .iso options
If new ISO’s are going to be produced:

A big one (650M) with contrib
diff CPU optimizations (qcc -Wc,-march=i[3-6]86 -or- K6)

–

I can’t find the reply to -

Are articles going to expire? or archived? msg counter reset?
would more inter-article links be useful ?

  • Process Specific Code Gen news:8vc474$66r$> 1@inn.qnx.com
    Is there a way to pass (append) those $CCFLAGS through make?

David Woodhouse <> David.Woodhouse@cnpl.enbridge.com> > wrote in message
news:> 3A1FF3EB.5392E39F@cnpl.enbridge.com> …
It’s a little difficult deciding where to post this one, so I’ll take a
guess at this newsgroup being close.

There have been several references to an NTO patch that will be coming
at some point in the future. At this time, has QSSL got a release date
selected, and a list of fixes/enhancements that will be included in it?

if the 91M one grows, as long as it stays under
Zip100 size (100,431,872 Bytes?) DOS file on Partition

I can’t find the message where I said how I did this
something like -

umount /fs/cd*
mount -t iso /fs/hd2-dos/QNXrtp.iso /fs/cd0

Is removable auto detection possible (on EIDE)? CD / Zip / etc…
(in dev-enum?) and appropriate devb-eide FLAGS set?

eject ioctl() ??? and user util

#8

Michael J. Ferrador <n2kra@orn.com> wrote:

Or is procnto, in QSSL tradition, hand-crafted in assembler?

This has never been the QSSL tradition - the vast majority of the kernel
and process manager for all QNX OS’s has been C. That’s even more important
now that we support architectures other than the X86.

–
Brian Stecher (bstecher@qnx.com) QNX Software Systems, Ltd.
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8