Neil
> Date: Thu, 27 Dec 2007 09:41:11 +0100> From: [EMAIL PROTECTED]> To:
> sharpos-developers@lists.sourceforge.net> Subject: Re: [SharpOS Developers]
> LogicalError: DiskDriverKernel> > On Dec 27, 2007 8:34 AM, Bruce Markham
> <[EMAIL PROTECTED]> wrote:
Actually I planned to make it work by the end of next week, but
unfortunately some other stuff
came up so it will be delayed ... no idea for how long. Hopefully only
2-3 weeks.
Chriss.
Sander van Rossen wrote:
>> Creating a simple SEH should be easy, simply make a calling convention
>> that put
Sander van Rossen wrote:
> While working on the floppy controller driver code i noticed that
> there are so many error conditions it's not even funny anymore..
> Having exception handling would *really* help keeping the code clean...
> how easy/hard is it to implement exception handling support
Sander van Rossen wrote:
>> Creating a simple SEH should be easy, simply make a calling convention
>> that put the pointer to the exception on the stack. After every method
>> call look for that exception and catch/return.
>>
>
> Allright, then the next question is: how far along are we with
>
> Creating a simple SEH should be easy, simply make a calling convention
> that put the pointer to the exception on the stack. After every method
> call look for that exception and catch/return.
Allright, then the next question is: how far along are we with
implementing type information and object
Sander van Rossen wrote:
> On Dec 27, 2007 3:40 PM, Jonathan Chayce Dickinson
> <[EMAIL PROTECTED]> wrote:
>
> [...]
> Sorry, i wasn't clear.. i mean after we implemented object instancing
> etc. how hard would it be to implement exception handling?
>
>
Creating a simple SEH should be easy, s
On Dec 27, 2007 3:40 PM, Jonathan Chayce Dickinson
<[EMAIL PROTECTED]> wrote:
> Sander van Rossen wrote:
> > While working on the floppy controller driver code i noticed that
> > there are so many error conditions it's not even funny anymore..
> > Having exception handling would *really* help keepi
Sander van Rossen wrote:
> While working on the floppy controller driver code i noticed that
> there are so many error conditions it's not even funny anymore..
> Having exception handling would *really* help keeping the code clean...
> how easy/hard is it to implement exception handling support
While working on the floppy controller driver code i noticed that
there are so many error conditions it's not even funny anymore..
Having exception handling would *really* help keeping the code clean...
how easy/hard is it to implement exception handling support in the
AOT? (assuming that we ha
On Dec 27, 2007 1:10 PM, Darx Kies <[EMAIL PROTECTED]> wrote:
> But I would suggest not to go that path but rather to use a Hardware
> Resource Manager.
ofcourse, i mentioned something like that before;
the tool that generates the code would write initialisation code, the
initialisation code would
I like the idea with the properties as well.
But I would suggest not to go that path but rather to use a Hardware
Resource Manager.
For example the VGA driver should not and needs not access the DMA or
ports that are
specific to query the PCI.
With the Hardware Resource Manager it would be eas
Sander van Rossen wrote:
> an usefull resource for naming pci vendor IDs:
>
>
Fun!!! The web is a great tool... First we need FS Access so that we can
load that file.
--
Jonathan Dickinson
an usefull resource for naming pci vendor IDs:
http://pciids.sourceforge.net/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/di
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
> ta
Sander van Rossen wrote:
> On Dec 27, 2007 7:31 AM, Jonathan Chayce Dickinson
> <[EMAIL PROTECTED]> wrote:
>
>> Can you get the disk driver working? I wan't to try plug ext2 into the
>> kernel.
>>
> We also need to think about kernel structure IMHO.
> Right now everything is almost a collec
I made a dumb disk controller. I can only detect what type of disk we
are dealing with:
--
Jonathan Dickinson
Index: ADC/FloppyDiskController.cs
===
--- ADC/FloppyDiskController.cs (revision 0)
+++ ADC/
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
On Dec 27, 2007 7:56 AM, Bruce Markham <[EMAIL PROTECTED]> wrote:
> That, my friend, is a really slick idea.
Well i can't take full credit for the idea since singularity does
something simular (on the language level, they have a modified version
of C#)
The idea to use properties like this is mine
That, my friend, is a really slick idea.
But I'm wondering...
I've been working with PCI. And PCI you use an out() to one port, and then
an in() from another, to read configuration data.
The parameters written to the first port determine from which PCI
configuration "registers" (and on which dev
On Dec 27, 2007 7:31 AM, Jonathan Chayce Dickinson
<[EMAIL PROTECTED]> wrote:
> Can you get the disk driver working? I wan't to try plug ext2 into the
> kernel.
Well that's the plan obviously ;)
I'm currently implementing a floppy controller driver, once that's
done we can start implementing all k
Can you get the disk driver working? I wan't to try plug ext2 into the
kernel.
--
Jonathan Dickinson
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Stu
21 matches
Mail list logo
