mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: groudier@club-internet.fr (Gérard Roudier)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	davej@suse.de, ink@jurassic.park.msu.ru (Ivan Kokshaysky),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: pdev_enable_device no longer used ?
Date: Sat, 9 Dec 2000 17:48:36 +0000 (GMT)	[thread overview]
Message-ID: <200012091748.eB9HmaO29722@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10012091500230.1058-100000@linux.local> from "Gérard Roudier" at Dec 09, 2000 03:26:43 PM

=?ISO-8859-1?Q?G=E9rard_Roudier?= writes:
> As a result, in my opinion:
> 
> - A device that requires some non zero cache line size value lower than
> the right value for a given system and that actually use MWIs must not be
> supported on that system, unless we know that the bridge does alias MWI to
> MW. (If such a device can be configured for not using MWI, any value for 
> the PCI cache line size will not break).
> 
> - A driver that blindly shoe-horns some value for the cache-line size must
> be fixed. Basically, it should not change the value if it is not zero and,
> at least, warn user if it has changed the value because it was zero.
> 
> What are the strong reasons that let some POST softwares not fill properly
> the cache line size of PCI devices ?

Erm, stupid observation coming up.  Isn't this what the architecture-
specific 'pcibios_set_master' function is for?  To do any architecture
specific fiddling with the device.

Surely, writing to the cache line size is not something that a driver
should be doing, but something that the architecture specific code
should be doing.  Likewise, fiddling with latency timers without good
reason (eg, broken latency timers) surely is asking for problems.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         Russell King        rmk@arm.linux.org.uk      --- ---
  | | | | http://www.arm.linux.org.uk/personal/aboutme.html   /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |
-
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/

  reply	other threads:[~2000-12-09 18:21 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 [this message]
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
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=200012091748.eB9HmaO29722@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@suse.de \
    --cc=groudier@club-internet.fr \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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®