Ros-dev

ros-dev@reactos.org

5788 discussions

Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change, waste more stack space.

by Aleksey

----- Original Message ----- From: "Alex Ionescu" <ionucu(a)videotron.ca> To: <ros-dev(a)reactos.org> Sent: Tuesday, April 24, 2007 7:44 AM Subject: Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change,waste more stack space. > Perhaps you could try convincing the GCC folks to actually properly > support declspec_align like MSVC does, instead of claiming to support it, > but actually ignoring it. Then you could also convince them to support > SEH, PDBs, STDCALL-default calling convention, etc ;) Speaking of PDB, there is a person who is doing a PDB generator from the debug info gcc generates (No idea whether he's subscribed to this llist, probably not). But it looks like he's having some progress. The tool will be file rossym, but the output will not be an embedded rsym section, but a .pdb file [hopefully] readable by WinDBG. WBR, Aleksey Bragin.

17 years, 5 months

Re: [ros-dev] [ros-diffs] [dgorbachev] 26482: Use allocation function instead of hack, save 12 bytes.

by Thomas Weidenmueller

This change is *wrong*. It won't guarantee the correct alignment!!! - Thomas dgorbachev(a)svn.reactos.org wrote: > Author: dgorbachev > Date: Tue Apr 24 02:06:34 2007 > New Revision: 26482 > > URL: http://svn.reactos.org/svn/reactos?rev=26482&view=rev > Log: > Use allocation function instead of hack, save 12 bytes. > > Modified: > trunk/reactos/ntoskrnl/include/internal/ex.h > > Modified: trunk/reactos/ntoskrnl/include/internal/ex.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/… > ============================================================================== > --- trunk/reactos/ntoskrnl/include/internal/ex.h (original) > +++ trunk/reactos/ntoskrnl/include/internal/ex.h Tue Apr 24 02:06:34 2007 > @@ -102,22 +102,13 @@ > #define MAX_HIGH_INDEX (MID_LEVEL_ENTRIES * MID_LEVEL_ENTRIES * LOW_LEVEL_ENTRIES) > > // > -// Detect GCC 4.1.2+ > +// Detect GCC > // > -#if 1 // (__GNUC__ * 10000 + __GNUC_MINOR__ * 100 + __GNUC_PATCHLEVEL__) < 40102 > - > -// > -// Broken GCC with Alignment Bug. We'll do alignment ourselves at higher cost. > -// > -#define DEFINE_WAIT_BLOCK(x) \ > - struct _AlignHack \ > - { \ > - UCHAR Hack[15]; \ > - EX_PUSH_LOCK_WAIT_BLOCK UnalignedBlock; \ > - } WaitBlockBuffer; \ > - PEX_PUSH_LOCK_WAIT_BLOCK x = (PEX_PUSH_LOCK_WAIT_BLOCK) \ > - ((ULONG_PTR)&WaitBlockBuffer.UnalignedBlock &~ 0xF); > - > +#ifdef __GNUC__ > + > +#define DEFINE_WAIT_BLOCK(x) \ > + PEX_PUSH_LOCK_WAIT_BLOCK x = __builtin_alloca(sizeof(EX_PUSH_LOCK_WAIT_BLOCK)); > + > #else > > // > @@ -125,8 +116,8 @@ > // local variable (the actual pointer) away, so we don't take any perf hit > // by doing this. > // > -#define DEFINE_WAIT_BLOCK(x) \ > - EX_PUSH_LOCK_WAIT_BLOCK WaitBlockBuffer; \ > +#define DEFINE_WAIT_BLOCK(x) \ > + EX_PUSH_LOCK_WAIT_BLOCK WaitBlockBuffer; \ > PEX_PUSH_LOCK_WAIT_BLOCK x = &WaitBlockBuffer; > > #endif > @@ -725,7 +716,7 @@ > if (InterlockedBitTestAndSet((PLONG)PushLock, EX_PUSH_LOCK_LOCK_V)) > { > /* Someone changed it, use the slow path */ > - DbgPrint("%s - Contention!\n", __FUNCTION__); > + // DbgPrint("%s - Contention!\n", __FUNCTION__); > ExfAcquirePushLockExclusive(PushLock); > } > > @@ -763,7 +754,7 @@ > if (ExpChangePushlock(PushLock, NewValue.Ptr, 0)) > { > /* Someone changed it, use the slow path */ > - DbgPrint("%s - Contention!\n", __FUNCTION__); > + // DbgPrint("%s - Contention!\n", __FUNCTION__); > ExfAcquirePushLockShared(PushLock); > } > > @@ -977,7 +968,7 @@ > OldValue.Ptr)) > { > /* We have waiters, use the long path */ > - DbgPrint("%s - Contention!\n", __FUNCTION__); > + // DbgPrint("%s - Contention!\n", __FUNCTION__); > ExfReleasePushLock(PushLock); > } > } > > >

17 years, 5 months

Re: [ros-dev] Legal Vista DVD free of charge

by theUser BL

Here the direct links to it: 64bit version: http://www.mediaonline.de/shop/product_5000_5000_-3_408234_5000.11951.12528… 32bit version: http://www.mediaonline.de/shop/product_5000_5000_-3_408232_5000.11951.12528… _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

17 years, 5 months

Legal Vista DVD free of charge

by theUser BL

Hi ReactOS-people! If you are from germany and are interested in Vista, then have a look at http://www.mediaonline.de/ There you can "buy" Microsoft Windows Vista Intallation DVDs 32bit and 64bit, german version, for 0 ! You only pay for shipment. This is already annonced on some places here in the internet. But if you still don't know it, I only want to tell it. The only problem: It comes without a key. It is only the Installation DVD, only the software - without key. But the DVD is legal! It is, if you have lost your DVD or if it is damaged or anything else, then you can together with you key again installing Vista. And if you have not a key, possible is it legal to test it 30 days, after it then shut down automatical. You can for example test it on an virtual machine, try to create some programs, which uses Vista-functions and run only on Vista, but not on XP. And then trying to let ReactOS also run this programs, which only runs on Vista. But for that better read the EULA, which is legal and which is not. But the DVDs are free of charge and legal. Greatings theuserbl _________________________________________________________________ Haben Spinnen Ohren? Finden Sie es heraus mit dem MSN Suche Superquiz via http://www.msn-superquiz.de Jetzt mitmachen und gewinnen!

17 years, 5 months

Re: [ros-dev] Boot Rev 26382

by Aleksey

Uhm, yes, specifically, cromwell's usb 2.4/2.5 stack + wrapper lack synchronization somewheh (AFAIR). I tried to fix all that in the usb 2.6 attempt, however I don't have motivation anymore, since adapting woodhead's usb stack into reactos, which *just works* :-). It will be even better when usb storage devices support will be finished too. And then, with time, we can implement a proper Win2k3 USB drivers stack, including HID devices. WBR, Aleksey. ----- Original Message ----- From: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> To: "ReactOS Development List" <ros-dev(a)reactos.org> Sent: Thursday, April 19, 2007 11:44 PM Subject: Re: [ros-dev] Boot Rev 26382 > Hi! > Aleksey wrote: >> I will finally move those cromwell usb drivers somewhere so they won't be >> installed even by "make install" :-) >> >> WBR, >> Aleksey Bragin. > > It's due to the new kernel structure, I would think. If and when I get > time I can > check into it. No telling when. > Thanks, > James

