Skip to contentSkip to conversation

2.4.21-rc7 AMD64 dpt_i2o fails compile

DISCUSSION Andi Kleen 3 participants 6 messages Jun 5, 2003 – Jun 6, 2003 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 20030605010841.A29837@devserv.devel.redhat.com.suse.lists.linux.kernel

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 1054808477.15276.0.camel@dhcp22.swansea.linux.org.uk.suse.lists.linux.kernel

Andi Kleen

author
#4 lore raw
Quoted 2 lines · Alan Cox

Fixing up dpt_i2o for the new DMA stuff is a major job. Fixing it for 64bit cleanness even more so.

If the hardware/firmware supports 64bit pointers then at least AMD64 can work without the PCI DMA API.

64bit cleanness is needed however.

-Andi

#5 lore raw
Quoted 7 lines · Andi Kleen
Quoted 2 lines · Alan Cox

Fixing up dpt_i2o for the new DMA stuff is a major job. Fixing it for 64bit cleanness even more so.

If the hardware/firmware supports 64bit pointers then at least AMD64 can work without the PCI DMA API.

32bit all around as far I as I can tell

author
#6 lore raw
Quoted 10 lines · Alan Cox
Quoted 7 lines · Andi Kleen
Quoted 2 lines · Alan Cox

Fixing up dpt_i2o for the new DMA stuff is a major job. Fixing it for 64bit cleanness even more so.

If the hardware/firmware supports 64bit pointers then at least AMD64 can work without the PCI DMA API.

32bit all around as far I as I can tell

Then fixing it to use the DMA code is best - you can use 32bit pointers fine then. Just the code in the driver itself needs to be able to tolerate a 64bit host.

-Andi

#7 lore raw
In reply to Alan Cox
Quoted 11 lines · Alan Cox
Quoted 3 lines · Andi Kleen
Quoted 1 line · Alan Cox

Fixing up dpt_i2o for the new DMA stuff is a major job. Fixing it

for

Quoted 4 lines
Quoted 1 line

64bit cleanness even more so.

If the hardware/firmware supports 64bit pointers then at least AMD64 can work without the PCI DMA API.

32bit all around as far I as I can tell

http://www.adaptec.com/worldwide/support/suppdetail.html?cat=%2fProduct%2fASR-2110S&prodkey=ASR-2110S
http://www.adaptec.com/worldwide/support/techspecs.html?prodkey=ASR-2110S&cat=%2fProduct%2fASR-2110S
Adaptec SCSI RAID 2110S claims to be a "64-bit/66MHz PCI-to-SCSI RAID card". The physical card is longer than normal 32-bit PCI cards with more pins that fit into a "64-bit PCI slot". Are Adaptec's claims of 64-bit hardware false?

32-bit Red Hat 9 with dpt_i2o is working great with Opteron and this card, so I have a safe option to fallback on if we can't fix the 64-bit operation.

Warren Togami
[email protected]

author
#8 lore raw
Quoted 4 lines

Adaptec SCSI RAID 2110S claims to be a "64-bit/66MHz PCI-to-SCSI RAID card". The physical card is longer than normal 32-bit PCI cards with more pins that fit into a "64-bit PCI slot". Are Adaptec's claims of 64-bit hardware false?

They are refering to 64bit PCI. That is not the same as support for 64bit operating systems. An 64bit OS can also support non 64bit hardware, but it needs proper support in the driver which the current linux driver doesn't have.

You will have to wait until somebody fixes the driver.

-Andi

#9 lore raw
In reply to Warren Togami
Quoted 6 lines · Warren Togami

http://www.adaptec.com/worldwide/support/suppdetail.html?cat=%2fProduct%2fASR-2110S&prodkey=ASR-2110S
http://www.adaptec.com/worldwide/support/techspecs.html?prodkey=ASR-2110S&cat=%2fProduct%2fASR-2110S
Adaptec SCSI RAID 2110S claims to be a "64-bit/66MHz PCI-to-SCSI RAID card". The physical card is longer than normal 32-bit PCI cards with more pins that fit into a "64-bit PCI slot". Are Adaptec's claims of 64-bit hardware false?

64bit bus isnt the same thing as 64bit capable or 64bit safe. The current driver will need some work for the latter