From owner-freebsd-drivers@FreeBSD.ORG Mon Jul 9 05:41:32 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 51DF2106564A; Mon, 9 Jul 2012 05:41:32 +0000 (UTC) (envelope-from mnln.l4@gmail.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id F20B18FC08; Mon, 9 Jul 2012 05:41:31 +0000 (UTC) Received: by ghbz22 with SMTP id z22so11261931ghb.13 for ; Sun, 08 Jul 2012 22:41:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=AadiKdSkvJLnQFAlGdhzeirKq1kdzxDBtg8MJS4osLU=; b=hiRVIg5VdGEbNCyqJ7eAo2saMsdy7cAvhXSRjnrNGKxTi6CyC8SD6t8OQUKl9FWiTu eeY9HFUsOGyPz+C/wiRhoNgxMC9R7GH7uisN9cKZacxbOqQhlLCf+GaJcnbwDyA+AnBK /IECHsTMiNVn/SeYsYG69vvwjIWz+WdOVajAluctOs4uJQpHjwAq+V08RgDponjwTMQN XCuryMG51m5kD3ENVrAVKfLbLeeA/9cI0qF/m+wGq5JjNrl7nQWpFrUZB708U76WTvgz yVz6ETflR3rAloFXsc35OEdL7o3hggIi14u7qivq3yAyhjdCT/zPTZ0Ottbic+Suf5Wy SxpQ== MIME-Version: 1.0 Received: by 10.50.17.226 with SMTP id r2mr7496270igd.47.1341812491194; Sun, 08 Jul 2012 22:41:31 -0700 (PDT) Received: by 10.231.69.5 with HTTP; Sun, 8 Jul 2012 22:41:31 -0700 (PDT) Date: Sun, 8 Jul 2012 22:41:31 -0700 Message-ID: From: "mnln.l4" To: freebsd-drivers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: Doesn't LAPIC timer stop when CPU goes to sleep state? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 05:41:32 -0000 I have FreeBSD 9.0-STABLE r237285, In my systl -a output, I see kern.eventimer.et.LAPIC.flags: 7 I am under the impression LAPIC timer may stop when CPU goes to sleep state. Shouldn't the flag be 15 as the example in EVENTTIMERS(4) man page? I have H67MA-E35 motherboard with Intel H67 chipset, and G840 dual core CPU. Thanks. From owner-freebsd-drivers@FreeBSD.ORG Mon Jul 9 10:59:34 2012 Return-Path: Delivered-To: freebsd-drivers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16D9D1065672; Mon, 9 Jul 2012 10:59:34 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0E3968FC16; Mon, 9 Jul 2012 10:59:29 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA02773; Mon, 09 Jul 2012 13:59:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4FFAB988.6050209@FreeBSD.org> Date: Mon, 09 Jul 2012 13:59:20 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120625 Thunderbird/13.0.1 MIME-Version: 1.0 To: "mnln.l4" References: In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, freebsd-drivers@FreeBSD.org Subject: Re: Doesn't LAPIC timer stop when CPU goes to sleep state? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 10:59:34 -0000 on 09/07/2012 08:41 mnln.l4 said the following: > I have FreeBSD 9.0-STABLE r237285, In my systl -a output, I see > > kern.eventimer.et.LAPIC.flags: 7 > > I am under the impression LAPIC timer may stop when CPU goes to sleep > state. Shouldn't the flag be 15 as the example in EVENTTIMERS(4) man > page? You don't have to be under an impression when you can get the facts from publicly available specifications and code. > I have H67MA-E35 motherboard with Intel H67 chipset, and G840 dual core CPU. > > Thanks. -- Andriy Gapon From owner-freebsd-drivers@FreeBSD.ORG Tue Jul 10 01:11:25 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3D45106564A; Tue, 10 Jul 2012 01:11:25 +0000 (UTC) (envelope-from mnln.l4@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 78F6F8FC08; Tue, 10 Jul 2012 01:11:25 +0000 (UTC) Received: by ggnm2 with SMTP id m2so12404138ggn.13 for ; Mon, 09 Jul 2012 18:11:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0YIrb+CI94IB4buwP38U/SvLEaAHzqMX+4XhderFdr4=; b=R4jKIqfYYkbNcd8+AmKNX6LftQBYwSHViz6kglf/wVyNYXUuLObWdQFa9CflcIDuFh x6kDG7lSqutJQIpByDfI++C3367ZoR4mNyBai6i4GPNq/ftbXeJ9FNj78a41xFvbrhaR R+LjgKCZHrF8ulx7rD2QrsDxW4nyrWaaMiQgXtGb7JUIjSkY2bTMkjpVWPgUrOuTn7V8 VqZf7Jcmb1JXQQ+4XVpB/vd4BWqKEj52U1JfdDKRSZQug4cKoKnGodVLMWVnuz8Hirp0 6MCnedCW70WRl7WshK/8jNOCzgwlZh6AoKAqTxt/miztYMtUdmYdmtkEk6FCoVlw3Ted mYbQ== MIME-Version: 1.0 Received: by 10.42.189.138 with SMTP id de10mr21579840icb.38.1341882678849; Mon, 09 Jul 2012 18:11:18 -0700 (PDT) Received: by 10.231.69.5 with HTTP; Mon, 9 Jul 2012 18:11:18 -0700 (PDT) In-Reply-To: <4FFAB988.6050209@FreeBSD.org> References: <4FFAB988.6050209@FreeBSD.org> Date: Mon, 9 Jul 2012 18:11:18 -0700 Message-ID: From: "mnln.l4" To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: Doesn't LAPIC timer stop when CPU goes to sleep state? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 01:11:26 -0000 http://wiki.freebsd.org/TuningPowerConsumption/ says LAPIC timer stops when CPU in C3, while I saw the flag is set to 7. Of course, I can read full spec and code (http://fxr.watson.org/fxr/source/x86/x86/local_apic.c?im=bigexcerpts#L251) to find out some processor's LAPIC timer runs in C3, but mailing list could be helpful to get some quick answer. On Mon, Jul 9, 2012 at 3:59 AM, Andriy Gapon wrote: > on 09/07/2012 08:41 mnln.l4 said the following: >> I have FreeBSD 9.0-STABLE r237285, In my systl -a output, I see >> >> kern.eventimer.et.LAPIC.flags: 7 >> >> I am under the impression LAPIC timer may stop when CPU goes to sleep >> state. Shouldn't the flag be 15 as the example in EVENTTIMERS(4) man >> page? > > You don't have to be under an impression when you can get the facts from publicly > available specifications and code. > >> I have H67MA-E35 motherboard with Intel H67 chipset, and G840 dual core CPU. >> >> Thanks. > > -- > Andriy Gapon > From owner-freebsd-drivers@FreeBSD.ORG Fri Jul 13 16:17:37 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C72410656AA for ; Fri, 13 Jul 2012 16:17:37 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.mail.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id A663C8FC0A for ; Fri, 13 Jul 2012 16:17:36 +0000 (UTC) Received: (qmail 7726 invoked by uid 0); 13 Jul 2012 16:12:19 -0000 Received: from 67.206.184.93 by rms-us018 with HTTP Content-Type: text/plain; charset="utf-8" Date: Fri, 13 Jul 2012 12:12:15 -0400 From: "Dieter BSD" Message-ID: <20120713161217.298420@gmx.com> MIME-Version: 1.0 To: freebsd-drivers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: ti1ycPYV3zOlNR3dAHAhqWd+IGRvb8DL Subject: siisch1 DISCONNECT requested - why? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 16:17:37 -0000 FreeBSD 8.2 amd64 SiI3132 SATA controller Seagate Barracuda LP 2 TB sata disk Disk has been working fine for ~1.5 years, zero problems. Suddenly: siisch1: DISCONNECT requested siisch1: siis_sata_connect() calling DELAY(100) [ previous line repeated a gazillion times ] siisch1: SATA connect timeout time=10000us status=00000000 siisch1: SIIS reset done: phy reset found no device (ada5:siisch1:0:0:0): lost device (ada5:siisch1:0:0:0): Synchronize cache failed (ada5:siisch1:0:0:0): removing device entry siisch1: CONNECT requested siisch1: SIIS reset... and the disk comes back. After umount/fsck/mount it is working ok again. Smartctl doesn't report any problems. System has ECC memory, conditioned power, air conditioning, ... I looked at siis.c but didn't find any clues. What would cause a disconnect request out of the blue? From owner-freebsd-drivers@FreeBSD.ORG Sat Jul 14 15:07:50 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 06E4E1065676 for ; Sat, 14 Jul 2012 15:07:50 +0000 (UTC) (envelope-from nvangoghs@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF188FC08 for ; Sat, 14 Jul 2012 15:07:49 +0000 (UTC) Received: by eabm6 with SMTP id m6so1402161eab.13 for ; Sat, 14 Jul 2012 08:07:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=G/wAtOLy3Bmm59iAcyLZBZX75qlncoPnReQxDyZqHjQ=; b=J5LVcxNi0GWSiT81QZFKAP6Qf0Vx7LIhfj5TglkkQlAuJiMvtdhN0/KNj/z6AYEkb0 qbTFxl+tEG6igiD7kHxDAMFMXJwCXdzxX1PF9z/ols2bA18RETx1aCscs87RJP0vLNG1 I3CeorN711XZrzqdGzmJ5ffTJsp0nMATSDF/neVpWVhnSOa5lmZDM7DRpY96jd7OcW3b ThlUfKznwyQaY7U6+NrBeHqBZLxEiSIQsZhJU1db+G/NO+2KrswIO/fEBDiHw8qiVDrR vne2rCPHcq3aR08QmumMIRCFzwEML6vj1+8jcRFm8OsbfmJm+ifiMriXlW2/k3ZpLUDv cSnA== Received: by 10.14.211.132 with SMTP id w4mr2321022eeo.39.1342278462922; Sat, 14 Jul 2012 08:07:42 -0700 (PDT) Received: from [192.168.0.2] (cpc7-dudl11-2-0-cust161.wolv.cable.virginmedia.com. [94.173.248.162]) by mx.google.com with ESMTPS id g46sm4366885eep.15.2012.07.14.08.07.40 (version=SSLv3 cipher=OTHER); Sat, 14 Jul 2012 08:07:42 -0700 (PDT) Message-ID: <50018B36.4000207@gmail.com> Date: Sat, 14 Jul 2012 16:07:34 +0100 From: nvangogh User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120613 Icedove/3.0.11 MIME-Version: 1.0 To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Precisely what hardware information is required? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2012 15:07:50 -0000 Hello, I am a novice as far as FreeBSD is concerned. However, I am interested in device driver development methodology and code. My question relates specifically to a particular wireless chipset for wifi. There is currently no device driver available under FreeBSD for the RTL 8191 SE chipset. Realtek have a web page explaining the features of the chip in general terms. There is source code available for certain linux distributions. Now I understand that it would be impossible to build such source code on FreeBSD. However, according to the documentation, the source code is divided into two parts i.e : 1. Firmware for the chip. There is a folder that contains 7 small files (on average 70kb) and they end with .bin.fw - I believe that these are the files containing assembly code for the chipset. How would one go about writing such code from scratch, with only general information about the driver? Would it be necessary to have technical information such as the number of registers in the chipset and eg how they interact? Or Is there a generic codebase of 'firmware' that will work with most wifi chipsets? What does the firmware actually do? 2. Source code. This is written in c. At this stage I have no questions about it. Kind Regards