From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: davej@suse.de
Cc: Martin Mares <mj@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pdev_enable_device no longer used ?
Date: Mon, 11 Dec 2000 00:28:50 +0100 [thread overview]
Message-ID: <20001211002850.A14393@pcep-jamie.cern.ch> (raw)
In-Reply-To: <20001209160403.A28562@atrey.karlin.mff.cuni.cz> <Pine.LNX.4.21.0012091803270.571-100000@neo.local>
In-Reply-To: <Pine.LNX.4.21.0012091803270.571-100000@neo.local>; from davej@suse.de on Sat, Dec 09, 2000 at 06:11:08PM +0000
Here are a few more:
net/acenic.c: pci_write_config_byte(ap->pdev, PCI_CACHE_LINE_SIZE,
net/gmac.c: PCI_CACHE_LINE_SIZE, 8);
scsi/sym53c8xx.c: printk(NAME53C8XX ": PCI_CACHE_LINE_SIZE set to %d (fix-up).\n",
video/pm2fb.c: WR32(p->pci_config, PCI_CACHE_LINE_SIZE, 0xff00);
-- Jamie
davej@suse.de wrote:
> > > 1. Is there reason for the drivers to be setting this themselves
> > > to hardcoded values ?
> >
> > Definitely not unless the devices are buggy and need a work-around.
>
> Maybe that's the case. The culprits are mostly IDE interfaces. Andre ?
>
> drivers/ide/cmd64x.c: (void) pci_write_config_byte(dev,PCI_CACHE_LINE_SIZE, 0x10);
> drivers/ide/cs5530.c: pci_write_config_byte(cs5530_0,PCI_CACHE_LINE_SIZE, 0x04);
> drivers/ide/hpt366.c: pci_write_config_byte(dev,PCI_CACHE_LINE_SIZE, 0x08);
> drivers/ide/ns87415.c: (void) pci_write_config_byte(dev,PCI_CACHE_LINE_SIZE, 0x10);
>
> drivers/atm/eni.c: pci_write_config_byte(eni_dev->pci_dev,PCI_CACHE_LINE_SIZE, 0x10);
> drivers/media/video/planb.c: pci_write_config_byte (pdev,PCI_CACHE_LINE_SIZE, 0x8);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-11 0:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 11:30 davej
2000-12-09 11:38 ` Russell King
2000-12-09 12:15 ` Ivan Kokshaysky
2000-12-09 12:36 ` davej
2000-12-09 12:53 ` Alan Cox
2000-12-09 13:08 ` davej
2000-12-09 13:44 ` Ivan Kokshaysky
2000-12-09 14:26 ` Gérard Roudier
2000-12-09 17:48 ` Russell King
2000-12-09 20:57 ` Alan Cox
2000-12-09 15:04 ` Martin Mares
2000-12-09 18:11 ` davej
2000-12-10 23:28 ` Jamie Lokier [this message]
2000-12-11 0:34 ` davej
2000-12-11 19:40 ` Gérard Roudier
2000-12-12 2:43 ` Jes Sorensen
2000-12-11 19:20 ` Gérard Roudier
2000-12-11 20:55 ` Martin Mares
2000-12-11 20:49 ` Gérard Roudier
2000-12-11 21:48 ` David S. Miller
2000-12-11 21:30 ` Gérard Roudier
2000-12-11 22:21 ` David S. Miller
2000-12-11 22:07 ` Gérard Roudier
2000-12-11 23:03 ` David S. Miller
2000-12-12 19:17 ` Gérard Roudier
2000-12-12 20:14 ` David S. Miller
2000-12-12 20:28 ` Gérard Roudier
2000-12-12 22:39 ` David S. Miller
2000-12-11 23:16 ` Martin Mares
2000-12-12 18:56 ` Gérard Roudier
2000-12-12 12:21 ` Adrian Cox
2000-12-12 2:39 ` Jes Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001211002850.A14393@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®