Higpoint ide

Hi all,

I have following problem with the ide driver, trying to use our cpci
harddisk card.

This does not work:

devb-eide eide vid=0x1103,did=0x0004 blk automount=hd0t79:/hd

No eide interfaces found

This works fine:

devb-eide eide ioport=0xe8800080:0xe8800088,irq=29 blk

automount=hd0t79:/hd
Path=0 - Generic IDE
target=0 lun=0 Direct-Access(0) - SAMSUNG MP0402H Rev: UC10

Ok, I could use the enumerator, to start the driver, but I am wondering,
why the 1st command-line does not work.
Any ideas?

Best regards
Michael

pci -v:
Class = Mass Storage (Unknown)
Vendor ID = 1103h, HighPoint Technologies Inc.
Device ID = 4h, HPT366/368/370/372 UDMA66/100 EIDE Controller
PCI index = 0h
Class Codes = 018000h
Revision ID = 4h
Bus number = 0
Device number = 20
Function num = 0
Status Reg = 230h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 8h un-cacheable
CPU Bus Master Translation = 80000000h
PCI IO Address = 800080h length 8 enabled
CPU IO Address = e8800080h
PCI IO Address = 800088h length 4 enabled
CPU IO Address = e8800088h
PCI IO Address = 800090h length 8 enabled
CPU IO Address = e8800090h
PCI IO Address = 800098h length 4 enabled
CPU IO Address = e8800098h
PCI IO Address = 800100h length 256 enabled
CPU IO Address = e8800100h
Subsystem Vendor ID = 1103h
Subsystem ID = 4h
PCI Expansion ROM = 800100h length 131072 disabled
CPU Expansion ROM = 0h
Max Lat = 8ns
Min Gnt = 8ns
PCI Int Pin = INT A
Interrupt line = 29

Michael Tasche <michael.tasche@esd-electronics.com> wrote:

Hi all,

I have following problem with the ide driver, trying to use our cpci
harddisk card.

This does not work:

devb-eide eide vid=0x1103,did=0x0004 blk automount=hd0t79:/hd

No eide interfaces found

This works fine:

devb-eide eide ioport=0xe8800080:0xe8800088,irq=29 blk

automount=hd0t79:/hd
Path=0 - Generic IDE
target=0 lun=0 Direct-Access(0) - SAMSUNG MP0402H Rev: UC10

Ok, I could use the enumerator, to start the driver, but I am wondering,
why the 1st command-line does not work.
Any ideas?

The pci output seems to indicate that the system isn’t x86? Unfortunately
only the x86 version of devb-eide has native support for the HPT chipset.
What platform and OS version are you using?

Kevin Chiles schrieb:

Michael Tasche <> michael.tasche@esd-electronics.com> > wrote:

Hi all,


I have following problem with the ide driver, trying to use our cpci
harddisk card.


This does not work:

devb-eide eide vid=0x1103,did=0x0004 blk automount=hd0t79:/hd

No eide interfaces found



This works fine:

devb-eide eide ioport=0xe8800080:0xe8800088,irq=29 blk

automount=hd0t79:/hd
Path=0 - Generic IDE
target=0 lun=0 Direct-Access(0) - SAMSUNG MP0402H Rev: UC10



Ok, I could use the enumerator, to start the driver, but I am wondering,
why the 1st command-line does not work.
Any ideas?


The pci output seems to indicate that the system isn’t x86? Unfortunately
only the x86 version of devb-eide has native support for the HPT chipset.
What platform and OS version are you using?

I use QNX 6.2.1 PPC.
I have just looked in the hardware support section.
You are right, only x86 seems to be supported.
Well, it seems to work fine, if I specify the io’s and irq directly.
Do you think, it could be dangerous to use the driver?

-Michael

Michael Tasche <michael.tasche@esd-electronics.com> wrote:

Kevin Chiles schrieb:
Michael Tasche <> michael.tasche@esd-electronics.com> > wrote:

Hi all,


I have following problem with the ide driver, trying to use our cpci
harddisk card.


This does not work:

devb-eide eide vid=0x1103,did=0x0004 blk automount=hd0t79:/hd

No eide interfaces found



This works fine:

devb-eide eide ioport=0xe8800080:0xe8800088,irq=29 blk

automount=hd0t79:/hd
Path=0 - Generic IDE
target=0 lun=0 Direct-Access(0) - SAMSUNG MP0402H Rev: UC10



Ok, I could use the enumerator, to start the driver, but I am wondering,
why the 1st command-line does not work.
Any ideas?


The pci output seems to indicate that the system isn’t x86? Unfortunately
only the x86 version of devb-eide has native support for the HPT chipset.
What platform and OS version are you using?

I use QNX 6.2.1 PPC.
I have just looked in the hardware support section.
You are right, only x86 seems to be supported.
Well, it seems to work fine, if I specify the io’s and irq directly.
Do you think, it could be dangerous to use the driver?

There shouldn’t be any problems with the driver as long as it doesn’t share
an interrupt and the boot monitor has performed basic initialization of the
chip. Also, since the driver will be running in compatibility mode you will
only be able to use one of the channels (doesn’t support shared interrupts).

Kevin Chiles schrieb:

Michael Tasche <> michael.tasche@esd-electronics.com> > wrote:

Kevin Chiles schrieb:

Michael Tasche <> michael.tasche@esd-electronics.com> > wrote:


Hi all,


I have following problem with the ide driver, trying to use our cpci
harddisk card.


This does not work:

devb-eide eide vid=0x1103,did=0x0004 blk automount=hd0t79:/hd

No eide interfaces found



This works fine:

devb-eide eide ioport=0xe8800080:0xe8800088,irq=29 blk

automount=hd0t79:/hd
Path=0 - Generic IDE
target=0 lun=0 Direct-Access(0) - SAMSUNG MP0402H Rev: UC10



Ok, I could use the enumerator, to start the driver, but I am wondering,
why the 1st command-line does not work.
Any ideas?


The pci output seems to indicate that the system isn’t x86? Unfortunately
only the x86 version of devb-eide has native support for the HPT chipset.
What platform and OS version are you using?


I use QNX 6.2.1 PPC.
I have just looked in the hardware support section.
You are right, only x86 seems to be supported.
Well, it seems to work fine, if I specify the io’s and irq directly.
Do you think, it could be dangerous to use the driver?


There shouldn’t be any problems with the driver as long as it doesn’t share
an interrupt and the boot monitor has performed basic initialization of the
chip. Also, since the driver will be running in compatibility mode you will
only be able to use one of the channels (doesn’t support shared interrupts).
Well, I am bit curious.

Why is interrupt-sharing possible on x86 and not on ppc ?
What means “running in compatibility mode” for the devb-eide driver ?