basilisk-devel — Basilisk II development-related discussion

Re: [B2-devel] Re: MacOS X port of Basilisk II

[Christian B. <cb...@st...>]

Hi!

On Mon, Jul 02, 2001 at 11:33:23AM +1000, ni...@in... wrote:
> [B2 logo]
> 	Or maybe something like a bank vault or a museum?
> Something that stores old stuff? (both shiny-new, of course!)

I probably should contact the guy who already designed a B2 logo...

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[Brian J. <bjj...@us...>]

--- Christian Bauer <cb...@st...> wrote:
> 
> On Wed, Jul 18, 2001 at 01:16:37PM -0500, Brian Johnson wrote:
> > It's quite slow.  But I noticed that if I move the mouse
> > constantly, it seems to speed up to its usual rate.  Something to
> > do with the new X event loop?
> 
> Try switching the threaded vs. POSIX.4 timer 60Hz interrupt around
> in unix_main.cpp.

That didn't work so well:  one_tick() takes the interrupt flag lock
via SetInterruptFlag(), so whenever the thread servicing the timer
interrupt happened to be holding the lock already (eg. via EmulOp()),
BII would deadlock.  I tried changing timer_event.sigev_notify from
SIGEV_SIGNAL to SIGEV_THREAD, which should cause pthreads to start a
new thread to run one_tick() when the timer expires.  But I somehow
ran into a segv with SIGSEGV blocked or ignored, making IRIX SIGKILL
the process before dbx could get a look at it.

I also tried using the threaded code, but rearranging the loop in
tick_func() to look like the one in redraw_func().  That didn't
change anything.

As a hack, I tried calling one_tick() from redraw_func(), right after
the video refresh.  That changed the behavior:  the cursor flashed at
its "correct" rate when the mouse was still, but went faster than it
should have when I moved the mouse around.

The code in redraw_func() sure looks correct to me, no matter how long
select() delays....  perhaps I'm getting bad values from
GetTicks_usec()?  On a whim, I tried hacking GetTicks_usec() to use
gettimeofday() instead of clock_gettime().  No change.

						Brian J. Johnson

--------------------------------------------------------------------

   "mv emacs /vmunix"
                               -- The future according to Michael Rawdon

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[Christian B. <cb...@st...>]

Hi!

On Wed, Jul 18, 2001 at 01:16:37PM -0500, Brian Johnson wrote:
> It's quite slow.  But I noticed that if I move the mouse constantly,
> it seems to speed up to its usual rate.  Something to do with the new
> X event loop?

Try switching the threaded vs. POSIX.4 timer 60Hz interrupt around in
unix_main.cpp.

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

Re: [B2-devel] Re: New SIGSEGV code to be committed

[Brian J. <bjj...@us...>]

