From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] rt2x00: new recipe for rt3070 version 2.1.2.0
Date: Sun, 07 Feb 2010 23:10:52 +0100 [thread overview]
Message-ID: <hkndpa$d3j$1@ger.gmane.org> (raw)
In-Reply-To: <20100207204235.GT24852@ibawizard.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-02-10 21:42, Petr Štetiar wrote:
> Koen Kooi <k.kooi@student.utwente.nl> [2010-02-07 20:14:05]:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 27-01-10 20:32, Petr Štetiar wrote:
>>> This patch adds support for rt3070 kernel driver, used for example by the new
>>> Belkin F6D4050v2 USB WiFi stick.
>>
>> How does this differ from recipes/ralink/rt3070_2.1.1.0.bb and why is it
>> in another directory?
>
> Hm, looks like I overlooked this recipe:( I've seen rt61 and rt73 recipes in
> rt2x00 (was searching for packages starting with 'rt') dir and I thought, that
> this dir is appropriate for my recipe also. Anyway rt3070 is called 3070, but
> it's 2870 with some mods, you can see outputs of 2870 in dmesg, even config
> file is called RT2870sta.dat, it's a weird driver but the only option.
>
> There's a difference in my recipe also, I create empty RT2870sta.dat file,
> because I was unable to get it working with it (what a driver reading config
> files from userspace) and I use it with iwconfig successfully.
>
> There's a bug[1] for it and probably can be closed, patch[2] which can be
> discarded also. And FYI the direct links at Ralink's site don't work
> anymore(you've to agree with GNU/GPL EULA :D before downloading it), so I
> kindly asked Laibsch if he could mirror it on OE.
>
> So, should I prepare a patch which will move recipes from rt2x00 dir to ralink
> dir and move my recipe there(newer version)? Thanks for you time reviewing my
> patch.
I have no strong opinion on that, I would only like to keep the wifi of
my touchbook working :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLbzpsMkyGM64RGpERAuweAJsGhuhaZsCgEQquAg12Y9S3VEuQMgCfVXWx
w5x8t7ISW1SOH9Yj0r6vtr0=
=PZcN
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-02-07 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 19:32 [PATCH] rt2x00: new recipe for rt3070 version 2.1.2.0 Petr Štetiar
2010-01-27 19:34 ` Petr Štetiar
2010-02-07 18:12 ` [PATCH v2] " Petr Štetiar
2010-02-07 19:14 ` [PATCH] " Koen Kooi
2010-02-07 20:42 ` Petr Štetiar
2010-02-07 22:10 ` Koen Kooi [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='hkndpa$d3j$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/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