pcmcia/hotplug

David Hinds dhinds at sonic.net
Mon Dec 29 12:51:10 GMT 2003


On Mon, Dec 29, 2003 at 08:26:42PM +0000, Matthew Wilcox wrote:
> On Mon, Dec 29, 2003 at 11:51:24AM -0800, David Hinds wrote:
> > > 20000000-20000fff : Texas Instruments PCI4410 PC card Cardbus Controller
> > > 20400000-207fffff : PCI CardBus #03
> > > 20800000-20bfffff : PCI CardBus #03
> > > 60000000-60000fff : card services
> > > 90000000-9fffffff : PCI Bus #01
> > >   90000000-97ffffff : ATI Technologies Inc Radeon Mobility M6 LY
> > >     90000000-902fffff : vesafb
> > > a0000000-a3ffffff : Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge
> > 
> > Hmmm.
> > 
> > The 2.6 memory probe code uses check_resource() against the parent of
> > the CardBus bridge.  In this system, that bridge is on PCI bus 2.  The
> > a0000000-a0ffffff range is allocated by a PCI device on another bus.
> 
> You mean check_region(), right?  If not, could you point me at the code
> in question?

No.  In drivers/pcmcia/rsrc_mgr.c, check_mem_resource() calls
check_resource() directly, which does only this:

        conflict = __request_resource(root, &tmp);
        if (!conflict)
                __release_resource(&tmp);


You are correct that check_region() appears to do the right thing, and
maybe the fix is just to use this instead of check_resource().

-- Dave



More information about the linux-pcmcia mailing list