Date: Thu, 05 Oct 2000 12:15:32 -0600 From: Warner Losh <imp@village.org> To: John Baldwin <jhb@FreeBSD.org> Cc: smp@FreeBSD.org Subject: Re: Releasing interrupts? Message-ID: <200010051815.MAA00860@harmony.village.org> In-Reply-To: Your message of "Thu, 05 Oct 2000 11:10:49 PDT." <XFMail.001005111049.jhb@FreeBSD.org> References: <XFMail.001005111049.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <XFMail.001005111049.jhb@FreeBSD.org> John Baldwin writes: : On 01-Oct-00 Warner Losh wrote: : > In message <XFMail.000930191309.jhb@FreeBSD.org> 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? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010051815.MAA00860>