On Dec 27, 2007 8:34 AM, Bruce Markham <[EMAIL PROTECTED]> wrote:
> PCI configuration information is located by writing a UInt32 (a combination
> of bus, slot, device sub-function, and the index of the UInt16 you want to
> read from the config data), to port 0xCF8. And then the UInt16 that you
> targeted can be read from port 0xCFC. Write parameters to one port, to read
> a specific value from another. The parameters vary based on where the device
> is at, and how you are trying to use it.
Well singularity uses a signature attribute at the class level like this:
[Signature("/pci/03/00/5333/8811")]
which contains the pci information about the device, this can then be
used to initialize the
ports and memory..
sorry if i'm being vague, i'd have to read up on pci specs before i
could say something more precise about how this could be done
semantically & in actuall code.
> I was just curious if you could brainstorm a semantic for it, since your
> brain is already on the right track for this idea.
>
> I mean, I know we *could* do this, *somehow*. I was j/c if you could think
> of anything.
>
> This is an awesome idea. The only problem is, I fear that in order to do it
> right, we'll have to wait a while before we do it. (I mean, the JIT/AOT
> could totally be augmented to do all this for us, leaving C# code generation
> completely out of the picture.)
Well that would be the ideal way of doing things eventually (security
wise), but for now we could use a tool which simply generates some c#
files..
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
