public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Andrea Shepard <andrea@persephoneslair.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, mmarek@suse.cz, jkosina@suse.cz,
	joe@perches.com, justinmattock@gmail.com, gregkh@suse.de,
	alan@linux.intel.com, jdmason@kudzu.us
Subject: Re: [00/22] Cyclades PC300 driver: summary of patch series
Date: Tue, 31 Jan 2012 20:20:30 +0100	[thread overview]
Message-ID: <m3d39z3cht.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20120130024243.GA10262@cronus.persephoneslair.org> (Andrea Shepard's message of "Sun, 29 Jan 2012 18:42:43 -0800")

Andrea Shepard <andrea@persephoneslair.org> writes:

> The Cyclades PC-300 is a line of PCI synchronous serial cards, which was
> produced in single and dual port models with either T1/E1 or V.35 ports.
> It used a Hitachi HD64572 (SCA-II) synchronous serial chip, and in the
> T1/E1 models an Infineon FALC-LH line interface/framing chip.  Copies
> of the hardware documentation may be found at [1].

BTW the V.35/V.24/X.21 version (i.e. non-T1/E1) are supported by the
pc300too.c driver. Or at least they're supposed to, I admit I haven't
used this kind of hw for several years (but can still test and fix, when
time permits).

Perhaps, just perhaps, merging T1/E1 support into pc300too.c would be
a better idea than dealing with Cyclades' old code.

The pc300too shares common SCA-II code with a driver for another hw,
pci200syn. I think it's been verified to work on non-x86-32 systems.

Esp. given this:

>  * Patches 01 through 16 merge in version 4.1.0, and fix build, portability
>    and style problems.  As of patch 16, the driver will build cleanly and
>    will detect hardware, but not operate reliably.
-- 
Krzysztof Halasa

      parent reply	other threads:[~2012-01-31 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  2:42 [00/22] Cyclades PC300 driver: summary of patch series Andrea Shepard
2012-01-30 10:28 ` Alan Cox
2012-01-31 19:20 ` Krzysztof Halasa [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=m3d39z3cht.fsf@intrepid.localdomain \
    --to=khc@pm.waw.pl \
    --cc=alan@linux.intel.com \
    --cc=andrea@persephoneslair.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=jdmason@kudzu.us \
    --cc=jkosina@suse.cz \
    --cc=joe@perches.com \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=netdev@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