Subject: Re: PCMCIA IDE problem.
To: Dustin Sallings <email@example.com>
From: enami tsugutomo <firstname.lastname@example.org>
Date: 11/07/1999 17:02:10
> Date: Fri, 5 Nov 1999 21:34:19 -0800 (PST)
> From: Dustin Sallings <email@example.com>
> Subject: Re: PCMCIA IDE problem.
> It is, here's all the pcmcia info:
> pcmcia0 at pcic0 controller 0 socket 0
> pcmcia0: CIS version PCMCIA 2.0 or 2.1
> pcmcia0: CIS info: IBM, PCMCIA Portable CD-ROM Drive
> pcmcia0: Manufacturer code 0xa4, product 0x2d
> pcmcia0: function 0: unspecified, ccr addr 200 mask 3
> pcmcia0: function 0, config table entry 1: I/O card; irq mask ff0f; iomask
> a, iospace 210 220; rdybsy_active wp_active bvd_active io16 irqlevel
> wdc2 at pcmcia0 function 0: can't handle card info
Hmm. # of iospace is 2. So, wdc_pcmcia_attach might try to call
pcmcia_io_alloc for them and one of them failed. Are you sure that
above two range of iospace (0x210..??? and 0x220 ..???) won't conflict
with other devices?
# Unfortunately, there was a bug in pcmcia_cis.c which prevent kernel
# from printing end of range of iospace. I just fixed it in rev 1.13.
# So, you need to update it and check how long each iospaces are.
# BTW, I'll be off from the net for a week...