OSDev Wiki talk:Wish List

Memory Management Wanted

How are we doing the MM page allocations and such? Currently, we've Page_Frame_Allocation. However, if more info is put into this article for each algorithm and such, it would grow too large and broad. Moreover, what about specific methods? (eg. Buddy system.) Any ideas on how this should be structured?--Alboin 19:52, 12 May 2008 (CDT)

I'd go for a stub-and-read-more approach. Pretty much like What order should I make things in?. You can get the templates from there too - Combuster 04:32, 13 May 2008 (CDT)

Theory Vs Code

Articles should be more focused on theory rather than code. Code is welcomed, and is useful for backing up an idea, but too much code leads to people copying and pasting and then give up when it comes to having to think for themselves. Theory is welcome more since it goes into detail about how and why, and is much easier to implement the idea into your OS rather than looking at a bunch of code and try to figure out what the heck they're trying to do. Also, it helps people who are not using Assembly/C/C++. - MessiahAndrw

Agreed. - Combuster 06:33, 14 December 2007 (CST)

Pages For Review

The wish list is a useful place to store ideas and should IMO be placed on the main page where now the PFR message lives. Until then, I'm looking for a check that the PFR tag here can be removed - Combuster 16:49, 27 August 2007 (CDT)

Looks fine here. --Alboin

Placed on main page. - Yayyak 03:39, 20 November 2007 (CST)

Section: Under Construction

IMO Pages Under Construction should be removed (and optionally put in a category, we have templates for that) - Combuster 11:13, 8 March 2007 (CST)

Went ahead for getting no comments - The WIP list was outdated anyway. If you feel offended revert and post comments here. - Combuster 03:52, 26 August 2007 (CDT)

Sections in wanted pages

I've put this section into little subsections, depending on how much we need them. While I don't think anybody will argue with that as an idea (somebody will prove me wrong there :P), perhaps my categorisation of things will be argued on. Go for it. I placed them depending on how easy they are to write, and how much we lack in that area. Yayyak 20:26, 15 September 2007 (CDT)

I moved the HPET topic to the lowest-priority category since it isn't required knowledge for almost all system in current use. Other than that, the ordering looks decent. - Combuster 17:18, 16 September 2007 (CDT)

C++ Runtime Support

This is listed under the Urgent list, but seems to be covered in the newlib part of OS Specific Toolchain. Should it be removed from the urgent list, or do people still want a separate page? -AJ 10:39, 20 November 2007 (CST)

My vote is that we can remove it. Also, there is this: 'More on C++: what support is needed to fully use C++ in a standalone environment? Why? Example code?'. Can this be removed from the non-urgent section, or does this need a proper article on it? - Yayyak 15:43, 20 November 2007 (CST)

I've got rid of the one in 'Urgent' at the moment - anyone who doesn't like this can always re-instate it! I have left the 'fully supporting c++ in a standalone environment', though. My thought behind this is that although we have articles about porting newlib and libsupc++, we don't currently have anything showing how things like exceptions and rtti are actually implemented. -AJ 10:36, 22 November 2007 (CST)