All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: linux-wireless <linux-wireless@vger.kernel.org>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Helmut Schaa <helmut.schaa@googlemail.com>
Subject: RT2880F based iNIC mini-PCI network card
Date: Sun, 15 Jul 2018 01:37:21 +0200	[thread overview]
Message-ID: <CACRpkdbdt5Jxa+=4kBGEjRdiVwv9Py3Lo5ngxB-sZO-Xgzb09g@mail.gmail.com> (raw)

I'm curious to hear if you have hints of this beast:

lspci:
00:0c.0 Class 0200: 1814:0801

AFAICT this is a ralink Mini PCI using the RT2880F dubbed
"iNIC" (intelligent NIC).

It is found sometimes soldered (!) onto the mini PCI sockets
in a few select routers.

I am trying to us it with D-Link DIR-685, the same mini PCI is
found in Asus DSL-N13, Asus WL-127n, Alcatel Lucent Cellpipe
7130, Pegatron WL227N-5G Wireless Card, and the Billion BiPAC
7800N.

I would try to hack on rt2xxx but I simply have no source code
for this, there are GPL drops for some of the above routers but
they just contain binaries, often in a path like this:
ralink_RT2880_iNIC/v1.1.8.3/build/module-v1.1.8.3

A DD-WRT source tree contained this:
#obj-$(CONFIG_RT2880v2_INIC_MII) += iNIC/mii/
#obj-$(CONFIG_RT2880v2_INIC_PCI) += iNIC/pci/

So there is apparently even a v2 version.

The board photos shows a RT2880F and a RT2850L antenna
driver on the board (the latter in a shield box).

Has someone seen a vendor tree where this leaked out by
mistake or so?

Any other hints to get it going?

I tried just adding the PCI IDs of course. The card reports back
as type "0000" making me suspect it does not behave like all the
others :(

Yours,
Linus Walleij

             reply	other threads:[~2018-07-14 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 23:37 Linus Walleij [this message]
2018-07-22 22:53 ` RT2880F based iNIC mini-PCI network card Linus Walleij

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='CACRpkdbdt5Jxa+=4kBGEjRdiVwv9Py3Lo5ngxB-sZO-Xgzb09g@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=helmut.schaa@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.