On Tue, Jun 15, 2010 at 10:02:44AM -0700, Doug Barton wrote:
> On 06/15/10 09:32, Lars Engels wrote:
> > On Tue, Jun 15, 2010 at 09:25:22AM -0700, Rui Paulo wrote:
> >>
> >> On 15 Jun 2010, at 09:17, Lars Engels wrote:
> >>
> >>> On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote:
>
> >
On 06/15/10 09:32, Lars Engels wrote:
On Tue, Jun 15, 2010 at 09:25:22AM -0700, Rui Paulo wrote:
On 15 Jun 2010, at 09:17, Lars Engels wrote:
On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote:
On 15 Jun 2010, at 08:03, Lars Engels wrote:
The issue is still present in r209168.
Wh
On Tue, Jun 15, 2010 at 09:25:22AM -0700, Rui Paulo wrote:
>
> On 15 Jun 2010, at 09:17, Lars Engels wrote:
>
> > On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote:
> >>
> >> On 15 Jun 2010, at 08:03, Lars Engels wrote:
> >>>
> >>> The issue is still present in r209168.
> >>
> >> Which
On 15 Jun 2010, at 09:17, Lars Engels wrote:
> On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote:
>>
>> On 15 Jun 2010, at 08:03, Lars Engels wrote:
>>>
>>> The issue is still present in r209168.
>>
>> Which driver? I works fine with my ath.
>>
>
> ath0: mem 0xd400-0xd400 ir
On Tue, Jun 15, 2010 at 09:00:51AM -0700, Rui Paulo wrote:
>
> On 15 Jun 2010, at 08:03, Lars Engels wrote:
> >
> > The issue is still present in r209168.
>
> Which driver? I works fine with my ath.
>
ath0: mem 0xd400-0xd400 irq 16 at device 0.0 on pci2
ath0: [ITHREAD]
ath0: AR2425 ma
On 15 Jun 2010, at 08:03, Lars Engels wrote:
> On Sun, May 30, 2010 at 07:48:38PM +0200, Lars Engels wrote:
>> On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote:
>>>
>>> On 29 May 2010, at 05:39, b. f. wrote:
>>>
On 5/28/10, Doug Barton wrote:
> On 5/28/2010 4:50 PM, b. f. wro
On Sun, May 30, 2010 at 07:48:38PM +0200, Lars Engels wrote:
> On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote:
> >
> > On 29 May 2010, at 05:39, b. f. wrote:
> >
> > > On 5/28/10, Doug Barton wrote:
> > >> On 5/28/2010 4:50 PM, b. f. wrote:
> > >>>
> > >>> I can't see any problems wh
On 28 May 2010, at 23:03, Doug Barton wrote:
> On 05/28/10 13:18, Doug Barton wrote:
>> I am trying to update -current in order to try kib's patch for the
>> nvidia driver, and the wpi driver won't establish a connection. I'm
>> using r207134 right now without any problems, but that's a long time
On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote:
>
> On 29 May 2010, at 05:39, b. f. wrote:
>
> > On 5/28/10, Doug Barton wrote:
> >> On 5/28/2010 4:50 PM, b. f. wrote:
> >>>
> >>> I can't see any problems when using WPA2 with AES on r208606 i386 with
> >>> uath(4). I'm updating this
On 05/29/10 03:54, b. f. wrote:
On 5/29/10, Rui Paulo wrote:
On 29 May 2010, at 05:39, b. f. wrote:
On 5/28/10, Doug Barton wrote:
On 5/28/2010 4:50 PM, b. f. wrote:
I can't see any problems when using WPA2 with AES on r208606 i386 with
uath(4). I'm updating this machine to r208630 toni
On 5/29/10, Rui Paulo wrote:
>
> On 29 May 2010, at 05:39, b. f. wrote:
>
>> On 5/28/10, Doug Barton wrote:
>>> On 5/28/2010 4:50 PM, b. f. wrote:
I can't see any problems when using WPA2 with AES on r208606 i386 with
uath(4). I'm updating this machine to r208630 tonight, and if I
On 29 May 2010, at 05:39, b. f. wrote:
> On 5/28/10, Doug Barton wrote:
>> On 5/28/2010 4:50 PM, b. f. wrote:
>>>
>>> I can't see any problems when using WPA2 with AES on r208606 i386 with
>>> uath(4). I'm updating this machine to r208630 tonight, and if I
>>> encounter problems with the later
On 5/28/10, Doug Barton wrote:
> On 5/28/2010 4:50 PM, b. f. wrote:
>>
>> I can't see any problems when using WPA2 with AES on r208606 i386 with
>> uath(4). I'm updating this machine to r208630 tonight, and if I
>> encounter problems with the later revision, I'll let you know.
>
> Ok, thanks.
>
>
On 5/28/2010 4:50 PM, b. f. wrote:
I can't see any problems when using WPA2 with AES on r208606 i386 with
uath(4). I'm updating this machine to r208630 tonight, and if I
encounter problems with the later revision, I'll let you know.
Ok, thanks.
Are
you saying that you experienced problems w
>On 05/28/10 13:18, Doug Barton wrote:
>> I am trying to update -current in order to try kib's patch for the
>> nvidia driver, and the wpi driver won't establish a connection. I'm
>> using r207134 right now without any problems, but that's a long time
>> back to try and do a binary search.
>>
>> I
On 05/28/10 13:18, Doug Barton wrote:
I am trying to update -current in order to try kib's patch for the
nvidia driver, and the wpi driver won't establish a connection. I'm
using r207134 right now without any problems, but that's a long time
back to try and do a binary search.
I don't see any ch
I am trying to update -current in order to try kib's patch for the
nvidia driver, and the wpi driver won't establish a connection. I'm
using r207134 right now without any problems, but that's a long time
back to try and do a binary search.
I don't see any changes to wpi or wpa_supplicant betwe
17 matches
Mail list logo
