Date: Fri, 12 May 1995 10:44:19 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: seki@sysrap.cs.fujitsu.co.jp (Masahiro SEKIGUCHI) Cc: FreeBSD-Hackers@FreeBSD.org Subject: Re: Questions/comments on ed driver Message-ID: <199505121744.KAA01158@gndrsh.aac.dev.com> In-Reply-To: <9505121027.AA23423@seki.sysrap.cs.fujitsu.co.jp> from "Masahiro SEKIGUCHI" at May 12, 95 07:27:46 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > I examined the ed driver (of 950412 SNAP.) I found some (essentially > 2) strangeness in it. I'm not sure I found bugs or just > misunderstood. > > It is appreciated if you hackers give me comments. > > 1. If_ed.c defines ETHER_MAX be 1518 and ETHER_MIN 64. The length > includes 4 bytes for CRC. However, it looks like the program compares > them against packet lengths *without* CRC. Probably a bug, David will have to decide that. > 2. When put into 16 bit operation (isa16bit is on), if_ed.c turns the > interface in 16 bit mode just before data transfer, and then back in 8 > bit mode everytime. The comment says it makes DOS reboot process > happy, but, if so, why cannot the back-in-8-bit process be done only > in kdc_shutdown() hook? What happens if you panic while the system is running and the board is in 16 bit mode? The system would fail to reboot :-(. The problem is that on some machines, if you leave the board in 16-bit mode, will hang during the BIOS boot. I think the comment should be correted to say that, or both BIOS/DOS. This one is not a bug. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505121744.KAA01158>