From: "Bjorn Helgaas" <bjorn.helgaas@hp.com>
To: "Jacek Luczak" <difrost@pin.if.uz.zgora.pl>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
linux-kernel@vger.kernel.org,
"Michael Thonke" <tk-shockwave@web.de>
Subject: Re: PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Date: Fri, 8 Apr 2005 21:34:26 -0600 (MDT) [thread overview]
Message-ID: <1539.24.9.197.67.1113017666.squirrel@mail.cce.hp.com> (raw)
In-Reply-To: <4257247B.8030604@pin.if.uz.zgora.pl>
> 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*? :-))
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.
If so, I think it's worth posting the small patch, so other users
of the device can at least get it working until syskonnect gets
things squared away.
My apologies if I'm misunderstanding the situation.
next prev parent reply other threads:[~2005-04-09 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 12:56 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 [this message]
2005-04-09 13:14 ` [PATCH] Against sk98lin driver from syskonnect [was: Re: PCI-Express not working/unuseable on Intel 925XE since 2.6.12-rc1[mm1-4]] Jacek Luczak
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=1539.24.9.197.67.1113017666.squirrel@mail.cce.hp.com \
--to=bjorn.helgaas@hp.com \
--cc=difrost@pin.if.uz.zgora.pl \
--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
all inboxes | Powered by JetHome®