Hello. (2013/07/04 1:35), Erik Fair wrote: > It would be very helpful to document in bge(4) just which chips support jumbo > frames (and how big).
I agree with you..... and I knew bge.4 is very obsolete..... :-( > Heck, it would be even more helpful if that was a capability that ifconfig(8) > could report because drivers declare it. Yes, I think ifconfig should report the hard limit of MTU, too. http://mail-index.netbsd.org/tech-kern/2013/07/03/msg015330.html OpenBSD has SIOCGIFHARDMTU and ifconfig print the limit using with the ioctl. It could be implemented using proplib, but I think ioctl is better than proplib to be consistent with SIOC[GS]MTU. > Erik <f...@netbsd.org> > > On Jul 2, 2013, at 22:49 , SAITOH Masanobu <msai...@netbsd.org> wrote: > >> Module Name: src >> Committed By: msaitoh >> Date: Wed Jul 3 05:49:36 UTC 2013 >> >> Modified Files: >> src/sys/dev/pci: if_bge.c >> >> Log Message: >> Add BGE_JUMBO_CAPABLE flag to some chips. Before this commit, >> the following chips support the jumbo frame function: >> >> 5700 >> 5701 >> 5702 >> 5703 >> 5704 >> >> With this commit, the following chip support it, too: >> >> 5714 >> 5780 >> 5717 >> 5718 >> 5719 (exclude rev. A0) >> 5720 >> 57765 >> 57766 >> >> >> To generate a diff of this commit: >> cvs rdiff -u -r1.253 -r1.254 src/sys/dev/pci/if_bge.c >> >> Please note that diffs are not public domain; they are subject to the >> copyright notices on the relevant files. >> > -- ----------------------------------------------- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org) * 英語 - 自動検出 * 英語 * 日本語 * 英語 * 日本語 <javascript:void(0);> <#>