public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: David Härdeman <david@2gen.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hard crash when trying to use PCI parallel port card
Date: Sat, 9 Dec 2000 11:09:33 +0000	[thread overview]
Message-ID: <20001209110933.B4106@redhat.com> (raw)
In-Reply-To: <3A317948.10163CC3@2gen.com>
In-Reply-To: <3A317948.10163CC3@2gen.com>; from david@2gen.com on Sat, Dec 09, 2000 at 01:14:00AM +0100

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

On Sat, Dec 09, 2000 at 01:14:00AM +0100, David Härdeman wrote:

> By looking at the windows drivers provided with the card I came to the
> conclusion that the onboard chip was an Oxford Semiconductor OX16PCI954
> which as far as I could understand is documented in
> http://www.oxsemi.com/products/uarts/ox16pci954/ox16pci954ds.pdf. I've

I've got a bunch of information from Titan in my inbox, and haven't
looked at how it affects this support.

There are different types of OX16PCI954..

> Looking at 2.2.18-pre25 I couldn't see that the patch had been included

I think it has.

> though and as far as I could understand (with my limited knowledge of C)
> the patch only added the PCI id's to the kernel.

Look closer. ;-) Yes, adding support for PCI parallel port cards
really isn't that many lines of code..

> <lspci -vvx>
> 00:0c.0 Communication controller: Titan Electronics Inc: Unknown device
> ffff

The patch you refer to won't see this card because it identifies
itself as a Titan Electronics card.  I'm looking at adding support for
this any day now (they should be sending me some samples shortly).

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2000-12-09 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09  0:14 Hard crash when trying to use PCI parallel port card David Härdeman
2000-12-09 11:09 ` Tim Waugh [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=20001209110933.B4106@redhat.com \
    --to=twaugh@redhat.com \
    --cc=david@2gen.com \
    --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