On Thu, 2005-03-31 at 14:03 -0800, Rajesh Shah wrote:
> Does this patch help?
YES! I can now power down the slot, see it gone from pci list, reenable
it, etc. Awesome. Thank you.
[EMAIL PROTECTED] ~]# lspci -s 08:00
08:00.0 Ethernet controller: Intel Corp.: Unknown device 105f (rev 03)
On Thu, 2005-03-31 at 14:03 -0800, Rajesh Shah wrote:
Does this patch help?
YES! I can now power down the slot, see it gone from pci list, reenable
it, etc. Awesome. Thank you.
[EMAIL PROTECTED] ~]# lspci -s 08:00
08:00.0 Ethernet controller: Intel Corp.: Unknown device 105f (rev 03)
08:00.1
On Wed, Mar 23, 2005 at 03:03:16PM -0800, Tom Duffy wrote:
>
> I have updated to Wilcox's rewrite, Rajesh's stuff, and Dely's latest
> patch. Still seeing these:
>
> [EMAIL PROTECTED] ~]# modprobe acpiphp
> acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> acpiphp: Slot [4] registered
On Mon, 2005-03-21 at 13:27, Greg KH wrote:
> On Mon, Mar 21, 2005 at 10:04:57AM -0800, Rajesh Shah wrote:
> > > - Are you wanting the acpi specific patches to go into the
> tree
> > > through the acpi developers? How about the ia64 specific
> > > patches?
> >
> > I honestly don't
On Mon, 2005-03-21 at 13:27, Greg KH wrote:
On Mon, Mar 21, 2005 at 10:04:57AM -0800, Rajesh Shah wrote:
- Are you wanting the acpi specific patches to go into the
tree
through the acpi developers? How about the ia64 specific
patches?
I honestly don't know what the
On Wed, Mar 23, 2005 at 03:03:16PM -0800, Tom Duffy wrote:
I have updated to Wilcox's rewrite, Rajesh's stuff, and Dely's latest
patch. Still seeing these:
[EMAIL PROTECTED] ~]# modprobe acpiphp
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
acpiphp: Slot [4] registered
On Tue, 2005-03-22 at 19:13 -0800, Dely Sy wrote:
> I just did a test of Rajesh's latest patch on 2.6.11.5 with
> Wilcox's acpiphp rewrite and the following patch. Hot-plug of
> PCI Express card worked fine on my i386 system
I have updated to Wilcox's rewrite, Rajesh's stuff, and Dely's latest
On Tue, 2005-03-22 at 19:13 -0800, Dely Sy wrote:
I just did a test of Rajesh's latest patch on 2.6.11.5 with
Wilcox's acpiphp rewrite and the following patch. Hot-plug of
PCI Express card worked fine on my i386 system
I have updated to Wilcox's rewrite, Rajesh's stuff, and Dely's latest
On Monday, March 21, 2005 5:07 PM, Dely Sy wrote:
> On Monday, March 21, 2005 10:05 AM, Rajesh Shah wrote:
> > On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
> > > - Does this break the i386 acpiphp functionality?
> > Dely Sy had tested hotplug with an earlier version of my patches
>
On Monday, March 21, 2005 5:07 PM, Dely Sy wrote:
On Monday, March 21, 2005 10:05 AM, Rajesh Shah wrote:
On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
- Does this break the i386 acpiphp functionality?
Dely Sy had tested hotplug with an earlier version of my patches
(with
On Monday, March 21, 2005 10:05 AM, Rajesh Shah wrote:
> On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
> > - Does this break the i386 acpiphp functionality?
> Dely Sy had tested hotplug with an earlier version of my patches
> (with minor differences from the current series) on i386
On Mon, Mar 21, 2005 at 12:34:07PM -0800, Paul Ionescu wrote:
>
> --- Rajesh Shah <[EMAIL PROTECTED]> wrote:
> >
> > No. The current patches only trigger when a _root_ bridge is
> > hot-added, not a PCI to PCI bridge (which is what the docking
> > station is). The code to support p2p bridge
Hi Rajesh,
--- Rajesh Shah <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 19, 2005 at 03:50:16PM +0200, Paul Ionescu wrote:
> >
> > Does this mean that when it will be ported for i386, I will be able to
> > really use my Docking Station ?
>
> No. The current patches only trigger when a _root_ bridge
On Sat, Mar 19, 2005 at 03:50:16PM +0200, Paul Ionescu wrote:
>
> Does this mean that when it will be ported for i386, I will be able to
> really use my Docking Station ?
No. The current patches only trigger when a _root_ bridge is
hot-added, not a PCI to PCI bridge (which is what the docking
On Mon, Mar 21, 2005 at 10:04:57AM -0800, Rajesh Shah wrote:
> > - Are you wanting the acpi specific patches to go into the tree
> > through the acpi developers? How about the ia64 specific
> > patches?
>
> I honestly don't know what the best approach is here - what do you
>
On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
>
> This all looks very good, nice job. I only had one minor comment on the
> patches, which I'll reply to directly.
>
> But I did have a few questions:
> - This series relys on Mathew's rewrite of the acpiphp driver.
> Is
On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
This all looks very good, nice job. I only had one minor comment on the
patches, which I'll reply to directly.
But I did have a few questions:
- This series relys on Mathew's rewrite of the acpiphp driver.
Is that
On Mon, Mar 21, 2005 at 10:04:57AM -0800, Rajesh Shah wrote:
- Are you wanting the acpi specific patches to go into the tree
through the acpi developers? How about the ia64 specific
patches?
I honestly don't know what the best approach is here - what do you
recommend? I
On Sat, Mar 19, 2005 at 03:50:16PM +0200, Paul Ionescu wrote:
Does this mean that when it will be ported for i386, I will be able to
really use my Docking Station ?
No. The current patches only trigger when a _root_ bridge is
hot-added, not a PCI to PCI bridge (which is what the docking
Hi Rajesh,
--- Rajesh Shah [EMAIL PROTECTED] wrote:
On Sat, Mar 19, 2005 at 03:50:16PM +0200, Paul Ionescu wrote:
Does this mean that when it will be ported for i386, I will be able to
really use my Docking Station ?
No. The current patches only trigger when a _root_ bridge is
On Mon, Mar 21, 2005 at 12:34:07PM -0800, Paul Ionescu wrote:
--- Rajesh Shah [EMAIL PROTECTED] wrote:
No. The current patches only trigger when a _root_ bridge is
hot-added, not a PCI to PCI bridge (which is what the docking
station is). The code to support p2p bridge hotplug will
On Monday, March 21, 2005 10:05 AM, Rajesh Shah wrote:
On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
- Does this break the i386 acpiphp functionality?
Dely Sy had tested hotplug with an earlier version of my patches
(with minor differences from the current series) on i386 and
On Fri, 18 Mar 2005 13:38:57 -0800, Rajesh Shah wrote:
> Here is a series of patches to support ACPI hot-add of a root bridge
> hierarchy. The added hierarchy may contain other p2p bridges and end/leaf
> I/O devices too. The root bridge itself is assumed to have been assigned
> resource ranges,
On Fri, 18 Mar 2005 13:38:57 -0800, Rajesh Shah wrote:
Here is a series of patches to support ACPI hot-add of a root bridge
hierarchy. The added hierarchy may contain other p2p bridges and end/leaf
I/O devices too. The root bridge itself is assumed to have been assigned
resource ranges, but
On Fri, Mar 18, 2005 at 01:38:57PM -0800, Rajesh Shah wrote:
> Here is a series of patches to support ACPI hot-add of a root
> bridge hierarchy. The added hierarchy may contain other p2p
> bridges and end/leaf I/O devices too. The root bridge itself is
> assumed to have been assigned resource
Here is a series of patches to support ACPI hot-add of a root
bridge hierarchy. The added hierarchy may contain other p2p
bridges and end/leaf I/O devices too. The root bridge itself is
assumed to have been assigned resource ranges, but the p2p
bridges and end devices are not required to be
Here is a series of patches to support ACPI hot-add of a root
bridge hierarchy. The added hierarchy may contain other p2p
bridges and end/leaf I/O devices too. The root bridge itself is
assumed to have been assigned resource ranges, but the p2p
bridges and end devices are not required to be
On Fri, Mar 18, 2005 at 01:38:57PM -0800, Rajesh Shah wrote:
Here is a series of patches to support ACPI hot-add of a root
bridge hierarchy. The added hierarchy may contain other p2p
bridges and end/leaf I/O devices too. The root bridge itself is
assumed to have been assigned resource ranges,
28 matches
Mail list logo
