Return-Path: <linux-wlan-user-owner@www.bitstorm.net>
Received: from fort-point-station.mit.edu by po12.mit.edu (8.9.2/4.7) id MAA04837; Sat, 17 Mar 2001 12:29:07 -0500 (EST)
Received: from www.bitstorm.net (majordom@mail.bitstorm.net [216.230.38.4]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id MAA01918 for <chris@mit.edu>; Sat, 17 Mar 2001 12:29:06 -0500 (EST)
Received: (from majordom@localhost) by www.bitstorm.net (8.9.0/8.9.1) id MAA27111 for linux-wlan-user-outgoing; Sat, 17 Mar 2001 12:13:09 -0500 (EST)
Received: from cx408397-a.irvn1.occa.home.com (IDENT:root@cx408397-a.irvn1.occa.home.com [24.1.175.29]) by www.bitstorm.net (8.9.0/8.9.1) with ESMTP id MAA27106 for <linux-wlan-user@absoval.com>; Sat, 17 Mar 2001 12:13:07 -0500 (EST)
Received: from home.com (IDENT:hjm@localhost [127.0.0.1]) by cx408397-a.irvn1.occa.home.com (8.9.3/8.9.3) with ESMTP id JAA17448 for <linux-wlan-user@absoval.com>; Sat, 17 Mar 2001 09:17:27 -0800
Message-ID: <3AB39C27.D2097E39@home.com>
Date: Sat, 17 Mar 2001 09:17:27 -0800
From: Harry Mangalam <mangalam@home.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.18 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-wlan-user@absoval.com
Subject: Re: [lwlan-user]: Re: linux-wlan-ng-0.1.8-pre5 works  perfectly(?)withOrinoco Silver
References: <Pine.LNX.4.10.10103171709060.11265-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-wlan-user@nightsky.com
Precedence: bulk
Reply-To: linux-wlan-user@absoval.com
X-Evolution: 00000118-0000

Hi Karlis,

Are you implying that the prism drivers work OK on 2.2.18 (with netlink)?  What PCMCIA & wlan version are you using?  What card?  NOt a DLink DWL 650 by any chance? :)


hjm

Karlis Peisenieks wrote:
> 
> On Fri, 16 Mar 2001, Mark S. Mathews wrote:
> 
> > I think this is a issue w/ 2.2.17 and 2.2.18.  I haven't spent much time
> > with them, but I think there's a symbol issue. (DUH!)  I haven't spent
> 
> Everything works fine on 2.2.18. Just netlink (CONFIG_NETLINK) has to be
> enabled.
> 
> Still you have to make sure that you compile wlan with kernel source that
> is configured as your running kernel (due to modversions).
> 
> What is output of commands:
> 
> grep netlink_kernel_create /proc/ksyms
> and
> objdump -r prism2sta_cs.o | grep netlink_kernel_create
> ?
> 
> > One thing I'm considering is not using netlink at all.  I'm thinking about
> > using a Unix domain socket instead of nelink for usermode event
> > notification.  We'll see.
> 
> Why? I suspect you will have a lot more trouble implementing kernel space
> unix socket "server" than making a FAQ with answer to given problem :).
> Especially taking into account that netlink was created exactly for such
> purposes (kernel/user space app communication). Netlink gives clean and
> easy way to iplement kernel-userapp interface for both - kernel side
> (which is the most important thing I guess) and user app.
> 
> I think that it would even be better (read - easier) to make "virtual"
> character device driver that would do this communication rather than using
> unix sockets.
> 
> Karlis
> 
> -----------------------------------------------
> The Linux WLAN User's Mailing List
> For more information about this list see:
> http://www.absoval.com/linux-wlan/lists.html

-- 
Cheers,
Harry

Harry J Mangalam -- (949) 856 2847 (v&f) -- hjm@ncgr.org || mangalam@home.com
-----------------------------------------------
The Linux WLAN User's Mailing List
For more information about this list see:
http://www.absoval.com/linux-wlan/lists.html
