Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 4 Mar 2002 13:47:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 4 Mar 2002 13:47:46 -0500 Received: from gordo.y12.doe.gov ([134.167.141.46]:60899 "EHLO gordo.y12.doe.gov") by vger.kernel.org with ESMTP id ; Mon, 4 Mar 2002 13:45:25 -0500 Message-ID: <3C83C0B8.659F1AE@y12.doe.gov> Date: Mon, 04 Mar 2002 13:45:12 -0500 From: David Dillow Organization: BWXT Y-12/ACT/UT Subcon/What a mess! X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.9-13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Garzik CC: linux-kernel@vger.kernel.org Subject: Re: [PATCH] IBM Lanstreamer bugfixes (round 3) In-Reply-To: <3C83A925.F93BF448@mandrakesoft.com> <3C83AE6B.9B5DE85F@y12.doe.gov> <3C83B2E7.B5EB0FB5@mandrakesoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jeff Garzik wrote: > > David Dillow wrote: > > > > Jeff Garzik wrote: > > > Set cache line size just like drivers/net/acenic.c does, and enable > > > memory-write-invalidate... > > > > Does this mean the setup pci_enable_device() does on the cache line size > > is not sufficient? > > pci_enable_device doesn't touch the PCI_COMMAND_INVALIDATE bit at all... Right, I was talking more about the cache line size... is it sufficient for that? As for PCI_COMMAND_INVALIDATE, what does that do for me; my PCI spec isn't handy.... > > I ask, because I've been relying on it for a driver I'm working on; > > should I be setting this as acenic does? It would seem that this is > > something many drivers would need to do... > > Yes, acenic is the code to copy, for setting that up. INVALIDATE, or cache line size? Thanks, Dave Dillow dillowd@y12.doe.gov - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/