From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Greg KH <greg@kroah.com>
Cc: Matthew Wilcox <willy@debian.org>,
Arjan van de Ven <arjanv@redhat.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 13:59:04 -0300 [thread overview]
Message-ID: <20040525165904.GF3385@logos.cnet> (raw)
In-Reply-To: <20040525144055.GA7252@kroah.com>
On Tue, May 25, 2004 at 07:40:56AM -0700, Greg KH wrote:
> On Tue, May 25, 2004 at 09:54:53AM -0300, Marcelo Tosatti wrote:
> >
> > Hi kernel fellows,
> >
> > On Tue, May 25, 2004 at 12:32:31PM +0100, Matthew Wilcox wrote:
> > > On Tue, May 25, 2004 at 01:00:06AM -0700, Greg KH wrote:
> > > > > how does this mesh with the "2.4 is now feature frozen"?
> > > >
> > > > As the major chunk of ACPI support just got added to the tree, and the
> > > > only reason that went in was for this patch, I assumed that it was
> > > > acceptable.
> >
> > major? the MMConfig support is minimal as I can see?
>
> It isn't that big of a patch, but it is make to core PCI code.
>
> > > > 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?
>
> Not that I can tell, the main point is accessing the extended config
> space, and speeding up the access to the device to its natural speed.
>
> > > I assume it was added because Len tries to keep ACPI in 2.4 and 2.6 as
> > > close to identical as possible. It certainly doesn't hurt anyone to add
> > > the ACPI functionality without the MMConfig support.
> >
> > I've humbly asked Len to stop doing big updates whenever possible on the
> > v2.4 ACPI code, and do bugfixes only instead. Is that a pain in the ass for you, Len?
> >
> > I asked that because it is common to see new bugs introduced by an ACPI update,
> > and you know that more than I do.
>
> Yes, I know that quite well :)
>
> So, because of this, you are saying that we should not apply these
> patches at this time?
Yeap, I would prefer not to apply them at this time. For one, Arjan told
me privately it can break XFree86 which accesses the PCI config space directly.
Right?
> If so, that's fine with me, as now any distro that wants to add this to
> their 2.4 kernel can, as the patches are public.
Yeap.
> > PS: Greg, about the PCI-Express hotplug drivers, I assume they are independant
> > on any of this?
>
> Yes, that is independant of these changes (that is required as there is
> no other way to control the pci hotplug controller of those systems,
> except with the driver I had submitted in the past to you.).
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2004-05-25 16:57 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
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 [this message]
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=20040525165904.GF3385@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=arjanv@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=willy@debian.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