[SharpOS Developers] Trunk Status Inquiry

[Bruce Markham]

Due to the lack of regularly scheduled development on the project, combined with the fact that there has still been development, I was hoping that a few of the people involved with changes in the trunk could put together summaries of what they have been working on for the last several months.

The majority of commits have been done by tgiphil - and some of those are larger than they appear because they are merges from sandboxes. LogicalError has also been doing lots of refactoring-type work (based on me just skimming through SVN logs since April). And mrfl has been posting some changes. (Is that grover?)

I think the best way for us to move forward is for us to get an idea of what you guys have been tinkering with. I mean, I can compile and run the kernel - and other than some instabilities (which we've always had, but they've certainly changed over time it seems), running the kernel in and of itself does not reveal much about the changes ("listresources" command is fascinating, but sometimes it makes QEmu lock up...). And frankly, I can't make heads or tails of the architecture from looking at the code anymore. (Which is from enthusiastic efforts on each of you all's parts, but largely seemingly uncoordinated.)

So what I'm really asking is - can each of you three, please take some time to tell us about your work on SharpOS recently? We have the development blog, which has sat untouched since obsethryl's interview. LogicalError already has posting priveleges - so if grover (mrfl?) and tgiphil could send me, privately, a Google Account alias of yours, (feel free to create one, or just send me a personal e-mail of yours that you want to sign in to blogger for SharpOS with), I'll get you guys posting privileges.

After which, I would ask that each of you spend the time, say about an hour, and write up an article on what you've been working on, and more importantly, why. Where it is going. What you want to see happen. And then you can e-mail the mailing list to let us know when you are finished, (preferably linking to the post), so that we can restore an organic feeling of what is going on here.

If you have time for graphics and diagrams, don't let me stop you. However, I'm really thinking all we need is baseline textual thoughts. Mention some classes you've written, some paradigms you are trying to apply, etc. I'm hoping it will make up for a lack of Redmine and regularly-attended-and-documented SharpOS meetings for the last 4 months.

[Zachary Gorden]

I actually have a similar question, and this pertains to the current mapping of the kernel in memory.  Because we don't have anything like ntldr or freeldr, the kernel needs to manually set up its page tables first, kinda like how Linux does it.  If we're following convention, I'll need to remap all of the addresses to their appropriate location in the upper 2GB.

So my question basically is, is there a current map of what the kernel looks like in memory?

[Bruce Markham]

Do not let the temptations of the topic-changers dissuade you!

Please heed my plea and give us all a small bit of colorful commentary on what you've been working on...

[Phil Garcia]

Hi! Thanks for bring this up.

 

I have been tinkering a lot with a device drivers architecture. See my e-mail July 24's email entitled Device Drivers & Attributes for some recent discussion. I have been working on both SharpOS and Ensemble projects. Sharp is a bottom up design, while Ensemble is a top down design. I will not go into the pros and cons of each design and implement approached - both have merits. However, my work at Ensemble is better - but I have been unable to port it back to SharpOS since the AOT is missing some language implementations and still has some serious bugs. To be frank, I'm given up the port due to AOT's limitations until Mike's MOSA compiler is ready. My personal goal is to include a basic device driver framework and some drivers included in the MOSA project.

In regards to Redmine, I have a Unix and Linux background - but no experience with Redmine itself. I had hoped someone with more experience would volunteer and tackle Redmine's stability issues. (Although, I'm thinking about trying Redmine on Windows for fun).

 

-Phil

 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-D...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

[grover]

Bruce,

I'm mrfl on sourceforge. So yes, those are my commits. They're mostly
in my sandbox for a VFS layer and the MOSA compiler. However VFS has
been taken over by Phil as he included a FAT driver in there.

Mike