Ros-dev

ros-dev@reactos.org

1 participants
5790 discussions

by Aleksey Bragin

I didn't thoroughly look through the OSS source code, but if it has some kind of platform-independent design in mind, then I would really recommend porting, and porting with as minimal changes to the original source code required (you probably are going to need a wrapper-library, for ioctls at least, plus NT-specific parts). I may help too, because of the usb stack wrapping I did a while ago. WBR, Aleksey Bragin. > > I've been in touch with the guy that ported OSS to Haiku (open- > source BeOS) > after some > discussion with the folks over at #winehackers to get some help > with audio > development. > > Anyway, basically the idea so far is to use OSS as a "fall-back" audio > driver > implementation. So unless there is a "better" driver installed (ie an > official one for > an audio device), ReactOS can use an Open Sound System driver instead. > > The result? There will at least be sound functionality. > > OSS is designed to be mostly platform-independent. By rewriting a > few of > the core > modules, the entire set of drivers will be able to work with whatever > platform you > desire. > > This can be implemented on top of the existing MME API architecture > for the > moment, and > can later be translated to use the WDM audio framework. > > Anyway, having stuck the OSS code into my local ReactOS source > tree, I'm > trying to > figure out how to get it to compile using rbuild. The first hurdle > I have > come across is > that there is extensive use of ioctl. Indeed it seems that most > ports of > OSS work on > platforms based on Posix (Unix?) > > So my main question at this time is how to handle this? The calls in > question appear to > be documented inside a file called "soundcard.h" in the OSS sources > however > this just > seems to be definitions for the ioctl codes. So I suspect a > majority of the > drivers are > calling ioctl. > > Therefore, I figure the best way around this is probably to provide > a fake > ioctl that > provides the expected functionality, and make this wrap > DeviceIoControl > with something > that can translate the ioctl parameters into whatever... > > The only other way I see around this is to rewrite all calls to > ioctl, and > rewrite the > IOCTL codes with NT-style ones. > > Thoughts/ideas?

17 years, 11 months

Re: [ros-dev] rbuild and HALs module optimization

by Aleksey Bragin

David, what does a kernel-dev have to do with rbuild? Also, recent massive commits to the rbuild itself, and to various .rbuild files hardly prove your "rbuild is an umaintained piece of ... stuff" theory. It's, by the least measure, offensive to Herve's (and there were a few different patches submitted by various authors submitted) work he's been doing with rbuild. Or what is a "maintained rbuild", by your definition? How more should it be maintained? Note: not improved (we have a number of improvements pending to be implemented in it), but *maintained*. Another thing is completely wrong and counter-productive: irc is a wrong place for such question, since not all devs are there all the time. Now, back to the actual question. The biggest difference between ntoskrnl and HAL is that the first is as machine-independent as possible (still including some dependent code, but it's conditionally included), while the latter is actually very hardware dependent, so it does not make sense to unite x86 and PowerPC HALs, because they are going to contain just simply different source code. With the best regards, Aleksey Bragin. On Sep 21, 2007, at 8:11 PM, David Hinz wrote: > > Marc Piulachs schrieb: >> Does anyone agree with me on this? Maybe I’m missing something >> here but >> I would like to improve it. > > I don't think you will have much luck getting an answer, as afaik > rbuild > is currently more or less unmaintained and our kernel-dev left the > project. > > Maybe arty or hpoussin do have an oppinion regarding your question, > but > they seem to be rather busy most of the time... > > Have you tried asking on irc? Most devs hang out there... > > Greets, > > David Hinz

17 years, 11 months

Open Sound System porting

by reactos-development＠silverblade.co.uk

Hi guys, I've been in touch with the guy that ported OSS to Haiku (open-source BeOS) after some discussion with the folks over at #winehackers to get some help with audio development. Anyway, basically the idea so far is to use OSS as a "fall-back" audio driver implementation. So unless there is a "better" driver installed (ie an official one for an audio device), ReactOS can use an Open Sound System driver instead. The result? There will at least be sound functionality. OSS is designed to be mostly platform-independent. By rewriting a few of the core modules, the entire set of drivers will be able to work with whatever platform you desire. This can be implemented on top of the existing MME API architecture for the moment, and can later be translated to use the WDM audio framework. Anyway, having stuck the OSS code into my local ReactOS source tree, I'm trying to figure out how to get it to compile using rbuild. The first hurdle I have come across is that there is extensive use of ioctl. Indeed it seems that most ports of OSS work on platforms based on Posix (Unix?) So my main question at this time is how to handle this? The calls in question appear to be documented inside a file called "soundcard.h" in the OSS sources however this just seems to be definitions for the ioctl codes. So I suspect a majority of the drivers are calling ioctl. Therefore, I figure the best way around this is probably to provide a fake ioctl that provides the expected functionality, and make this wrap DeviceIoControl with something that can translate the ioctl parameters into whatever... The only other way I see around this is to rewrite all calls to ioctl, and rewrite the IOCTL codes with NT-style ones. Thoughts/ideas? -------------------------------------------------------------------- mail2web.com - Microsoft® Exchange solutions from a leading provider - http://link.mail2web.com/Business/Exchange

17 years, 11 months

Documentation

by Colin Finck

Hello, Recently, some developers wrote documentation about certain stuff related to ReactOS. But this documentation was only placed on their own web servers. In my opinion, it would be better if such stuff would (also) be committed to the "documentation" directory in SVN. Having documentation there makes sure that it does not get lost. Additionally, if the source file is committed (not a PDF or something like that), another person could extend the documentation further. I agree that not all documentary stuff needs to be on SVN. An example might be Magnus' Win32k syscall tables. But for example Andrew Greenwood's documentation about the Windows Multimedia Subsystems looks like something, which should be committed in my opinion. If you don't agree on committing this stuff, it would be nice if we could at least agree on an official document format, which should be used in the SVN tree. >From what I see, most documentations were created by using OpenOffice, so I think the OpenDocument Text format (ODT) would be a great choice. It is also supported by most word processors, thus most people should be able to open an ODT file. Up to now, I used RTF for formatted text documentations in SVN, but this format does not support things like shapes. Regards, Colin

