From: Mike Houston <mikeserv@bmts.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22-rc2
Date: Thu, 24 May 2007 14:26:44 -0400 [thread overview]
Message-ID: <20070524142644.837a26ed.mikeserv@bmts.com> (raw)
In-Reply-To: <alpine.LFD.0.98.0705231044160.3890@woody.linux-foundation.org>
On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Wed, 23 May 2007, Mike Houston wrote:
> >
> > I still happen to have a Windows Vista install kicking around, so
> > to make sure we're not flogging a dead horse I booted that and
> > let it set up the yukon2 chip and I tested it. (more to make sure
> > that eeprom update didn't break it). I used it for a bit and
> > successfully transferred some large files from box running Samba.
> > MS must be using some specific workaround or something.
>
> I think there is some lspci-like thing for windows too.
>
> Can you do the equivalent of "lspci -vvxxx" on that box under both
> Linux and Windows? _If_ it's some PCI config space thing (which is
> not at all guaranteed - it could be about setup in random MMIO
> ranges) it might give us some clues.
>
This is the sky2 issue with Gigabyte 88E8056 onboard LAN.
I've had no luck getting pciutils compiled for win32, but I found a
utility that gives similar output called Craig Hart's PCI bus sniffer
(pci32.exe).
Here is the output of pci32 with hex dump from within Windows Vista:
http://www.mikeserv.org/files/pci32_info.txt
Here is the output of lspci -vvxxx from within Linux:
http://www.mikeserv.org/files/lspci.txt
I hope this is helpful,
Mike Houston
next prev parent reply other threads:[~2007-05-24 18:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 5:17 Linux 2.6.22-rc2 Linus Torvalds
2007-05-19 6:54 ` Andrey Borzenkov
2007-05-19 14:28 ` [BUG: 2.6.22-rc2] SLAB doesn't like usb_get_configuration() Indan Zupancic
[not found] ` <6101e8c40705190950jb093d65l611995895a182ec0@mail.gmail.com>
2007-05-19 16:51 ` Fwd: " oliver pinter
2007-05-19 18:20 ` Christoph Lameter
2007-05-19 19:33 ` Greg KH
2007-05-19 22:10 ` Indan Zupancic
2007-05-20 12:57 ` Linux 2.6.22-rc2: make -j makes it unresponsive Rafael J. Wysocki
2007-05-20 13:01 ` Krzysztof Halasa
2007-05-20 13:23 ` Rafael J. Wysocki
2007-05-20 21:05 ` Linux 2.6.22-rc2 Mike Houston
2007-05-21 15:45 ` Stephen Hemminger
2007-05-21 17:10 ` Mike Houston
2007-05-21 17:37 ` Stephen Hemminger
2007-05-22 2:58 ` Mike Houston
2007-05-22 4:31 ` Stephen Hemminger
2007-05-22 4:36 ` Jeff Garzik
2007-05-22 4:42 ` Stephen Hemminger
2007-05-22 5:04 ` Linus Torvalds
2007-05-22 17:19 ` Stephen Hemminger
2007-05-22 17:54 ` H. Peter Anvin
2007-05-22 22:14 ` Mike Houston
2007-05-23 0:00 ` Linus Torvalds
2007-05-23 0:29 ` Stephen Hemminger
2007-05-23 1:53 ` Linus Torvalds
2007-05-23 14:58 ` Stephen Hemminger
2007-05-23 17:39 ` Mike Houston
2007-05-23 17:46 ` Linus Torvalds
2007-05-23 18:04 ` Stephen Hemminger
2007-05-24 18:26 ` Mike Houston [this message]
2007-05-24 22:08 ` sky2/pci issues on Gigabyte Stephen Hemminger
2007-05-24 22:48 ` Linus Torvalds
2007-05-24 23:04 ` Stephen Hemminger
2007-05-25 0:01 ` Mike Houston
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=20070524142644.837a26ed.mikeserv@bmts.com \
--to=mikeserv@bmts.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=torvalds@linux-foundation.org \
/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