Hi
Does QNX4 use any information provided by the BIOS at boot time?
I may need to load a little ISR into unused RAM before QNX4 is started. If
QNX is going to trounce my ISR, by testing memory and initializing the
Interrupt Controller, then I’d like to know. I don’t want to waist my time.
Regards, Clint
“clint” <clintl@hotmail.com> wrote in
news:01c1b456$2aac3300$7cc809c0@mobile-insyp:
Does QNX4 use any information provided by the BIOS at boot time?
I may need to load a little ISR into unused RAM before QNX4 is started.
If QNX is going to trounce my ISR, by testing memory and initializing
the Interrupt Controller, then I’d like to know. I don’t want to waist
my time.
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
I suppose that means my ISR loaded into RAM shall be trounced when QNX4
starts…
That means there is no chance of the pre-QNX4-start ISR communicating
information to the post-QNX4-start ISR; the trouncing I am supposing is QNX
disrupting all of ram by testing it and sizing it.
PS: the ISR is operating a Comm Port used to responds to other system
components. The other system components will force the system’s power to be
cycled if not responded to appropriately.
Adam Mallory <amallory@qnx.com> wrote in article
Xns91B45F2C4F64Camalloryqnxcom@209.226.137.4…
“clint” <> clintl@hotmail.com> > wrote in
news:01c1b456$2aac3300$7cc809c0@mobile-insyp:Does QNX4 use any information provided by the BIOS at boot time?
I may need to load a little ISR into unused RAM before QNX4 is started.
If QNX is going to trounce my ISR, by testing memory and initializing
the Interrupt Controller, then I’d like to know. I don’t want to waist
my time.You should attach an ISR inside QNX4 if you want it to run after QNX has
booted.
\Cheers,
AdamQNX Software Systems Ltd.
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
On 13 Feb 2002 23:07:18 GMT, “clint” <clintl@hotmail.com> wrote:
I suppose that means my ISR loaded into RAM shall be trounced when QNX4
starts…
That means there is no chance of the pre-QNX4-start ISR communicating
information to the post-QNX4-start ISR; the trouncing I am supposing is QNX
disrupting all of ram by testing it and sizing it.PS: the ISR is operating a Comm Port used to responds to other system
components. The other system components will force the system’s power to be
cycled if not responded to appropriately.
The OS takes over all IRQ stubbing them if not currently used.
As suggested, write the ISR under QNX4 and respond to the other system
components once booted.
You have the OS now at your disposal, better to use it than to fight it 
“clint” <clintl@hotmail.com> wrote in
news:01c1b4e4$7143daa0$7cc809c0@mobile-insyp:
I suppose that means my ISR loaded into RAM shall be trounced when QNX4
starts…
That means there is no chance of the pre-QNX4-start ISR communicating
information to the post-QNX4-start ISR; the trouncing I am supposing is
QNX disrupting all of ram by testing it and sizing it.
Well I’m not sure exactly how you’ll “load” you ISR into RAM before the OS
loads - unless of course you’re writing the IPL to boot strap the OS.
I’m not sure what kind of information you would need to communicate pre-os
to a post-os ISR, that couldn’t be done when the OS is loaded.
PS: the ISR is operating a Comm Port used to responds to other system
components. The other system components will force the system’s power
to be cycled if not responded to appropriately.
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>