John Nagle wrote:
That’s very nice. A bit depressing, but nice.
There isn’t much of a QNX community left, though.
[… ]
For all who are interested in the “left” QNX community:
The 4th European QNX-Night will be the 25th QNX Anniversary-Night !!!
You can meet even Dan and talk with him in person…
Nuremberg/Germany, Feb. 22th, 2005
http://www.qnx-night.com
it’s on the first evening of the
www.embedded-world-2005.de
hotel reservation is comfortable via www.hrs.de
We expect an increasing number of attendees …
\
-
/\ /\ * * *
-
-
/ / \ / \ *
-
- / / \ \ * a HAPPY and PROSPEROUS
/ / \ \ * *
-
/ / \ \ * * NEW YEAR *
-
/ / \ \ * * * *
-
-
Jutta
Jutta,
I have been rude to you and Armin recently, but I just realized how wrong I
am to do that. You two are probably of the most gracious and kind
individuals I’ve met online. You guys don’t have to do this QNX-night
thing, but every year you are hard at work putting it together.
I can’t come, but for what its worth, thanks for the invite and thanks for
doing all this. You are the best.
Have a great new year…
Kevin
“Jutta Steinhoff” <j-steinhoff@web.de> wrote in message
news:cr3jgj$2ak$1@inn.qnx.com…
John Nagle wrote:
That’s very nice. A bit depressing, but nice.
There isn’t much of a QNX community left, though.
[… ]
For all who are interested in the “left” QNX community:
The 4th European QNX-Night will be the 25th QNX Anniversary-Night !!!
You can meet even Dan and talk with him in person…
Nuremberg/Germany, Feb. 22th, 2005
http://www.qnx-night.com
it’s on the first evening of the
www.embedded-world-2005.de
hotel reservation is comfortable via > www.hrs.de
We expect an increasing number of attendees …
\
-
/\ /\ * * *
-
-
/ / \ / \ *
-
- / / \ \ * a HAPPY and PROSPEROUS
/ / \ \ * *
-
/ / \ \ * * NEW YEAR *
-
/ / \ \ * * * *
-
-
Jutta
Who said all embedding needs to be “deeply embedded”. Any runtime
environment using QNX is effectively a custom target.
I believe you’ve missed the point. Most customers don’t need much
customisation - just the ability to deselect some of the more fatty parts of
the OS such as the dev environment.
In most cases we are quite happy to have the standard boot image
(including diskboot), we just don’t want to install the development
system and any other components which are not part of the runtime
license.
Actually, with 6.21, you already had that. If you boot 6.21 NC it
first installs the runtime and then reboots to complete the install
of the dev environment. Just exit the installer and you are done.
That’s not true. The runtime installation was a half-cocked installation of
6.2.0 which contains unfixed bugs such as in the devn-rtl device driver.
Version sensitive stuff like qconn is also a problem. If you abort where you
suggest, the result is an unsupported and obsolete version. Not 6.2.1.
Robert Muil wrote:
Actually, with 6.21, you already had that. If you boot 6.21 NC it
first installs the runtime and then reboots to complete the install
of the dev environment. Just exit the installer and you are done.
That’s not true. The runtime installation was a half-cocked installation of
6.2.0 which contains unfixed bugs such as in the devn-rtl device driver.
Version sensitive stuff like qconn is also a problem. If you abort where you
suggest, the result is an unsupported and obsolete version. Not 6.2.1.
Correct. In fact, what you have at that moment contains drivers
that won’t run with the kernel currently loaded. There were
some small, but critical, changes in the kernel in anticipation
of supporting 64-bit machines. (Did 64-bit support ever happen?)
That’s also a problem with the 6.21NC disk booted in CD-only mode.
It comes up with mismatched kernel and drivers. Ethernet probably
won’t work, even though it may work when you install the whole
system properly.
As far as I know, the last version that worked right in CD-only
mode was QNX 6.20.
Also, you can’t install QNX 6.21 properly if the clock on the
machine has an earlier date than the build date of the repository.
So set the clock first on new machines.
QNX 6.21NC, properly installed, is a good system.
If you have a copy of “mkifs” (distributed free with QNX 6.0NC)
you can build a minimal system for an embedded target.
Of course, you can’t sell the target; it’s the “non commercial”
version. But you can develop, and then buy distribution licenses
in bulk when the product works.
John Nagle
John Nagle wrote:
Robert Muil wrote:
[…]
Also, you can’t install QNX 6.21 properly if the clock on the
machine has an earlier date than the build date of the repository.
So set the clock first on new machines.
QNX 6.21NC, properly installed, is a good system.
If you have a copy of “mkifs” (distributed free with QNX 6.0NC)
you can build a minimal system for an embedded target.
Of course, you can’t sell the target; it’s the “non commercial”
version.
But you can develop, and then buy distribution licenses
in bulk when the product works.
John, just for correctness:
before buying distribution licenses you have to buy Momentics …
Cheers,
Correct. In fact, what you have at that moment contains drivers
that won’t run with the kernel currently loaded. There were
some small, but critical, changes in the kernel in anticipation
of supporting 64-bit machines. (Did 64-bit support ever happen?)
It was for >32bit support, so the address pointers changed to 64bits.
And yes, this support exists today for Neutrino on PPC and x86 - 32bit
CPUs with >32bits of address space.
chris
I know that I am able to do 64-bit arithmetic But how does one enable true
64-bit OS for x86?
“Chris McKillop” <cdm@killerstuff.net> wrote in message
news:cs2e8q$hf9$1@inn.qnx.com…
It was for >32bit support, so the address pointers changed to 64bits.
And yes, this support exists today for Neutrino on PPC and x86 - 32bit
CPUs with >32bits of address space.
chris
Bill Caroselli wrote:
I know that I am able to do 64-bit arithmetic But how does one enable true
64-bit OS for x86?
You don’t. Neutrino is a 32bit OS. However, there are extensions (some
would call them hacks, both at the hardware and software level) to
address more then 32bits of memory. On x86 it is called PAE and I
forget the name for the hack on PPC.
chris
Bill Caroselli <qtps@earthlink.net> wrote:
I know that I am able to do 64-bit arithmetic But how does one enable true
64-bit OS for x86?
Install FreeBSD? 
(Well, it is qnx.cafe!)
“Chris McKillop” <> cdm@killerstuff.net> > wrote in message
news:cs2e8q$hf9$> 1@inn.qnx.com> …
It was for >32bit support, so the address pointers changed to 64bits.
And yes, this support exists today for Neutrino on PPC and x86 - 32bit
CPUs with >32bits of address space.
chris
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~museum/
Thanks for the suggestion Robert, but I am adie hardQNX developer.
Bill Caroselli
“Robert Krten” <rk@parse.com> wrote in message
news:cs5t79$9g6$2@inn.qnx.com…
Bill Caroselli <> qtps@earthlink.net> > wrote:
I know that I am able to do 64-bit arithmetic But how does one enable
true
64-bit OS for x86?
ducking>Install FreeBSD? >
(Well, it is qnx.cafe!)
“Chris McKillop” <> cdm@killerstuff.net> > wrote in message
news:cs2e8q$hf9$> 1@inn.qnx.com> …
It was for >32bit support, so the address pointers changed to 64bits.
And yes, this support exists today for Neutrino on PPC and x86 - 32bit
CPUs with >32bits of address space.
chris
\
[If replying via email, you’ll need to click on the URL that’s emailed to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~museum/
What does PAE buy me, and how doI implement it?
BillCaroselli
“Chris McKillop” <cdm@killerstuff.net> wrote in message
news:cs53fk$k8u$1@inn.qnx.com…
Bill Caroselli wrote:
I know that I am able to do 64-bit arithmetic But how does one enable
true
64-bit OS for x86?
You don’t. Neutrino is a 32bit OS. However, there are extensions (some
would call them hacks, both at the hardware and software level) to
address more then 32bits of memory. On x86 it is called PAE and I
forget the name for the hack on PPC.
chris
Physical Address Extension. It’s not the only hack - there’s also PSE (Page
Size Extension).
You don’t implement it. Intel and OS vendors do…
http://www.linuxclustersinstitute.org/Linux-HPC-Revolution/Archive/PDF00/Tutorial_IA-32.pdf
“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:cs6tgl$3ri$1@inn.qnx.com…
What does PAE buy me, and how doI implement it?
BillCaroselli
“Chris McKillop” <> cdm@killerstuff.net> > wrote in message
news:cs53fk$k8u$> 1@inn.qnx.com> …
Bill Caroselli wrote:
I know that I am able to do 64-bit arithmetic But how does one enable
true
64-bit OS for x86?
You don’t. Neutrino is a 32bit OS. However, there are extensions (some
would call them hacks, both at the hardware and software level) to
address more then 32bits of memory. On x86 it is called PAE and I
forget the name for the hack on PPC.
chris
Hello Robert
Is it too big a deal to just install the entire OS on one host and then pick
and choose the components that you require on any custom run-time host that
you are preparing. You can then prepare a script to do the work for you.
This is what most people have always done.
Bill Caroselli
“Robert Muil” <r.muil@crcmining.com.au> wrote in message
news:cs05us$p1n$1@inn.qnx.com…
Who said all embedding needs to be “deeply embedded”. Any runtime
environment using QNX is effectively a custom target.
I believe you’ve missed the point. Most customers don’t need much
customisation - just the ability to deselect some of the more fatty parts
of
the OS such as the dev environment.
In most cases we are quite happy to have the standard boot image
(including diskboot), we just don’t want to install the development
system and any other components which are not part of the runtime
license.
Actually, with 6.21, you already had that. If you boot 6.21 NC it
first installs the runtime and then reboots to complete the install
of the dev environment. Just exit the installer and you are done.
That’s not true. The runtime installation was a half-cocked installation
of
6.2.0 which contains unfixed bugs such as in the devn-rtl device driver.
Version sensitive stuff like qconn is also a problem. If you abort where
you
suggest, the result is an unsupported and obsolete version. Not 6.2.1.
Bill Caroselli wrote:
Hello Robert
Is it too big a deal to just install the entire OS on one host and then pick
and choose the components that you require on any custom run-time host that
you are preparing.
Do you have all information about dependencies e.g. between binaries and
libraries?? What about the different versions??
How do you handle the ‘package files system’ of QNX6.2 ??
Do you give any warranty about the consistency of your hacked QNX
configuration?
Your customers are happy with your self cooked CD ??
Armin
You can then prepare a script to do the work for you.
This is what most people have always done.
Bill Caroselli
“Robert Muil” <> r.muil@crcmining.com.au> > wrote in message
news:cs05us$p1n$> 1@inn.qnx.com> …
Who said all embedding needs to be “deeply embedded”. Any runtime
environment using QNX is effectively a custom target.
I believe you’ve missed the point. Most customers don’t need much
customisation - just the ability to deselect some of the more fatty parts
of
the OS such as the dev environment.
In most cases we are quite happy to have the standard boot image
(including diskboot), we just don’t want to install the development
system and any other components which are not part of the runtime
license.
Actually, with 6.21, you already had that. If you boot 6.21 NC it
first installs the runtime and then reboots to complete the install
of the dev environment. Just exit the installer and you are done.
That’s not true. The runtime installation was a half-cocked installation
of
6.2.0 which contains unfixed bugs such as in the devn-rtl device driver.
Version sensitive stuff like qconn is also a problem. If you abort where
you
suggest, the result is an unsupported and obsolete version. Not 6.2.1.
\
Chris McKillop wrote:
Bill Caroselli wrote:
I know that I am able to do 64-bit arithmetic But how does one
enable true
64-bit OS for x86?
You don’t. Neutrino is a 32bit OS.
Yes … and it is an embedded systems. 64bit CPU are mainly used for
desktop workstations used for computing intensitive applications.
(CAD a.s.o …)
Armin
However, there are extensions (some
would call them hacks, both at the hardware and software level) to
address more then 32bits of memory. On x86 it is called PAE and I
forget the name for the hack on PPC.
chris
Armin Steinhoff wrote:
Chris McKillop wrote:
Bill Caroselli wrote:
I know that I am able to do 64-bit arithmetic But how does one
enable true
64-bit OS for x86?
You don’t. Neutrino is a 32bit OS.
Yes … and it is an embedded systems. 64bit CPU are mainly used for
desktop workstations used for computing intensitive applications.
(CAD a.s.o …)
Like Cisco routers, which are already hitting the 4GB wall
in the high-end units like the 12816.
64 bit support is going to be needed by the router customers.
John Nagle
I know this is an old post but since it is addressed to me, let me reply.
I only work with the latest version of QNX. I also only have ot support
software that I wrote. I have never had to product a back version of
anything. If there’s a problem discovered I can reship the newest latest
version. That’s a luxery that I have.
As for prerequisits, the linker/loader will tell me most of what I need.
Extensive testing in the environment I intent to use the system will flush
out anything else, at least so far.
“Armin Steinhoff” <a-steinhoff@web.de> wrote in message
news:csahvn$po4$1@inn.qnx.com…
Bill Caroselli wrote:
Hello Robert
Is it too big a deal to just install the entire OS on one host and then
pick
and choose the components that you require on any custom run-time host
that
you are preparing.
Do you have all information about dependencies e.g. between binaries and
libraries?? What about the different versions??
How do you handle the ‘package files system’ of QNX6.2 ??
Do you give any warranty about the consistency of your hacked QNX
configuration?
Your customers are happy with your self cooked CD ??
Armin
You can then prepare a script to do the work for you.
This is what most people have always done.
Bill Caroselli
“Robert Muil” <> r.muil@crcmining.com.au> > wrote in message
news:cs05us$p1n$> 1@inn.qnx.com> …
Who said all embedding needs to be “deeply embedded”. Any runtime
environment using QNX is effectively a custom target.
I believe you’ve missed the point. Most customers don’t need much
customisation - just the ability to deselect some of the more fatty
parts
of
the OS such as the dev environment.
In most cases we are quite happy to have the standard boot image
(including diskboot), we just don’t want to install the development
system and any other components which are not part of the runtime
license.
Actually, with 6.21, you already had that. If you boot 6.21 NC it
first installs the runtime and then reboots to complete the install
of the dev environment. Just exit the installer and you are done.
That’s not true. The runtime installation was a half-cocked installation
of
6.2.0 which contains unfixed bugs such as in the devn-rtl device driver.
Version sensitive stuff like qconn is also a problem. If you abort where
you
suggest, the result is an unsupported and obsolete version. Not 6.2.1.
\