Date: Tue, 4 Jun 1996 09:54:54 -0600 From: Nate Williams <nate@sri.MT.net> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: nate@sri.MT.net (Nate Williams), mobile@freebsd.org Subject: Re: Laptop hardware FOUND Message-ID: <199606041554.JAA17336@rocky.sri.MT.net> In-Reply-To: <199606041603.BAA07962@genesis.atrad.adelaide.edu.au> References: <199606041523.JAA17249@rocky.sri.MT.net> <199606041603.BAA07962@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'll try the -SNAP 'apm' again now that I'm happier about what does what. It should work w/out any changes necessary, though I haven't seen the most recent version yet to make sure. > > > And speaking of hackery, is it normal for the pcic to share an interrupt > > > with another port? I was half hoping to use the IR port, but it's on the > > > same interrupt as the pcic, so it never probes... > > > > You need to remove the interrupt that the IR port uses from > > /etc/pccard.conf. It steals one of the interrupts from the list, so if > > it's not a free interrupt remove it. > > Sorry, should have been clearer; 'pcic' as in the PC-Card chipset in the > machine (what is probed at boot time). There are only two free interrupts > and a very small collection of free ports in this blasted system, but > I only have one card so that's not a problem. Hmm, I thought the pcic controller was assigned an IRQ the first time pccardd was run, but it's been almost 2 months since I messed with this stuff. Actually, that doesn't make sense now that I think about it since how would you know when the boards are switched in/out (the card daemon needs to know that *before* it's run). Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606041554.JAA17336>