On 2014/09/14 20:01, Jérémie Courrèges-Anglas wrote: > Brad Smith <b...@comstyle.com> writes: > > > On 14/09/14 1:29 PM, Jérémie Courrèges-Anglas wrote: > >> Brad Smith <b...@cvs.openbsd.org> writes: > >> > >>> CVSROOT: /cvs > >>> Module name: src > >>> Changes by: b...@cvs.openbsd.org 2014/09/13 18:17:09 > >>> > >>> Modified files: > >>> share/man/man4 : bge.4 bnx.4 em.4 ixgb.4 lge.4 msk.4 nge.4 re.4 > >>> sk.4 ti.4 vge.4 > >>> > >>> Log message: > >>> - Don't capitalize jumbo. > >>> - Don't try to keep track of jumbo frame sizes in the pages. Users can > >>> use `ifconfig hwfeatures' to determine what the hardware supports. > >> > >> This means that one willing to buy hw can't just look at the manpage to > >> find a nic with appropriate max jumbo size. > > > > There were enough of the pages that didn't mention the particular size > > supported anyway. > > Yes, I saw that. But is this the right move? > > > The man pages IMO are the wrong place to look for that > > information. > > What's the appropriate place, if not manpages?
IMHO, the spec sheet for the NIC / chip. For "off-brand" NICs the manpages aren't really going to help anyway as they're liable to change chip (or at least revision) at short notice, and for any "proper" hardware that is exactly the sort of information that appears in spec sheets. > I don't expect lambda > users to jump into /sys/dev, and I wouldn't consider it convenient > personnally. I don't think the driver manuals can sensibly go into enough detail in many cases, with some NICs there are differences between revisions, some drivers cover a huge range of adapters, etc.
