From: Andreas Mohr <andim2@users.sourceforge.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-user@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: VIA VT6307 OHCI version?
Date: Sun, 4 Nov 2007 20:31:09 +0100 [thread overview]
Message-ID: <20071104193109.GA4033@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <m33avvdlbq.fsf@maximus.localdomain>
Hi,
On Sun, Oct 28, 2007 at 09:40:41PM +0100, Krzysztof Halasa wrote:
> Stefan Richter <stefanr@s5r6.in-berlin.de> writes:
>
> >> Compile with the usual spell: gcc -Wall -O2 vt6307ohciver.c -o vt6307ohciver
> >
> > I also had to specify "-lpci" on Mandrake 10.1, "-lpci -lz" on Gentoo.
>
> Of course you're right, just typed faster than thought.
> Actually I had to add these two on Fedora, too.
And in general the pciutils-dev package should be installed.
> Ok so it seems rev 80 is VT6307 and (at least) rev 46 is VT6306.
> I think my googling for lspci reports confirms that.
As does my card:
# lspci |grep 1394
00:09.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 46)
root@andi:/tmp# ./vt6307ohciver 00:09.0
I/O region #1 is at A000
It seems your VT6307 chip is connected to 93c46 EEPROM
Page size is 4096 (0x1000) bytes
GUID PROM register address is 0xdb140004
Mapping 8 (0x8) bytes of memory at 0xdb140000
Mapped mem region #0 at virtual address 0xb7ee5000
GUID PROM register is at virtual address 0xb7ee5004
EEPROM dump:
00: 00 11 06 66 45 55 56 E1 04 04 32 55 F8 00 A2 02
10: A1 00 40 63 06 11 44 30 03 DF 40 80 00 20 00 73
20: 3C 10 00 00 00 00 FF FF FF FF FF FF FF FF FF FF
Your VT6307 chip is in OHCI 1.0 mode
And viewing from a quite problematic angle (card is in running PC,
difficult to view) strongly seems to indicate a VT630_6_ (the "6" is
quite clearly visible).
This means that I currently cannot offer any mfct. date data however,
unfortunately.
Andreas Mohr
next prev parent reply other threads:[~2007-11-04 19:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3sl4ciz1h.fsf@maximus.localdomain>
[not found] ` <4714EF01.2060609@s5r6.in-berlin.de>
2007-10-16 20:20 ` Krzysztof Halasa
2007-10-16 20:33 ` Krzysztof Halasa
2007-10-16 21:06 ` Stefan Richter
2007-10-17 19:38 ` Krzysztof Halasa
2007-10-17 20:11 ` Stefan Richter
2007-10-17 20:54 ` Krzysztof Halasa
2007-10-17 21:06 ` Stefan Richter
2007-10-18 0:07 ` Krzysztof Halasa
2007-10-19 22:42 ` Krzysztof Halasa
2007-10-20 6:31 ` Stefan Richter
2007-10-20 13:03 ` Krzysztof Halasa
2007-10-20 13:13 ` Stefan Richter
2007-10-20 23:23 ` Krzysztof Halasa
2007-10-28 17:41 ` Stefan Richter
2007-10-28 20:40 ` Krzysztof Halasa
2007-10-28 23:12 ` Stefan Richter
2007-10-29 12:53 ` Krzysztof Halasa
2007-11-03 19:15 ` Stefan Richter
2007-11-04 16:54 ` Krzysztof Halasa
2007-11-04 19:31 ` Andreas Mohr [this message]
2007-11-04 23:00 ` Krzysztof Halasa
2007-11-05 18:25 ` Andreas Mohr
2007-11-05 19:14 ` Stefan Richter
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=20071104193109.GA4033@rhlx01.hs-esslingen.de \
--to=andim2@users.sourceforge.net \
--cc=andi@lisas.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-user@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.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®