linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryszard <ryszard99@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	Florian Fainelli <florian@openwrt.org>,
	Patrick McHardy <kaber@trash.net>,
	linux-wireless@vger.kernel.org
Subject: Re: virtual access poitns (ath5k/mac80211)
Date: Sat, 21 Aug 2010 13:07:26 +1000	[thread overview]
Message-ID: <AANLkTikanjZf0LEqZjw5toeJz02Tcs6EcAiNdagJh=sQ@mail.gmail.com> (raw)
In-Reply-To: <4C618713.9030303@candelatech.com>

I've managed to compile and get bens kernel installed.  the problem i
had (for future reference) was the physical media not being
recognised.  adding rootdelay=130 to the kernel options seemed to have
fixed that.

On 11 August 2010 03:06, Ben Greear <greearb@candelatech.com> wrote:
> On 08/10/2010 09:54 AM, Luis R. Rodriguez wrote:
>>
>> On Sun, Aug 1, 2010 at 3:21 PM, Ben Greear<greearb@candelatech.com>
>>  wrote:
>
>>> You would not believe how hard it is to keep up with the wireless tree.
>>>  Last time,
>>> by the time we had something stable, upstream had changed too much to
>>> merge.
>>
>> This is why you should not do your development outside of
>> wireless-testing. If you are doing development on a stable kernel tree
>> then you will likely run into huge issues. You should do development
>> on wireless-testing.git, always rebase when John has a new update, and
>> break your changes out into a small changes as possible. If you follow
>> these basic rules I believe you will likely have better luck with
>> keeping your code up to date.
>
> That sounds nice, but at that time I was carrying a lot of other patches
> needed to make my test environment work.  Fortunately, .35 pretty much
> works out of the box, so I can develop on pristine upstream kernels now.
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>

  parent reply	other threads:[~2010-08-21  3:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-01  1:53 virtual access poitns (ath5k/mac80211) Ryszard
2010-08-01  9:37 ` Florian Fainelli
2010-08-01 20:56   ` Ryszard
2010-08-01 22:21     ` Ben Greear
     [not found]       ` <AANLkTi=FEFrKdXUHN-h-BZruvNzSmwXdPcq9-OgZcFAM@mail.gmail.com>
2010-08-02  5:00         ` Ben Greear
     [not found]           ` <AANLkTim8i245P0nGcnpsf63_O8xXeby9re=pX53WfOwV@mail.gmail.com>
2010-08-07  5:23             ` Ryszard
2010-08-08 18:51               ` Ben Greear
2010-08-09 23:58                 ` Ryszard
2010-08-10  0:05                   ` Ben Greear
2010-08-10  0:11                     ` Ryszard
2010-08-10 16:54       ` Luis R. Rodriguez
2010-08-10 17:06         ` Ben Greear
2010-08-10 17:39           ` Luis R. Rodriguez
2010-08-21  3:07           ` Ryszard [this message]
2010-08-23  4:43             ` Ryszard
2010-08-30  2:47               ` Ryszard
2010-08-30 23:52                 ` Ryszard
2010-08-31  0:05                   ` Ben Greear
2010-08-31  0:29                     ` Ryszard
2010-08-31 10:19                       ` Ryszard

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='AANLkTikanjZf0LEqZjw5toeJz02Tcs6EcAiNdagJh=sQ@mail.gmail.com' \
    --to=ryszard99@gmail.com \
    --cc=florian@openwrt.org \
    --cc=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@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).