On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote:
>
> On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote:
> > On Mon, 7 Jul 2014 11:48:36 -0700
> > Adrian Chadd wrote:
> >
> >> I'd just look at porting over the openbsd driver. There's no 11n
> >> support in the openbsd code though
Sweet!
Can you run the same commands above on the Avila board?
Would you mind filing a PR to ensure we get that option into the
relevant kernel(s) ?
(I'm kinda tempted to suggest we auto-select the scaling factor at
startup depending upon physical RAM .. )
-a
On 7 July 2014 12:32, John Hay
On Mon, Jul 07, 2014 at 11:59:03AM -0700, hiren panchasara wrote:
> On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd wrote:
> > On 7 July 2014 11:28, John Hay wrote:
> >> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote:
> >>> On 7 July 2014 10:12, Ian Lepore wrote:
> >>> > On Mon, 2014
On Mon, 7 Jul 2014 12:16:12 -0700
Adrian Chadd wrote:
> On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote:
> > On Mon, 7 Jul 2014 11:48:36 -0700
> > Adrian Chadd wrote:
> >
> >> I'd just look at porting over the openbsd driver. There's no 11n
> >> support in the openbsd code though!
> >
> >
On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote:
> On Mon, 7 Jul 2014 11:48:36 -0700
> Adrian Chadd wrote:
>
>> I'd just look at porting over the openbsd driver. There's no 11n
>> support in the openbsd code though!
>
> That's bad, I hope that the 802.11n protocol will be implemented since
On Mon, 7 Jul 2014 11:48:36 -0700
Adrian Chadd wrote:
> I'd just look at porting over the openbsd driver. There's no 11n
> support in the openbsd code though!
That's bad, I hope that the 802.11n protocol will be implemented since it was
released in 2009.
What do you recommend to do?
>
>
> -
On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd wrote:
> On 7 July 2014 11:28, John Hay wrote:
>> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote:
>>> On 7 July 2014 10:12, Ian Lepore wrote:
>>> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
>>> >> hi,
>>> >>
>>> >> That cal
I'd just look at porting over the openbsd driver. There's no 11n
support in the openbsd code though!
-a
On 7 July 2014 11:46, Carlos Jacobo Puga Medina wrote:
> On Mon, 7 Jul 2014 11:23:52 -0700
> Adrian Chadd wrote:
>
>> On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote:
>> > Hi people,
On Mon, 7 Jul 2014 11:23:52 -0700
Adrian Chadd wrote:
> On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote:
> > Hi people,
> >
> > Does anyone still work to porting the otus driver from OpenBSD?
> >
> > https://github.com/erikarn/otus/tree/master/otus
>
> Nope. I got stuck on trying to figur
On 7 July 2014 11:28, John Hay wrote:
> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote:
>> On 7 July 2014 10:12, Ian Lepore wrote:
>> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
>> >> hi,
>> >>
>> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote:
> On 7 July 2014 10:12, Ian Lepore wrote:
> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
> >> hi,
> >>
> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
> >> fine, but it couldn't allocate the DMA ma
On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote:
> Hi people,
>
> Does anyone still work to porting the otus driver from OpenBSD?
>
> https://github.com/erikarn/otus/tree/master/otus
Nope. I got stuck on trying to figure out how to correctly implement
the synchronous/asynchronous message qu
On 7 July 2014 10:12, Ian Lepore wrote:
> On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
>> hi,
>>
>> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
>> fine, but it couldn't allocate the DMA map.
>>
>> What's the output of "vmstat -z" ? I wonder if it's failing an al
On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote:
> hi,
>
> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
> fine, but it couldn't allocate the DMA map.
>
> What's the output of "vmstat -z" ? I wonder if it's failing an allocation.
>
>
>
> -a
Lack of bounce buffers
On Mon, Jul 07, 2014 at 09:25:34AM -0700, Adrian Chadd wrote:
> hi,
>
> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
> fine, but it couldn't allocate the DMA map.
>
> What's the output of "vmstat -z" ? I wonder if it's failing an allocation.
:~ # vmstat -z
ITEM
hi,
That call is returning ENOMEM. I'm not sure why. It allocated an mbuf
fine, but it couldn't allocate the DMA map.
What's the output of "vmstat -z" ? I wonder if it's failing an allocation.
-a
On 7 July 2014 07:25, John Hay wrote:
> Hi Guys,
>
> I'm further with getting my stuff working
Hi people,
Does anyone still work to porting the otus driver from OpenBSD?
https://github.com/erikarn/otus/tree/master/otus
Regards,
--
Carlos Jacobo Puga Medina
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
Hi,
You have a bug in the "Needs MFC" state which has not been touched in 7 or more
days. This email serves as a reminder that you may want to MFC this bug or
marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a
comment and I won't remind you again
18 matches
Mail list logo
