mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Gulick <gulickconsulting@direcway.com>
To: gene.heskett@verizon.net
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: TI Firewire controller ?
Date: Thu, 01 Apr 2004 10:19:53 -0600	[thread overview]
Message-ID: <1080836393.5300.20.camel@localhost.localdomain> (raw)
In-Reply-To: <200403312354.17104.gene.heskett@verizon.net>

On Wed, 2004-03-31 at 22:54, Gene Heskett wrote:
> Greetings;
> 
> I bought, 3 or so years back, a 1394 controller, thinking
> that maybe it had a chance to become a standard, like USB
> is now.
> 
> lspci -vv reports this:
> 00:0b.0 FireWire (IEEE 1394): Texas Instruments FireWire Controller (rev 01) (prog-if 10 [OHCI])
>         Subsystem: Texas Instruments: Unknown device 8010
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32 (750ns min, 1000ns max), cache line size 08
>         Interrupt: pin A routed to IRQ 11
>         Region 0: Memory at e3007000 (32-bit, non-prefetchable) [size=2K]
>         Region 1: Memory at e3000000 (32-bit, non-prefetchable) [size=16K]
>         Capabilities: [44] Power Management version 1
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> Is there any chance that this card can actually be used with modern devices?
> Or should I bin it and save the couple of watts its burning?

There should probably be a mail list for 1394 (and USB for that matter)
as this is the kernel mail list.

I will respond to your query though.

If the information is correct and the card is OHCI (not the same as USB
OHCI), then it should work just fine.  OHCI is a standard interface to
the 1394 link chip.  If you plug that card into a Mac or Windose box, it
would be recognized as such and the drivers loaded. The same holds true
for Linux.

Matt

----------------------------------------
Matt Gulick
Sr. Staff Engineer
Adaptec, Inc.
gulickconsulting@direcway.com
matt_gulick@adaptec.com
(715) 426-0884



      reply	other threads:[~2004-04-01 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  4:54 Gene Heskett
2004-04-01 16:19 ` Matt Gulick [this message]

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=1080836393.5300.20.camel@localhost.localdomain \
    --to=gulickconsulting@direcway.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®