Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#74 66Mhz PCI kernel cmd line arg

closed-out-of-date
Jeff Garzik
5
2002-08-09
2001-06-03
Jeff Garzik
No

Message-ID: <3B16EC77.3253DBE@sun.com>
Date: Thu, 31 May 2001 18:14:31 -0700
From: Tim Hockin <thockin@sun.com>
Organization: Sun Microsystems, Inc.
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Martin Mares <mj@ucw.cz>
CC: linux-kernel@vger.kernel.org, alan@redhat.com
Subject: [PATCH] 66MHz PCI flag from commandline
References:
<20010403110005.A3222@atrey.karlin.mff.cuni.cz>
<200104041818.NAA08621@isunix.it.ilstu.edu>
<20010404201259.A7820@atrey.karlin.mff.cuni.cz>
<3ACB7798.1908657B@sun.com>
<20010404220712.B929@albireo.ucw.cz>
<3ACB8021.D446929E@sun.com>
<20010404221547.B1040@albireo.ucw.cz>
Content-Type: multipart/mixed;
boundary="------------444ED779DC1728EB5DF6A733"

Martin,

We spoke a while back about a pcispeed= command line
param to set the PCI
busspeed values (for later querying, if needed).
Attached is my patch to
implement the feature we agreed upon. It is against
linux-2.4.5.

Below is our previous discussion, as a refresher :).
Please let me know if
this is not suitable for general inclusion in the
kernel, and I'll try to
make it so.

Tim

(cc: lkml, alan)

Martin Mares wrote:
> > What do you think of my pcispeed=0:33,2:66 idea?

> anything -- the 33/66 MHz values from the PCI specs
are only upper limits),
> I'll welcome this option, but otherwise I'd rather
like to use the measuring
> code in IDE driver as it requires no user
intervention to get the right
> timing.

--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com

Discussion

  • Jeff Garzik
    Jeff Garzik
    2001-06-03

    patch against 2.4.5

     
    Attachments
  • Jeff Garzik
    Jeff Garzik
    2002-08-09

    • labels: 310100 --> net_drivers
    • status: open --> closed-out-of-date