From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 5 10:53:12 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0450216A4CE for ; Fri, 5 Mar 2004 10:53:12 -0800 (PST) Received: from efesto.telvia.it (efesto.telvia.it [213.155.192.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA26B43D2D for ; Fri, 5 Mar 2004 10:53:08 -0800 (PST) (envelope-from nicola.martella@telvia.it) Received: from Nicola (unverified [62.123.79.153]) by efesto.telvia.it for ; Fri, 5 Mar 2004 19:53:04 +0100 Message-ID: <000901c402e3$6c296360$2700000a@Nicola> From: "Nicola Martella" To: Date: Fri, 5 Mar 2004 19:55:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailman-Approved-At: Sat, 06 Mar 2004 04:54:47 -0800 Subject: FreeBSD 4.8 on Soekris X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2004 18:53:12 -0000 I'm currently running FreeBSD 4.8 on a Soekris with Geode's CPU. As i told you in the last email, i see in the pciconf -lv that the SC1100 Watchdog (which is embedded on the mobo, not a pci card) is taken from another driver. What i'm asking myself is if it's normal that the pci generic driver gets control of the device this way, but then i don't understand how i can register as the driver to that watchdog, or if it's a problem due to the fact that it's actually not exactly an x86. I mean, i just wrote the driver for the watchdog, but being Geode an x86 clone, it may be possible that i gotta not only write the driver but also something more about the porting in order to solve this problem? Am i wrong? I can't see any way to solve this problem otherwhise as long as my driver's probe() function isn't called for my watchdog device! This is pciconf -lv for the watchdog device: chip2@pci0:18:5: class=0x068000 card=0x0505100b chip=0x0515100b rev=0x00 hdr=0x00 vendor = 'National Semiconductor' class = bridge subclass = PCI-unknown I don't really know what to do about that. Thanks in advance Claudio Martella P.S. = please reply to claudio.martella@acaro.org