Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262224AbUDAEyW (ORCPT ); Wed, 31 Mar 2004 23:54:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262260AbUDAEyV (ORCPT ); Wed, 31 Mar 2004 23:54:21 -0500 Received: from out006pub.verizon.net ([206.46.170.106]:56288 "EHLO out006.verizon.net") by vger.kernel.org with ESMTP id S262224AbUDAEyT (ORCPT ); Wed, 31 Mar 2004 23:54:19 -0500 From: Gene Heskett Reply-To: gene.heskett@verizon.net Organization: Organization: None, detectable by casual observers To: linux-kernel mailing list Subject: TI Firewire controller ? Date: Wed, 31 Mar 2004 23:54:17 -0500 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200403312354.17104.gene.heskett@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [151.205.9.48] at Wed, 31 Mar 2004 22:54:18 -0600 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1723 Lines: 36 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- SERR-