Re: Enabling MSI on the Asus Vintage AH-1

On Sat, Dec 23, 2006 at 09:54:58PM +0000, Bruce M. Simpson wrote:
 > Hi,
 > 
 > It looks like MSI was detected, but not used by the msk(4) driver on the 
 > Asus Vintage AH-1.
 > 
 > This is a uniprocessor Athlon64 system. The PCI bridges on this system 
 > aren't in the MSI blacklist, however, there are several odd messages 
 > regarding a non-default MSI window. Looking at the code suggests it 
 > expects to see the MSI window at 0xfee00000.
 > 
 > BTW: This system's on-board SATA controller stopped working with 6.2-RC, 
 > so I'm using an add-on PCI-e card for SATA to connect the root disk.
 > 
 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
 > pci0: <ACPI PCI bus> on pcib0
 > pci0: physical bus=0

[...]

 > pcib2: <ACPI PCI-PCI bridge> at device 6.0 on pci0
 > pcib2:   secondary bus     2
 > pcib2:   subordinate bus   2
 > pcib2:   I/O decode        0xc000-0xcfff
 > pcib2:   memory decode     0xfe400000-0xfe4fffff
 > pcib2:   no prefetched decode
 > pci2: <ACPI PCI bus> on pcib2
 > pci2: physical bus=2
 > found-> vendor=0x11ab, dev=0x4362, revid=0x19
 >        bus=2, slot=0, func=0
 >        class=02-00-00, hdrtype=0x00, mfdev=0
 >        cmdreg=0x0107, statreg=0x4010, cachelnsz=16 (dwords)
 >        lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
 >        intpin=a, irq=5
 >        powerspec 2  supports D0 D1 D2 D3  current D0
 >        VPD Ident: Marvell Yukon 88E8053 Gigabit Ethernet Controller
 >        PN: Yukon 88E8053
 >        EC: Rev. 1.9
 >        MN: Marvell
 >        SN: AbCdEfG32a88a
 >        CP: id 1, BAR16, off 0x3cc
 >        RV: 0x24
 >        MSI supports 2 messages, 64 bit
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I think Yukon II supports one MSI message. But all systems I know
reported that it supports two MSI messages. This is main reason why
msk(4) doesn't use MSI ATM. I don't know why Yukon II claims to
support two MSI messages.(for dual port MAC configuraiton?)

You can force to use MSI by assigning 'msic = 1' before calling
pci_alloc_msi(9) in mskc_attach(). However it wouldn't work if you
reload the msk(4) again. Other than that it works well with MSI.

 >        map[10]: type 1, range 64, base 0xfe4fc000, size 14, enabled
 > pcib2: requested memory range 0xfe4fc000-0xfe4fffff: good
 >        map[18]: type 4, range 32, base 0xc800, size  8, enabled
 > pcib2: requested I/O range 0xc800-0xc8ff: in range
 > pcib2: matched entry for 2.0.INTA
 > pcib2: slot 0 INTA hardwired to IRQ 18
 > mskc0: <Marvell Yukon 88E8053 Gigabit Ethernet> port 0xc800-0xc8ff mem 
 > 0xfe4fc000-0xfe4fffff irq 18 at device 0.0 on pci2
 > mskc0: MSI count : 2
 > mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfe4fc000
 > mskc0: RAM buffer size : 48KB
 > mskc0: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff)
 > mskc0: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff)
 > msk0: <Marvell Technology Group Ltd. Yukon EC Id 0xb6 Rev 0x02> on mskc0
 > msk0: bpf attached
 > msk0: Ethernet address: 00:15:f2:32:a8:8a
 > miibus0: <MII bus> on msk0
 > e1000phy0: <Marvell 88E1111 Gigabit PHY> on miibus0
 > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 
 > 1000baseTX-FDX, auto
 > ioapic0: routing intpin 18 (PCI IRQ 18) to vector 49
 > mskc0: [MPSAFE]
 > mskc0: [FAST]
 > 

-- 
Regards,
Pyun YongHyeon