17 years, 5 months

Re: [ros-dev] A New RosBE made by me

by Aleksey

> OT: > Did we decide to place RosBE in our svn? Did the question ever come up? > Thanks, > James Do you mean the src code of the RosBE? It should already be there. As for binaries - as always we put them to sf.net. WBR, Aleksey.

17 years, 5 months

Re: [ros-dev] Boot Rev 26382

by Aleksey

I will finally move those cromwell usb drivers somewhere so they won't be installed even by "make install" :-) WBR, Aleksey Bragin. ----- Original Message ----- From: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> To: "ReactOS Development List" <ros-dev(a)reactos.org> Sent: Wednesday, April 18, 2007 10:47 PM Subject: Re: [ros-dev] Boot Rev 26382 > Hi! > I did get it to boot by removing the usb drivers. > 8^D > James

17 years, 5 months

Re: [ros-dev] Ros-dev Digest, Vol 32, Issue 12

by Lucio Diaz

Aleksey Bragin wrote: --------------------------- That shows you really did not even slightly investigated how the website works. And instead you're proposing a whole workflow for developers, so they mandatory spent a few hours per week maintaining all the stuff you. During that 2 years you should have spent just a bit of time, even 20 minutes, to overview our website and systems we have there, and another 20 minutes to read online manuals/help for them. Excuses like "I didn't have time" hardly apply here. ------------------------- -Irony on- I suppouse that copying each individual resource file, every time it is updated, dont waste developers time.-Irony off- It is your operating system, your servers and your time, you can do as you please. It is not my intention to propose a whole workflow to developers, i only sugested an idea for an easy to use translation tool, noone have to waste time, something similar to the compilation environments, and the IDEs, but some people prefer making things by hand in the command line, but again, is your os and your time, i will decide what to do with my time and if i can or i want to use bugzilla. I feel molested by your tone, i have spent more time on reactos than what you could imagine, but thats not the matter, i think this is a good project, with a great goal, i believe that the easier for everybody to get involved, the best for the project, and my sugestion was going in that direction. I have read the ML for years, and almost never posted a word, i dont have the skill to help much, but offer what "i can", you can take it or not. Regards, Lucio Diaz. ____________________________________________________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com

