All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Davidson <kiloman@oatmail.org>
To: linux-serial@vger.kernel.org
Subject: Equinox SST-8P Serial Controller and Linux
Date: Thu, 12 Feb 2004 08:16:09 -0800	[thread overview]
Message-ID: <402BA6C9.2090501@oatmail.org> (raw)

Hello all,

I'm working on getting an Equinox SST-8P Multiport Serial adapter to 
work under linux.

I found an old (WAY old, 1997) post from Alan Cox talking about how the 
vendor-provided binary drivers suck, and are distributed poorly:

http://www.geocrawler.com/archives/3/59/1997/1/0/2206254/

The current release of the drivers claims to have been tested against 
4.2.21, and appear to work with the current release of 2.4 (tried with 
2.4.25-rc1). Full source is provided, and there's no mention of a 
license in any of the files or included documentation. There's a 
copywright header on the source files, but that's it. The source itself 
sets MODULE_LICENSE("GPL"), so I'm going to assume they meant it. Here's 
a link:

http://www.equinox.com/Driver_Search_Results153.cfm?uid=331

Has anyone ever tried to add support for this device to the kernel, via 
the 'non-standard serial port' section? I don't see any options for it 
in 2.5 or 2.6, and the driver certainly won't compile against either tree.

As I understand it, this board does some odd tricks with memory mapping 
to accelerate transfers:

ftp://gsyprf10.external.hp.com/pub/equinox/eqnx_sst-8p.pdf

I've never really mucked about much with kernel drivers, but I'm 
passable in C, and have browsed through O'Reilly's 'Linux Device 
Drivers'. Is porting a 2.4 driver to 2.6 something that can be worked 
through with sweat, tears, and some RTFMing, or should I just give up 
and leave my server in 2.4 in the hopes that Equinox will release 2.6 
drivers for this EOL'd card?

-Brad

                 reply	other threads:[~2004-02-12 16:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=402BA6C9.2090501@oatmail.org \
    --to=kiloman@oatmail.org \
    --cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.