On Fri, 2007-03-23 at 17:28 +0100, thomas schorpp wrote: > > i agree for this to be a 32bit dma busmaster chip, > > since pci_resource_flags and lspci say 64bit mem resource type > > > > aic7xxx: pci_resource_start fffff000 *maddr 20000 mem64 4 > > > > we've a bug in the x86_64 linux pci config, BIOS is ok, the hardware > > worked fine in a winxp_x64 test setup a few months ago. > > > > will ask LKML. > > > > y > > tom > > sorry, wrong according to http://download.adaptec.com/pdfs/aic7892.pdf. > > "66 MHz, 64-bit, PCI interface that > supports zero wait-state memory; > also operates on 33 MHz, 32-bit > PCI busses" > > this chip is capable of 64bit addressing, as pci_resource_nnnn (checking this) on x86_64 platform > and lspci on x86_64 *and* AMDK7 configured kernels reports, even on PCI/32, right? > or is it impossible to do multiplexed 64bit mem addressing on PCI/32? It can only do 37 bit addressing ... only the aic79xx can do the full 64 bits, so I suspect it should never get a 64 bit BAR, since it wouldn't be able to decode the full 32 bits. I can fix the mmio check not to hang, but the card won't actually work mmio until whatever's assigning the BAR above 32 bits is fixed (that could either be a kernel PCI bug or a BIOS bug). > Why are the driver structure address members 32bits wide types if therere PCI/64 card > models with this chips as listet in aic7xxx.txt kernel doc and stated in aic7892.pdf? > I'll adapt the respective driver structures and function args now to 64bit and see what happens... > > can adaptec.inc pls comment? since the aha19160 card is still in production state, > i assume they want to have a linux x86_64 dma capable driver. so far it is not, > or can other users having this card pls confirm my pci system broken? James - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
