From: Jacek Luczak <difrost@pin.if.uz.zgora.pl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, Michael Thonke <tk-shockwave@web.de>
Subject: [PATCH] Against sk98lin driver from syskonnect [was: Re: PCI-Express not working/unuseable on Intel 925XE since 2.6.12-rc1[mm1-4]]
Date: Sat, 09 Apr 2005 15:14:12 +0200 [thread overview]
Message-ID: <4257D524.3080002@pin.if.uz.zgora.pl> (raw)
In-Reply-To: <1539.24.9.197.67.1113017666.squirrel@mail.cce.hp.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Bjorn Helgaas napisał(a):
>>Version from syskonnect site require only changing usage of
>>pci_dev->slot_name to pci_name(pci_dev) in skge.c and skethtool.c. After
>>that everything should work fine. So I think there is no need to post my
>>path here but if you really whant I may do this. Whole path agains
>>2.6.12-rc2 take about 1.2 MB (diffstat attached below).
>
>
> I agree, no need to post a whole 1.2MB patch (goodness, what's
> in this driver, anyway, that it would need a 1.2MB *patch*? :-))
I'm wondering too :)
> But you seem to be saying that the driver from syskonnect (and possibly
> the one in 2.6.12-rc1-bk3 as well) does not work as-is, and that you have
> a small patch that makes it work.
The one that is in 2.6.12-rc1-bk2 and latest 2.6.13-rc2 doesn't work
with Marvell Yukon 88E8053 GigE.
Attached patch convert pci_dev->slot_name usage to pci_name() in skge.c
and skethtool.c. First you must apply patch generated by install script
and after that apply this patch:-)
Regards
Jacek
---
drivers/net/sk98lin/skethtool.c | 2 +-
drivers/net/sk98lin/skge.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
---
[-- Attachment #2: sk98lin_syskonnect.patch --]
[-- Type: text/plain, Size: 1034 bytes --]
--- linux-2.6.12-rc2/drivers/net/sk98lin/skge.c 2005-04-09 14:49:39.000000000 +0200
+++ linux/drivers/net/sk98lin/skge.c 2005-04-09 02:04:49.000000000 +0200
@@ -4026,7 +4026,7 @@
*/
* ((SK_U32 *)pMemBuf) = 0;
* ((SK_U32 *)pMemBuf + 1) = pdev->bus->number;
- * ((SK_U32 *)pMemBuf + 2) = ParseDeviceNbrFromSlotName(pdev->slot_name);
+ * ((SK_U32 *)pMemBuf + 2) = ParseDeviceNbrFromSlotName(pci_name(pdev));
if(copy_to_user(Ioctl.pData, pMemBuf, Length) ) {
Err = -EFAULT;
goto fault_diag;
--- linux-2.6.12-rc2/drivers/net/sk98lin/skethtool.c 2005-04-09 14:49:39.000000000 +0200
+++ linux/drivers/net/sk98lin/skethtool.c 2005-04-09 02:04:49.000000000 +0200
@@ -1136,7 +1136,7 @@
strncpy(edrvinfo->driver, DRIVER_FILE_NAME , 32);
strncpy(edrvinfo->version, versionString , 32);
strncpy(edrvinfo->fw_version, "N/A", 32);
- strncpy(edrvinfo->bus_info, pAC->PciDev->slot_name, 32);
+ strncpy(edrvinfo->bus_info, pci_name(pAC->PciDev), 32);
#ifdef ETHTOOL_GSTATS
edrvinfo->n_stats = SK98LIN_STATS_LEN;
#endif
prev parent reply other threads:[~2005-04-09 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 12:56 PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4] Michael Thonke
2005-04-01 14:43 ` Jacek Luczak
2005-04-01 16:07 ` Michael Thonke
2005-04-01 18:23 ` Jacek Luczak
2005-04-01 19:01 ` Michael Thonke
2005-04-01 19:23 ` Jacek Luczak
2005-04-08 20:43 ` Bjorn Helgaas
2005-04-09 0:40 ` Jacek Luczak
2005-04-09 3:34 ` Bjorn Helgaas
2005-04-09 13:14 ` Jacek Luczak [this message]
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=4257D524.3080002@pin.if.uz.zgora.pl \
--to=difrost@pin.if.uz.zgora.pl \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tk-shockwave@web.de \
/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