From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: 2.6.17-mm4 Date: Fri, 30 Jun 2006 11:07:53 +0100 Message-ID: <1151662073.31392.4.camel@localhost.localdomain> References: <20060629013643.4b47e8bd.akpm@osdl.org> <6bffcb0e0606291339s69a16bc5ie108c0b8d4e29ed6@mail.gmail.com> <20060629204330.GC13619@redhat.com> <20060629210950.GA300@elte.hu> <20060629230517.GA18838@elte.hu> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Dave Jones , Michal Piotrowski , Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:6556 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S932243AbWF3Jvn (ORCPT ); Fri, 30 Jun 2006 05:51:43 -0400 To: Ingo Molnar In-Reply-To: <20060629230517.GA18838@elte.hu> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Ar Gwe, 2006-06-30 am 01:05 +0200, ysgrifennodd Ingo Molnar: > it does things like: > > static const unsigned long qd_port[2] = { 0x30, 0xB0 }; > static const unsigned long ide_port[2] = { 0x170, 0x1F0 }; > > [...] > unsigned long port = qd_port[i]; > [...] > r = inb_p(port); > outb_p(0x19, port); > res = inb_p(port); > outb_p(r, port); > > so it reads/writes port 0x30 and 0xb0. Are those used by something else > on modern hardware? Not especially. Perhaps the best thing to do here would be to make qdi compiled into the kernel (as opposed to modular) only do so if "probe_qdi=1" or similar is set. Will sort that out if nobody beats me to it. Alan