From owner-freebsd-smp Thu Oct 5 11:54: 3 2000 Delivered-To: freebsd-smp@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0122137B674 for ; Thu, 5 Oct 2000 11:53:53 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95Irbi09931; Thu, 5 Oct 2000 11:53:37 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010051815.MAA00860@harmony.village.org> Date: Thu, 05 Oct 2000 11:53:52 -0700 (PDT) From: John Baldwin To: Warner Losh Subject: Re: Releasing interrupts? Cc: smp@FreeBSD.org Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 05-Oct-00 Warner Losh wrote: > In message John Baldwin writes: >: On 01-Oct-00 Warner Losh wrote: >: > In message John Baldwin writes: >: >: Grr. I'd test it on my laptop, but pccard isnt' attaching to my >: >: pcic_pci controller. I've tried the following patch but no go: >: > >: > The reason is that the pcic_p.c isn't putting the cardbus bridge into >: > legacy mode correctly. I'd bet a case of beer that the patch you >: > included won't work. >: >: Argh. I figured it out. I didn't have the pcic hints setup. I'd >: expect the pcic-pci driver to attach a pcic child just like the >: atapci driver attaches an ata child. :( Anyway we can get this fixed, >: or is it already on the todo list? > > I don't care about bugs in OLDCARD that are at this level. This is a > fundamental breakage in OLDCARD, imho. NEWCARD will eventually have a > cardbus bridge driver that talks to the cardbus bridge chip using the > yenta protocol (which defines a memory mapped version of the i82365SL > register set, so there's opportunity for code sharing), rather than > relying on the pci driver to put the device into a mode the isa driver > can recognize. > > I also noticed that the interrupt process didn't go away when I > ejected a pccard. I inserted another card and this process seemed to > keep the new card from working. Ideas? We don't have a kthread_cancel(), so there is no good way to kill the thread. However, the code should handle adding and removing handlers ok. In inthand_add() we check to see if the thread we are adding a handler to has no handlers and if not we act as if we are sort of creating a new ithread. > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message