Markus Trippelsdorf wrote:
On Mon, Feb 12, 2007 at 10:51:44AM -0800, Tejun Heo wrote:Conversion to resource-managed iomap was buggy causing init failures on both vt6420 and 6421 - BAR5 wasn't mapped for both controllers while on vt6420 sata_via tried to map BAR0-4 twice. Fix it.
Great, can anyone verify this on vt6421? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] sata_via: fix resource-managed iomap conversion
- From: Jay Cliburn <[email protected]>
- Re: [PATCH] sata_via: fix resource-managed iomap conversion
- From: Jarek Poplawski <[email protected]>
- Re: [PATCH] sata_via: fix resource-managed iomap conversion
- References:
- [git patches] libata updates 1 of 3
- From: Jeff Garzik <[email protected]>
- Re: [git patches] libata updates 1 of 3
- From: Markus Trippelsdorf <[email protected]>
- Re: [git patches] libata updates 1 of 3
- From: Tejun Heo <[email protected]>
- Re: [git patches] libata updates 1 of 3
- From: Markus Trippelsdorf <[email protected]>
- [PATCH] sata_via: fix resource-managed iomap conversion
- From: Tejun Heo <[email protected]>
- Re: [PATCH] sata_via: fix resource-managed iomap conversion
- From: Markus Trippelsdorf <[email protected]>
- [git patches] libata updates 1 of 3
- Prev by Date: Re: High CPU usage with sata_nv
- Next by Date: Re: Which CPU for VIA C7/Esther?
- Previous by thread: Re: [PATCH] sata_via: fix resource-managed iomap conversion
- Next by thread: Re: [PATCH] sata_via: fix resource-managed iomap conversion
- Index(es):
 |