All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Matthew Wilcox <willy@debian.org>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [BK PATCH] PCI Express patches for 2.4.27-pre3
Date: Tue, 25 May 2004 14:24:13 +0100	[thread overview]
Message-ID: <20040525132413.GD29154@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040525130116.GA16852@devserv.devel.redhat.com>

On Tue, May 25, 2004 at 03:01:16PM +0200, Arjan van de Ven wrote:
> 
> On Tue, May 25, 2004 at 09:54:53AM -0300, Marcelo Tosatti wrote:
> > > > Marcelo, feel free to tell me otherwise if you do not want
> > > > this in the 2.4 tree. 
> > 
> > Is this code necessary for PCI-Express devices/busses to work properly?
> 
> afaik not. It's an enhancement to make config space access to them somewhat
> faster, but they just work using the existing method.

It also allows access to the top 3840 bytes of config space.  The *spec*
says you can't require access to that area for correct functioning of
the device, but we all know how much people love to follow specs.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-05-25 13:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 21:01 [BK PATCH] PCI Express patches for 2.4.27-pre3 Greg KH
2004-05-24 21:02 ` Greg KH
2004-05-24 21:02   ` Greg KH
2004-05-25  6:53 ` Arjan van de Ven
2004-05-25  8:00   ` Greg KH
2004-05-25 11:32     ` Matthew Wilcox
2004-05-25 12:54       ` Marcelo Tosatti
2004-05-25 13:01         ` Arjan van de Ven
2004-05-25 13:24           ` Matthew Wilcox [this message]
2004-05-25 14:41             ` Greg KH
2004-05-26  2:49               ` Jeff Garzik
2004-05-26  4:29                 ` Greg KH
2004-05-25 14:40         ` Greg KH
2004-05-25 16:59           ` Marcelo Tosatti
2004-05-25 17:05             ` Greg KH
     [not found] <1ZuS0-1b4-15@gated-at.bofh.it>
     [not found] ` <1ZuS3-1b4-35@gated-at.bofh.it>
2004-05-24 22:21   ` Andi Kleen
2004-05-24 22:40     ` Greg KH
     [not found] ` <1ZE52-8sy-15@gated-at.bofh.it>
     [not found]   ` <1ZFaF-10N-13@gated-at.bofh.it>
     [not found]     ` <1ZIrV-3xS-7@gated-at.bofh.it>
     [not found]       ` <1ZJHt-4At-33@gated-at.bofh.it>
2004-05-25 13:38         ` Andi Kleen
     [not found]         ` <1ZLpV-5YK-37@gated-at.bofh.it>
     [not found]           ` <1ZNBb-7QA-1@gated-at.bofh.it>
2004-05-25 17:14             ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-05-26  6:29 Durairaj, Sundarapandian
2004-05-26 13:48 ` Matthew Wilcox
2004-05-26 17:03 ` Greg KH
2004-05-26 17:30   ` Jeff Garzik

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=20040525132413.GD29154@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=arjanv@redhat.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=marcelo.tosatti@cyclades.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.