A few NDIS packet allocation bugs were fixed which caused miniports that stored OOB data and accessed the packet extension to corrupt packet data and eventually crash. I've recently fixed some checks in NdisMRegisterMiniport that allows XP intermediate drivers to load. I also fixed sending requests to connection-oriented miniports. I've added NDIS 5.1 exports that we were previously lacking (most notably safe buffer APIs which are required for NDIS 5.1 miniports). Some memory allocation bugs were also fixed. The main problem with NDIS 5.1 drivers is the lack of S/G support in HAL (PRO/100 and PRO/1000 XP drivers are affected by this). The other major problem is the absence of an interrupt resource in the resource list which causes several drivers to fail (real hw rtl8139 is affected by this, but QEMU rtl8139 is not). We have made some major progress with compatibility since 0.3.9. For example, 20 out of 27 tested NICs work (from the wiki).
As you may noticed, May month is over, here is an update on that
month's development plan, and a request to responsible people to
comment on those too.
Crashes were not that rare, I would say they were quite often. Fixed.
On Apr 28, 2009, at 9:25 PM, Aleksey Bragin wrote:
> - USB support for keyboard and mouse devices. Right now, it needs
> fixing the rare crash during booting (bug is bugzilled, comment
> explaining how to solve the problem is attached, some investigation
> remains), and more testing on real hardware.
USB enabled in trunk.
Fixed, uniata enabled in trunk.
> - Uniata support: it solves many problems at once, such as a stupid
> 8Gb limit which is a nonsense for a 2009-year operating system, and
> Serial ATA support, which greatly enhances possible ReactOS usability
> (along with the first item of this list). I use it in my builds
> everyday for more than a month, it works very good. Problems:
> VirtualBox CDROM support (it doesn't recognize it), on my
> realhardware it also experiences similar problems. Bug is also
> bugzilled, a lot of debug logs attached, so everyone can participate.
Situation improved, would be good if Cameron could provide a short
> - Common NICs support: Cameron is doing great work, testers too.
> There are some outstanding problems, which you can see from http://
> www.reactos.org/wiki/index.php/Supported_Hardware/Network_cards
overview of what exactly has been improved, what NICs are supported now.
Johannes - would you comment please, what improvements sound system
> - Sound support: Johannes knows best, but getting any progress with
> sound by 0.3.10 release date is greatly appreciated.
got from 1st of may till today?
Olaf - please comment.
> - Videocards support: Olaf performs some tesitng and bugreporting.
> Third party drivers support is rather weak, http://www.reactos.org/
> wiki/index.php/Supported_Hardware/Video_cards , and usually is
> limited by VMWare's video driver which is being one of the most
> supported through the ReactOS development history.
Olaf and Victor Martinez - please comment.
> Besides of that, Olaf is organizing the Golden Apps testing, so that
> we won't discover regressions occasionally or by the time the release
> is branched and everyone is awaiting, but instead that's going to
> happen on a periodical basis, and he's going to manage this process
> with help of our fellow testers.
Updated release time would be to branch either end of this week or
> Target 0.3.10 release date is month from now on - that means,
> somewhere in the end of May. Certainly, if our goals aren't met, the
> release is going to be rescheduled and that's it, but, I'd like to
> ask to concentrate on the above problems first. They are hard to
> solve when every problem is being approached by one person, but with
> a common effort they aren't going to be a problem.
beginning of the next week. Any objections, comments, proposals?
With the best regards,
Aleksey Bragin.
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev