From: Andreas Mohr <andim2@users.sourceforge.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: andi@lisas.de, 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: Mon, 5 Nov 2007 19:25:30 +0100 [thread overview]
Message-ID: <20071105182530.GA6113@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <m38x5dhb0f.fsf@maximus.localdomain>
Hi,
On Mon, Nov 05, 2007 at 12:00:16AM +0100, Krzysztof Halasa wrote:
> Andreas Mohr <andim2@users.sourceforge.net> writes:
> > 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.
>
> Yeah. I think (feel or something) VIA does the usual thing with
> revision numbers so rev 0x46 means always the same silicon (VT6306)
> and rev 0x80 is always the same VT6307. There might be other
> revisions but I think we won't find non-VT6306 rev 0x46 or
> non-VT6307 rev 0x80.
OK, PC was off now (good to be using S2D instead of S2R ;),
the card data is:
"SN1394", "STARNET V1.0"
mfct.: 0450
VIA VT6306
0449CD TAIWAN
2HG1002703
(IOW, a moderately new VT6306 card)
SEEPROM:
ATMEL 418
93C46
PI27 A
I'm only an occasional Firewire user (external backup HDD, miniDV
grabbing), but I'm very thankful for your nice investigations!
Andreas Mohr
next prev parent reply other threads:[~2007-11-05 18:25 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
2007-11-04 23:00 ` Krzysztof Halasa
2007-11-05 18:25 ` Andreas Mohr [this message]
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=20071105182530.GA6113@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®