Bug 30049

Summary: [f: 4.4] Bad iomem assigned in some cases.
Product: Base System Reporter: M. Warner Losh <imp>
Component: kernAssignee: Warner Losh <imp>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description M. Warner Losh 2001-08-24 19:50:00 UTC
> : nsp0 at port 0x240-0x24f iomem 0xc8800-0xc97ff irq 5 slot 0 on pccard0
> :                                ^^^^^^^^^^^^^^^
> Nothing should have changed in the memory allocation scheme.  The
> above address looks wrong to me.  Maybe it was with the addition of
> the orm device and that 0xc8000 was taken.  Maybe we're not aligning
> things properly (since the memory needs to be 4k aligned, iirc, at the
> bridge level).
> 
> Do you have a orm device?  If so, what does it say?

Yes,
jm3wud@cel% dmesg | grep orm
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff on isa0

But if my memory is correct, iomem used to be 0xd0000- something. And
the line,
memory  0xd4000  96k
in /etc/defautls/pccard.conf seems to be ignored,

From: Warner Losh <imp@harmony.village.org>
Date: Thu, 23 Aug 2001 01:55:30 -0600
> Maybe this patch will help?

Unfortunately, no. Dmesg was same,
nsp0 at port 0x240-0x24f iomem 0xc8800-0xc97ff irq 5 slot 0 on pccard0

The lines of PCIC from dmesg was as follows,

pcic2: <Vadem 469> at port 0x3e0-0x3e1 on isa0
pcic2: Polling mode
pccard0: <PC Card bus (classic)> on pcic2
pccard1: <PC Card bus (classic)> on pcic2

// Noriaki Mitsunaga //

Fix: 

None offered.
How-To-Repeat: 
Insert a nsp into the sytem.  Or some other pccard that requires
memory mapped.  Notice that it appears to be ignoring your memory line
in pccard.conf.
Comment 1 Warner Losh freebsd_committer freebsd_triage 2001-08-24 19:54:17 UTC
Responsible Changed
From-To: freebsd-bugs->imp

I'll deal.
Comment 2 Warner Losh freebsd_committer freebsd_triage 2004-06-29 16:22:12 UTC
State Changed
From-To: open->closed

I believe that I've fixed this.