|
From: Michael B. <mb...@fe...> - 2002-10-15 18:55:11
|
On Wed, 2 Oct 2002, Boris wrote: > Yes, its true. You can make $500can [Because I live in canada] just to > get the Prism2_pci driver working properly. Yes, The prism2_pci driver > works but *only* for small bootable images. Anything larger then > around 18-20mb's causes errors to occur. Im sure you are asking why > not just make smaller images but thats not what we want to do. The > Realtek 8029 and Realtek 8139 driver boots up our 42mb images no > problem but the Prism2_pci driver doesn't. We will pay for anyone to > properly correct this issue. Not a quick hack but a proper fix. If the > driver is working properly then what is causing it stop working. > [Check out our specs]. More information can be found on our website > [Just a quick website ]. > Check out http://www.thinovations.com/wireless/ OK, this issue is now resolved. A working version for 5.0 is in CVS. The fix has been ported to 5.1 and checked in but not yet tested (it's simple enough that I don't expect any problems). The cause of the problem is that the Prism2 card receives a constant stream of INFO events during the download. The driver was ignoring these events, since it isn't sophisticated to do anything with the information that they contain anyway. However, for each INFO event, the Prism2 allocates an internal buffer that holds the actual information. It expects the driver to read this buffer and then acknowledge the event, thereby freeing up the buffer. Since the Etherboot driver was completely ignoring the INFO events, over the course of time the Prism2 would exhaust its buffer space. This was only visible on very large images (~20MB and more). The solution was simple: simply acknowledge the INFO events as they occur. We still ignore the contents of the events, but acknowledging them frees up the buffers and so the internal storage does not become exhausted. Problem solved. Michael Brown http://www.fensystems.co.uk |
