All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Olivetti <luca@ventoso.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Mediatek MT7601U big endian fixes
Date: Wed, 24 Sep 2014 20:49:32 +0200	[thread overview]
Message-ID: <5423123C.5000607@ventoso.org> (raw)
In-Reply-To: <20140924175135.GB31690@tuxdriver.com>

El 24/09/14 19:51, John W. Linville ha escrit:

>> Do you know if is there somebody (at ralink/mediatek or elsewhere)
>> working on integrating this chipset in the in-kernel driver?
>>
>> Bye
>> -- 
>> Luca
> 
> I don't know of anyone from Ralink/MediaTek or otherwise working
> on that.  I sent some emails to MediaTek on this issue recently,
> but I made the mistake of including someone from the community who
> actively undermind my attempts to reach-out to MediaTek...

Oh, that's bad. It's not that the driver doesn't work (it does, once
patched), but it doesn't integrate nicely (i.e. no mac80211 support).

> If you (or anyone else) want to work on integrating device support
> from that driver with the in-kernel drivers then I encourage you to
> do so. 

Unfortunately, I'm not the right person for the job :-(
That's why I asked.

> If you happen to have better contacts with MediaTek than I
> have, then please feel free to reach out to them and/or to put them
> in contact with me.

I don't know anybody at Mediatek, I just contacted them about the issue
through their web form. I didn't think I could fix it by myself. In
fact, I still don't understand why it's necessary to  byte swap
structures that are already defined differently for big endian/little
endian, see the point above about me not being the right person for the
job ;-)


Bye
-- 
Luca

      reply	other threads:[~2014-09-24 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 17:19 Mediatek MT7601U big endian fixes Luca Olivetti
2014-09-24 17:51 ` John W. Linville
2014-09-24 18:49   ` Luca Olivetti [this message]

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=5423123C.5000607@ventoso.org \
    --to=luca@ventoso.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.