--- Gwenole Beauchesne <gb...@di...> wrote:
> 
> > The new code seems to work fine on IRIX, just like the old code did.
> 
> Is your SGI box using siginfo_t or a sigcontext subterfuge ?
> [Look at your config.h for the appropriate #define]

(Sorry it's taken so long for me to get back to you on this.)

#define HAVE_SIGINFO_T 1
/* #undef HAVE_SIGCONTEXT_SUBTERFUGE */


> > At least in 68030 mode.  Whenever I try to use 68030+FPU or 68040,
> > I get all kinds of nasty FP bugs, usually including wild
> > references and core dumps.  See bug 422776.  Is this a known
> > problem with the UAE FPU core on big endian or non-x68 systems?
> > I'm using MacOS 7.5.5.
> 
> What do you mean with wild references ?
> 
> When the FPE is enabled, do you get core dumps because the sigsegv
> handler fail to handle the faultive address or do you get some
> SIGBUS error because of possible mis-aligned accesses in the FPE
> code ?

Here's what I got on a recent CVS build.  Using 68030+FPU, direct
addressing, I started up the calculator and entered 4 / 3.  When I
typed the 3, B2 core dumped with a SIGBUS:

bjjsgi> dbx BasiliskII core
dbx version 7.3.2 73509_May21 MR May 21 2001 17:15:31
Core from signal SIGBUS: Bus error
(dbx) where
>  0 ::do_get_mem_word(0x84c9c000, 0xf72a62, 0x5c0ea5e, 0x0, 0x5c0e926, 0x4, 0xf7291a, 0x10107b28) ["/d3/BasiliskII2/BasiliskII/src/sony.cpp":40, 0x100c0fb0]
   1 ::m68k_run_1(void)(0x84c9c000, 0xf72a62, 0x5c0ea5e, 0x0, 0x10107b44, 0x6c74, 0x10107b30, 0x4edb82e) ["/d3/BasiliskII2/BasiliskII/src/sony.cpp":1223, 0x100374e0]
   2 ::m68k_go(int)(0x84c9c000, 0xf72a62, 0x5c0ea5e, 0x0, 0x10107b44, 0x6c74, 0x10107b30, 0x4edb82e) ["/d3/BasiliskII2/BasiliskII/src/sony.cpp":1253, 0x100c0ef8]
   3 ::main(0x1, 0x7fff2ec4, 0x5c0ea5e, 0x0, 0x10107b44, 0x6c74, 0x10107b30, 0x4edb82e) ["/d3/BasiliskII2/BasiliskII/src/main.cpp":558, 0x100d3758]
   4 __start() ["/xlv55/kudzu-apr12/work/irix/lib/libc/libc_n32_M4/csu/crt1text.s":177, 0x10033f48]
(dbx) $pc-16/8i
 [::m68k_reset(void):1078, 0x100c0fa0]  jr      ra
 [::m68k_reset(void):173, 0x100c0fa4]   sw      at,-6260(gp)
 [???, 0x100c0fa8]      nop
 [???, 0x100c0fac]      nop
*[::do_get_mem_word:40, 0x100c0fb0]     lbu     v1,0(a0)
 [::do_get_mem_word:40, 0x100c0fb4]     lbu     v0,1(a0)
 [::do_get_mem_word:40, 0x100c0fb8]     sll     v1,v1,8
 [::do_get_mem_word:40, 0x100c0fbc]     jr      ra
 [::do_get_mem_word:40, 0x100c0fc0]     or      v0,v0,v1
r0/zero=0x0     r1/at=0xf72a66
r2/v0=0xffffffff80000000        r3/v1=0x4e00
r4/a0=0xffffffff84c9c000        r5/a1=0xf72a62
r6/a2=0x5c0ea5e r7/a3=0x0
r8/a4=0x5c0e926 r9/a5=0x4
r10/a6=0xf7291a r11/a7=0x10107b28
r12/t0=0x10107b44       r13/t1=0x6c74
r14/t2=0x10107b30       r15/t3=0x4edb82e
r16/s0=0x1      r17/s1=0x7fff2ec4
r18/s2=0x7fff2ecc       r19/s3=0x7fff2fc8
r20/s4=0x0      r21/s5=0x0
r22/s6=0x0      r23/s7=0x101103e8
r24/t8=0xf72926 r25/t9=0x1007d7c0
r26/k0=0x0      r27/k1=0x50087e72a
r28/gp=0x1010f570       r29/sp=0x7fff2c10
r30/s8/fp=0x0   r31/ra=0x100374e8

mdlo=0x1e       mdhi=0x2
cause=0x10      pc=0x100c0fb0
fpcsr=0x41800004        sr=0x0
badvaddr=0x84c9c000     fpeir=0x0

Looks like it tried to load from a bad Mac PC value.  It's suspicious
that v0 (the return value from a recent subroutine) is
0xffffffff80000000... sign extension problem?


> BTW, do MIPS processors support 128-bit FP precision ?

No.  Just single- (32-bit) and double-precision (64-bit) IEEE.

> > (Although the new code does change the symptoms of the problem a
> > bit:  now direct addressing core dumps (with an appropriate
> > message from the segv handler) and real mode hangs Speedometer.)
> 
> Could you tell me the address reported by the segv handler and the
> MEMBaseDiff offset value ?

I'm having trouble tracking it down...   perhaps it got optimized
away.

> I used to get a crash in real mode with Speedometer under Linux/x86.
> Probably the patch I added in rom_patches.cpp make it hang on a
> big-endian system ?
> 
> Can you disable the patch and tell me if it crashes for you too ?
> [Search for "Speedometer" in rom_patches.cpp]

That looks like it only applies to real addressing.  This latest crash
happened with direct addressing.

						Brian

--------------------------------------------------------------------

   "My bicycle is an elegant form of transportation.  It carries me far
    faster than I can run, yet I can carry it with one hand."
                                           -- me

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[Brian J. <bjj...@us...>]

--- Christian Bauer <cb...@st...> wrote:
> 
> On Wed, Jul 11, 2001 at 12:49:08PM -0500, Brian Johnson wrote:
> > But I do get a BadMatch error whenever I try to switch into monochrome
> > mode:
> 
> I think I just fixed that.

Yep, it works now.  Thanks!

> > One other oddity:  Maelstrom seems to run slowly, perhaps about half
> > the speed it should.
> 
> Does the caret cursor ("General Controls") blink faster or slower?

It's quite slow.  But I noticed that if I move the mouse constantly,
it seems to speed up to its usual rate.  Something to do with the new
X event loop?

						Brian

--------------------------------------------------------------------

   "We are Microsoft. UNIX is irrelevant.  OS/2 is irrelevant. Openness
    is futile.  Prepare to be assimilated."
                                           -- pr...@tu...
                                           -- (quoted by Eric Berggren)

Re: [B2-devel] Re: BasiliskII/src/Unix video_x.cpp

[<gb...@di...>]

Hi,

> Sounds like a window manager problem to me. I've read the relevant sectio=
ns
> in the ICCCM again and I believe that the implementation in B2 is correct=
.
> I've tried it with twm and Sawfish and observe none of these effects.

That's odd, the tests with Speedometer 3.2x don't show those effects,
but do with Speedometer 4.0x when depth changes or B2 is booting. I will
try with another window manager than kwm (KDE 2.1.1).

Note however that I don't see those effects with XFree 4.1 on my machine
at work and the same (if memory still goes well) KDE version. I will
also try on the Debian system.

Bye,
Gwenol=E9.

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[<gb...@di...>]

Hi,

> > But I do get a BadMatch error whenever I try to switch into monochrome
> > mode:
>=20
> I think I just fixed that.

Indeed. So does the crash due to double deallocation.

Thanks,
Gwenol=E9.

Re: [B2-devel] Re: BasiliskII/src/Unix video_x.cpp

[Christian B. <cb...@st...>]

Hi!

On Sat, Jul 14, 2001 at 12:35:38PM +0100, Gwenole Beauchesne wrote:
> I have just tried with CVS 13/07/2001, the palette is still changed with
> inconsistent values.

Sounds like a window manager problem to me. I've read the relevant sections
in the ICCCM again and I believe that the implementation in B2 is correct.
I've tried it with twm and Sawfish and observe none of these effects.

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[Christian B. <cb...@st...>]

Hi!

On Wed, Jul 11, 2001 at 12:49:08PM -0500, Brian Johnson wrote:
> But I do get a BadMatch error whenever I try to switch into monochrome
> mode:

I think I just fixed that.

> One other oddity:  Maelstrom seems to run slowly, perhaps about half
> the speed it should.

Does the caret cursor ("General Controls") blink faster or slower?

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

Re: [B2-devel] Re: BasiliskII/src/Unix video_x.cpp

[<gb...@di...>]

> On Sun, Jul 01, 2001 at 08:03:30AM +0200, Gwenole Beauchesne wrote:
> > Well, when I start B2, the display has psychadelic colors (as if the
> > color palette changed but it can't [1]) then I focus onto another
> > window. The colors become as expected when I simply switch back to the
> > B2 window.
> 
> Could you try again with the latest CVS sources? There have been lots
> of small changes and fixes to the gamma table code.

I have just tried with CVS 13/07/2001, the palette is still changed with
inconsistent values.

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[<gb...@di...>]

Hi,

> I haven't seen that particular problem; running just the QuickDraw
> section of the Speedometer tests seems to work fine on my box.  But I
> do get a BadMatch error whenever I try to switch into monochrome mode:
>=20
>   Gdk-ERROR **: BadMatch (invalid parameter attributes)
>   serial 3461 error_code 8 request_code 1 minor_code 0

Indeed, I so that in the train on a Linux/ppc box too. Actually, it
seems we can take the default colormap in 1-bit mode only if

        vis =3D=3D DefaultVisual(x_depth, screen) as well

[see the window driver just befor XCreateWindow() is called]

> (BTW, we should be able to greatly increase blitter performance by
> doing 64-bit loads and stores on machines which can do them directly.
> Something to think about.)

Yes, I will have a look at it now that I have access to a full 64-bit
system ;-)

Bye,
Gwenol=E9.

Re: [B2-devel] Problems with Speedometer 4.x & depth switching

[Brian J. <bjj...@us...>]

--- Gwenole Beauchesne <gb...@di...> wrote:
> 
> While performing a few tests with Speedometer 4.x, in "all tests"
> (cmd-'A') mode, the first graphics test will switch the depth and
> then restores it back for the disk and fpu performance test.
> 
> Then, "Benchmark mix" and "FPU benchmark" tests are run. Finally, in
> "QuickDraw tests" the depth is switched again, test is carried out,
> but when it's time to switch depth back to its original value, B2
> crashes with the following.
> 
> do_handle_screen_fault: unhandled address 0x8
> ...

I haven't seen that particular problem; running just the QuickDraw
section of the Speedometer tests seems to work fine on my box.  But I
do get a BadMatch error whenever I try to switch into monochrome mode:

  Gdk-ERROR **: BadMatch (invalid parameter attributes)
  serial 3461 error_code 8 request_code 1 minor_code 0

The other video modes seem to work just great, and B2 finds an
appropriate visual for all of them (my machine supports 8, 12, 15, and
24 plane visuals.)  They are even pretty fast, as reported by
Speedometer.  Although the basic CPU performance seems to have taken a
hit in recent weeks.  I should run some more performance profiles...

(BTW, we should be able to greatly increase blitter performance by
doing 64-bit loads and stores on machines which can do them directly.
Something to think about.)

One other oddity:  Maelstrom seems to run slowly, perhaps about half
the speed it should.  This is under either a 30hz or 60hz refresh
rate.  I think the latest round of changes to the video and timing
code introduced the problem; I believe it was fine (and even a bit too
fast) with the first iterations of the depth switching code.

						Brian

--------------------------------------------------------------------

  "Great works are performed not by power, but by perseverance."
                                           -- Samuel Johnson

[B2-devel] Problems with Speedometer 4.x & depth switching

[Gwenole B. <gb...@di...>]

Hi,

While performing a few tests with Speedometer 4.x, in "all tests"
(cmd-'A') mode, the first graphics test will switch the depth and then
restores it back for the disk and fpu performance test.

Then, "Benchmark mix" and "FPU benchmark" tests are run. Finally, in
"QuickDraw tests" the depth is switched again, test is carried out, but
when it's time to switch depth back to its original value, B2 crashes with
the following.

do_handle_screen_fault: unhandled address 0x8
D0: 00000000 D1: 0000003a D2: 00000004 D3: 00000001
D4: 00000084 D5: 00000004 D6: 00000001 D7: 0000000c
A0: 01d2d1f6 A1: 000092a0 A2: 00009350 A3: 000092a0
A4: 00002128 A5: 01d348d8 A6: 01d2d11a A7: 01d2d0ae
USP=3D00000000 ISP=3D01d2d0ae MSP=3D00000000 VBR=3D00000000
T=3D00 S=3D1 M=3D0 X=3D0 N=3D0 Z=3D0 V=3D0 C=3D0 IMASK=3D0
FP0: 0 FP1: 0 FP2: 0 FP3: 0
FP4: 0 FP5: 0 FP6: 0 FP7: 0
N=3D0 Z=3D0 I=3D0 NAN=3D0
0000938a: 7119 0c68 0001 001a 6604 ILLEGAL.L
next PC: 0000938c

That's in EmulOp VIDEO_CONTROL and I suspect a null pointer offset by 8.

Bye,
Gwenol=E9 [investigating if time permits it]

Re: [B2-devel] Re: Visuals?

[Christian B. <cb...@st...>]

Hi!

On Mon, Jul 09, 2001 at 01:16:25PM -0500, Brian Johnson wrote:
>      o    Certain fields in the XSetWindowAttributes structure that is passed
>           to XCreateWindow(3X) must be consistent with the visual and depth.

It seems that it is _required_ to set the background_pixel, border_pixel and
colormap attributes to use non-default visuals. Anyway, I think it works now
(it does with my Matrox 8+24 mode). The code is in CVS.

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

[B2-devel] Re: Visuals?

[Brian J. <bjj...@us...>]

On 9 Jul 2001 Brian Johnson wrote:
> On 6 Jul 2001 Christian Bauer wrote:
> > 
> > I've committed some code that tries to select an optimal visual
> > for the requested Mac color depth. However, I was only able to
> > test it with X servers that support exactly one depth so it is
> > possible that some logic in the code is wrong. I have tried it
> > with the 8+24 overlay mode of my Matrox card with XFree86 4.0.3
> > but that gives me a BadMatch error when trying to open a 24-bit
> > window, for no apparent reason.
> 
> I see similar behavior on my SGI box, with a 24-bit default visual.
> I forget what my default Mac video settings are... probably 8 bit.
> B2 starts booting, but appears to try to change the video modes at
> some point, and dies with a BadMatch error: ...

Here's some interesting info from the VkVisual man page which may be
relevant:

REVIEW OF X11 VISUAL INFORMATION
     Many developers do not quite understand how X and Xt deal with
     information that is related to X11 visuals.  This information is
     important if one is going to put part or all of an application's GUI in a
     non-default visual.  Following is a summary of some of the more important
     points.

   X11 Visual Attributes
     X11 does not attach any semantic meaning to a visual.  For example, there
     is no concept of an "overlay visual".  There is, however, a semi-standard
     convention that has been adopted by SGI and by some other workstation
     vendors:

     o    A visual's level is the framebuffer level the visual is associated
          with.  This is a hardware-related term.  It has nothing to do with X
          window stacking order.

     o    Levels less than zero are underlays.  As of this writing (8/96), SGI
          has no hardware that has underlay planes that are supported by the X
          server.

     o    Level zero is the normal planes.  The default visual is generally
          (but not necessarily) in the normal planes.

     o    Levels greater than zero are overlay planes.

     o    Each X11 visual is associated with exactly one level.

     o    SERVER_OVERLAY_VISUALS is a property on the root window, relating
          each X11 visual to its level.

     An X11 window has several attributes that need to be consistent when the
     window is created.  If an application sets these values inconsistently,
     or if it allows an inconsistent value to be inherited, the X server will
     return a fatal BadMatch error.

     o    XCreateWindow(3X) must be passed a consistent visual and depth.

     o    Certain fields in the XSetWindowAttributes structure that is passed
          to XCreateWindow(3X) must be consistent with the visual and depth.
          The significant fields are:

          background pixmap - must be NULL or of the stated depth.

          background pixel - is used if the background pixmap is NULL.  The
          pixel value must not exceed the colormap size.

          border pixmap - must be NULL or of the stated depth.

          border pixel - is used if the border pixmap is NULL.  The pixel
          value must not exceed the colormap size.

          colormap - must match the visual.

     The depth and visual cannot be changed after the window is created.  The
     XSetWindowAttributes values can  be changed later.

						Brian

--------------------------------------------------------------------

  "With this scheme, it is straightforward to locate a Transport Service
   Access Point anywhere in the known universe."
                                           -- Tanenbaum

[B2-devel] Re: Patch for daylight savings time

[Brian J. <bjj...@us...>]

Christian Bauer wrote:
> On Thu, Jul 05, 2001 at 02:13:35PM -0500, Brian Johnson wrote:
> > But wouldn't the easier way to do this be to call localtime(), and
> > reconstruct the local time in seconds from the tm_sec, tm_min,
> > tm_hour, tm_yday, and tm_year fields?
> 
> Excellent idea. I've committed some code to the CVS that adds a
> TimeToMacTime(time_t) function for this purpose. The TIME_OFFSET constant
> is gone, and the file dates in the ExtFS are also correct now.

That seems to have broken timer_unix.cpp for Irix, where Delay_usec()
needs pthread.h:

--- timer_unix.cpp      2001/07/09 11:22:00     1.11
+++ timer_unix.cpp      2001/07/09 14:02:09
@@ -233,6 +233,7 @@
 #elif defined(HAVE_PTHREADS) && defined(sgi)
 // SGI pthreads has a bug when using pthreads+signals+nanosleep,
 // so instead of using nanosleep, wait on a CV which is never signalled.
+#include <pthread.h>
 #define USE_COND_TIMEDWAIT
 #endif

						Brian

--------------------------------------------------------------------

   "Occasionally get out of the office, the lab, the computer room, smell
    the flowers and take a look at the physical world around you."
                                           -- Rob Cook

[B2-devel] Re: Visuals?

[Brian J. <bjj...@us...>]

On 6 Jul 2001 Christian Bauer wrote:
> On Thu, Jul 05, 2001 at 02:29:08PM -0500, Brian Johnson wrote:
> > Could BII be made to choose the visual with the lowest depth greater
> > than or equal to the requested Mac screen depth?
> 
> I've committed some code that tries to select an optimal visual for the
> requested Mac color depth. However, I was only able to test it with X
> servers that support exactly one depth so it is possible that some logic
> in the code is wrong. I have tried it with the 8+24 overlay mode of my
> Matrox card with XFree86 4.0.3 but that gives me a BadMatch error when
> trying to open a 24-bit window, for no apparent reason.

I see similar behavior on my SGI box, with a 24-bit default visual.
I forget what my default Mac video settings are... probably 8 bit.  B2
starts booting, but appears to try to change the video modes at some
point, and dies with a BadMatch error:

  bjjsgi> ./BasiliskII
  Basilisk II V0.9 by Christian Bauer et al.
  Reading ROM file...
  WARNING: Cannot open /d3/floppy (No such file or directory)
  Using libaudio audio output
  Gdk-ERROR **: BadMatch (invalid parameter attributes)
    serial 296 error_code 8 request_code 1 minor_code 0

A few months ago I tried hardcoding a non-default visual number, just
to see if it worked, and I got the same result.  Is there some special
magic needed to use non-default visuals?

						Brian

--------------------------------------------------------------------

   Q:  How many Microsoft programmers does it take to change a lightbulb?  
   A:  None.  They don't bother.  They simply change the standard
       to darkness.
                                           -- Shad Aumann

[B2-devel] Recent VOSF changes

[Gwenole B. <gb...@di...>]

Hi,

Recent changes in VOSF code (between 2001/07/02 and today) were intented
to workaround a few problems on Linux/ia64. Unfortunately, those changes
seem to have yielded lesser performance in windowed mode (around 18%!) on
other architectures (say a P3/800).

Sorry for the inconvenience, I will try to fix that soon.

Bye,
Gwenol=E9.

Re: [B2-devel] Visuals?

[Christian B. <cb...@st...>]

Hi!

On Thu, Jul 05, 2001 at 02:29:08PM -0500, Brian Johnson wrote:
> Could BII be made to choose the visual with the lowest depth greater
> than or equal to the requested Mac screen depth?

I've committed some code that tries to select an optimal visual for the
requested Mac color depth. However, I was only able to test it with X
servers that support exactly one depth so it is possible that some logic
in the code is wrong. I have tried it with the 8+24 overlay mode of my
Matrox card with XFree86 4.0.3 but that gives me a BadMatch error when
trying to open a 24-bit window, for no apparent reason. Several parts of
GNOME also crash in the 8+24 mode, so I suspect an X server bug. The
8-bit visuals work fine, but have some kind of "semitransparency" that
is a miracle to me...

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

Re: [B2-devel] Patch for daylight savings time

[Christian B. <cb...@st...>]

Hi!

On Thu, Jul 05, 2001 at 02:13:35PM -0500, Brian Johnson wrote:
> But wouldn't the easier way to do this be to call localtime(), and
> reconstruct the local time in seconds from the tm_sec, tm_min,
> tm_hour, tm_yday, and tm_year fields?

Excellent idea. I've committed some code to the CVS that adds a
TimeToMacTime(time_t) function for this purpose. The TIME_OFFSET constant
is gone, and the file dates in the ExtFS are also correct now.

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

[B2-devel] Visuals?

[Brian J. <bjj...@us...>]

X wizards,

Knowing next to nil about X programming I'm a bit out of my league
here, but it looks like the new video depth support code always uses
the X display's default visual, with a corresponding pixmap depth and
layout.  That seems suboptimal for X servers like SGI's, which support
dozens of visuals at many depths (see bug 217330 for a complete list:
  http://sourceforge.net/tracker/index.php?func=detail&aid=217330&group_id=2123&atid=102123
It's a bit long to include here.)

Could BII be made to choose the visual with the lowest depth greater
than or equal to the requested Mac screen depth?  I'd think that would
cut down drastically on the amount of data movement needed, especially
when running in Mac 8-bit mode using the raw copy blitter.

BTW, the on-the-fly depth and resolution switching really rocks!  I
can play Maelstorm and Continuum just as well as on a real Mac.  Now I
have to get volume support into the Irix sound driver so I don't
distract my coworkers....

						Brian

--------------------------------------------------------------------

  Ethernet (n): something used to catch the etherbunny
                                           -- Quoted by Khan Tran

[B2-devel] Patch for daylight savings time

[Brian J. <bjj...@us...>]

I finally tracked down why the MacOS time always reas as GMT when
running BII on Irix:  the __SVR4 case in TimerDateTime() wasn't
getting selected, since Irix defines _SVR4_SOURCE instead of __SVR4.

But even with fixed #ifdefs, it didn't pick up on daylight savings
time.  Apparently Irix uses separate globals for the offset from GMT
for daylight savings time and standard time.  The following seems to
do the right thing on Irix:

> cvs diff -u timer_unix.cpp
Index: timer_unix.cpp
===================================================================
RCS file: /cvs/BasiliskII/src/Unix/timer_unix.cpp,v
retrieving revision 1.9
diff -u -r1.9 timer_unix.cpp
--- timer_unix.cpp      2001/02/02 20:52:58     1.9
+++ timer_unix.cpp      2001/07/05 19:01:26
@@ -60,6 +60,9 @@
        time_t utc_now = time(NULL);
 #if defined(__linux__) || defined(__SVR4)
        time_t local_now = utc_now - timezone;
+#elif defined(sgi)
+       time_t local_now = utc_now - (localtime(&utc_now)->tm_isdst ?
+                                     altzone : timezone);
 #elif defined(__FreeBSD__) || defined(__NetBSD__)
        time_t local_now = utc_now + localtime(&utc_now)->tm_gmtoff;
 #else


I have no idea if "altzone" is supported on any other systems; the
Linux man pages don't mention it.

But wouldn't the easier way to do this be to call localtime(), and
reconstruct the local time in seconds from the tm_sec, tm_min,
tm_hour, tm_yday, and tm_year fields?  That way localtime() would do
all the timezone and daylight savings time adjustments, in a fully
portable way.

						Brian

--------------------------------------------------------------------

  "Think big thoughts but relish small pleasures."
                                        -- Life's Little Instruction Book

[B2-devel] Re: MacOS X port of Basilisk II

[<ni...@in...>]

Gwenole wrote:
> 2. Mixing C++ and Objective-C is not quite possible at the current time.
> Therefore, Nigel implemented a few C wrappers. However, I think we don't
> need them if we declare functions in src/include/*.h with "C" external
> linkage. If this approach works, I will remove Nigel's C wrappers and
> commit patched versions of includes with various #ifndef __cplusplus__ /
> extern "C" clauses.

I commented:
> 1) I think that will just cause link errors, as the files would have been
>    compiled one way (as C++ interfaces, because they are in .cpp files),
>    but referenced as another. (C interfaces in my Objective-C source)

Gwenole said:
> No, they will have "C" linkage because they would have been declared as
> such (extern "C").

	If you insert #ifndef __cpluscplus__ wrappers, wouldn't the
declaration depend on the compiler which is processing them, and thus
vary between the .cpp and .m files?


Apple copyright stuff deleted
...
> >       I haven't looked at that site yet, but it could potentially be
> > a problem, as could some of the structures I typed into extfs_MacOSX.cpp
> 
> OK if that's a problem, I will keep the "unix" version if it works. I
> haven't tried it yet with my Darwin/X11 port.

	The unix version works, but because OS X uses different
conventions for storing the resource and finder files, it isn't
very useful. i.e. You cannot access programs stored on MacOS X
mounted HFS volumes.

	The structures I put in extfs_MacOSX.cpp are similar,
copyright wise, to the stuff in macos_util.h. They are based on
information published by Apple (whether from Inside Macintosh,
or from the Apple Universal Headers).

	I suspect that if we rename or obfuscate the stuff I have
typed in, that will be enough to get around any copyright issues.
But then again, I am not a lawyer, and Apple might be monitoring
this very mailing list :-)


I wrote:
> 	What if I produce a parody of the happy face, like a wrinkled
> old version thereof?

Christian answered:
> 
> B2 is not a wrinkled version of anything! ;-)

	True, but B2 emulates an old Mac, running an old MacOS.
That is what it could mean.

	Or maybe something like a bank vault or a museum?
Something that stores old stuff? (both shiny-new, of course!)

-- 
| Nigel Pearson, ni...@in... | "Reality is that which,   |
|   Telstra NW-D, Sydney, Australia.    |  when you stop believing  |
| Office: 9206 3468    Fax:  9212 6329  |  in it, doesn't go away." |
| Mobile: 0408 664435  Home: 9792 6998  | Philip K. Dick - 'Valis.' |

Re: [B2-devel] Re: [Basilisk-cvs] BasiliskII/src/Unix video_x.cpp

[Christian B. <cb...@st...>]

On Sun, Jul 01, 2001 at 08:03:30AM +0200, Gwenole Beauchesne wrote:
> Well, when I start B2, the display has psychadelic colors (as if the
> color palette changed but it can't [1]) then I focus onto another
> window. The colors become as expected when I simply switch back to the
> B2 window.

Could you try again with the latest CVS sources? There have been lots
of small changes and fixes to the gamma table code.

Bye,
Christian

-- 
  / Coding on PowerPC and proud of it
\/ http://www.uni-mainz.de/~bauec002/

[B2-devel] Re: [Basilisk-cvs] BasiliskII/src/Unix video_x.cpp

[<gb...@di...>]

Hi,

> Log Message:
> gamma tables work with X11

Well, when I start B2, the display has psychadelic colors (as if the
color palette changed but it can't [1]) then I focus onto another
window. The colors become as expected when I simply switch back to the
B2 window.

Footnotes:
[1] I am using XFree 4.0.3 in 16 bpp mode.

Bye,
Gwenol=E9