Hi,
Does the new RTP release support ata/100 drives? I got burned
by a new dell I bought expressly to use with qnx that had an ata/100
drive instead of the ata/66 that was on my test dell system.
In a more general vein, why aren’t important compatibility issues like
this noted on the qnx website? The ‘supported hardware’ laundry
list isn’t always sufficient to tell if a system will work with qnx or not.
Could you add a list of known compatability 'gotcha’s?
Thanks,
Arthur
Based on limited responses to my old post
http://qnx.iaware.org/pipermail/qdn.public.qnxrtp.installation/2000-November/001016.html
you are probably out of luck 
frank
On Wed, 24 Jan 2001, Arthur wrote:
Hi,
Does the new RTP release support ata/100 drives? I got burned
by a new dell I bought expressly to use with qnx that had an ata/100
drive instead of the ata/66 that was on my test dell system.In a more general vein, why aren’t important compatibility issues like
this noted on the qnx website? The ‘supported hardware’ laundry
list isn’t always sufficient to tell if a system will work with qnx or not.
Could you add a list of known compatability 'gotcha’s?Thanks,
Arthur
\
All ata100 drives can work in lower modes as well. However, for RTP to
work in any DMA mode the controller must be programmed by BIOS into a
mode supported by RTP. I bet by default it will be programmed into
highest mode supported by drive (DMA-5), in which case RTP drive will
happily accept ‘dma’ argument but performance won’t be like DMA. You
have to either force DMA-2 mode in BIOS (if it provides that option) or
disable higher modes on the drive using DOS utitlity supplied by
manufacturer.
Arthur wrote:
Hi,
Does the new RTP release support ata/100 drives? I got burned
by a new dell I bought expressly to use with qnx that had an ata/100
drive instead of the ata/66 that was on my test dell system.In a more general vein, why aren’t important compatibility issues like
this noted on the qnx website? The ‘supported hardware’ laundry
list isn’t always sufficient to tell if a system will work with qnx or not.
Could you add a list of known compatability 'gotcha’s?Thanks,
Arthur
Igor,
You da man! I’m still confused though.
QNX RTP without the dma option will work with which dma modes?
i.e. ata/100 (ultra dma 5), ata/66 (ultra dma 4), ata/33 (ultra dma 2)
QNX RTP with the dma option will work with which dma modes?
i.e. ata/100 (ultra dma 5), ata/66 (ultra dma 4), ata/33 (ultra dma 2)
And for the QSSL guys, please put this kind of information on known
incompatabilites somewhere appropriate on your website. (Or if
I missed it, please put it somewhere more prominent, such as near the
supported hardware list.)
Thanks,
Arthur
“Igor Kovalenko” <Igor.Kovalenko@motorola.com> wrote in message
news:3A6F35FB.7461D805@motorola.com…
All ata100 drives can work in lower modes as well. However, for RTP to
work in any DMA mode the controller must be programmed by BIOS into a
mode supported by RTP. I bet by default it will be programmed into
highest mode supported by drive (DMA-5), in which case RTP drive will
happily accept ‘dma’ argument but performance won’t be like DMA. You
have to either force DMA-2 mode in BIOS (if it provides that option) or
disable higher modes on the drive using DOS utitlity supplied by
manufacturer.
- igor
Arthur wrote:
Hi,
Does the new RTP release support ata/100 drives? I got burned
by a new dell I bought expressly to use with qnx that had an ata/100
drive instead of the ata/66 that was on my test dell system.In a more general vein, why aren’t important compatibility issues like
this noted on the qnx website? The ‘supported hardware’ laundry
list isn’t always sufficient to tell if a system will work with qnx or
not.
Could you add a list of known compatability 'gotcha’s?Thanks,
Arthur
Arthur wrote:
Igor,
You da man! I’m still confused though.
QNX RTP without the dma option will work with which dma modes?
i.e. ata/100 (ultra dma 5), ata/66 (ultra dma 4), ata/33 (ultra dma 2)
None. Not even in PIO modes. It will work in the ‘lowest common mode’ of
ATA protocol which I don’t even remember what it is, but performance
will be limited by approx 3Mb/sec. You can try using PIO modes (pass
‘pio’ option) but it does not help much.
QNX RTP with the dma option will work with which dma modes?
i.e. ata/100 (ultra dma 5), ata/66 (ultra dma 4), ata/33 (ultra dma 2)
DMA2 currently, and only on supported chipsets (and only when chipset is
programmed by BIOS into DMA2). Which means if you have newer motherboard
with modes higher than DMA2, it is probably unsupported and DMA won’t
work at all.
The most common chipset is probably Intel 82371A/B (aka PIIX4) and it
works. I also happen to know that SiS5513 works too, but there is no
full list of supported chipsets anywhere.
And for the QSSL guys, please put this kind of information on known
incompatabilites somewhere appropriate on your website. (Or if
I missed it, please put it somewhere more prominent, such as near the
supported hardware list.)
How many monkeys do you need before it will happen Kevin?
“Igor Kovalenko” <Igor.Kovalenko@motorola.com> wrote in message
news:3A760A63.7B6B6691@motorola.com…
Arthur wrote:
Igor,
You da man! I’m still confused though.
QNX RTP without the dma option will work with which dma modes?
i.e. ata/100 (ultra dma 5), ata/66 (ultra dma 4), ata/33 (ultra dma
2)
None. Not even in PIO modes. It will work in the ‘lowest common mode’ of
ATA protocol which I don’t even remember what it is, but performance
will be limited by approx 3Mb/sec. You can try using PIO modes (pass
‘pio’ option) but it does not help much.QNX RTP with the dma option will work with which dma modes?
i.e. ata/100 (ultra dma 5), ata/66 (ultra dma 4), ata/33 (ultra dma
2)
DMA2 currently, and only on supported chipsets (and only when chipset is
programmed by BIOS into DMA2). Which means if you have newer motherboard
with modes higher than DMA2, it is probably unsupported and DMA won’t
work at all.The most common chipset is probably Intel 82371A/B (aka PIIX4) and it
works. I also happen to know that SiS5513 works too, but there is no
full list of supported chipsets anywhere.And for the QSSL guys, please put this kind of information on known
incompatabilites somewhere appropriate on your website. (Or if
I missed it, please put it somewhere more prominent, such as near the
supported hardware list.)
How many monkeys do you need before it will happen Kevin?
You know better then this Igor. Kevin is not the one with the monkeys.
Why don’t you pester the one that makes the call instead
- igor
Because i already tried that.
So, I’m trying an indirect approach now 
Mario Charest wrote:
You know better then this Igor. Kevin is not the one with the monkeys.
Why don’t you pester the one that makes the call instead
\
- igor
“Igor Kovalenko” <Igor.Kovalenko@motorola.com> wrote in message
news:3A76E28C.82F3598A@motorola.com…
Because i already tried that.
Then I should have known better 
So, I’m trying an indirect approach now >
Mario Charest wrote:
You know better then this Igor. Kevin is not the one with the monkeys.
Why don’t you pester the one that makes the call instead
\
- igor