From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 14:13:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1308837B401 for ; Fri, 4 Jul 2003 14:13:51 -0700 (PDT) Received: from remt28.cluster1.charter.net (remt28.cluster1.charter.net [209.225.8.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id B93424400B for ; Fri, 4 Jul 2003 14:13:49 -0700 (PDT) (envelope-from glennpj@charter.net) Received: from [24.158.214.251] (HELO gforce.johnson.home) by remt28.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6) with ESMTP id 81329332; Fri, 04 Jul 2003 17:13:48 -0400 Received: from gforce.johnson.home (localhost [127.0.0.1]) by gforce.johnson.home (8.12.9/8.12.9) with ESMTP id h64LDlgc000775; Fri, 4 Jul 2003 16:13:47 -0500 (CDT) (envelope-from glenn@gforce.johnson.home) Received: (from glenn@localhost) by gforce.johnson.home (8.12.9/8.12.9/Submit) id h64LDQEQ000774; Fri, 4 Jul 2003 16:13:26 -0500 (CDT) From: Glenn Johnson Date: Fri, 4 Jul 2003 16:13:26 -0500 To: Soeren Schmidt Message-ID: <20030704211326.GA736@gforce.johnson.home> Mail-Followup-To: Soeren Schmidt , John Reynolds , current@freebsd.org References: <3F026B4D.4040901@reynoldsnet.org> <200307020807.h6287l5m076059@spider.deepcore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307020807.h6287l5m076059@spider.deepcore.dk> User-Agent: Mutt/1.5.4i cc: John Reynolds cc: current@freebsd.org Subject: Re: features of ICH5/ICH5-R supported in -current or 5.1-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2003 21:13:51 -0000 On Wed, Jul 02, 2003 at 10:07:46AM +0200, Soeren Schmidt wrote: > It seems John Reynolds wrote: > > Hi all, I'm wondering if some of the features of the ICH5 found in > > the springdale and canterwood platforms (i865/i875) are currently > > supported in either 5.1-RELEASE or -CURRENT? > > > > I've read through some of the ATA code commits and see a few > > comments related to ICH5 and I believe I spotted where the plain ATA > > controller is recognized (and in theory fully supported as this > > shouldn't have changed from ICH4). But I still have questions about > > the following: > > > > 1) S-ATA: Is the S-ATA controller in ICH5 supported and if not, > > are there plans to support it? If not, is the problem > > documentation or hardware to test with? > > I have committed code to support the SATA part of the ICH5, but so far > noone has been able to test it and get back to me with results.. I just set up a system with an Abit IS7-E motherboard. This board has the 865-PE chipset with the ICH5. I installed a Maxtor 80 GB SATA drive. The drive is seen by the BIOS as using ATA-100 but FreeBSD reports the drive as using UDMA133. Is this some sort of SATA-PATA bridging? I have a CD burner attached to the first PATA channel and the BIOS automatically maps the SATA drive to IDE-2. I am attaching the output of dmesg. Let me know what else you need. ---begin dmesg output--- 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 #5: Fri Jul 4 15:52:32 CDT 2003 glenn@gforce.johnson.home:/usr/obj/usr/src/sys/GFORCE Preloaded elf kernel "/boot/kernel/kernel" at 0xc047e000. Preloaded elf module "/boot/kernel/vesa.ko" at 0xc047e1f4. Preloaded elf module "/boot/kernel/if_xl.ko" at 0xc047e2a0. Preloaded elf module "/boot/kernel/miibus.ko" at 0xc047e34c. Preloaded elf module "/boot/kernel/snd_es137x.ko" at 0xc047e3f8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc047e4a8. Preloaded elf module "/boot/kernel/agp.ko" at 0xc047e554. Preloaded elf module "/boot/kernel/random.ko" at 0xc047e5fc. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc047e6a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2405465652 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2405.47-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 536805376 (511 MB) avail memory = 516460544 (492 MB) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec00000 Pentium Pro MTRR support enabled VESA: v2.0, 131072k memory, flags:0x1, mode table:0xc03c9c02 (1000022) VESA: ATI RADEON 9100 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00fdc50 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 19 -> irq 9 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 23 -> irq 11 IOAPIC #0 intpin 17 -> irq 16 agp0: mem 0xf0000000-0xf7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.3 (no driver attached) pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 IOAPIC #0 intpin 20 -> irq 17 pcm0: port 0xa000-0xa03f irq 17 at device 4.0 on pci2 pcm0: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xa400-0xa47f mem 0xfb000000-0xfb00007f irq 16 at device 9.0 on pci2 xl0: Ethernet address: 00:01:02:84:81:50 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 10 at device 31.2 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 31.3 (no driver attached) fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: