Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-14 Thread Mark Lord
Tejun Heo wrote: Mark Lord wrote: Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. ... +libata.force=[LIBATA] Force

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-13 Thread Mark Lord
Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. ... + libata.force= [LIBATA] Force configurations. The format is comma +

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-13 Thread Tejun Heo
Mark Lord wrote: Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. ... +libata.force=[LIBATA] Force configurations. The format

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-12 Thread Tejun Heo
Jeff Garzik wrote: Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. For example, you can say use 1.5Gbps for all fan-out ports attached

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-12 Thread Tejun Heo
This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. For example, you can say use 1.5Gbps for all fan-out ports attached to the second port but allow 3.0Gbps for

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-08 Thread Tejun Heo
Sam Ravnborg wrote: I have lost the actual patch. But what you see is what happens when you mix const and non-const data in the same section. Look for use of __initdata for const data and replace it with __initconst. And modpost cannot warn about it as gcc errors out before we look at the

[PATCH #upstream] libata: implement libata.force module parameter

2008-02-01 Thread Tejun Heo
This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. For example, you can say use 1.5Gbps for all fan-out ports attached to the second port but allow 3.0Gbps for

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-01 Thread Bartlomiej Zolnierkiewicz
On Feb 1, 2008 6:28 PM, Jeff Garzik [EMAIL PROTECTED] wrote: Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. For example, you can

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-01 Thread Jeff Garzik
Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. For example, you can say use 1.5Gbps for all fan-out ports attached to the second port

Re: [PATCH #upstream] libata: implement libata.force module parameter

2008-02-01 Thread Sam Ravnborg
On Fri, Feb 01, 2008 at 12:28:35PM -0500, Jeff Garzik wrote: Tejun Heo wrote: This patch implements libata.force module parameter which can selectively override ATA port, link and device configurations including cable type, SATA PHY SPD limit, transfer mode and NCQ. For example, you can say