es40-developers Mailing List for AlphaServer ES40 Emulator (Page 3)
Status: Alpha
Brought to you by:
iamcamiel
Menu
▾
▴
es40-developers — ES40 Developers List
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
(132) |
Mar
(117) |
Apr
(27) |
May
(1) |
Jun
(16) |
Jul
|
Aug
|
Sep
(4) |
Oct
(5) |
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Camiel V. <iam...@gm...> - 2008-04-29 09:57:20
|
Hello again,
I've changed the floppy stuff to use the CDisk class. To add a
floppy-controller to your emulated system, you should add these lines
to your configuration file:
fdc0=floppy
{
disk0.0={...}
disk0.1={...}
}
Brian, could you check this with the floppy images you have? I've
tried to do this without taking enough time to fully understand the
floppy code, so I might be wrong somewhere...
Camiel.
On Tue, Apr 29, 2008 at 10:27 AM, Camiel Vanderhoeven
<iam...@gm...> wrote:
> Hi Brian,
>
> I've applied the system patch. I've changed it a little so the range
> check is only performed when CHECK_MEM_RANGES is defined. I've added
> both defines to the configure_1.m4 script, with default values of
> false for DUMP_MEMMAP and true for CHECK_MEM_RANGES.
>
> I've also updated CDiskController and all its descendants to eliminate
> the dependence on CPCIDevice. I'll now start on adapting your floppy
> changes to use CDisk disk images (or real devices). I'll also make it
> possible to disable the floppy-device entirely for the people that
> don't need it (probably the majority of users).
>
> As for removable media: this is something we should start addressing
> sometime soon. I'm proposing to handle this in two possible ways:
>
> 1) for physical devices (CDiskDevice) we should check with the OS
> whether a media change has occurred.
>
> 2) for non-phisical devices, I'm proposing the introduction of a new
> Disk Class (CDiskChanger?) that is both a CDisk and a CDiskController.
> Other disks connect to it, and which disk is active can be selected
> through the serial port menu. The DiskChanger class itself is a simple
> wrapper around the selected disk's methods. So you'd have something
> like this in the config file:
>
> disk0.0 = changer {
> disk 0.0 = {...}
> disk 0.1 = {...}
> ...
> }
>
> Camiel.
>
>
>
> On Tue, Apr 22, 2008 at 3:58 PM, Brian Wheeler <bdw...@in...> wrote:
> > Here's a few patches for things I've been working on:
> >
> >
> > 1) system.diff
> >
> > * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order
> > that it is searched:
> >
> > ES40 Memory Map
> > Physical Address Size Device/Index
> > ---------------- -------- -------------------------
> > 0000080110000000 100000 sys0(tsunami)/0
> > 0000080100000000 8000000 sys0(tsunami)/0
> > 00000801fc000080 1 pci0.7(ali)/0
> > 00000801fc000000 8 pci0.7(ali)/4100
> > 00000801fc000008 8 pci0.7(ali)/4096
> > 00000801fc000081 b pci0.7(ali)/4098
> > 00000801fc0000c0 10 pci0.7(ali)/4101
> > 00000801fc0000d0 10 pci0.7(ali)/4097
> > 00000801fc000481 b pci0.7(ali)/4099
> > 00000801fc00040b 1 pci0.7(ali)/4102
> > 00000801fc0004d6 1 pci0.7(ali)/4103
> > 00000801fc0003f0 6 pci0.7(ali)/0
> > 00000801fc0003f7 1 pci0.7(ali)/1
> > 00000801fe009800 100 pci0.19(ali_usb)/2055
> > 00000801fc000061 1 pci0.7(ali)/1
> > 00000801fc000070 4 pci0.7(ali)/2
> > 00000801fe003800 100 pci0.7(ali)/2055
> > 00000801fc000040 4 pci0.7(ali)/6
> > 00000801fc000020 2 pci0.7(ali)/7
> > 00000801fc0000a0 2 pci0.7(ali)/8
> > 00000801fc0004d0 2 pci0.7(ali)/30
> > 00000801f8000000 1 pci0.7(ali)/20
> > 00000801fc0003bc 4 pci0.7(ali)/27
> > 00000801fc000060 1 pci0.7(ali)/0
> > 00000801fc000064 1 pci0.7(ali)/1
> > 00000801fc0001f0 8 pci0.15(ali_ide)/1
> > 00000801fc0003f6 1 pci0.15(ali_ide)/2
> > 00000801fc000170 8 pci0.15(ali_ide)/3
> > 00000801fc000376 2 pci0.15(ali_ide)/4
> > 00000801fc00f000 8 pci0.15(ali_ide)/5
> > 00000801fc00f008 8 pci0.15(ali_ide)/6
> > 00000801fe007800 100 pci0.15(ali_ide)/2055
> > 00000801fc0001f0 8 pci0.15(ali_ide)/2048
> > 00000801fc0003f4 4 pci0.15(ali_ide)/2049
> > 00000801fc000170 8 pci0.15(ali_ide)/2050
> > 00000801fc000374 4 pci0.15(ali_ide)/2051
> > 00000801fc00f000 10 pci0.15(ali_ide)/2052
> > 00000801fc0003f8 8 serial0(serial)/0
> >
> > * When changing/defining memory regions, a simple bounds check is
> > performed, which prints out warnings if there appears to be an overlap:
> >
> > WARNING: Start address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7)
> > is within memory range of pci0.7(ali)/0 (00000801fc0003f0-00000801fc0003f5).
> > WARNING: End address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7)
> > is within memory range of pci0.7(ali)/1 (00000801fc0003f7-00000801fc0003f7).
> >
> >
> > 2) floppy.diff
> >
> > This covers DMA.* FloppyController.* and PCIDevice.h changes to make the
> > floppy sort of work. It won't boot from it and I can't figure out why.
> > It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but
> > it is a start.
> >
> > P00>>>boot dva0
> > (boot dva0.0.0.1000.0 -flags A)
> > Block 001E2000 is not in any zone, call pc aa524
> > Block 001E6000 is not in any zone, call pc aa524
> > block 0 of dva0.0.0.1000.0 is not a valid boot block
> > bootstrap failure
> > P00>>>
> >
> > Brian
> >
>
>
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> > Don't miss this year's exciting event. There's still time to save $100.
> > Use priority code J8TL2D2.
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > _______________________________________________
> > Es40-developers mailing list
> > Es4...@li...
> > https://lists.sourceforge.net/lists/listinfo/es40-developers
> >
> >
>
|
|
From: Camiel V. <iam...@gm...> - 2008-04-29 08:28:01
|
Hi Brian,
I've applied the system patch. I've changed it a little so the range
check is only performed when CHECK_MEM_RANGES is defined. I've added
both defines to the configure_1.m4 script, with default values of
false for DUMP_MEMMAP and true for CHECK_MEM_RANGES.
I've also updated CDiskController and all its descendants to eliminate
the dependence on CPCIDevice. I'll now start on adapting your floppy
changes to use CDisk disk images (or real devices). I'll also make it
possible to disable the floppy-device entirely for the people that
don't need it (probably the majority of users).
As for removable media: this is something we should start addressing
sometime soon. I'm proposing to handle this in two possible ways:
1) for physical devices (CDiskDevice) we should check with the OS
whether a media change has occurred.
2) for non-phisical devices, I'm proposing the introduction of a new
Disk Class (CDiskChanger?) that is both a CDisk and a CDiskController.
Other disks connect to it, and which disk is active can be selected
through the serial port menu. The DiskChanger class itself is a simple
wrapper around the selected disk's methods. So you'd have something
like this in the config file:
disk0.0 = changer {
disk 0.0 = {...}
disk 0.1 = {...}
...
}
Camiel.
On Tue, Apr 22, 2008 at 3:58 PM, Brian Wheeler <bdw...@in...> wrote:
> Here's a few patches for things I've been working on:
>
>
> 1) system.diff
>
> * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order
> that it is searched:
>
> ES40 Memory Map
> Physical Address Size Device/Index
> ---------------- -------- -------------------------
> 0000080110000000 100000 sys0(tsunami)/0
> 0000080100000000 8000000 sys0(tsunami)/0
> 00000801fc000080 1 pci0.7(ali)/0
> 00000801fc000000 8 pci0.7(ali)/4100
> 00000801fc000008 8 pci0.7(ali)/4096
> 00000801fc000081 b pci0.7(ali)/4098
> 00000801fc0000c0 10 pci0.7(ali)/4101
> 00000801fc0000d0 10 pci0.7(ali)/4097
> 00000801fc000481 b pci0.7(ali)/4099
> 00000801fc00040b 1 pci0.7(ali)/4102
> 00000801fc0004d6 1 pci0.7(ali)/4103
> 00000801fc0003f0 6 pci0.7(ali)/0
> 00000801fc0003f7 1 pci0.7(ali)/1
> 00000801fe009800 100 pci0.19(ali_usb)/2055
> 00000801fc000061 1 pci0.7(ali)/1
> 00000801fc000070 4 pci0.7(ali)/2
> 00000801fe003800 100 pci0.7(ali)/2055
> 00000801fc000040 4 pci0.7(ali)/6
> 00000801fc000020 2 pci0.7(ali)/7
> 00000801fc0000a0 2 pci0.7(ali)/8
> 00000801fc0004d0 2 pci0.7(ali)/30
> 00000801f8000000 1 pci0.7(ali)/20
> 00000801fc0003bc 4 pci0.7(ali)/27
> 00000801fc000060 1 pci0.7(ali)/0
> 00000801fc000064 1 pci0.7(ali)/1
> 00000801fc0001f0 8 pci0.15(ali_ide)/1
> 00000801fc0003f6 1 pci0.15(ali_ide)/2
> 00000801fc000170 8 pci0.15(ali_ide)/3
> 00000801fc000376 2 pci0.15(ali_ide)/4
> 00000801fc00f000 8 pci0.15(ali_ide)/5
> 00000801fc00f008 8 pci0.15(ali_ide)/6
> 00000801fe007800 100 pci0.15(ali_ide)/2055
> 00000801fc0001f0 8 pci0.15(ali_ide)/2048
> 00000801fc0003f4 4 pci0.15(ali_ide)/2049
> 00000801fc000170 8 pci0.15(ali_ide)/2050
> 00000801fc000374 4 pci0.15(ali_ide)/2051
> 00000801fc00f000 10 pci0.15(ali_ide)/2052
> 00000801fc0003f8 8 serial0(serial)/0
>
> * When changing/defining memory regions, a simple bounds check is
> performed, which prints out warnings if there appears to be an overlap:
>
> WARNING: Start address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7)
> is within memory range of pci0.7(ali)/0 (00000801fc0003f0-00000801fc0003f5).
> WARNING: End address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7)
> is within memory range of pci0.7(ali)/1 (00000801fc0003f7-00000801fc0003f7).
>
>
> 2) floppy.diff
>
> This covers DMA.* FloppyController.* and PCIDevice.h changes to make the
> floppy sort of work. It won't boot from it and I can't figure out why.
> It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but
> it is a start.
>
> P00>>>boot dva0
> (boot dva0.0.0.1000.0 -flags A)
> Block 001E2000 is not in any zone, call pc aa524
> Block 001E6000 is not in any zone, call pc aa524
> block 0 of dva0.0.0.1000.0 is not a valid boot block
> bootstrap failure
> P00>>>
>
> Brian
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
>
>
|
|
From: Brian W. <bdw...@in...> - 2008-04-23 15:57:45
|
Not sure what I did, but it went away. The floppy device now sort of works for read-only: P00>>>boot dva0 (boot dva0.0.0.1000.0 -flags A) block 0 of dva0.0.0.1000.0 is a valid boot block reading 81 blocks from dva0.0.0.1000.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = a200(41472) initializing HWRPB at 2000 initializing page table at ff56000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code However, the emulator segfaults at that point. My debugger shows that the crash is in CAlphaCPU::vmspal_ent_dtbm_single(int flags). Could be a threading thing, as well, since the last message on the console is: *** IP interrupt set for CPU 0 from CPU 0(@ 110d5) It doesn't work in any guest OSes at this point...but it doesn't hang them either... I'm going to hold off doing too much more until the CDisk class gets straightened out. Out of curiosity, how are you planning on handling removable media? It seems like we'll need an out-of-band way to notify es40 of a disk change. Brian On Wed, 2008-04-23 at 08:42 -0400, Brian Wheeler wrote: > On Wed, 2008-04-23 at 14:38 +0200, Camiel Vanderhoeven wrote: > > Hi Brian, > > > > I've seen a message very similar during my early attempts (pre-2007) > > to get the emulator working: > > > > This is serial port #0 on AlphaSim > > *** keyboard not plugged in... > > 64 Meg of system memory > > Block FFF56020 is not in any zone, call pc 53a78 > > free: call pc 5a118 > > probing hose 1, PCI > > > > But I was never able to determine the cause of it. I was then still > > trying to emulate a DS10; I switched to an ES40 because I could find > > more information about it, and never saw the error message since. > > > > It seems to be related to the SRM's IO system. > > > > That'd make some sense, since that's part of the address that was > requested with the DMA transfer. I'll see if I can get more details. > > Brian > > > > Camiel. > > > > > > On Wed, Apr 23, 2008 at 2:30 PM, Brian Wheeler <bdw...@in...> wrote: > > > > > > On Wed, 2008-04-23 at 11:02 +0200, Vanderhoeven, C. (Camiel) wrote: > > > > Hi Brian, > > > > > > > > This looks promising. I'll start applying your patches when I get home. > > > > > > > > There is one thing though, I think that the floppy-controller should use > > > > CDisk class devices for its drives. That requires a modification to the > > > > CDiskController class and its dependant classes (CDiskController should > > > > no longer have PCIDevice as a base class (because the Floppy Controller > > > > is not a PCI device), and the Symbios and IDE controllers should inherit > > > > from PCIDevice directly). This is something I meant to do a while ago, > > > > so I'll start implementing that as well. > > > > > > > > > > The CDisk thing I just hadn't gotten around to, since I was just trying > > > to get it to not fail utterly :) > > > > > > Any idea what > > > > > > > > > Block 001E2000 is not in any zone, call pc aa524 > > > > > > from SRM means? > > > > > > Brian > > > > > > > > > > > > > Thanks Brian! > > > > > > > > Camiel. > > > > > > > > > > > > -----Oorspronkelijk bericht----- > > > > Van: es4...@li... > > > > [mailto:es4...@li...] Namens Brian > > > > Wheeler > > > > Verzonden: dinsdag 22 april 2008 15:58 > > > > Aan: ES40 Developer Discussions > > > > Onderwerp: [ES40-developers] Misc Patches > > > > > > > > Here's a few patches for things I've been working on: > > > > > > > > > > > > 1) system.diff > > > > > > > > * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order > > > > that it is searched: > > > > > > > > ES40 Memory Map > > > > Physical Address Size Device/Index > > > > ---------------- -------- ------------------------- > > > > 0000080110000000 100000 sys0(tsunami)/0 > > > > 0000080100000000 8000000 sys0(tsunami)/0 > > > > 00000801fc000080 1 pci0.7(ali)/0 > > > > 00000801fc000000 8 pci0.7(ali)/4100 > > > > 00000801fc000008 8 pci0.7(ali)/4096 > > > > 00000801fc000081 b pci0.7(ali)/4098 > > > > 00000801fc0000c0 10 pci0.7(ali)/4101 > > > > 00000801fc0000d0 10 pci0.7(ali)/4097 > > > > 00000801fc000481 b pci0.7(ali)/4099 > > > > 00000801fc00040b 1 pci0.7(ali)/4102 > > > > 00000801fc0004d6 1 pci0.7(ali)/4103 > > > > 00000801fc0003f0 6 pci0.7(ali)/0 > > > > 00000801fc0003f7 1 pci0.7(ali)/1 > > > > 00000801fe009800 100 pci0.19(ali_usb)/2055 > > > > 00000801fc000061 1 pci0.7(ali)/1 > > > > 00000801fc000070 4 pci0.7(ali)/2 > > > > 00000801fe003800 100 pci0.7(ali)/2055 > > > > 00000801fc000040 4 pci0.7(ali)/6 > > > > 00000801fc000020 2 pci0.7(ali)/7 > > > > 00000801fc0000a0 2 pci0.7(ali)/8 > > > > 00000801fc0004d0 2 pci0.7(ali)/30 > > > > 00000801f8000000 1 pci0.7(ali)/20 > > > > 00000801fc0003bc 4 pci0.7(ali)/27 > > > > 00000801fc000060 1 pci0.7(ali)/0 > > > > 00000801fc000064 1 pci0.7(ali)/1 > > > > 00000801fc0001f0 8 pci0.15(ali_ide)/1 > > > > 00000801fc0003f6 1 pci0.15(ali_ide)/2 > > > > 00000801fc000170 8 pci0.15(ali_ide)/3 > > > > 00000801fc000376 2 pci0.15(ali_ide)/4 > > > > 00000801fc00f000 8 pci0.15(ali_ide)/5 > > > > 00000801fc00f008 8 pci0.15(ali_ide)/6 > > > > 00000801fe007800 100 pci0.15(ali_ide)/2055 > > > > 00000801fc0001f0 8 pci0.15(ali_ide)/2048 > > > > 00000801fc0003f4 4 pci0.15(ali_ide)/2049 > > > > 00000801fc000170 8 pci0.15(ali_ide)/2050 > > > > 00000801fc000374 4 pci0.15(ali_ide)/2051 > > > > 00000801fc00f000 10 pci0.15(ali_ide)/2052 > > > > 00000801fc0003f8 8 serial0(serial)/0 > > > > > > > > * When changing/defining memory regions, a simple bounds check is > > > > performed, which prints out warnings if there appears to be an overlap: > > > > > > > > WARNING: Start address for pci0.15(ali_ide)/2049 > > > > (00000801fc0003f4-00000801fc0003f7) > > > > is within memory range of pci0.7(ali)/0 > > > > (00000801fc0003f0-00000801fc0003f5). > > > > WARNING: End address for pci0.15(ali_ide)/2049 > > > > (00000801fc0003f4-00000801fc0003f7) > > > > is within memory range of pci0.7(ali)/1 > > > > (00000801fc0003f7-00000801fc0003f7). > > > > > > > > > > > > 2) floppy.diff > > > > > > > > This covers DMA.* FloppyController.* and PCIDevice.h changes to make the > > > > floppy sort of work. It won't boot from it and I can't figure out why. > > > > It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but > > > > it is a start. > > > > > > > > P00>>>boot dva0 > > > > (boot dva0.0.0.1000.0 -flags A) > > > > Block 001E2000 is not in any zone, call pc aa524 Block 001E6000 is not > > > > in any zone, call pc aa524 block 0 of dva0.0.0.1000.0 is not a valid > > > > boot block bootstrap failure > > > > P00>>> > > > > > > > > Brian > > > > > > > > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is gezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. > > > > > > > > This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > > > Don't miss this year's exciting event. There's still time to save $100. > > > > Use priority code J8TL2D2. > > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > > > _______________________________________________ > > > > Es40-developers mailing list > > > > Es4...@li... > > > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > > Don't miss this year's exciting event. There's still time to save $100. > > > Use priority code J8TL2D2. > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > > _______________________________________________ > > > Es40-developers mailing list > > > Es4...@li... > > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > Don't miss this year's exciting event. There's still time to save $100. > > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Brian W. <bdw...@in...> - 2008-04-23 12:42:56
|
On Wed, 2008-04-23 at 14:38 +0200, Camiel Vanderhoeven wrote: > Hi Brian, > > I've seen a message very similar during my early attempts (pre-2007) > to get the emulator working: > > This is serial port #0 on AlphaSim > *** keyboard not plugged in... > 64 Meg of system memory > Block FFF56020 is not in any zone, call pc 53a78 > free: call pc 5a118 > probing hose 1, PCI > > But I was never able to determine the cause of it. I was then still > trying to emulate a DS10; I switched to an ES40 because I could find > more information about it, and never saw the error message since. > > It seems to be related to the SRM's IO system. > That'd make some sense, since that's part of the address that was requested with the DMA transfer. I'll see if I can get more details. Brian > Camiel. > > > On Wed, Apr 23, 2008 at 2:30 PM, Brian Wheeler <bdw...@in...> wrote: > > > > On Wed, 2008-04-23 at 11:02 +0200, Vanderhoeven, C. (Camiel) wrote: > > > Hi Brian, > > > > > > This looks promising. I'll start applying your patches when I get home. > > > > > > There is one thing though, I think that the floppy-controller should use > > > CDisk class devices for its drives. That requires a modification to the > > > CDiskController class and its dependant classes (CDiskController should > > > no longer have PCIDevice as a base class (because the Floppy Controller > > > is not a PCI device), and the Symbios and IDE controllers should inherit > > > from PCIDevice directly). This is something I meant to do a while ago, > > > so I'll start implementing that as well. > > > > > > > The CDisk thing I just hadn't gotten around to, since I was just trying > > to get it to not fail utterly :) > > > > Any idea what > > > > > > Block 001E2000 is not in any zone, call pc aa524 > > > > from SRM means? > > > > Brian > > > > > > > > > Thanks Brian! > > > > > > Camiel. > > > > > > > > > -----Oorspronkelijk bericht----- > > > Van: es4...@li... > > > [mailto:es4...@li...] Namens Brian > > > Wheeler > > > Verzonden: dinsdag 22 april 2008 15:58 > > > Aan: ES40 Developer Discussions > > > Onderwerp: [ES40-developers] Misc Patches > > > > > > Here's a few patches for things I've been working on: > > > > > > > > > 1) system.diff > > > > > > * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order > > > that it is searched: > > > > > > ES40 Memory Map > > > Physical Address Size Device/Index > > > ---------------- -------- ------------------------- > > > 0000080110000000 100000 sys0(tsunami)/0 > > > 0000080100000000 8000000 sys0(tsunami)/0 > > > 00000801fc000080 1 pci0.7(ali)/0 > > > 00000801fc000000 8 pci0.7(ali)/4100 > > > 00000801fc000008 8 pci0.7(ali)/4096 > > > 00000801fc000081 b pci0.7(ali)/4098 > > > 00000801fc0000c0 10 pci0.7(ali)/4101 > > > 00000801fc0000d0 10 pci0.7(ali)/4097 > > > 00000801fc000481 b pci0.7(ali)/4099 > > > 00000801fc00040b 1 pci0.7(ali)/4102 > > > 00000801fc0004d6 1 pci0.7(ali)/4103 > > > 00000801fc0003f0 6 pci0.7(ali)/0 > > > 00000801fc0003f7 1 pci0.7(ali)/1 > > > 00000801fe009800 100 pci0.19(ali_usb)/2055 > > > 00000801fc000061 1 pci0.7(ali)/1 > > > 00000801fc000070 4 pci0.7(ali)/2 > > > 00000801fe003800 100 pci0.7(ali)/2055 > > > 00000801fc000040 4 pci0.7(ali)/6 > > > 00000801fc000020 2 pci0.7(ali)/7 > > > 00000801fc0000a0 2 pci0.7(ali)/8 > > > 00000801fc0004d0 2 pci0.7(ali)/30 > > > 00000801f8000000 1 pci0.7(ali)/20 > > > 00000801fc0003bc 4 pci0.7(ali)/27 > > > 00000801fc000060 1 pci0.7(ali)/0 > > > 00000801fc000064 1 pci0.7(ali)/1 > > > 00000801fc0001f0 8 pci0.15(ali_ide)/1 > > > 00000801fc0003f6 1 pci0.15(ali_ide)/2 > > > 00000801fc000170 8 pci0.15(ali_ide)/3 > > > 00000801fc000376 2 pci0.15(ali_ide)/4 > > > 00000801fc00f000 8 pci0.15(ali_ide)/5 > > > 00000801fc00f008 8 pci0.15(ali_ide)/6 > > > 00000801fe007800 100 pci0.15(ali_ide)/2055 > > > 00000801fc0001f0 8 pci0.15(ali_ide)/2048 > > > 00000801fc0003f4 4 pci0.15(ali_ide)/2049 > > > 00000801fc000170 8 pci0.15(ali_ide)/2050 > > > 00000801fc000374 4 pci0.15(ali_ide)/2051 > > > 00000801fc00f000 10 pci0.15(ali_ide)/2052 > > > 00000801fc0003f8 8 serial0(serial)/0 > > > > > > * When changing/defining memory regions, a simple bounds check is > > > performed, which prints out warnings if there appears to be an overlap: > > > > > > WARNING: Start address for pci0.15(ali_ide)/2049 > > > (00000801fc0003f4-00000801fc0003f7) > > > is within memory range of pci0.7(ali)/0 > > > (00000801fc0003f0-00000801fc0003f5). > > > WARNING: End address for pci0.15(ali_ide)/2049 > > > (00000801fc0003f4-00000801fc0003f7) > > > is within memory range of pci0.7(ali)/1 > > > (00000801fc0003f7-00000801fc0003f7). > > > > > > > > > 2) floppy.diff > > > > > > This covers DMA.* FloppyController.* and PCIDevice.h changes to make the > > > floppy sort of work. It won't boot from it and I can't figure out why. > > > It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but > > > it is a start. > > > > > > P00>>>boot dva0 > > > (boot dva0.0.0.1000.0 -flags A) > > > Block 001E2000 is not in any zone, call pc aa524 Block 001E6000 is not > > > in any zone, call pc aa524 block 0 of dva0.0.0.1000.0 is not a valid > > > boot block bootstrap failure > > > P00>>> > > > > > > Brian > > > > > > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is gezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. > > > > > > This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > > Don't miss this year's exciting event. There's still time to save $100. > > > Use priority code J8TL2D2. > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > > _______________________________________________ > > > Es40-developers mailing list > > > Es4...@li... > > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > Don't miss this year's exciting event. There's still time to save $100. > > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Camiel V. <iam...@gm...> - 2008-04-23 12:38:37
|
Hi Brian, I've seen a message very similar during my early attempts (pre-2007) to get the emulator working: This is serial port #0 on AlphaSim *** keyboard not plugged in... 64 Meg of system memory Block FFF56020 is not in any zone, call pc 53a78 free: call pc 5a118 probing hose 1, PCI But I was never able to determine the cause of it. I was then still trying to emulate a DS10; I switched to an ES40 because I could find more information about it, and never saw the error message since. It seems to be related to the SRM's IO system. Camiel. On Wed, Apr 23, 2008 at 2:30 PM, Brian Wheeler <bdw...@in...> wrote: > > On Wed, 2008-04-23 at 11:02 +0200, Vanderhoeven, C. (Camiel) wrote: > > Hi Brian, > > > > This looks promising. I'll start applying your patches when I get home. > > > > There is one thing though, I think that the floppy-controller should use > > CDisk class devices for its drives. That requires a modification to the > > CDiskController class and its dependant classes (CDiskController should > > no longer have PCIDevice as a base class (because the Floppy Controller > > is not a PCI device), and the Symbios and IDE controllers should inherit > > from PCIDevice directly). This is something I meant to do a while ago, > > so I'll start implementing that as well. > > > > The CDisk thing I just hadn't gotten around to, since I was just trying > to get it to not fail utterly :) > > Any idea what > > > Block 001E2000 is not in any zone, call pc aa524 > > from SRM means? > > Brian > > > > > Thanks Brian! > > > > Camiel. > > > > > > -----Oorspronkelijk bericht----- > > Van: es4...@li... > > [mailto:es4...@li...] Namens Brian > > Wheeler > > Verzonden: dinsdag 22 april 2008 15:58 > > Aan: ES40 Developer Discussions > > Onderwerp: [ES40-developers] Misc Patches > > > > Here's a few patches for things I've been working on: > > > > > > 1) system.diff > > > > * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order > > that it is searched: > > > > ES40 Memory Map > > Physical Address Size Device/Index > > ---------------- -------- ------------------------- > > 0000080110000000 100000 sys0(tsunami)/0 > > 0000080100000000 8000000 sys0(tsunami)/0 > > 00000801fc000080 1 pci0.7(ali)/0 > > 00000801fc000000 8 pci0.7(ali)/4100 > > 00000801fc000008 8 pci0.7(ali)/4096 > > 00000801fc000081 b pci0.7(ali)/4098 > > 00000801fc0000c0 10 pci0.7(ali)/4101 > > 00000801fc0000d0 10 pci0.7(ali)/4097 > > 00000801fc000481 b pci0.7(ali)/4099 > > 00000801fc00040b 1 pci0.7(ali)/4102 > > 00000801fc0004d6 1 pci0.7(ali)/4103 > > 00000801fc0003f0 6 pci0.7(ali)/0 > > 00000801fc0003f7 1 pci0.7(ali)/1 > > 00000801fe009800 100 pci0.19(ali_usb)/2055 > > 00000801fc000061 1 pci0.7(ali)/1 > > 00000801fc000070 4 pci0.7(ali)/2 > > 00000801fe003800 100 pci0.7(ali)/2055 > > 00000801fc000040 4 pci0.7(ali)/6 > > 00000801fc000020 2 pci0.7(ali)/7 > > 00000801fc0000a0 2 pci0.7(ali)/8 > > 00000801fc0004d0 2 pci0.7(ali)/30 > > 00000801f8000000 1 pci0.7(ali)/20 > > 00000801fc0003bc 4 pci0.7(ali)/27 > > 00000801fc000060 1 pci0.7(ali)/0 > > 00000801fc000064 1 pci0.7(ali)/1 > > 00000801fc0001f0 8 pci0.15(ali_ide)/1 > > 00000801fc0003f6 1 pci0.15(ali_ide)/2 > > 00000801fc000170 8 pci0.15(ali_ide)/3 > > 00000801fc000376 2 pci0.15(ali_ide)/4 > > 00000801fc00f000 8 pci0.15(ali_ide)/5 > > 00000801fc00f008 8 pci0.15(ali_ide)/6 > > 00000801fe007800 100 pci0.15(ali_ide)/2055 > > 00000801fc0001f0 8 pci0.15(ali_ide)/2048 > > 00000801fc0003f4 4 pci0.15(ali_ide)/2049 > > 00000801fc000170 8 pci0.15(ali_ide)/2050 > > 00000801fc000374 4 pci0.15(ali_ide)/2051 > > 00000801fc00f000 10 pci0.15(ali_ide)/2052 > > 00000801fc0003f8 8 serial0(serial)/0 > > > > * When changing/defining memory regions, a simple bounds check is > > performed, which prints out warnings if there appears to be an overlap: > > > > WARNING: Start address for pci0.15(ali_ide)/2049 > > (00000801fc0003f4-00000801fc0003f7) > > is within memory range of pci0.7(ali)/0 > > (00000801fc0003f0-00000801fc0003f5). > > WARNING: End address for pci0.15(ali_ide)/2049 > > (00000801fc0003f4-00000801fc0003f7) > > is within memory range of pci0.7(ali)/1 > > (00000801fc0003f7-00000801fc0003f7). > > > > > > 2) floppy.diff > > > > This covers DMA.* FloppyController.* and PCIDevice.h changes to make the > > floppy sort of work. It won't boot from it and I can't figure out why. > > It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but > > it is a start. > > > > P00>>>boot dva0 > > (boot dva0.0.0.1000.0 -flags A) > > Block 001E2000 is not in any zone, call pc aa524 Block 001E6000 is not > > in any zone, call pc aa524 block 0 of dva0.0.0.1000.0 is not a valid > > boot block bootstrap failure > > P00>>> > > > > Brian > > > > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is gezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. > > > > This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > Don't miss this year's exciting event. There's still time to save $100. > > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Brian W. <bdw...@in...> - 2008-04-23 12:31:01
|
On Wed, 2008-04-23 at 11:02 +0200, Vanderhoeven, C. (Camiel) wrote: > Hi Brian, > > This looks promising. I'll start applying your patches when I get home. > > There is one thing though, I think that the floppy-controller should use > CDisk class devices for its drives. That requires a modification to the > CDiskController class and its dependant classes (CDiskController should > no longer have PCIDevice as a base class (because the Floppy Controller > is not a PCI device), and the Symbios and IDE controllers should inherit > from PCIDevice directly). This is something I meant to do a while ago, > so I'll start implementing that as well. > The CDisk thing I just hadn't gotten around to, since I was just trying to get it to not fail utterly :) Any idea what Block 001E2000 is not in any zone, call pc aa524 from SRM means? Brian > Thanks Brian! > > Camiel. > > > -----Oorspronkelijk bericht----- > Van: es4...@li... > [mailto:es4...@li...] Namens Brian > Wheeler > Verzonden: dinsdag 22 april 2008 15:58 > Aan: ES40 Developer Discussions > Onderwerp: [ES40-developers] Misc Patches > > Here's a few patches for things I've been working on: > > > 1) system.diff > > * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order > that it is searched: > > ES40 Memory Map > Physical Address Size Device/Index > ---------------- -------- ------------------------- > 0000080110000000 100000 sys0(tsunami)/0 > 0000080100000000 8000000 sys0(tsunami)/0 > 00000801fc000080 1 pci0.7(ali)/0 > 00000801fc000000 8 pci0.7(ali)/4100 > 00000801fc000008 8 pci0.7(ali)/4096 > 00000801fc000081 b pci0.7(ali)/4098 > 00000801fc0000c0 10 pci0.7(ali)/4101 > 00000801fc0000d0 10 pci0.7(ali)/4097 > 00000801fc000481 b pci0.7(ali)/4099 > 00000801fc00040b 1 pci0.7(ali)/4102 > 00000801fc0004d6 1 pci0.7(ali)/4103 > 00000801fc0003f0 6 pci0.7(ali)/0 > 00000801fc0003f7 1 pci0.7(ali)/1 > 00000801fe009800 100 pci0.19(ali_usb)/2055 > 00000801fc000061 1 pci0.7(ali)/1 > 00000801fc000070 4 pci0.7(ali)/2 > 00000801fe003800 100 pci0.7(ali)/2055 > 00000801fc000040 4 pci0.7(ali)/6 > 00000801fc000020 2 pci0.7(ali)/7 > 00000801fc0000a0 2 pci0.7(ali)/8 > 00000801fc0004d0 2 pci0.7(ali)/30 > 00000801f8000000 1 pci0.7(ali)/20 > 00000801fc0003bc 4 pci0.7(ali)/27 > 00000801fc000060 1 pci0.7(ali)/0 > 00000801fc000064 1 pci0.7(ali)/1 > 00000801fc0001f0 8 pci0.15(ali_ide)/1 > 00000801fc0003f6 1 pci0.15(ali_ide)/2 > 00000801fc000170 8 pci0.15(ali_ide)/3 > 00000801fc000376 2 pci0.15(ali_ide)/4 > 00000801fc00f000 8 pci0.15(ali_ide)/5 > 00000801fc00f008 8 pci0.15(ali_ide)/6 > 00000801fe007800 100 pci0.15(ali_ide)/2055 > 00000801fc0001f0 8 pci0.15(ali_ide)/2048 > 00000801fc0003f4 4 pci0.15(ali_ide)/2049 > 00000801fc000170 8 pci0.15(ali_ide)/2050 > 00000801fc000374 4 pci0.15(ali_ide)/2051 > 00000801fc00f000 10 pci0.15(ali_ide)/2052 > 00000801fc0003f8 8 serial0(serial)/0 > > * When changing/defining memory regions, a simple bounds check is > performed, which prints out warnings if there appears to be an overlap: > > WARNING: Start address for pci0.15(ali_ide)/2049 > (00000801fc0003f4-00000801fc0003f7) > is within memory range of pci0.7(ali)/0 > (00000801fc0003f0-00000801fc0003f5). > WARNING: End address for pci0.15(ali_ide)/2049 > (00000801fc0003f4-00000801fc0003f7) > is within memory range of pci0.7(ali)/1 > (00000801fc0003f7-00000801fc0003f7). > > > 2) floppy.diff > > This covers DMA.* FloppyController.* and PCIDevice.h changes to make the > floppy sort of work. It won't boot from it and I can't figure out why. > It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but > it is a start. > > P00>>>boot dva0 > (boot dva0.0.0.1000.0 -flags A) > Block 001E2000 is not in any zone, call pc aa524 Block 001E6000 is not > in any zone, call pc aa524 block 0 of dva0.0.0.1000.0 is not a valid > boot block bootstrap failure > P00>>> > > Brian > > Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is gezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. > > This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Vanderhoeven, C. (Camiel) <c.v...@mi...> - 2008-04-23 09:02:30
|
Hi Brian, This looks promising. I'll start applying your patches when I get home. There is one thing though, I think that the floppy-controller should use CDisk class devices for its drives. That requires a modification to the CDiskController class and its dependant classes (CDiskController should no longer have PCIDevice as a base class (because the Floppy Controller is not a PCI device), and the Symbios and IDE controllers should inherit from PCIDevice directly). This is something I meant to do a while ago, so I'll start implementing that as well. Thanks Brian! Camiel. -----Oorspronkelijk bericht----- Van: es4...@li... [mailto:es4...@li...] Namens Brian Wheeler Verzonden: dinsdag 22 april 2008 15:58 Aan: ES40 Developer Discussions Onderwerp: [ES40-developers] Misc Patches Here's a few patches for things I've been working on: 1) system.diff * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order that it is searched: ES40 Memory Map Physical Address Size Device/Index ---------------- -------- ------------------------- 0000080110000000 100000 sys0(tsunami)/0 0000080100000000 8000000 sys0(tsunami)/0 00000801fc000080 1 pci0.7(ali)/0 00000801fc000000 8 pci0.7(ali)/4100 00000801fc000008 8 pci0.7(ali)/4096 00000801fc000081 b pci0.7(ali)/4098 00000801fc0000c0 10 pci0.7(ali)/4101 00000801fc0000d0 10 pci0.7(ali)/4097 00000801fc000481 b pci0.7(ali)/4099 00000801fc00040b 1 pci0.7(ali)/4102 00000801fc0004d6 1 pci0.7(ali)/4103 00000801fc0003f0 6 pci0.7(ali)/0 00000801fc0003f7 1 pci0.7(ali)/1 00000801fe009800 100 pci0.19(ali_usb)/2055 00000801fc000061 1 pci0.7(ali)/1 00000801fc000070 4 pci0.7(ali)/2 00000801fe003800 100 pci0.7(ali)/2055 00000801fc000040 4 pci0.7(ali)/6 00000801fc000020 2 pci0.7(ali)/7 00000801fc0000a0 2 pci0.7(ali)/8 00000801fc0004d0 2 pci0.7(ali)/30 00000801f8000000 1 pci0.7(ali)/20 00000801fc0003bc 4 pci0.7(ali)/27 00000801fc000060 1 pci0.7(ali)/0 00000801fc000064 1 pci0.7(ali)/1 00000801fc0001f0 8 pci0.15(ali_ide)/1 00000801fc0003f6 1 pci0.15(ali_ide)/2 00000801fc000170 8 pci0.15(ali_ide)/3 00000801fc000376 2 pci0.15(ali_ide)/4 00000801fc00f000 8 pci0.15(ali_ide)/5 00000801fc00f008 8 pci0.15(ali_ide)/6 00000801fe007800 100 pci0.15(ali_ide)/2055 00000801fc0001f0 8 pci0.15(ali_ide)/2048 00000801fc0003f4 4 pci0.15(ali_ide)/2049 00000801fc000170 8 pci0.15(ali_ide)/2050 00000801fc000374 4 pci0.15(ali_ide)/2051 00000801fc00f000 10 pci0.15(ali_ide)/2052 00000801fc0003f8 8 serial0(serial)/0 * When changing/defining memory regions, a simple bounds check is performed, which prints out warnings if there appears to be an overlap: WARNING: Start address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7) is within memory range of pci0.7(ali)/0 (00000801fc0003f0-00000801fc0003f5). WARNING: End address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7) is within memory range of pci0.7(ali)/1 (00000801fc0003f7-00000801fc0003f7). 2) floppy.diff This covers DMA.* FloppyController.* and PCIDevice.h changes to make the floppy sort of work. It won't boot from it and I can't figure out why. It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but it is a start. P00>>>boot dva0 (boot dva0.0.0.1000.0 -flags A) Block 001E2000 is not in any zone, call pc aa524 Block 001E6000 is not in any zone, call pc aa524 block 0 of dva0.0.0.1000.0 is not a valid boot block bootstrap failure P00>>> Brian Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is gezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. |
|
From: Brian W. <bdw...@in...> - 2008-04-22 13:58:15
|
Here's a few patches for things I've been working on: 1) system.diff * if DUMP_MEMMAP is defined, es40 drops out its memory map in the order that it is searched: ES40 Memory Map Physical Address Size Device/Index ---------------- -------- ------------------------- 0000080110000000 100000 sys0(tsunami)/0 0000080100000000 8000000 sys0(tsunami)/0 00000801fc000080 1 pci0.7(ali)/0 00000801fc000000 8 pci0.7(ali)/4100 00000801fc000008 8 pci0.7(ali)/4096 00000801fc000081 b pci0.7(ali)/4098 00000801fc0000c0 10 pci0.7(ali)/4101 00000801fc0000d0 10 pci0.7(ali)/4097 00000801fc000481 b pci0.7(ali)/4099 00000801fc00040b 1 pci0.7(ali)/4102 00000801fc0004d6 1 pci0.7(ali)/4103 00000801fc0003f0 6 pci0.7(ali)/0 00000801fc0003f7 1 pci0.7(ali)/1 00000801fe009800 100 pci0.19(ali_usb)/2055 00000801fc000061 1 pci0.7(ali)/1 00000801fc000070 4 pci0.7(ali)/2 00000801fe003800 100 pci0.7(ali)/2055 00000801fc000040 4 pci0.7(ali)/6 00000801fc000020 2 pci0.7(ali)/7 00000801fc0000a0 2 pci0.7(ali)/8 00000801fc0004d0 2 pci0.7(ali)/30 00000801f8000000 1 pci0.7(ali)/20 00000801fc0003bc 4 pci0.7(ali)/27 00000801fc000060 1 pci0.7(ali)/0 00000801fc000064 1 pci0.7(ali)/1 00000801fc0001f0 8 pci0.15(ali_ide)/1 00000801fc0003f6 1 pci0.15(ali_ide)/2 00000801fc000170 8 pci0.15(ali_ide)/3 00000801fc000376 2 pci0.15(ali_ide)/4 00000801fc00f000 8 pci0.15(ali_ide)/5 00000801fc00f008 8 pci0.15(ali_ide)/6 00000801fe007800 100 pci0.15(ali_ide)/2055 00000801fc0001f0 8 pci0.15(ali_ide)/2048 00000801fc0003f4 4 pci0.15(ali_ide)/2049 00000801fc000170 8 pci0.15(ali_ide)/2050 00000801fc000374 4 pci0.15(ali_ide)/2051 00000801fc00f000 10 pci0.15(ali_ide)/2052 00000801fc0003f8 8 serial0(serial)/0 * When changing/defining memory regions, a simple bounds check is performed, which prints out warnings if there appears to be an overlap: WARNING: Start address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7) is within memory range of pci0.7(ali)/0 (00000801fc0003f0-00000801fc0003f5). WARNING: End address for pci0.15(ali_ide)/2049 (00000801fc0003f4-00000801fc0003f7) is within memory range of pci0.7(ali)/1 (00000801fc0003f7-00000801fc0003f7). 2) floppy.diff This covers DMA.* FloppyController.* and PCIDevice.h changes to make the floppy sort of work. It won't boot from it and I can't figure out why. It is hardcoded to use disk1of3 from NetBSD 4.0 and is really messy, but it is a start. P00>>>boot dva0 (boot dva0.0.0.1000.0 -flags A) Block 001E2000 is not in any zone, call pc aa524 Block 001E6000 is not in any zone, call pc aa524 block 0 of dva0.0.0.1000.0 is not a valid boot block bootstrap failure P00>>> Brian |
|
From: Camiel V. <iam...@gm...> - 2008-04-18 09:25:51
|
Hi Brian, I saw you had a question (in the code) as to the documentation for the IO port 480 range; Well, there is a bit of info in the datasheet (there's a link on http://www.es40.org/Ali_M1543C) on page 173: Channel Low-page register High-page register 0 0x87 0x487 1 0x83 0x483 2 0x81 0x481 3 0x82 0x482 5 0x8B 0x48B 6 0x89 0x489 7 0x8A 0x48A On Thu, Apr 17, 2008 at 10:27 PM, Brian Wheeler <bdw...@in...> wrote: > I rewrote the dma controller in preparation for screwing around with the > floppy controller. It contains everything except the actual meat: the > transfer itself...I need to see how the floppy disk is going to work > before I can fill that in. > > Brian > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > > |
|
From: Brian W. <bdw...@in...> - 2008-04-17 20:27:13
|
I rewrote the dma controller in preparation for screwing around with the floppy controller. It contains everything except the actual meat: the transfer itself...I need to see how the floppy disk is going to work before I can fill that in. Brian |
|
From: Camiel V. <iam...@gm...> - 2008-04-09 13:27:57
|
Thanks Brian, I just applied it. On Wed, Apr 9, 2008 at 2:45 PM, Brian Wheeler <bdw...@in...> wrote: > Just a little patch which makes the RMC versions come out right: > > Firmware > SRM Console: V7.2-1 > ARC Console: > PALcode: OpenVMS PALcode V1.98-104, Tru64 UNIX PALcode V1.92-105 > Serial ROM: V2.22G > RMC ROM: V1.0 > RMC Flash ROM: V1.0 > > > > Index: DPR.cpp > =================================================================== > RCS file: /cvsroot/es40/es40/src/DPR.cpp,v > retrieving revision 1.21 > diff -u -r1.21 DPR.cpp > --- DPR.cpp 17 Mar 2008 20:20:39 -0000 1.21 > +++ DPR.cpp 9 Apr 2008 12:44:23 -0000 > @@ -340,14 +340,14 @@ > // 3009:300B RMC Rev Level of RMC first byte is letter Rev [x/t/v] second 2 bytes are major/minor. > // This is the rev level of the RMC on-chip code. > state.ram[0x3009] = 'V'; > - state.ram[0x300a] = 0x01; > - state.ram[0x300b] = 0x00; > + state.ram[0x300a] = 0x31; > + state.ram[0x300b] = 0x30; > > // 300C:300E RMC Rev Level of RMC first byte is letter Rev [x/t/v] second 2 bytes are major/minor. > // This is the rev level of the RMC flash code. > state.ram[0x300c] = 'V'; > - state.ram[0x300d] = 0x01; > - state.ram[0x300e] = 0x00; > + state.ram[0x300d] = 0x31; > + state.ram[0x300e] = 0x30; > > // 300F:3010 300F RMC Revision Field of the DPR Structure > // 3400 SROM Size of Bcache in MB > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Brian W. <bdw...@in...> - 2008-04-09 12:45:27
|
Just a little patch which makes the RMC versions come out right: Firmware SRM Console: V7.2-1 ARC Console: PALcode: OpenVMS PALcode V1.98-104, Tru64 UNIX PALcode V1.92-105 Serial ROM: V2.22G RMC ROM: V1.0 RMC Flash ROM: V1.0 Index: DPR.cpp =================================================================== RCS file: /cvsroot/es40/es40/src/DPR.cpp,v retrieving revision 1.21 diff -u -r1.21 DPR.cpp --- DPR.cpp 17 Mar 2008 20:20:39 -0000 1.21 +++ DPR.cpp 9 Apr 2008 12:44:23 -0000 @@ -340,14 +340,14 @@ // 3009:300B RMC Rev Level of RMC first byte is letter Rev [x/t/v] second 2 bytes are major/minor. // This is the rev level of the RMC on-chip code. state.ram[0x3009] = 'V'; - state.ram[0x300a] = 0x01; - state.ram[0x300b] = 0x00; + state.ram[0x300a] = 0x31; + state.ram[0x300b] = 0x30; // 300C:300E RMC Rev Level of RMC first byte is letter Rev [x/t/v] second 2 bytes are major/minor. // This is the rev level of the RMC flash code. state.ram[0x300c] = 'V'; - state.ram[0x300d] = 0x01; - state.ram[0x300e] = 0x00; + state.ram[0x300d] = 0x31; + state.ram[0x300e] = 0x30; // 300F:3010 300F RMC Revision Field of the DPR Structure // 3400 SROM Size of Bcache in MB |
|
From: Camiel V. <iam...@gm...> - 2008-04-09 08:36:10
|
Hello Everyone, Some people hinted that it might be a good idea to set up a new website for the ES40 Emulator, with a URL that is easier to remember. I am proud to present to you that URL: http://es40.org. I am aware that the content is fairly limited at this point, and mainly consists of a couple of links to the other sites, but I'm sure that will improve over time. I've also setup a Wiki containing some information about the emulator. Feel free to expand upon the information, and to create new subjects there. If you have hints, tips, or any other information you'd like to share, please add them where you think they would be appropriate. Have a great day! Camiel. |
|
From: Brian W. <bdw...@in...> - 2008-04-04 15:13:29
|
On Fri, 2008-04-04 at 16:01 +0100, Camiel Vanderhoeven wrote: > Hello everyone, > > I'm going to give a presentation about the ES40 Emulator at HP's > OpenVMS bootcamp in May. I'm putting the material together, and I'm > hoping you may have a few ideas what to speak on. I've got an hour, > and the session will be at a basic level. So far, I'm thinking of > talking about the following: > > * Emulation in general: when, why > * How to create an emulator (study the documentation, study the > hardware, filter out the logic, implement it in software, test and > analyze it, then re-iterate for fine-tuning) > * How the architecture of the ES40 was mapped into software-objects > * How we started with a "bare-bones" system until we got OpenVMS > running, then started adding things > * How the ES40 emulator is kept portable (portable libraries, new build system) > * Useful open-source resources > * Need for an active community, and how to build one > * SourceForge.net features > > If you have any additional suggestions, or suggestions for one of > these points, please let me know. I will certainly make my > presentation public after the bootcamp. > Sounds really cool. You may mention how much brain-bleach is needed to filter through all of the 'legacy' devices' behavior! Brian > Thanks! > > Camiel. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Camiel V. <iam...@gm...> - 2008-04-04 15:01:36
|
Hello everyone, I'm going to give a presentation about the ES40 Emulator at HP's OpenVMS bootcamp in May. I'm putting the material together, and I'm hoping you may have a few ideas what to speak on. I've got an hour, and the session will be at a basic level. So far, I'm thinking of talking about the following: * Emulation in general: when, why * How to create an emulator (study the documentation, study the hardware, filter out the logic, implement it in software, test and analyze it, then re-iterate for fine-tuning) * How the architecture of the ES40 was mapped into software-objects * How we started with a "bare-bones" system until we got OpenVMS running, then started adding things * How the ES40 emulator is kept portable (portable libraries, new build system) * Useful open-source resources * Need for an active community, and how to build one * SourceForge.net features If you have any additional suggestions, or suggestions for one of these points, please let me know. I will certainly make my presentation public after the bootcamp. Thanks! Camiel. |
|
From: Paco L. <pac...@gm...> - 2008-04-04 10:04:31
|
Hi: Maybe people is interested in a mirror of the now down VMSONE. You can find all the openvms kits for Alpha and vax: http://www.moehre.org/mirrors/openvmsvmsone/ovmskits/axp_kits2003/ Note VMSONE was the web of John Wisniewski : http://wiz.openvms.org/stories.php Paco * * |
|
From: Pepito G. <pep...@ya...> - 2008-03-31 19:44:17
|
Hi!
I have done it! But I had to remove the configuration
files. I was not enough to run @tcpip$config.
now,new error
Begin Startup...
%TCPIP-I-INFO, TCP/IP Services startup beginning at
31-MAR-2008 19:36:45.53
%TCPIP-I-NORMAL, timezone information verified
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:54.98
%%%%%%%%%%%
Message from user INTERnet on AEDES1
INTERnet Loaded
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:55.01
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "inet" configured by process 0001001F
Status: success
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:55.05
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "net" configured by process 0001001F
Status: success
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:55.10
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "socket" configured by process 0001001F
Status: success
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:55.15
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "iptunnel" configured by process 0001001F
Status: success
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:55.20
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "ipv6" configured by process 0001001F
Status: success
%%%%%%%%%%% OPCOM 31-MAR-2008 19:36:55.26
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "snmpinfo" configured by process 0001001F
Status: success
%RUN-S-PROC_ID, identification of created process is
0000009F
%SYSTEM-F-ACCVIO, access violation, reason mask=00,
virtual address=00000000000A
408C, PC=000000007AFD55F8, PS=0000001B
Improperly handled condition, image exit forced.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000000
00000000000A408C
000000007AFD55F8
000000000000001B
Register dump:
R0 = 00000000000A4000 R1 = 00000000000108D0 R2
= 000000007AF724D8
R3 = 000000007AEC37E0 R4 = 0000000000020044 R5
= 000000007FFCF940
R6 = 0000000000000000 R7 = 000000007AF19F00 R8
= 000000007FFAC1F8
R9 = 000000007AEC39E0 R10 = 000000007AEC37E0
R11 = 000000007FFCE3E0
R12 = 0000000000000000 R13 = 000000007AF79328
R14 = 0000000000020000
R15 = 000000007AF75C20 R16 = 000000007AEC39E8
R17 = 000000007AEC37E0
R18 = 000000007AEC39D8 R19 = 0000000000000000
R20 = 0000F80000000000
R21 = 0000000000000FFF R22 = 000000007AF727C0
R23 = 000000007AF727C0
R24 = 000000007AEC39E8 R25 = 0000000000000003
R26 = 000000007AFD4F04
R27 = 000000007AF724D8 R28 = 000000007AFD4EA0
R29 = 000000007AEC3760
SP = 000000007AEC3760 PC = 000000007AFD55F8 PS
= 200000000000001B
%TCPIP-I-STARTCOMM, starting communication
%%%%%%%%%%% OPCOM 31-MAR-2008 19:37:00.25
%%%%%%%%%%%
Message from user INTERnet on AEDES1
INTERnet Started
%TCPIP-I-SETPROTP, setting protocol parameters
%TCPIP-I-DEFINTE, defining interfaces
%%%%%%%%%%% OPCOM 31-MAR-2008 19:37:03.99
%%%%%%%%%%%
Message from user INTERnet on AEDES1
INTERnet ACP Created INTERnet interface: WE0
%TCPIP-I-DHCPC_STRD_CLNT, DHCP client started with PID
000000A1
aedes1$dqa0:[sys0.syscommon.][sysexe]tcpip$dhcp_client_conf.exe;1:
timed out aft
er 30 seconds
%TCPIP-E-DHCPC_TIMEOUT, controlling program timed out
%TCPIP-E-DHCPCONFERR, DHCP client failed to configure
interface WE0
-TCPIP-E-DHCPC_TIMEOUT, controlling program timed out
%%%%%%%%%%% OPCOM 31-MAR-2008 19:37:43.30
%%%%%%%%%%%
Message from user Proxy Server on AEDES1
Loading proxy server image TCPIP$PROXY_SERVICES
%%%%%%%%%%% OPCOM 31-MAR-2008 19:37:43.44
%%%%%%%%%%%
Message from user INTERnet on AEDES1
Subsystem "proxy" configured by process 0001001C
Status: success
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
%TCPIP-I-PROXYLOADED, loaded 0 NFS proxy records
%TCPIP-I-LOADSERV, loading TCPIP server proxy
information
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0
proxy records
-TCPIP-I-SERVSKIP, skipped 0 communication proxy
records
-TCPIP-I-SERVTOTAL, total of 0 proxy records read
%TCPIP-S-STARTDONE, TCPIP$PROXY startup completed
%TCPIP-S-STARTDONE, TCPIP$DHCP_CLIENT startup
completed
%TCPIP-S-STARTDONE, TCP/IP Services startup completed
at 31-MAR-2008 19:38:17.31
Startup request completed.
Press Return to continue ...
Pepito
--- "Hittner, David T." <dav...@ng...>
escribió:
> Since the ES40 21143 ethernet interfaces are EWx:,
> the "SE0" in the error message indicates that you
> either ran the TCP/IP configuration under Personal
> Alpha or didn't run it at all.
>
> Rerun @SYS$STARTUP:TCPIP$CONFIG and try again.
>
> Dave
>
> -----Original Message-----
> From: es4...@li...
>
[mailto:es4...@li...]
> On Behalf Of Pepito Grillo
> Sent: Sunday, March 30, 2008 12:53 PM
> To: ES40 Developer Discussions
> Subject: Re: [ES40-developers] access violation fun
> :-)
>
> Hi!
>
> The error I get with TCPIP is:
> %TCPIP-I-SETPROTP, setting protocol parameters
> %TCPIP-I-DEFINTE, defining interfaces
> %TCPIP-E-INVINTER, error defining interface: SE0
> -TCPIP-I-ACPQIO, failure on internet ACP QIO
> -SYSTEM-W-NOSUCHDEV, no such device available
> %%%%%%%%%%% OPCOM 30-MAR-2008 15:54:55.86
> %%%%%%%%%%% I hope it helps...
>
> Pepito
>
> --- Fausto Saporito <fa...@un...> escribió:
>
> > Hello all,
> >
> > some interesting news, from the installation world
> > :-)
> > Today I was able to install OpenVMS 8.3 without
> any ACCESS VIOLATION
> > error. All went fine, in about one hour and half.
> > I used ODS2, not ODS5.
> >
> > Anyway, the installation of CXML (a layered
> product) generates always
> > an access violation. The DHCP client doesn't work
> (it starts but I
> > have no IP address), and if I try to use a manual
> IP address when I
> > have to set the HOST name in the host database I
> have a new ACCESS
> > VIOLATION, so the TCPIP doesn't work for me.
> >
> > I installed successfully the UPDATE_V6 of VMS, but
> after the reboot I
> > got a new access violation related to PTHREAD and
> ACME (I don't
> > remember exactly the name of the process).
> > Then I was not able to install the VMS83A_SYS_V007
> update, cause I
> > have another ACCESS VIOLATION, during the product
> install
> > (verification phase).
> >
> > During this last try, the emulator hung and on the
> DOS console I had
> > the following error, looping:
> >
> > Unknown opcode: 00.00
> >
> > Then when I pressed CTRL-C to stop everything, I
> got on the DOS
> > console these other errors:
> >
> > Unknown opcode: 00.00
> > Unknown opcode: 1c.23
> > Unknown opcode: 1b.06
> > Unknown opcode: 00.00
> > Unknown opcode: 00.294000
> > Unknown opcode: 00.00
> > Unknown opcode: 00.00
> > Unknown opcode: 00.00
> > Unknown opcode: 00.00
> > Unknown opcode: 00.00
> > Unknown opcode: 00.00
> > Unknown opcode: 00.00
> >
> > C:\Users\p\es40_cvs_exe>
> >
> > regards,
> > fausto
> >
> >
>
-------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> just about anything
> > Open Source.
> >
>
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> > _______________________________________________
> > Es40-developers mailing list
> > Es4...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/es40-developers
> >
>
>
>
> ______________________________________________
> Enviado desde Correo Yahoo!
> Disfruta de una bandeja de entrada más inteligente.
> http://es.docs.yahoo.com/mail/overview/index.html
>
>
-------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for just
> about anything Open Source.
>
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
>
https://lists.sourceforge.net/lists/listinfo/es40-developers
>
>
-------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
>
https://lists.sourceforge.net/lists/listinfo/es40-developers
>
______________________________________________
Enviado desde Correo Yahoo!
Disfruta de una bandeja de entrada más inteligente. http://es.docs.yahoo.com/mail/overview/index.html
|
|
From: Hittner, D. T. <dav...@ng...> - 2008-03-31 15:11:28
|
Since the ES40 21143 ethernet interfaces are EWx:, the "SE0" in the error message indicates that you either ran the TCP/IP configuration under Personal Alpha or didn't run it at all. Rerun @SYS$STARTUP:TCPIP$CONFIG and try again. Dave -----Original Message----- From: es4...@li... [mailto:es4...@li...] On Behalf Of Pepito Grillo Sent: Sunday, March 30, 2008 12:53 PM To: ES40 Developer Discussions Subject: Re: [ES40-developers] access violation fun :-) Hi! The error I get with TCPIP is: %TCPIP-I-SETPROTP, setting protocol parameters %TCPIP-I-DEFINTE, defining interfaces %TCPIP-E-INVINTER, error defining interface: SE0 -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available %%%%%%%%%%% OPCOM 30-MAR-2008 15:54:55.86 %%%%%%%%%%% I hope it helps... Pepito --- Fausto Saporito <fa...@un...> escribió: > Hello all, > > some interesting news, from the installation world > :-) > Today I was able to install OpenVMS 8.3 without any ACCESS VIOLATION > error. All went fine, in about one hour and half. > I used ODS2, not ODS5. > > Anyway, the installation of CXML (a layered product) generates always > an access violation. The DHCP client doesn't work (it starts but I > have no IP address), and if I try to use a manual IP address when I > have to set the HOST name in the host database I have a new ACCESS > VIOLATION, so the TCPIP doesn't work for me. > > I installed successfully the UPDATE_V6 of VMS, but after the reboot I > got a new access violation related to PTHREAD and ACME (I don't > remember exactly the name of the process). > Then I was not able to install the VMS83A_SYS_V007 update, cause I > have another ACCESS VIOLATION, during the product install > (verification phase). > > During this last try, the emulator hung and on the DOS console I had > the following error, looping: > > Unknown opcode: 00.00 > > Then when I pressed CTRL-C to stop everything, I got on the DOS > console these other errors: > > Unknown opcode: 00.00 > Unknown opcode: 1c.23 > Unknown opcode: 1b.06 > Unknown opcode: 00.00 > Unknown opcode: 00.294000 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > > C:\Users\p\es40_cvs_exe> > > regards, > fausto > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for just about anything > Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > ______________________________________________ Enviado desde Correo Yahoo! Disfruta de una bandeja de entrada más inteligente. http://es.docs.yahoo.com/mail/overview/index.html ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Es40-developers mailing list Es4...@li... https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Pepito G. <pep...@ya...> - 2008-03-30 16:53:10
|
Hi! The error I get with TCPIP is: %TCPIP-I-SETPROTP, setting protocol parameters %TCPIP-I-DEFINTE, defining interfaces %TCPIP-E-INVINTER, error defining interface: SE0 -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-W-NOSUCHDEV, no such device available %%%%%%%%%%% OPCOM 30-MAR-2008 15:54:55.86 %%%%%%%%%%% I hope it helps... Pepito --- Fausto Saporito <fa...@un...> escribió: > Hello all, > > some interesting news, from the installation world > :-) > Today I was able to install OpenVMS 8.3 without any > ACCESS VIOLATION > error. All went fine, in about one hour and half. > I used ODS2, not ODS5. > > Anyway, the installation of CXML (a layered product) > generates always > an access violation. The DHCP client doesn't work > (it starts but I > have no IP address), and if I try to use a manual IP > address when I > have to set the HOST name in the host database I > have a new ACCESS > VIOLATION, so the TCPIP doesn't work for me. > > I installed successfully the UPDATE_V6 of VMS, but > after the reboot I > got a new access violation related to PTHREAD and > ACME (I don't > remember exactly the name of the process). > Then I was not able to install the VMS83A_SYS_V007 > update, cause I > have another ACCESS VIOLATION, during the product > install > (verification phase). > > During this last try, the emulator hung and on the > DOS console I had > the following error, looping: > > Unknown opcode: 00.00 > > Then when I pressed CTRL-C to stop everything, I got > on the DOS > console these other errors: > > Unknown opcode: 00.00 > Unknown opcode: 1c.23 > Unknown opcode: 1b.06 > Unknown opcode: 00.00 > Unknown opcode: 00.294000 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > Unknown opcode: 00.00 > > C:\Users\p\es40_cvs_exe> > > regards, > fausto > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > ______________________________________________ Enviado desde Correo Yahoo! Disfruta de una bandeja de entrada más inteligente. http://es.docs.yahoo.com/mail/overview/index.html |
|
From: Fausto S. <fa...@un...> - 2008-03-29 20:30:24
|
Hello all, some interesting news, from the installation world :-) Today I was able to install OpenVMS 8.3 without any ACCESS VIOLATION error. All went fine, in about one hour and half. I used ODS2, not ODS5. Anyway, the installation of CXML (a layered product) generates always an access violation. The DHCP client doesn't work (it starts but I have no IP address), and if I try to use a manual IP address when I have to set the HOST name in the host database I have a new ACCESS VIOLATION, so the TCPIP doesn't work for me. I installed successfully the UPDATE_V6 of VMS, but after the reboot I got a new access violation related to PTHREAD and ACME (I don't remember exactly the name of the process). Then I was not able to install the VMS83A_SYS_V007 update, cause I have another ACCESS VIOLATION, during the product install (verification phase). During this last try, the emulator hung and on the DOS console I had the following error, looping: Unknown opcode: 00.00 Then when I pressed CTRL-C to stop everything, I got on the DOS console these other errors: Unknown opcode: 00.00 Unknown opcode: 1c.23 Unknown opcode: 1b.06 Unknown opcode: 00.00 Unknown opcode: 00.294000 Unknown opcode: 00.00 Unknown opcode: 00.00 Unknown opcode: 00.00 Unknown opcode: 00.00 Unknown opcode: 00.00 Unknown opcode: 00.00 Unknown opcode: 00.00 C:\Users\p\es40_cvs_exe> regards, fausto |
|
From: Brian W. <bdw...@in...> - 2008-03-27 13:28:13
|
It looks like a variable declaration got dropped at some point.
In AliM1543C_ide.cpp, add
u32 base,control;
at line 1108, right before the do { block.
Now for the bigger problem: IDE instability. I've been pounding on it,
thinking that I've got some goofy lock problem, but after a quick
experiment it turns out that its not the case. I removed all of the
locking and it worked just fine -- in the sense that it behaves exactly
the same as when locking is enabled.
So, that begs a much bigger question: is it the threading or the cpu
clock that's causing the trouble? They both happened nearly at the same
time so I just assumed that there was locking issues, but I'm becoming
more concerned about the clock.
So...how does the clock work now compared to the single-threaded
clock?
Brian
|
|
From: Camiel V. <iam...@gm...> - 2008-03-26 19:40:47
|
Hello all, I've just committed a patch that aims to do the following: * Avoid the "warning: deprecated conversion from string constant to 'char*'" warnings. * Actually use the configuration data collected by the configure script. These changes work without problems on my windows and linux systems, but if there are any problems on other systems, I'd like to hear of it. Camiel. |
|
From: Camiel V. <iam...@gm...> - 2008-03-25 08:45:06
|
Hello Pepito, I fixed this. Thanks! Camiel. On Mon, Mar 24, 2008 at 9:14 PM, Pepito Grillo <pep...@ya...> wrote: > Hi! > I've had two errors compiling the latest from cvs. > Index: Cirrus.cpp > =================================================================== > RCS file: /cvsroot/es40/es40/src/Cirrus.cpp,v > retrieving revision 1.20 > diff -r1.20 Cirrus.cpp > 1396c1396 > < #endi > --- > > #endif > Index: System.cpp > =================================================================== > RCS file: /cvsroot/es40/es40/src/System.cpp,v > retrieving revision 1.73 > diff -r1.73 System.cpp > 2154c2154 > < state.pctl[pcibus].wsba[j], > state.pchip[pcibus].wsm[j], > --- > > state.pchip[pcibus].wsba[j], > state.pchip[pcibus].wsm[j], > Index: config_debug.h > =================================================================== > > > > > I have also a question. I can get TCPIP on OpenVMS to > work properly. > I get an error trying to configure the device. Any > idea? > > > Pepito > > > > ______________________________________________ > Enviado desde Correo Yahoo! > Disfruta de una bandeja de entrada más inteligente. http://es.docs.yahoo.com/mail/overview/index.html > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Pepito G. <pep...@ya...> - 2008-03-24 20:14:35
|
Hi!
I've had two errors compiling the latest from cvs.
Index: Cirrus.cpp
===================================================================
RCS file: /cvsroot/es40/es40/src/Cirrus.cpp,v
retrieving revision 1.20
diff -r1.20 Cirrus.cpp
1396c1396
< #endi
---
> #endif
Index: System.cpp
===================================================================
RCS file: /cvsroot/es40/es40/src/System.cpp,v
retrieving revision 1.73
diff -r1.73 System.cpp
2154c2154
< state.pctl[pcibus].wsba[j],
state.pchip[pcibus].wsm[j],
---
> state.pchip[pcibus].wsba[j],
state.pchip[pcibus].wsm[j],
Index: config_debug.h
===================================================================
I have also a question. I can get TCPIP on OpenVMS to
work properly.
I get an error trying to configure the device. Any
idea?
Pepito
______________________________________________
Enviado desde Correo Yahoo!
Disfruta de una bandeja de entrada más inteligente. http://es.docs.yahoo.com/mail/overview/index.html
|
|
From: Camiel V. <iam...@gm...> - 2008-03-21 14:29:13
|
Hi Brian,
On Thu, Mar 20, 2008 at 7:36 PM, Brian Wheeler <bdw...@in...> wrote:
> Camiel, is it possible (and/or legitimate) to do something like this:
>
> {
> SCOPED_WRITE_LOCK(some_rwlock);
> .
> .
> .
> some_rwlock->unlock();
> a_long_running_function_like_fread();
> some_rwlock->writeLock();
> .
> .
> .
> }
>
> So I can release my lock while trying to run the fread() on physical
> devices?
Yes, that should be possible. Just make sure that you always lock it
again in this case. The destructor on the ScopedLock will always try
to unlock it, and not all implementations like trying to unlock an
already unlocked mutex.
> Where does one put the -DDEBUG_IDE style flags when using configure?
This is something I've given considerable thought. I wanted to have a
couple of questions about this when running configure. At first I
wanted to do this from the configure script itself; I've been playing
around with a couple of m4 macro's that should do this, but never
managed to get it working. Using read failed because stdin was no
longer the terminal. So instead, I've changed the reconf script in
such a way that it renames the original configure script to
configure_2.sh; then it creates a script called configure_1.sh that
contains questions for debugging flags, and finally creates a new
configure script that calls configure_1.sh followed by configure_2.sh.
This is all in CVS now.
When you run ./configure now, you get a couple of questions such as:
camiel@linux-laptop:~/es40> ./configure
This is the debug-options configuration script for the ES40 emulator
If you don't want any debugging options enabled, answer YES to the
following question
Do you want the defaults for all options? [yes]: no
Do you want to show the cycle counter? [yes]:
Do you want to enable VGA debugging? [no]: yes
Do you want to enable Serial Port debugging? [no]: no
Do you want to enable one or more IDE debugging options? [no]: yes
Do you want to enable all IDE debugging? [no]: yes
Do you want to enable unknown memory access debugging? [no]: no
After which the normal configure script runs. If you ever want to
change debugging flags without running configure, simply run
./configure_1.sh
The debugging flags are stored in src/config_debug.h:
camiel@linux-laptop:~/es40> cat src/config_debug.h
// This file contains the debug configuration options.
// This file was generated by configure_1.sh
// Enable the cycle counter
//#define HIDE_COUNTER 1
// Enable VGA debugging
#define DEBUG_VGA 1
// Disable Serial Port debugging
//#define DEBUG_SERIAL 1
// Enable all IDE debugging
#define DEBUG_IDE 1
// Disable unknown memory access debugging
//#define DEBUG_UNKMEM 1
If you want to add debugging flags, don't change configure_1.sh
directly; instead, edit configure_1.m4; it has a list of debugging
options like this:
ES_ASK_DEBUG_Q(IDE Busmaster, IDE_BUSMASTER)
ES_ASK_DEBUG_Q(IDE Command, IDE_COMMAND)
ES_ASK_DEBUG_Q(IDE DMA, IDE_DMA)
ES_ASK_DEBUG_Q(IDE Interrupt, IDE_INTERRUPT)
ES_ASK_DEBUG_Q(IDE Command Register, IDE_REG_COMMAND)
ES_ASK_DEBUG_Q(IDE Control Register, IDE_REG_CONTROL)
ES_ASK_DEBUG_Q(IDE ATAPI Packet, IDE_PACKET)
ES_ASK_DEBUG_Q(IDE Thread, IDE_THREADS)
ES_ASK_DEBUG_Q(IDE Mutexes, IDE_LOCKS)
Then run ./reconfig, and you should have up-to-date configure scripts.
You should have Automake (1.10), Autoconf (2.61) and m4 (1.4.10). The
version numbers are those on my linux box, older versions might not
work with our scripts.
I'm pretty fond of this solution, but if there's anything in here
you're not happy with, please let me know.
Camiel.
|
1 message has been excluded from this view by a project administrator.
