Send users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com

or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."


Today's Topics:

   1. Re: Is the
      git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git back
      ? (Matt Chen)
   2. Re: Is the
      git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git back
      ? (Helmut Schaa)
   3. Re: Is the
      git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git back
      ? (Ivo Van Doorn)
   4. Re: Support for Ralink 5370 WiFi USB dongle (Ingvar Hagelund)


----------------------------------------------------------------------

Message: 1
Date: Wed, 9 Nov 2011 18:23:59 +0800
From: Matt Chen <[email protected]>
To: Helmut Schaa <[email protected]>,  Kevin Chou (???)
        <[email protected]>
Cc: joeyli <[email protected]>, [email protected]
Subject: Re: [rt2x00-users] Is the
        git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git back ?
Message-ID:
        <CALx5=V_NoHHLLzfaeSgnL=fjnzm6vhvsuwospfkowegx9h2...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

2011/11/8 Helmut Schaa <[email protected]>:
> On Tue, Nov 8, 2011 at 3:24 PM, Ivo Van Doorn <[email protected]> wrote:
>> _however_ I think this is the nice
>> timing to discuss if we actually still want the tree to return, or that we
>> directly push all our changes towards wireless-testing.
>
> Good point. At the moment we don't have many conflicts and directly pushing
> to John would reduce your workload at least ...
This sounds like we will never need rt2x00 git, so does it mean we
will be supposed to submit patches to linux-wireless ?
If so ....

Hi Kevin,
There may be something changed in the upstream.
And would you please let your RD who work with upstream understand of
this information. If rt2x00 community decide to pick up linux-wirless
instead of rt2x00, your RD should change to submit to  linux-wireless
for their patches. ;-)



> Helmut
>



------------------------------

Message: 2
Date: Wed, 9 Nov 2011 11:36:28 +0100
From: Helmut Schaa <[email protected]>
To: Matt Chen <[email protected]>
Cc: Kevin Chou (???) <[email protected]>, joeyli
        <[email protected]>, [email protected]
Subject: Re: [rt2x00-users] Is the
        git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git back ?
Message-ID:
        <CAGXE3d83G0S7FrAi=POWzeVH3-=8odblo1ahew3cbxuutnc...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2011/11/9 Matt Chen <[email protected]>:
> 2011/11/8 Helmut Schaa <[email protected]>:
>> On Tue, Nov 8, 2011 at 3:24 PM, Ivo Van Doorn <[email protected]> wrote:
>>> _however_ I think this is the nice
>>> timing to discuss if we actually still want the tree to return, or that we
>>> directly push all our changes towards wireless-testing.
>>
>> Good point. At the moment we don't have many conflicts and directly pushing
>> to John would reduce your workload at least ...
> This sounds like we will never need rt2x00 git, so does it mean we
> will be supposed to submit patches to linux-wireless ?

Don't know yet. I'm not against pushing patches directly to
linux-wireless but I'd
prefer to still keep the rt2x00 list CC'ed (or at least the
maintainers directly) for
every patch submission.

It's really up to Ivo to decide since he was doing all the patch
handling before :)
but I don't have a strong opinion for either way.

> There may be something changed in the upstream.
> And would you please let your RD who work with upstream understand of
> this information. If rt2x00 community decide to pick up linux-wirless
> instead of rt2x00, your RD should change to submit to ?linux-wireless
> for their patches. ;-)

rt2x00 git is always very close to Johns wireless-testing tree, so
there shouldn't
be much difference. Only sometimes Ivo keeps some experimental patches for
some time in rt2x00 git before submitting to John.

Helmut



------------------------------

Message: 3
Date: Wed, 9 Nov 2011 11:43:23 +0100
From: Ivo Van Doorn <[email protected]>
To: Helmut Schaa <[email protected]>
Cc: Kevin Chou (???) <[email protected]>, joeyli
        <[email protected]>, [email protected]
Subject: Re: [rt2x00-users] Is the
        git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git back ?
Message-ID:
        <caozox0wurh19qnkykxuaxatyu8_ofyweh0geyn45tf6rgng...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

> Don't know yet. I'm not against pushing patches directly to
> linux-wireless but I'd
> prefer to still keep the rt2x00 list CC'ed (or at least the
> maintainers directly) for
> every patch submission.

Definately!

>> There may be something changed in the upstream.
>> And would you please let your RD who work with upstream understand of
>> this information. If rt2x00 community decide to pick up linux-wirless
>> instead of rt2x00, your RD should change to submit to ?linux-wireless
>> for their patches. ;-)
>
> rt2x00 git is always very close to Johns wireless-testing tree, so
> there shouldn't
> be much difference. Only sometimes Ivo keeps some experimental patches for
> some time in rt2x00 git before submitting to John.

Yeah, but that was simply to keep my experimental patches out in the open,
that might also be solved by me sending more RFC patches. ;)

Ivo



------------------------------

Message: 4
Date: Thu, 10 Nov 2011 00:41:56 +0100
From: Ingvar Hagelund <[email protected]>
To: [email protected]
Subject: Re: [rt2x00-users] Support for Ralink 5370 WiFi USB dongle
Message-ID: <1320882116.3355.5.camel@lardal>
Content-Type: text/plain; charset="UTF-8"

* Gertjan van Wingerde 
> > > So, the RF chipset if properly reported here.
> > > 
> > > Also note that the RF chipset identification was not a guess, as this 
> > > code was submitted by Ralink
> > > themselves.
> > > 
> > > I seem to recall that you are running on a PPC32 platform, is that 
> > > correct?
> > > 
> > > Would it be possible for you to connect the device to an x86 based 
> > > platform, to make sure that we
> > > aren't running in some strange BE related problem?

* Ingvar Hagelund
> Built on a fedora 15 laptop running a 3.1.0 kernel from fedora 16 on x86_64. 
> Driver seems to work well, and I get decent speed over WPA2, at least 12Mbps.
> 
> This is with no patches, just latest compat-wireless. So this might mean that 
> the problems I saw may have been related to the 32bit ppc arch specifically.

So, this could be related to endianess. I'm willing to work with this
and do testing, though I'm not much of a coder. I had a look at the code
that does endian "decoding" when necessary, and it seems that those
parts were merged earlier this fall.

So ... I'm a bit at a loss here. What should I do? I could try to remove
the endian bit-juggling here and there, and check if the RF chipset
changes, perhaps. Any other suggestions?

Ingvar





------------------------------

_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com


End of users Digest, Vol 33, Issue 8
************************************

Reply via email to