On Wed, Jan 04, 2006 at 01:35:08PM +0100, Jiri Benc wrote:
On Tue, 03 Jan 2006 18:06:30 +0100, Johannes Berg wrote:
How about
- get rid of all the embedded algorithms (AES, Michael, RC4,
CRC) and use the crypto layer from the kernel
Definitely.
Yes, that is also on my to-do list.
On Tue, 03 Jan 2006 18:06:30 +0100, Johannes Berg wrote:
How about
- get rid of all the embedded algorithms (AES, Michael, RC4,
CRC) and use the crypto layer from the kernel
Definitely.
The list wasn't complete, it was the things that need (from my POV) to
be resolved first only. There
On Wed, 2006-01-04 at 13:35 +0100, Jiri Benc wrote:
The list wasn't complete, it was the things that need (from my POV) to
be resolved first only. There are more issues - some of them are known
to me, including this one, but I have them stored mostly as comments at
corresponding places in my
On Wed, 04 Jan 2006 13:41:43 +0100, Johannes Berg wrote:
Oh another question: is the stack capable of having a raw device
associated with the actual hardware device that sees all incoming and
outgoing frames including 802.11 headers? I'd love to have that for
debugging...
Sure, wlan0ap. It
On 1/4/06, Jiri Benc [EMAIL PROTECTED] wrote:
On Wed, 04 Jan 2006 13:41:43 +0100, Johannes Berg wrote:
The list wasn't complete, it was the things that need (from my POV) to
be resolved first only. There are more issues - some of them are known
to me, including this one, but I have them
On Monday 02 January 2006 09:22, Ivo van Doorn wrote:
Hi rt2x00-devel netdev lists,
First I would like to wish everybody a happy new year!
Secondly I would like to make the announcement that the rt2x00 project
has decided to switch ieee80211 stack used in the rt2x00-beta series.
I'll
On Tue, 2006-01-03 at 04:20 -0500, Michael Wu wrote:
On Monday 02 January 2006 09:22, Ivo van Doorn wrote:
Hi rt2x00-devel netdev lists,
First I would like to wish everybody a happy new year!
Secondly I would like to make the announcement that the rt2x00 project
has decided to switch
On Mon, 2006-01-02 at 15:43 +0100, Jiri Benc wrote:
My todo list currently starts with these items:
How about
- get rid of all the embedded algorithms (AES, Michael, RC4,
CRC) and use the crypto layer from the kernel
- port IPW drivers instead of just moving everything around,
get rid
On Mon, 2 Jan 2006 15:22:37 +0100, Ivo van Doorn wrote:
I don't know if there is a list of known issues with the stack,
but apparently the 80211.ko module doesn't load on a 64bit machine.
My todo list currently starts with these items:
- Don't copy ieee80211_tx_control and ieee80211_rx_status
On Monday 2 January 2006 15:43, Jiri Benc wrote:
On Mon, 2 Jan 2006 15:22:37 +0100, Ivo van Doorn wrote:
I don't know if there is a list of known issues with the stack,
but apparently the 80211.ko module doesn't load on a 64bit machine.
My todo list currently starts with these items:
-
Another thing I notice was that fragments are handed 1 frame at a time, but
making the device
kick the TX-ring after each frame. Shouldn't for fragmented frames the ring
be kicked after the
last fragment has been given to the device?
Good question. It should be guaranteed that no
On Mon, 2 Jan 2006 19:32:42 +0100, Ivo van Doorn wrote:
Perhaps it is an idea to use a similar method as used in the ipw stack,
where the xmit function is passing a list of sk_buffers. This way all
fragments
are passed to the device, and device can place all entries onto the buffer
and kick
12 matches
Mail list logo
