mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-user@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: VIA VT6307 OHCI version?
Date: Mon, 29 Oct 2007 13:53:01 +0100	[thread overview]
Message-ID: <m3abq2ccb6.fsf@maximus.localdomain> (raw)
In-Reply-To: <47251744.6090206@s5r6.in-berlin.de> (Stefan Richter's message of "Mon, 29 Oct 2007 00:12:04 +0100")

Stefan Richter <stefanr@s5r6.in-berlin.de> writes:

> This device is a somewhat buggy PCI card which somebody sent me after
> unsuccessful attempts to get it properly working under Linux.  Among
> more serious trouble, ohci1394 reads a bogus maximum async payload (a
> zero value) from the BusOptions register during startup.  This has
> occasionally been reported for some VT6306 in the past.  I haven't
> really tested this card myself yet, it's currently stuck in a PC which I
> don't use anymore.

I see. I think you may be able to cure this problem with my program,
adding corrected values in addition to write to 0x11 should do the
trick. 93c46 is 16-bit, little-endian here. You'd have to divide the
addresses shown by the dump by 2 of course.
I'd make sure the values are ok before rebooting, there is some
possibility a badly corrupted EEPROM may prevent BIOS from starting.

I think I'd leave GUID (16-bit words at 0, 1, 2, 3) and PCI subsystem
IDs (words at 0xA and 0xB) unchanged, and for all other locations I'd
fill in the 6307 values.

Of course I don't know if the program will be able to write to VT6306,
so I'd test the broken card first.

> VT6306 CardBus card in my main PC:
> MMIO=[80000000-800007ff]  Max Packet=[1024]  IR/IT contexts=[4/8]
> ieee1394: Host added: ID:BUS[2-00:1023]  GUID[00110600000041cc]

The difference is of course at 0x0E, not 0x1E. Maybe the byte at 0x0A
is 0x92 for 4 IR contents and 0xA2 for 8 contents. That would also
make sense wrt the broken 6306 as it has 0x00 there.
-- 
Krzysztof Halasa

  reply	other threads:[~2007-10-29 12:53 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 [this message]
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
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=m3abq2ccb6.fsf@maximus.localdomain \
    --to=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®