Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Dec 2009 14:22:20 -0800
From:      "David Christensen" <davidch@broadcom.com>
To:        "Julian Elischer" <julian@elischer.org>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Rafael Ganascim <rganascim@gmail.com>
Subject:   RE: bge driver and MSI
Message-ID:  <5D267A3F22FD854F8F48B3D2B52381933A31693938@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <4B1DB10A.5060005@elischer.org>
References:  <2f7feda40912010931i3cf7d90dmb2a8d08ecd40589f@mail.gmail.com> <5D267A3F22FD854F8F48B3D2B52381933A3169363C@IRVEXCHCCR01.corp.ad.broadcom.com> <4B1DB10A.5060005@elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> > MSI is broken on this device (actually all PCI/PCI-X devices in the=20
> > 57XX family).  The interrupt will be asserted as expected=20
> but masking=20
> > the interrupt does not work.  For those newer 1Gb PCIe=20
> devices that do=20
> > work correctly with MSI, only a single message is actually=20
> supported.
>=20
> Might be a good thing of someone would work up a man page=20
> paragraph to this effect.
>=20

As a more general question, what would be the right medium to
document such device errata as it relates to a driver?  Is the=20
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 consensus?

Dave=




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D267A3F22FD854F8F48B3D2B52381933A31693938>