[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58cb370e0802010946v3544a4echc08a17f678222555@mail.gmail.com>
Date: Fri, 1 Feb 2008 18:46:32 +0100
From: "Bartlomiej Zolnierkiewicz" <bzolnier@...il.com>
To: "Jeff Garzik" <jeff@...zik.org>
Cc: "Tejun Heo" <htejun@...il.com>,
"IDE/ATA development list" <linux-ide@...r.kernel.org>,
"Mark Lord" <liml@....ca>, "Alan Cox" <alan@...rguk.ukuu.org.uk>,
"Sam Ravnborg" <sam@...nborg.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH #upstream] libata: implement libata.force module parameter
On Feb 1, 2008 6:28 PM, Jeff Garzik <jeff@...zik.org> 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
> > to the second port but allow 3.0Gbps for the PMP device itself, oh,
> > the device attached to the third fan-out port chokes on NCQ and
> > shouldn't go over UDMA4" by the following.
> >
> > libata.force=2:1.5g,2.15:3.0g,2.03:noncq,udma4
> >
> > Signed-off-by: Tejun Heo <htejun@...il.com>
> > ---
> > I guess it's about time we add something like this. More than
> > anything else this should help debugging and can serve as a last
> > resort to work around problems.
> >
> > Thanks.
> >
> > Documentation/kernel-parameters.txt | 35 +++
> > drivers/ata/libata-core.c | 375 +++++++++++++++++++++++++++++++++++-
> > drivers/ata/libata-eh.c | 8
> > drivers/ata/libata.h | 1
> > 4 files changed, 415 insertions(+), 4 deletions(-)
>
> ACK, but it breaks the build due to section type conflicts:
>
> drivers/ata/libata-core.c:108: error: ata_force_param_buf causes a
> section type conflict
>
> Given that the data is marked __initdata and the code is marked __init,
> I cannot see the problem.
the data is marked as "const"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists