On Tue, May 12, 2009 at 09:05:09PM -0600, Myles Watson wrote:
I actually couldn't find anything different in the file between how the registers were programmed. I didn't look for too long. I've since been told that the Broadcom chip we're talking about doesn't have AHCI, so I don't know... Except that FILO works with the board.
Samuel posted a log after patching SeaBIOS that had:
ATA controller 0 at 000001f0/000003f0 (dev 00000170 prog_if 00000080) ATA controller 1 at 00000170/00000370 (dev 00000170 prog_if 00000080) ATA controller 2 at 00001050/00001090 (dev 00000171 prog_if 0000008f) ATA controller 3 at 00001060/000010a0 (dev 00000171 prog_if 0000008f) powerup IDE floating powerup IDE floating ata_detect drive=0 sc=000000ff sn=000000ff dh=000000ff powerup IDE floating powerup IDE floating ata_detect drive=1 sc=000000ff sn=000000ff dh=000000ff powerup IDE floating powerup IDE floating ata_detect drive=2 sc=000000ff sn=000000ff dh=000000ff powerup IDE floating powerup IDE floating ata_detect drive=3 sc=000000ff sn=000000ff dh=000000ff powerup iobase=00001050 st=0000007f powerup iobase=00001050 st=0000007f ata_detect drive=4 sc=000000ff sn=000000ff dh=000000ff powerup iobase=00001050 st=0000007f powerup iobase=00001050 st=0000007f ata_detect drive=5 sc=000000ff sn=000000ff dh=000000ff powerup iobase=00001060 st=0000007f powerup iobase=00001060 st=0000007f ata_detect drive=6 sc=000000ff sn=000000ff dh=000000ff powerup iobase=00001060 st=0000007f powerup iobase=00001060 st=0000007f ata_detect drive=7 sc=000000ff sn=000000ff dh=000000ff
The above indicates that SeaBIOS found the HT1000, but that the ioport registers weren't responding to writes. (A 0xaa/0x55 pattern should have been seen instead of 0xff.) Filo has the same register presence check - so I'm not sure why filo doesn't have the same issue.
Too bad we didn't get it figured out before it got shipped to the data center. At least it worked out for him.
I thought someone else on the list had one of these machines. Oh well, maybe next time.
-Kevin