Re: FYI, I've switched my primary desktop to AMD64.

2003-10-17 Thread Joe Marcus Clarke
On Fri, 2003-10-17 at 13:17, Peter Wemm wrote:
[snip]

> I've been working on getting mozilla-firebird up and running but that is
> easier said than done because the core infrastructure (nspr, xpcom etc)
> haven't got official support for amd64 yet.  There are patches in the
> bugzilla database though.  If all else fails, I'll use remote X from my
> laptop or something evil like that.  Or finish off the 32 bit i386 binary
> support (I need to do that anyway - I haven't even tried to see if a
> FreeBSD/i386 binary of mozilla works, it might already work)

Please let me know when you have the nspr and xpcom patches, and I'll
make sure they get committed to out repo.  I'm not sure how helpful it
will be, but Marcel has done most of the work on the ia64 side for
Mozilla, and those patches are already in our tree.  Thanks.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc




signature.asc
Description: This is a digitally signed message part


FYI, I've switched my primary desktop to AMD64.

2003-10-17 Thread Peter Wemm
I finally worked up the nerve to commit to eating my own dogfood.  :-)

I've actually been doing my primary development on amd64 boxes for a while,
and now that the consumer products have been officially launched, I figured
it was about time.  Most of the key components are in place.

I've upgraded my home machine to an Asus SK8N + Athlon64 FX-51 (niiice!).
My i386 box is in pieces, there is no going back now.  For some strange
reason I've had to pay attention to some of the sharp edges I'd been putting
off for a while.

I'm using an older nvidia geforce4 ti4200 for the video, so I had to fix
a misconfiguration in the Xserver (I forgot to have it open /dev/io).  The
previous cards I'd used were all matrox which were solely mmio driven and
didn't run into this problem.

I've been working on getting mozilla-firebird up and running but that is
easier said than done because the core infrastructure (nspr, xpcom etc)
haven't got official support for amd64 yet.  There are patches in the
bugzilla database though.  If all else fails, I'll use remote X from my
laptop or something evil like that.  Or finish off the 32 bit i386 binary
support (I need to do that anyway - I haven't even tried to see if a
FreeBSD/i386 binary of mozilla works, it might already work)

Anyway, the 24 hours later status is: Thumbs up!

And now to do the same thing to my work desktop.  I'm planning to use
an Asus K8V + Athlon64 3200+ there.

Anyway, in case anybody is interested, the dmesg of my home box looks like
this:
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #3: Thu Oct 16 11:37:26 PDT 2003
[EMAIL PROTECTED]:/home/src/sys/amd64/compile/OVERCEE
Preloaded elf kernel "/boot/kernel/kernel" at 0x806ef000.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 FX-51 Processor (2200.01-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0xf58  Stepping = 8
  
Features=0x78bfbff
  AMD Features=0xe050
real memory  = 1072955392 (1023 MB)
avail memory = 1011191808 (964 MB)
Pentium Pro MTRR support enabled
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_cpu0:  port 0x530-0x537 on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
isab0:  at device 1.0 on pci0
isa0:  on isab0
pci0:  at device 1.1 (no driver attached)
ohci0:  mem 0xfebfd000-0xfebfdfff irq 11 at device 2.0 
on pci0
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0:  on ohci0
usb0: USB revision 1.0
uhub0: (0x10de) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1:  mem 0xfebfe000-0xfebfefff irq 5 at device 2.1 
on pci0
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1:  on ohci1
usb1: USB revision 1.0
uhub1: (0x10de) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0:  mem 0xfebffc00-0xfebffcff irq 10 at device 
2.2 on pci0
ehci_pci_attach: companion usb0
ehci_pci_attach: companion usb1
usb2: EHCI version 1.0
usb2: companion controllers, 4 ports each: usb0 usb1
usb2:  on ehci0
usb2: USB revision 2.0
uhub2: (0x10de) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
pcm0:  port 0xec00-0xec7f,0xe800-0xe8ff mem 0xfebfb000-0xfebfbfff irq 
11 at device 6.0 on pci0
pcm0: 
atapci0:  port 0xffa0-0xffaf at device 8.0 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
pcib1:  at device 10.0 on pci0
pci1:  on pcib1
ahc0:  port 0xd800-0xd8ff mem 0xfc9ff000-0xfc9f irq 5 
at device 4.0 on pci1
aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs
fxp0:  port 0xdf00-0xdf3f mem 
0xfc80-0xfc8f,0xfc9fe000-0xfc9fefff irq 11 at device 5.0 on pci1
fxp0: Ethernet address 00:d0:b7:21:31:94
miibus0:  on fxp0
inphy0:  on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
puc0:  port 0xdfe0-0xdfe7,0xdff0-0xdff7,0xdf80-0xdf9f irq 11 
at device 6.0 on pci1
sio4:  on puc0
sio4: type 16550A
sio4: unable to activate interrupt in fast mode - using normal mode
sio5:  on puc0
sio5: type 16550A
sio5: unable to activate interrupt in fast mode - using normal mode
puc1:  port 0xdfa0-0xdfa7,0xdfa8-0xdfaf,0xdf40-0xdf5f irq 5 
at device 7.0 on pci1
sio6:  on puc1
sio6: type 16550A
sio6: unable to activate interrupt in fast mode - using normal mode
sio7:  on puc1
sio7: type 16550A
sio7: unable to activate interrupt in fast mode - using normal mode
atapci1:  port 
0xdc00-0xdc7f,0xdf60-0xdf6f,0xde80-0xdebf mem 
0xfc9a-0xfc9b,0xfc9fd000-0xfc9fdfff irq 11 at device 8.0 on pci1
atapci1: [MPSAFE]
ata2: at 0xfc9fd000 on atapci1
ata2: [MPSAFE]
ata3: at 0xfc9fd000 on atapci1
ata3: [MPSAFE]
ata4: at 0xfc9fd000 on atapci1
ata4: [MPSAFE]
fwohci0:  mem 
0xfc9f8000-0xfc9fbfff,0xfc9fc80