lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20181002220937.GA29970@kroah.com>
Date:   Tue, 2 Oct 2018 15:09:37 -0700
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Lidza Louina <lidza.louina@...il.com>
Cc:     markh@...pro.net, Sehro Rautenkranz <sehro@...ro.org>,
        driverdev-devel@...uxdriverproject.org, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: dgnc: Fix Kconfig help header and text

On Mon, Oct 01, 2018 at 12:49:50PM -0400, Lidza Louina wrote:
> On Mon, Oct 1, 2018 at 8:09 AM Mark Hounschell <markh@...pro.net> wrote:
> 
> > 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
> >
> 
> Thanks for the heads up Mark. I've totally neglected this driver and should
> have caught this earlier. I'm okay with removing it from staging. We can
> bring it back if they need it.

Ok, I'll go delete it, thanks.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