[RFC] staging: ks7010: How to proceed with Spectec SDW-823 microSD driver

[RFC] staging: ks7010: How to proceed with Spectec SDW-823 microSD driver

[Philipp Hortmann]

Hi Wolfram,

you contributed a driver ks7010 to the staging subsystem in 2016.

In the first commit description you stated that you have not been able 
to connect to a WPA-protected network. Did you manage to connect to a 
WPA-protected network at a later time? Have you done any tests with this 
hardware in the years up to today?

I am asking because I tried to find a test device to test it. That is 
difficult in 2024.

Do you think the driver can be removed or should it stay in the mainline 
kernel?

Thanks for your response.

Bye Philipp

Re: [RFC] staging: ks7010: How to proceed with Spectec SDW-823 microSD driver

[Wolfram Sang]

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

Hi Philipp,

> In the first commit description you stated that you have not been able to
> connect to a WPA-protected network. Did you manage to connect to a
> WPA-protected network at a later time? Have you done any tests with this
> hardware in the years up to today?

I was about to say I never connected to a WPA-network, but my
documentation says I actually did. Good documentation :)

https://elinux.org/Tests:SDIO-KS7010

About testing, when the first set of staging-cleanup patches came in, I
actually tested them. But after some weeks, I stopped doing that because
the amount of patches was just too high and the developers mostly too
inexperienced to understand potential side-effects of their changes. I
didn't have the bandwidth to educate them.

> I am asking because I tried to find a test device to test it. That is
> difficult in 2024.

I still have one or two cards. You could have one if you want. That
doesn't change the whole situation, of course.

> Do you think the driver can be removed or should it stay in the mainline
> kernel?

Frankly, I think it can be removed. When I upstreamed the code, it
served two purposes:

a) I needed to test SDIO communication on my back then recent boards.
   That worked, but I have other hardware now with SDIO on board.

b) there were different versions of KS7010 drivers floating on the net.
   I combined them into one and made sure it was easy to compile with
   upstream Linux. We have that definitive version in the history now.

As both purposes are fulfilled, I don't think we need to maintain this
code anymore. I couldn't imagine someone wants to convert it from WEXT
to cfg80211/nl80211 which would be needed for mainline.

Thanks and happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[RFC] staging: gdm724x: How to proceed with drivers gdmtty and gdmulte

[Philipp Hortmann]

Dear Sirs,

Won Kang contributed a driver gdm724x to the Linux kernel staging 
subsystem in 2013. Have you done any tests with this hardware in the 
years up to today?

struct usb_device_id lists the following devices the driver can work with:
PID_GDM7240		0x8000
PID_GDM7243		0x9000

but on http://www.linux-usb.org/usb.ids I can only find:
0x1076  GCT Semiconductor, Inc.
	0x0031  Bluetooth Device
	0x0032  Bluetooth Device
	0x8002  LU150 LTE Modem [Yota LU150]

I am asking because I tried to find a test device to test it. That is 
difficult in 2024.

Do you think the driver can be removed or should it stay in the mainline 
kernel?

Thanks for your response.

Regards,

Philipp Hortmann

Re: [RFC] staging: gdm724x: How to proceed with drivers gdmtty and gdmulte

[Greg Kroah-Hartman]

On Wed, Apr 24, 2024 at 08:33:25PM +0200, Philipp Hortmann wrote:
> Dear Sirs,
> 
> Won Kang contributed a driver gdm724x to the Linux kernel staging subsystem
> in 2013. Have you done any tests with this hardware in the years up to
> today?
> 
> struct usb_device_id lists the following devices the driver can work with:
> PID_GDM7240		0x8000
> PID_GDM7243		0x9000
> 
> but on http://www.linux-usb.org/usb.ids I can only find:
> 0x1076  GCT Semiconductor, Inc.
> 	0x0031  Bluetooth Device
> 	0x0032  Bluetooth Device
> 	0x8002  LU150 LTE Modem [Yota LU150]

Note, not all USB devices (I would guess only a fraction) are listed in
the usb.ids file because USB devices are self-described (i.e. the
strings are in the device itself).  So don't go by the presence or not
of a device in this file to determine if it is "real" or not.

thanks,

greg k-h