Yeah, you have to pay for the spec...however n2794.pdf (Which you can grab from numerous places on the web) contains the vast majority of that spec (It's an earlier draft). I don't have both so I couldn't say how great the differences are, but AFAIK it's not huge.Candy wrote: As for the practical section, what DO you want in those headers? I don't have the spec, it's not for download @ ISO or something, don't have any books, what am I supposed to use as source for guidelines?
OS Dreamers
-
Curufir
Re:OS Dreamers
Re:OS Dreamers
Ok, thanks for the quick & useful reactions (not here but in email). Thanks Curufir for the zip of the code and thanks Solar for the actual explanation and hints.
An update should be on the way today (added some comments in math.h, and updated one. asin is not an arc cosine
).
Do you want the functions to have descriptions such as those in string.h? If so, I've got myself a nice & big job to do
. This is doxygen/javadoc right?
Greetings, Candy
PS: Might be nice to the creator of this thread if we were to open a pdclib-discuss thread somewhere. Possibly here? it's related to osdev after all...
An update should be on the way today (added some comments in math.h, and updated one. asin is not an arc cosine
). Do you want the functions to have descriptions such as those in string.h? If so, I've got myself a nice & big job to do
. This is doxygen/javadoc right?Greetings, Candy
PS: Might be nice to the creator of this thread if we were to open a pdclib-discuss thread somewhere. Possibly here? it's related to osdev after all...
Re:OS Dreamers
I reopened the SF forum for PDCLib. Seems like the need resurfaces every once in a while.Candy wrote: PS: Might be nice to the creator of this thread if we were to open a pdclib-discuss thread somewhere. Possibly here? it's related to osdev after all...
https://sourceforge.net/forum/forum.php ... _id=328577
Every good solution is obvious once you've found it.
-
aeoj
Re:OS Dreamers
one reason i use windows is that being the most popular os for personal computers, lots of applications have been written (or ported) for it
one reason to use vmware is i wish to run a specific application not available in my current os, without having to reboot - don't care which os is best, just to do my job through alt-tab
alternatively, java applications are famous (to an extent) due to the fact that they need no porting - instead of porting 1000 apps to 100 platforms (1000x100!), you consider writing 100 interpreters
a kernel, no matter how much we want it, is always platform oriented; one level of abstraction would be to seperate platform specific implementations from platform indepedent library calls (two layers kernel); despite probable performance impacts, it would be a lot easier, and a lot safer, when need arises for porting
drivers are a whole another story .. we all know that most often than not, inside a box resides a single processor; every single instruction to be commited it will have to pass from it; if you wish to control a device, you should write specific library functions, embedded in the kernel; the same device, under a different os, will need a seperate set of drivers
and yet, in most cases, these are not simplistic analog devices, they have silicon boards hidden inside! true, they communicate through registers, but, for instance, graphic cards tend to possess a rather powerfull graphics engine - a mission critical processor; and where you can find a processor, you can always find a bios, flash memories, rom; eventually, what lies inside your box is a bonsai network, based on buses, usbs, and staff
life has it, that in networks, to form any kind of communication, you need protocols; protocols that each interested part will follow and respect, unless chaos rules;
that implies, that device specific instructions do not concern tha master processor, the loaded kernel, or the corresponding os - that is the job of the embedded processor; what we need is a generic driver, quering a device for available functions, and providing an interface to the applications' level; from a device's perspective, one couldn't care less for the running os; in its rom would be stored instructions as how to operate, plus instructions as how to communicate (protocols..) with the rest of the machine; noticed anything ?! it is os indepedent ^_^
one reason to use vmware is i wish to run a specific application not available in my current os, without having to reboot - don't care which os is best, just to do my job through alt-tab
alternatively, java applications are famous (to an extent) due to the fact that they need no porting - instead of porting 1000 apps to 100 platforms (1000x100!), you consider writing 100 interpreters
a kernel, no matter how much we want it, is always platform oriented; one level of abstraction would be to seperate platform specific implementations from platform indepedent library calls (two layers kernel); despite probable performance impacts, it would be a lot easier, and a lot safer, when need arises for porting
drivers are a whole another story .. we all know that most often than not, inside a box resides a single processor; every single instruction to be commited it will have to pass from it; if you wish to control a device, you should write specific library functions, embedded in the kernel; the same device, under a different os, will need a seperate set of drivers
and yet, in most cases, these are not simplistic analog devices, they have silicon boards hidden inside! true, they communicate through registers, but, for instance, graphic cards tend to possess a rather powerfull graphics engine - a mission critical processor; and where you can find a processor, you can always find a bios, flash memories, rom; eventually, what lies inside your box is a bonsai network, based on buses, usbs, and staff
life has it, that in networks, to form any kind of communication, you need protocols; protocols that each interested part will follow and respect, unless chaos rules;
that implies, that device specific instructions do not concern tha master processor, the loaded kernel, or the corresponding os - that is the job of the embedded processor; what we need is a generic driver, quering a device for available functions, and providing an interface to the applications' level; from a device's perspective, one couldn't care less for the running os; in its rom would be stored instructions as how to operate, plus instructions as how to communicate (protocols..) with the rest of the machine; noticed anything ?! it is os indepedent ^_^
Re:OS Dreamers
That's called being lazy.aeoj wrote: one reason i use windows is that being the most popular os for personal computers, lots of applications have been written (or ported) for it
Aren't those applications better suited being rewritten? They're slower, their stability depends on the stability of their interpreter, the validity of the interpreter, and they were not designed for the user of that OS. How many people use wine?alternatively, java applications are famous (to an extent) due to the fact that they need no porting - instead of porting 1000 apps to 100 platforms (1000x100!), you consider writing 100 interpreters
I get the feeling you read my OS design documents, but yes, that's a good idea. Put in a bunch of modules in the middle to convert from the very platform specific lowlevel stuff to the highlevel interface, and it's exactly my design.a kernel, no matter how much we want it, is always platform oriented; one level of abstraction would be to seperate platform specific implementations from platform indepedent library calls (two layers kernel); despite probable performance impacts, it would be a lot easier, and a lot safer, when need arises for porting
Call that ACPI, and think about how expensive & slow THOSE interpreters are. I for one don't want an interpreted video card driver nor an interpreted DVD player driver. Think about those thingsdrivers are a whole another story .. we all know that most often than not, inside a box resides a single processor; every single instruction to be commited it will have to pass from it; if you wish to control a device, you should write specific library functions, embedded in the kernel; the same device, under a different os, will need a seperate set of drivers
and yet, in most cases, these are not simplistic analog devices, they have silicon boards hidden inside! true, they communicate through registers, but, for instance, graphic cards tend to possess a rather powerfull graphics engine - a mission critical processor; and where you can find a processor, you can always find a bios, flash memories, rom; eventually, what lies inside your box is a bonsai network, based on buses, usbs, and staff
life has it, that in networks, to form any kind of communication, you need protocols; protocols that each interested part will follow and respect, unless chaos rules;
that implies, that device specific instructions do not concern tha master processor, the loaded kernel, or the corresponding os - that is the job of the embedded processor; what we need is a generic driver, quering a device for available functions, and providing an interface to the applications' level; from a device's perspective, one couldn't care less for the running os; in its rom would be stored instructions as how to operate, plus instructions as how to communicate (protocols..) with the rest of the machine; noticed anything ?! it is os indepedent ^_^
Invariably, when I first saw this OS topic, I had the extremely strong suspicion you opened it. It fits you perfectly.
-
Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:OS Dreamers
nice prose, but how is it connected with the current topic ?aeoj wrote: one reason i use windows (...) it is os indepedent ^_^
btw, would you mind to pick up a single guest name (if you fear registering) rather than generating a random 4/5 letters pattern everytime ? nobody gets fooled by your fanthom behaviour and it just gives us the feeling you have something to hide. Be what you are, not just an IP address
...and at the 'drivers are OS-independent' point, don't count on this. Even the simplest driver need to allocate memory and communicate with the user programs or the kernel modules in some way, and *this* is OS-specific.
You'll better understand what i mean if you get a look at nvidia driver's "sources" for linux or at the Universal Driver Infrastructure work...
-
Schol-R-LEA
Re:OS Dreamers
While Poet's style is highly recognizable, and his antics anusing for a while, I have to agree with Pype. Even when he gives a straight answer, there's a hint of mockery to it; I'm not knocking mockery, mind you - there are plenty of things around that deserve to be mocked - but this hide-and-seek game gets annoying after a while, especially when it is so transparent.
BTW, Poet, look in the lower right-hand corner of your message tell me what you see. You do realize that anyone could trace you from that IP address any time they want, don't you? Even if it's a dynamic address, it should be persistent enough to trace unless you refresh it after each post. Oh, I suppose you could be posting from a public site or have routed through several different sites to hide your tracks, but I doubt it. Peek-a-boo, I see you.
EDIT: I stand corrected; your ISP apparently does not allow you to traceroute into their own network. The last server I could get a trace for was uch-heraklio-ATM.grnet.gr, which tells us nothing (you've already mentioned living in Greece). Very well, then; keep your secrets. I doubt anyone would care if you hadn't made such a point of it in the first place.
BTW, Poet, look in the lower right-hand corner of your message tell me what you see. You do realize that anyone could trace you from that IP address any time they want, don't you? Even if it's a dynamic address, it should be persistent enough to trace unless you refresh it after each post. Oh, I suppose you could be posting from a public site or have routed through several different sites to hide your tracks, but I doubt it. Peek-a-boo, I see you.
EDIT: I stand corrected; your ISP apparently does not allow you to traceroute into their own network. The last server I could get a trace for was uch-heraklio-ATM.grnet.gr, which tells us nothing (you've already mentioned living in Greece). Very well, then; keep your secrets. I doubt anyone would care if you hadn't made such a point of it in the first place.