Phil Quinton wrote:
> In article <44170BA8.3090000@tadpole.com>, garrett_damore@tadpole.com 
> says...
>
>   
>> This a bit in the mapping register that determines whether the mapping
>> is for IO space or memory space.
>>
>> I'm surprised that the "ath" driver has to know about this detail though
>> -- it should be handled automatically as part of Cardbus_mapreg_map.
>>     
>
> That's the thing, ALL the drivers in dev/cardbus do it.. After they 
> Cardbus_mapreg_map, they take the bus_addr_t * returned from the map 
> command.. OR it with the memory type MEM or IO and then 
> Cardbus_conf_write it back.
>
> I Don't understand why.
>   

This sounds like something bogus in either the framework not handling
this automatically or Cardbus drivers doing something they don't need to
do.  Look at the Cardbus code to find out which it is. :-)



-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191