linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Lidza Louina <lidza.louina@gmail.com>,
	Sehro Rautenkranz <sehro@sehro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	driverdev-devel@linuxdriverproject.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: dgnc: Fix Kconfig help header and text
Date: Mon, 1 Oct 2018 08:09:48 -0400	[thread overview]
Message-ID: <cdd97ca9-68c8-3a5e-faa1-d19cd5fe93a7@compro.net> (raw)
In-Reply-To: <CA+t4uCMAgpNtpdLfxNY_cmx7WONKOYjiaTBDGRNd+7H_GUdRAA@mail.gmail.com>

On 9/28/18 3:59 PM, Lidza Louina wrote:
> I haven't done work on this driver in a long time. I looked up the 
> devices, and they seem to already have an existing Linux driver: 
> https://www.digi.com/products/usb-and-serial-connectivity/serial-cards/digineo and 
> https://www.digi.com/support/productdetail?pid=1694
> 
> I've contacted the company to see if the driver is still needed in 
> staging. I'll send an update once they get back to me.
> 
> Lidza
> 

Good luck with that. Digi obsoleted ALL their PCI serial cards several 
months ago. They would not even respond to requests from me to include 
their firmware for their PCI dgap cards into the kernel firmware 
package. The card for the dgnc driver is a pci-e card that may still be 
supported by them however. Also there does appear to be an already in 
kernel driver for these "PCI-e" cards too. It actually works as I have a 
couple of these cards. The module name is "jsm".


03:00.0 Serial controller: Digi International Device 00f0 (rev 02) 
(prog-if 02 [16550])
         Subsystem: Digi International Device 00f0
         Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx-
         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
         Interrupt: pin A routed to IRQ 29
         Region 0: Memory at f7200000 (32-bit, non-prefetchable) [size=4K]
         Capabilities: [40] Power Management version 2
                 Flags: PMEClk+ DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold-)
                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
         Kernel driver in use: jsm
         Kernel modules: jsm


Regards
Mark

  parent reply	other threads:[~2018-10-01 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  6:20 [PATCH] staging: dgnc: Fix Kconfig help header and text sehro rautenkranz
2018-09-25 15:34 ` Randy Dunlap
2018-09-25 15:53   ` sehro rautenkranz
2018-09-25 16:00     ` Randy Dunlap
2018-09-25 16:22       ` sehro rautenkranz
2018-09-25 18:46         ` Greg Kroah-Hartman
2018-09-25 19:49           ` Randy Dunlap
2018-09-25 23:41             ` [PATCH v3] " Sehro Rautenkranz
     [not found]               ` <CA+t4uCMAgpNtpdLfxNY_cmx7WONKOYjiaTBDGRNd+7H_GUdRAA@mail.gmail.com>
2018-10-01 12:09                 ` Mark Hounschell [this message]
     [not found]                   ` <CA+t4uCPFZSTjyN-Wd3ppOp-edAXfSSTTdT8uab+-E53=Htv9+A@mail.gmail.com>
2018-10-01 17:38                     ` Mark Hounschell
2018-10-02 22:09                     ` Greg Kroah-Hartman

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=cdd97ca9-68c8-3a5e-faa1-d19cd5fe93a7@compro.net \
    --to=markh@compro.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lidza.louina@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sehro@sehro.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;
as well as URLs for NNTP newsgroup(s).