Re: Resource assignment oddities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 24, 2013 at 8:59 AM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
> On Thu, May 23, 2013 at 4:16 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> That should not happen, because the only reason we're reassigning is
> for IO space, and we shouldn't be touching the MEM assignments.  I
> agree that we should fix that.

yes, that is

https://patchwork.kernel.org/patch/2608461/

>
> I do not agree that your current patches are the right way to fix
> this.  You are trying to make a relatively small patch that we can
> wedge into v3.10 in a hurry.  I would prefer that we work out a
> cleaner solution that simplifies reassignment, *then* figure out the
> best way to backport it as needed.

ok, we can leave per root bus method to v3.11.

we can put only one patch in v3.10.

https://patchwork.kernel.org/patch/2608461/
PCI: Don't let mmio fallback to must-only, if ioport fails with must+optional

that should fix the problem that Ben and Shan met.

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux