From: Greg KH <greg@kroah.com>
To: Torben Mathiasen <torben.mathiasen@hp.com>
Cc: linux-kernel@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net, stormy_peters@hp.com,
john.cagle@hp.com, dan.zink@hp.com
Subject: Re: [PATCH-2.4.20] PCI-X hotplug support for Compaq driver
Date: Wed, 15 Jan 2003 15:05:54 -0800 [thread overview]
Message-ID: <20030115230554.GC25816@kroah.com> (raw)
In-Reply-To: <20030115095513.GA2761@tmathiasen>
On Wed, Jan 15, 2003 at 10:55:13AM +0100, Torben Mathiasen wrote:
> Hi Greg,
>
> Attached is a patch against 2.4.20 (should apply to .21-pre3 and BK-current as
> well) that adds 66/100/133MHz PCI-X support to the Compaq Hotplug driver.
>
> Please apply.
Looks almost ready. Could you make up a 2.5 version first? I don't
like to have new features in 2.4 before they go into 2.5.
> /* inline functions */
> -
> +extern inline struct slot *find_slot (struct controller *ctrl, u8 device);
Can you just make this a normal function then, with a more private name?
> +/*
> + * get_controller_speed - find the current frequency/mode of controller.
> + *
> + * @ctrl: controller to get frequency/mode for.
> + *
> + * Returns controller speed.
> + *
> + */
> static inline u8 get_controller_speed (struct controller *ctrl)
Thanks for documenting this and get_adapter_speed().
> +static char *get_speed_string (int speed)
> +{
> + switch(speed) {
> + case(PCI_SPEED_33MHz):
> + return "33MHz PCI";
> + case(PCI_SPEED_66MHz):
> + return "66MHz PCI";
> + case(PCI_SPEED_50MHz_PCIX):
> + return "50MHz PCI-X";
> + case(PCI_SPEED_66MHz_PCIX):
> + return "66MHz PCI-X";
> + case(PCI_SPEED_100MHz_PCIX):
> + return "100MHz PCI-X";
> + case(PCI_SPEED_133MHz_PCIX):
> + return "133MHz PCI-X";
> + default:
> + return "UNKNOWN";
> + }
> +}
Ick, why? Just for a debugging message? That /proc file is on the
short list of things to delete :)
> --- linux-2.4.20/drivers/hotplug/pci_hotplug.h Thu Nov 28 17:53:13 2002
> +++ linux-2.4.20-pcix/drivers/hotplug/pci_hotplug.h Mon Jan 6 22:54:47 2003
> @@ -33,9 +33,10 @@
> enum pci_bus_speed {
> PCI_SPEED_33MHz = 0x00,
> PCI_SPEED_66MHz = 0x01,
> - PCI_SPEED_66MHz_PCIX = 0x02,
> - PCI_SPEED_100MHz_PCIX = 0x03,
> - PCI_SPEED_133MHz_PCIX = 0x04,
> + PCI_SPEED_50MHz_PCIX = 0x02,
> + PCI_SPEED_66MHz_PCIX = 0x03,
> + PCI_SPEED_100MHz_PCIX = 0x04,
> + PCI_SPEED_133MHz_PCIX = 0x05,
> PCI_SPEED_66MHz_PCIX_266 = 0x09,
> PCI_SPEED_100MHz_PCIX_266 = 0x0a,
> PCI_SPEED_133MHz_PCIX_266 = 0x0b,
Where are you getting the PCI_SPEED_50MHz_PCIX value from? I took these
values from the Hotplug PCI draft spec. Has 02 been reserved for 50MHz
PCIX and the other values changed?
If it's not in the spec, I'd recommend adding it to the end of the list,
with a big comment about why it's different from the spec values.
thanks,
greg k-h
next prev parent reply other threads:[~2003-01-15 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 9:55 [PATCH-2.4.20] PCI-X hotplug support for Compaq driver Torben Mathiasen
2003-01-15 23:05 ` Greg KH [this message]
2003-01-16 11:47 ` Torben Mathiasen
2003-01-16 18:35 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030115230554.GC25816@kroah.com \
--to=greg@kroah.com \
--cc=dan.zink@hp.com \
--cc=john.cagle@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=stormy_peters@hp.com \
--cc=torben.mathiasen@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox