> As a more general question, what would be the right medium to
> document such device errata as it relates to a driver? Is the
> man page the best location or would it be better to add a
> table near the top of the driver file which summarizes the
> bugs and the workarounds? Is there a general
David Christensen wrote:
MSI is broken on this device (actually all PCI/PCI-X devices in the
57XX family). The interrupt will be asserted as expected
but masking
the interrupt does not work. For those newer 1Gb PCIe
devices that do
work correctly with MSI, only a single message is actually
> > MSI is broken on this device (actually all PCI/PCI-X devices in the
> > 57XX family). The interrupt will be asserted as expected
> but masking
> > the interrupt does not work. For those newer 1Gb PCIe
> devices that do
> > work correctly with MSI, only a single message is actually
> sup
David Christensen wrote:
Can the bge driver use more than one MSI message? If
possible, what the advantage of this on a SMP system (better
CPU distribution on interrupts?)?
[...]
--
MSI is broken on this device (actually all PCI/PCI-X devices
in the 57XX family). The interrupt will be a
> Can the bge driver use more than one MSI message? If
> possible, what the advantage of this on a SMP system (better
> CPU distribution on interrupts?)?
>
> I have an Broadcom BCM5703X, with 8 MSI messages:
> --
> b...@pci0:1:2:0:class=0x02 card=0x00cb0e11
> chip=0x16a714e4 rev=0x02
>
On Tue, Dec 01, 2009 at 03:31:37PM -0200, Rafael Ganascim wrote:
> Hi list,
>
> Can the bge driver use more than one MSI message? If possible, what the
> advantage of this on a SMP system (better CPU distribution on interrupts?)?
>
> I have an Broadcom BCM5703X, with 8 MSI messages:
> --
> b...@p
