From: Pat Erley <pat-lkml@erley.org>
To: Huseyin <revanthedarth@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Developing a new Driver
Date: Tue, 10 Mar 2015 18:08:32 -0500 [thread overview]
Message-ID: <54FF7970.10402@erley.org> (raw)
In-Reply-To: <8BC2636B-D1F0-431C-90F4-1290A4158DC2@gmail.com>
On 03/10/2015 04:42 PM, Huseyin wrote:
> Hello everyone,
>
> I want to develop a driver for my usb wireless adapter. The device name is AirTies Air 2410, codes are 0x1eda 0x2410. The company’s other usb wireless adapters (for example, AirTies Air 2310, 0x1eda 0x2310) were using ralink rt2800 driver, but this one doesn’t work with it.
>
> I opened up the device’s case, I could only find out that the board was plotech e169497, 6 94v-0. I googled but these seem to be too vague and I cannot go any further with it. I couldn’t find any other text on the board.
>
> I also contacted the company (AirTies) but they didn’t bother to reply. They provide drivers for windows only.
>
> What should be the next step? Reverse-engineering the windows driver (I have no expertise on the subject, and little expertise on windows altogether) or trying to write a new driver using ralink or any other existing driver code? Is it a good idea to guess that the driver I’m going to develop will be similar to rt2800? This way I can make rt2800 recognize my device and try to find out what goes wrong (which, seems to me, would be meaningless if device is using a chipset not related to ralink), and change those parts.
>
> I asked a little about the subject in the #kernelnewbies channel, people redirected me to this mail list.
>
> When I make rt2800 driver recognize my device, this is what I get:
>
> ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1000 with error -110
> ieee80211 phy0: rt2800_probe_rt: Error - Invalid RT chipset 0xffff, rev 8800 detected
> ieee80211 phy0: rt2x00lib_probe_dev: Error - Failed to allocate device
> usbcore: registered new interface driver rt2800usb
>
Based on their driver, it's a broadcom chip in there:
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/bcmh43xx.cat
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/bcmihvsrv.dll
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/bcmihvui.dll
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/bcmwlcoi.dll
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/bcmwlhigh6.inf
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/bcmwlhigh6.sys
inflating:
AirTiesWirelessUSBAdapterSetup_1.0.1.0/Drivers/Air2410-Air2411/VistaDriver/WdfCoInstaller01005.dll
I don't know what the status of broadcom and usb drivers is though.
next prev parent reply other threads:[~2015-03-10 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 21:42 Developing a new Driver Huseyin
2015-03-10 23:08 ` Pat Erley [this message]
2015-03-10 23:15 ` Jonas Gorski
2015-03-11 5:55 ` Rafał Miłecki
2015-03-12 20:42 ` Huseyin Olgac
2015-03-11 8:56 ` Arend van Spriel
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=54FF7970.10402@erley.org \
--to=pat-lkml@erley.org \
--cc=linux-wireless@vger.kernel.org \
--cc=revanthedarth@gmail.com \
/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).