17 years, 11 months

Re: [ros-dev] Bugzilla's bug assigning process

by Aleksey Bragin

There is a list linked from that wikipage, which has a simple 1:1 relationship between developer and some development area. If it's wrong, please edit it. WBR, Aleksey Bragin. On Sep 21, 2007, at 3:04 AM, Ged wrote: > Aleksey Bragin wrote: >> If there are any questions, please post them right away here. >> > > How are these bugs being assigned? > I've been watching and most of the bugs which have been assigned have > been assigned to the wrong developer. > > Ged.

17 years, 11 months

rbuild and HALs module optimization

by Marc Piulachs

If we don't have a ntoskrnl rbuild module for every supported architecture I don't understand why we do have a separate HAL rbuild module for every architecture (X86 , PowePC) and sub architecture (x86-Generic , x86-xbox , PowerPC-Generic) Currently we have a very complicated logic to compile the appropriate HAL with conditions (IF) and alias that point to the correct module for the target architecture. At the end always two dlls are going to be generated for every architecture hal_up and hal_mp so what's the reason to have a specific module for every architecture and not two generic modules that represent the two possible HAL modes (uniprocessor and multiprocessor) that dynamically include the appropriate source code for the platform (Architecture + Sub Architecture) being build? For example : <module name="hal_generic" > (common code to all architectures, sub architectures , UP and MP HALs) </module> <module name="hal_up" installname="halup.dll"> <library>hal_generic</library> <library>.. (common files to all UP HALs) <if property="ARCH" value="i386"> (X86 common files to all X86 UP HALs) <if property="OARCH" value="xbox"> (xbox specific files) </if> </if> </if propery="ARCH" value="powerpc"> (PPC common files) </if> </module> And the same for multiprocessor <module name="hal_mp" installname="halmp.dll" /> both files can be simply copied to the install cd and usetup will install the correct HAL renamed as hal.dll depending on the user selection. IMHO it greatly simplifies the process and is a more elegant solution than the current one.

17 years, 11 months

Bugzilla's bug assigning process

by Aleksey Bragin

Hello, as you may already noticed Amine started his work as a bugzilla maintainer today, and some people were surprised by bugs being assigned to them. Amine does a preliminary bugs assignment, according to developers' work history in ReactOS. You are free to reassign to another dev, or reasign back to Ros-bugs(a)reactos.org if you don't want to fix that bug. Also, it's very important that you put your valid email address to the bugzilla account, so that it works correctly and emails you when needed. If there are any questions, please post them right away here. With the best regards, Aleksey Bragin.

17 years, 11 months

Re: [ros-dev] Documentation

by Aleksey Bragin

Not a problem, but this should be done on a standalone machine, preferably the server at Christoph's place, or I can utilize my own machine for this too. WBR, Aleksey Bragin. On Sep 20, 2007, at 6:00 PM, Ged wrote: > Timo Kreuzer wrote: >> So we should think about updating our >> doxygen and probably keeping it at a quite up to date state (only >> a few >> days old if possible). > > I fully agree. > Aleksey, is there any reason this can't be stuck in a cron job and run > weekly? > Doxygen is a great tool which we can't really make much use of at the > moment. > > Ged.

17 years, 11 months

29102 - Fix an old rbuild bug: .gch file now depends of intermediate module directory, and can create it if needed

by Timo Kreuzer

Revision: 29102 Autor: hpoussin Datum: 11:34:05, Mittwoch, 19. September 2007 Meldung: Fix an old rbuild bug: .gch file now depends of intermediate module directory, and can create it if needed ---- Verändert : /trunk/reactos/tools/rbuild/backend/mingw/modulehandler.cpp Does this fix bug 2369? http://www.reactos.org/bugzilla/show_bug.cgi?id=2369

17 years, 11 months

Re: [ros-dev] Problems with resources or something else

by carlo.bramix

Hello, I saw the bug #2225. In my opinion the bug isn't into the CopyImage() but into DrawIconEx() instead. I checked the copyico test app and after debugging a little I discovered that CopyImage() received an already corrupted pixel map. But probably, this fact is known to you too. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Fri, 14 Sep 2007 21:14:55 +0200 Subject : Re: [ros-dev] Problems with resources or something else > Hi, > > This problem has nothing to do with resource compilation. > It's a bug in our CopyImage function, which exists since some time. If you > try the current builds from our BuildBot, you will have the same problem. > > Regards, > > Colin > > > > -----Original Message----- > > From: ros-dev-bounces(a)reactos.org > > [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix > > Sent: Thursday, September 13, 2007 10:22 AM > > To: ros-dev > > Subject: [ros-dev] Problems with resources or something else > > > > Hello, > > it's long time that I compile ReactOS and I have some errors > > into the start menu bar. > > My results are almost identical to this screenshot: > > > > http://www.reactos.org/media/screenshots/2007/ros_033_xara3d.jpg > > > > As you can see, the two icons after the start button and the > > '1','2','3','4' buttons are corrupted. > > Actually I'm using the windres.exe that I received from here: > > > > http://www.reactos.org/archives/public/ros-dev/2007-July/009548.html > > > > Do you have some idea? > > > > Sincerely, > > > > Carlo Bramini > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

17 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev