X-UIDL: 3395 X-Mozilla-Keys: Return-Path: os2-wireless_users-owner@2rosenthals.com Received: from mail.2rosenthals.com (localhost [127.0.0.1] ) by mail.2rosenthals.com (Hethmon Brothers Smtpd) ; Mon, 8 Dec 2003 16:16:39 -0500 Received: from mail1.no-ip.com (mail1.no-ip.com [63.215.241.221] ) by mail.2rosenthals.com (Hethmon Brothers Smtpd) ; Mon, 8 Dec 2003 16:16:37 -0500 X-Envelope-To: Received: (qmail 6147 invoked by uid 89); 8 Dec 2003 19:29:20 -0000 Received: from unknown (HELO basicbox4.server-home.net) (195.137.212.26) by mail1.no-ip.com with SMTP; 8 Dec 2003 19:29:20 -0000 Received: from localhost (D88f1.d.pppool.de [80.184.136.241]) by basicbox4.server-home.net (Postfix) with SMTP id DAD18336971 for ; Mon, 8 Dec 2003 20:29:51 +0100 (CET) X-Mailer: PMMail 2.20.2300 for OS/2 Warp 4.5 In-Reply-To: <3FD3F860.5040305@2rosenthals.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20031208192951.DAD18336971@basicbox4.server-home.net> Date: Mon, 08 Dec 2003 20:31:15 +0100 (MEZ) Sender: os2-wireless_users-owner X-Listname: os2-wireless_users@2rosenthals.com Reply-To: os2-wireless_users@2rosenthals.com From: "Jens Glathe" To: "os2-wireless_users@2rosenthals.com" Subject: [OS2Wireless] Can't copy to/from server X-List-Unsubscribe: Send email to mailusers-request@2rosenthals.com X-List-Owner: mailusers-owner@2rosenthals.com On Sun, 07 Dec 2003 23:04:48 -0500, Lewis G Rosenthal wrote: Hi all, >I realize. What's happening is solely on the client side. > >> The signal strength indicator on WifiState drops to yellow and >>the system locks up and/or becomes sluggish until I get WifiState closed and >>then the system is responsive again. >> >That's interesting to note. With WiFiState closed, if you start a >transfer, does it behave normally? Thinking about this, I recall a note about a PRISM 2.5 hardware error on the linux developer list. Transmit/Receive is using the BAP0 (Base Access Pointer or something like this) register, and IOCTL is using BAP1. I have no real influence on this unless I'd redesign the HCF library. If an access to BAP0 and BAP1 occurs within 5 microseconds, the chip can lock up one or both of the BAP registers (AFAIR) and nothing goes from there. Since 5 microseconds is a pretty short time, but an awfully long time to let the CPU do nothing in between, I don't have a real fix for this. This could happen more often if you have lots of simultaneous transfers going on. A way to fix this would be a keep-alive timer which would check the activity of the registers (and generates some activity itself in case nothing is going on) and resets the whole card if BAP transfers hang. It is on the list. BTW: Does anybody on the list have knowledge how to write a driver with 32-bit ring 0 code? with best regards Jens. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, send a message to steward@2rosenthals.com with the command "unsubscribe os2-wireless_users" in the body (omit the quotes). For help with other commands, send a message to steward@2rosenthals.com with the command "help" in the body (omit the quotes). =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=