From owner-freebsd-sparc64@FreeBSD.ORG Mon Oct 24 09:37:45 2005 Return-Path: X-Original-To: freebsd-sparc64@FreeBSD.org Delivered-To: freebsd-sparc64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2505716A41F for ; Mon, 24 Oct 2005 09:37:45 +0000 (GMT) (envelope-from reko.turja@liukuma.net) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83AEF43D46 for ; Mon, 24 Oct 2005 09:37:43 +0000 (GMT) (envelope-from reko.turja@liukuma.net) Received: from rekon ([213.113.4.180] [213.113.4.180]) by mxfep02.bredband.com with SMTP id <20051024093742.FFXN11792.mxfep02.bredband.com@rekon> for ; Mon, 24 Oct 2005 11:37:42 +0200 Message-ID: <065301c5d87e$979b1850$b40471d5@rekon> From: "Reko Turja" To: Date: Mon, 24 Oct 2005 12:37:46 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Cc: Subject: Sbus qec network driver - in system already or possible to port? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2005 09:37:45 -0000 I acquired some old ultrasparcs from the "junk room" of our school and to my delight found out that all three of them are capable of running FreeBSD/sparc64. I'm considering using the Ultra1 I got as a firewall at home as it has decent enough processor and memory for firewall use, but have still one stumbling block I need to solve. I have older 4 port quad-port sbus card (http://docs.sun.com/source/800-7123-11/ch1.html) readily available, but there seems to be no driver for it (both Net and Open do support the card however). So the base question is whether there already is compatible driver in the system or is it possible with very mediocre C skills to use the existing drivers from netbsd or openbsd and port those to FreeBSD? -Reko (uname -a and dmesg are as follows, I'm aware of dying battery btw ;)) FreeBSD testmachine.some.net 6.0-RC1 FreeBSD 6.0-RC1 #0: Mon Oct 10 20:37:51 UTC 2005 root@u60.samsco.home:/usr/obj/usr/src/sys/GENERIC sparc64 stray vector interrupt 2033 Copyright (c) 1992-2005 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 6.0-RC1 #0: Mon Oct 10 20:37:51 UTC 2005 root@u60.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "tick" frequency 167000000 Hz quality 1000 real memory = 268435456 (256 MB) avail memory = 241369088 (230 MB) cpu0: Sun Microsystems UltraSparc-I Processor (167.00 MHz CPU) nexus0: sbus0: on nexus0 sbus0: clock 25.000 MHz sbus dvma: DVMA map: 0xfc000000 to 0xffffffff sbus0: [FAST] sbus0: [FAST] initializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 100 auxio0: mem 0x1900000 on sbus0 sbus0: mem 0xc000000-0xc0001ff irq 2020 type unknown (no driver attached) sbus0: mem 0-0x7ffff,0x1380000-0x13fffff type unknown (no driver attached) sbus0: mem 0x1400000-0x1400007 irq 2025 type block (no driver attached) eeprom0: mem 0x1200000-0x1201fff on sbus0 eeprom0: model mk48t59 eeprom0: mk48txx_attach: battery low eeprom0: cannot attach time of day clock device_attach: eeprom0 attach returned 6 puc0: mem 0x1100000-0x1100003 irq 2024 on sbus0 uart0: on puc0 uart1: on puc0 puc1: mem 0x1000000-0x1000003 irq 2024 on sbus0 uart2: on puc1 uart2: keyboard (1200,n,8,1) kbd0 at sunkbd0 uart3: on puc1 sbus0: mem 0x1300000-0x1300007 type unknown (no driver attached) sbus0: mem 0x1304000-0x1304002 type unknown (no driver attached) esp0: mem 0x8800000-0x880000f,0x8810000-0x881003f irq 2016 on sbus0 esp0: FAS366/HME, 40MHz, SCSI ID 7 hme0: mem 0x8c00000-0x8c00107,0x8c02000-0x8c03fff,0x8c04000-0x8c05fff,0x8c06000-0x8c07fff,0x8c07000-0x8c0701f irq 2017 on sbus0 miibus0: on hme0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 08:00:20:13:de:ad sbus0: mem 0xc800000-0xc80001b irq 2018 type unknown (no driver attached) sbus0: mem 0-0x7fff,0x10000-0x17fff,0x20000-0x20fff,0x30000-0x30cff,0x40000-0x40003,0x400000-0x5fffff irq 1989 type unknown (no driver attached) sbus0: mem 0x20000-0x2ffff,0x40000-0x5ffff irq 1996 type unknown (no driver attached) creator0: on nexus0 creator0: console creator0: resolution 1152x900 syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x300> Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle cd0 at esp0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 15) cd0: cd present [76760 x 512 byte records] da0 at esp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) Trying to mount root from ufs:/dev/da0a warning: no time-of-day clock registered, system time will not be set accurately