Wiki Improvement Coordination
Re: Wiki Improvement Coordination
So it's better to just remove it?
Re: Wiki Improvement Coordination
removed it.
- Nutterts
- Member
- Posts: 159
- Joined: Wed Aug 05, 2015 5:33 pm
- Libera.chat IRC: Nutterts
- Location: Drenthe, Netherlands
Re: Wiki Improvement Coordination
If nobody has a problem with it I'll look into updating the raspberry pi page and I guess I could add a barebone for the Go language.
"Always code as if the guy who ends up maintaining it will be a violent psychopath who knows where you live." - John F. Woods
Failed project: GoOS - https://github.com/nutterts/GoOS
Failed project: GoOS - https://github.com/nutterts/GoOS
Re: Wiki Improvement Coordination
Could somebody make a page about the z80 processor? Might be fun for people with a ti-84 calculator.
- BASICFreak
- Member
- Posts: 284
- Joined: Fri Jan 16, 2009 8:34 pm
- Location: Louisiana, USA
Re: Wiki Improvement Coordination
Added content to the "MBR" WiKi, "x86 Examples" Section.
It's a very basic example MBR, actually my current MBR minus the text output - and the actual read sectors function.
I wish it wasn't a code dump, but all the information is already covered in the WiKi article - in great detail I may add.
Best regards,
B!
It's a very basic example MBR, actually my current MBR minus the text output - and the actual read sectors function.
I wish it wasn't a code dump, but all the information is already covered in the WiKi article - in great detail I may add.
Best regards,
B!
BOS Source Thanks to GitHub
BOS Expanded Commentary
Both under active development!
BOS Expanded Commentary
Both under active development!
Sortie wrote:
- Don't play the role of an operating systems developer, be one.
- Be truly afraid of undefined [behavior].
- Your operating system should be itself, not fight what it is.
Re: Wiki Improvement Coordination
Feel free to do so. That's what Wikis are all about.kenod wrote:Could somebody make a page about the z80 processor? Might be fun for people with a ti-84 calculator.
Re: Wiki Improvement Coordination
I don't really know much about it (read none). That's why I posted the message, in case somebody else knows
Re: Wiki Improvement Coordination
It's really a pretty simple processor. The User Manual ought to tell you all you need to know: www.zilog.com/docs/z80/um0080.pdf
Re: Wiki Improvement Coordination
Thanks, I will to try to take a look at it as soon as possible
Re: Wiki Improvement Coordination
I've been slowly working through a more or less complete rewrite of the UEFI page. I'm biased, but I think that UEFI and x86-64 is under-emphasized on the wiki.
I also like Brendan's view of a "tour" through the wiki:
I also like Brendan's view of a "tour" through the wiki:
Brendan wrote:Specifically, I like the idea of something that explains all the options, and branches off to "option specific" pages (which converge again as the reader progresses). For example:
Code: Select all
Intro | Project Goals (e.g. knowing what yours is) | OS types / | \ Monolithic Micro Exo-kernel \ | / Languages/Toolchains / | \ Assembly GCC CLANG \ | / Boot loaders / \ GRUB Roll your own \ / Memory Management . . .
- beyondsociety
- Member
- Posts: 39
- Joined: Tue Oct 17, 2006 10:35 pm
- Location: Eagle, ID (USA)
- Contact:
Re: Wiki Improvement Coordination
I was comparing my mbr code to what basicfreak added to the mbr page and noticed he used 0xfff8 for his real mode stack compared to the usual 0x7c00 as mentioned on that same page. I was just curious as to why he choose that address compared to 0x7c00 which is right below the bootloader.
"I think it may be time for some guru meditation"
"Barbarians don't do advanced wizardry"
"Barbarians don't do advanced wizardry"
- BASICFreak
- Member
- Posts: 284
- Joined: Fri Jan 16, 2009 8:34 pm
- Location: Louisiana, USA
Re: Wiki Improvement Coordination
I chose that location due to where my buffers and variables are, and I know that area is free. You can easily choose 0x7C00, but I use 0x7B80 - 0x7C00 for variables.beyondsociety wrote:I was comparing my mbr code to what basicfreak added to the mbr page and noticed he used 0xfff8 for his real mode stack compared to the usual 0x7c00 as mentioned on that same page. I was just curious as to why he choose that address compared to 0x7c00 which is right below the bootloader.
It doesn't matter where the stack is, as long as it is in valid memory and not interfering with code/data. And all the way threw the OSLoader, 0xA000-0xFFFF is free, while the rest of the segment is assigned a function (use).
I have 4-5 pages in my notebook dedicated to my memory map during the OSLoader, and this was the "best" location I found for the stack. - I cannot wait till my OSLoader is done, what I have on GIT is just not what I want...
BOS Source Thanks to GitHub
BOS Expanded Commentary
Both under active development!
BOS Expanded Commentary
Both under active development!
Sortie wrote:
- Don't play the role of an operating systems developer, be one.
- Be truly afraid of undefined [behavior].
- Your operating system should be itself, not fight what it is.
- beyondsociety
- Member
- Posts: 39
- Joined: Tue Oct 17, 2006 10:35 pm
- Location: Eagle, ID (USA)
- Contact:
Re: Wiki Improvement Coordination
Thanks, I've been getting the urge to work on my os lately and my bootloader needs a rewrite. Seeing all these posts on efi, makes me want to revamp my bootloader and finally add support for efi.
"I think it may be time for some guru meditation"
"Barbarians don't do advanced wizardry"
"Barbarians don't do advanced wizardry"