17 years, 5 months

Tr : [Qemu-devel] Re: QEMU drivers repository

by Sylvain Petreolle

May these VESA drivers be useful for ros testing ? ----- Message transféré ---- De : Jan Jezabek <jezabek(a)poczta.onet.pl> À : qemu-devel(a)nongnu.org Envoyé le : Mercredi, 18 Avril 2007, 21h25mn 40s Objet : [Qemu-devel] Re: QEMU drivers repository Natalia Portillo wrote: > Hi all, > I have collected all drivers I could for GD-5446 in > http://www.claunia.com/qemu/drivers/index.html > Hi, If you're interested in NT 3.51 you can find a graphics driver here: http://www.navozhdeniye.narod.ru/vbemp.htm It's a generic VESA driver, but it was the only one I could find that supported high resolution true-color display in NT 3.51, so maybe it's worth to put a link on your page. As for network - I had a good experience with the Realtek 8029 drivers: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=15&PFi… WBR, JJ

17 years, 5 months

Re: [ros-dev] DbgPrint() - DPRINT() - DPRINT1()

by Aleksey

Hi Peter, it's a good idea to post an explanation here (might be someone will edit this into a page in our wiki). 1. Traditional DPRINT debug printing ("old way"): All source code files have an #define NDEBUG atop of them, a developer could get a detailed tracing of function calls inside this src code file. DPRINT1()s are used when that code branch must always notify a user / developer (examples are: critical error, not fully implemented branch with a reminder to finish implementation, and any other kind of a situation which occurs rarely and may have a severe impact on a system). 2. "Wine-way" of debug print messages. The printing is done using three macros: TRACE(), WARN(), ERR(). Respectively, TRACE() is the most frequently printed, WARN() is less frequently, and ERR() is an equivalent of a DPRINT1() - always printed, in error situations. In order to enable TRACE() and WARN() debug prints, one must add a #define YDEBUG to the respective place inside an interesting source code file. (Wine has a concept of debug channels, which can be turned on and off, however ReactOS for now does not implement this). 3. Other ways exist, specific for drivers / applications (e.g. for miniport / port / class drivers, client drivers usually use their class's driver's debug print routine, a custom one, having custom severities levels). 4. Newer ways of debug printing (kernel-specific, look for debug channels in windows 2003, debug printing in Vista, -- OSR magazine had a nice article about these). WBR, Aleksey Bragin. ----- Original Message ----- From: <breakoutbox(a)web.de> To: <Ros-dev(a)reactos.org> Sent: Thursday, April 19, 2007 4:21 PM Subject: [ros-dev] DbgPrint() - DPRINT() - DPRINT1() > Hello, > > can please anybody explain me how You want DbgPrint() - DPRINT() - > DPRINT1() to be used ? > I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but > it is not shown on serial debug (?) > (and also SOME ot these DPRINT1() .. ) > > 1) > If I use DPRINT1() instead, it is always shown. > If I use DbgPrint() instead, it is only shown when #DEBUG is defined in > the file + in *.rbuild > But what's the sense of DPRINT() then ? > => > > 2) > 2nd stage: on installing from BootCD I can see serial debug only when I > select DEBUG from startup options. > Is this DPRINT1() suppressed when I DON'T select DEBUG ? > > 3) > Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in > other files in /DRIVER/ and /NTOSKRNL/ ..) ? > I now have to change every serial debug output to be able to see anything > .. ( if You don't explain me ... ;-) ) > > > Best regards, > Peter.

17 years, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev