From owner-freebsd-hardware Tue Apr 9 17:04:41 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA01224 for hardware-outgoing; Tue, 9 Apr 1996 17:04:41 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA01219 for ; Tue, 9 Apr 1996 17:04:38 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u6nUe-000wuTC; Tue, 9 Apr 96 17:10 PDT Received: from cc:Mail by ccgate.infoworld.com id AA829094604; Tue, 09 Apr 96 15:41:49 PST Date: Tue, 09 Apr 96 15:41:49 PST From: "Brett Glass" Message-Id: <9603098290.AA829094604@ccgate.infoworld.com> To: davidg@Root.COM Cc: freebsd-hardware@freebsd.org Subject: Re: Artisoft AE-3 Ethernet card: How to use large buffer? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You can't without 1) knowing how the memory is laid out (probably > starts at 0 and goes for 64K), and 2) modifying the driver to deal with > it. Can there be more than 64K of memory on the NS chip? > If I make an assumption about the memory layout, I could make the > changes in a few minutes. This would be great! > You're the first person to ever complain that I didn't have sufficient > comments in my code or that it was difficult to read. ...although it has > been hacked on by a fair number of people since I wrote it (the GWETHER > stuff, for example), and may have degraded somewhat. Multiple authors always make code more difficult to read, because they introduce inconsistencies in style. I'm certainly not pointing a finger at anyone, because I don't know the code's history. > That only works for shared-memory type cards of which the NE2000 is not. > As for telling you how to set the amount of RAM, there are hints in the > manual page for the driver, too: "man 4 ed". It looks (again, correct me if I'm wrong) as if the code once had a provision for this, but the lines are inside an #if 0...#endif. A comment in the vicinity says "probably not needed - NE boards come only two ways." > *If* the driver was modified to deal specially with this case, you > would set the memory size via the "iosiz " option in the kernel config > file device line. There's an example at the top of the manual page. For > "-c", you would say "iosiz ed0 65536". This would be excellent. > Now the question is, after having been insulted about my code, if I want > to actually help you make the changes to the driver to support your extra > memory. Hmmm. No insult intended. Much of the confusion appears to have been caused by code you did not write. In any event, if you can help, I'd gladly contribute as well. --Brett P.S. -- This board, like most has no EPROM. Is it worthwhile to reclaim the memory space reserved for it?