From owner-freebsd-ppc@FreeBSD.ORG Mon Oct 27 19:31:26 2003 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F11C16A4CF for ; Mon, 27 Oct 2003 19:31:26 -0800 (PST) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC86443F3F for ; Mon, 27 Oct 2003 19:31:25 -0800 (PST) (envelope-from resistor@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h9S3VPT7011676 for ; Mon, 27 Oct 2003 19:31:25 -0800 (PST) Received: from [192.168.0.9] (unpc-784-21.pc.ts2athga.ath.ga.charter.com [66.190.87.69]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 3.0) with ESMTP id h9S3VOCQ024493 for ; Mon, 27 Oct 2003 19:31:25 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v606) In-Reply-To: <200310280325.ABX08857@dommail.onthenet.com.au> References: <200310280325.ABX08857@dommail.onthenet.com.au> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <349AD08C-08F7-11D8-A5E5-000A279431A2@mac.com> Content-Transfer-Encoding: 7bit From: Owen Anderson Date: Mon, 27 Oct 2003 22:31:23 -0500 To: freebsd-ppc@freebsd.org X-Mailer: Apple Mail (2.606) Subject: Re: New tarball available X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2003 03:31:26 -0000 Sounds like a plan. I'd do just that if I had the faintest idea how. What files do I need to go poking around in, and what tools do I need to use for it? Owen Anderson On Oct 27, 2003, at 10:25 PM, peterg@ptree32.com.au wrote: >>> I think the only drivers compiled in are the fxp and gem. >>> I'm assuming this isn't the on-board ethernet ? >> >> Nope. It's the built-in Gigabit ethernet on my PowerMac > G4/400. It's >> registered under OS X 10.3 as en0 if that helps at all. > > OK, I'm pretty sure this is a GEM, but with a different > PCI ID than what's in the kernel. I noticed that NetBSD's > if_gm.c recognizes the GEM3, which is what you might have. > > If you're keen, you could binary-patch the kernel > to recognize the variant. Simply locate the GEM2 device > ID, 0x0024106b and change it to 0x0032106b. > > later, > > Peter. > >