Re: How to find a right value for hw.cbb.start_memory?

"Sergey A. Osokin" <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
On Thu, Dec 18, 2003 at 09:39:33AM -0800, Kevin Oberman wrote:
> > Does anyone have an idea how to find a right value for
> > hw.cbb.start_memory?
> > 
> > I use a 3Com Megahertz 56K Modem (3CXM756) with
> > my HP 6100 Omnibook notebook and with
> > device	pcic
> > device	card	1
> > works fine.
> > 
> > Part of verbose boot:
> > pcib2: device pccard0 requested decoded memory range 0xd0000-0xd0000
> > pcic: mem addr 0xd0000: reg 48: d0 0 d0 0 0 7f 10
> > pcic: mem addr 0: reg 48: 0 0 0 0 0 0 0
> > ...
> > pcib2: device pccard0 requested decoded I/O range 0x3f8-0x3ff
> > pcib2: device pccard0 requested decoded I/O range 0x2f8-0x2ff
> > ...
> > pccard0: Assigning sio4: io 0x2f8-0x2ff irq 10 flags 0x0
> > pcib2: device sio4 requested decoded I/O range 0x2f8-0x2ff
> > pcic: I/O win 0 flags 11 2f8-2ff
> > pcic: I/O win 0 flags 1 2f8-2ff
> > sio4 at port 0x2f8-0x2ff irq 10 slot 0 on pccard0
> > pcib2: device sio4 requested decoded I/O range 0x2f8-0x2ff
> > pcic: I/O win 0 flags 11 2f8-2ff
> > sio4: type 16550A
> > sio4: Forcing IRQ to 10
> > sio4: unable to activate interrupt in fast mode - using normal mode
> > 
> > I tried to use
> > device cbb
> > device pccard
> > device cardbus
> > but its don't work for me:
> > pcib2: device pccard0 requested decoded memory range 0x88000000-0xffffffff
> > CIS is too long -- truncating
> > pccard0: Card has no functions!
> > cbb0: PC Card card activation failed
> > 
> > Also I tried to change hw.cbb.start_memory to 0xd0202000,
> > but it don't help me.
> 
> hw.cbb.start_memory ust be greater than the actual DRAM on the
> system. So if you have 512 MB of memory (as I do), a working value will
> be at least 0x20000000. It might need to be higher. For 768M, start at
> 0x30000000 and if you have 1 GB, start at 0x40000000. 
> 
> I have 512 MB and set it at 0x20000000. I see agp at 0xe0000000, cbb0 at
> 0x50000000, cbb1 at 0x51000000 and fxp0 at 0xd0200000. I I tried
> starting at 0xd0202000, I would not have space for everything.

I think I found a right value, its 0xd0000000.

> You may also need hw.pci.allow_unsupported_io_range="1".

Already have this option in my /boot/loader.conf.local, thanks.

At this time I have some stranges with PCMCIA card, I already
drop a letter to imp@.  I think we have a bug in cbb implementation,
because if I have the hw.cbb.start_memory="3489660928" in
loader.conf.local kernel at boot time reports:
pcib2: device pccard0 requested decoded memory range 0xd0000000-0xffffffff
pccard0: Card has no functions!
cbb0: PC Card card activation failed
cbb0: ready never happened, status = 0c
start (d0000000) < sc->membase (d0200000)
end (ffffffff) > sc->memlimit (d02fffff)

And if I remove hw.cbb.start_memory string from loader.conf.local
and reboot machine, after boot I change hw.cbb.start_memory
from default to 3489660928 (aka 0xd0000000), remove card, then
insert again, I see in /var/log/messages:
Dec 18 16:27:53 hp6k1 kernel: pcib2: device pccard0 requested decoded memory range 0xd0000000-0xffffffff
Dec 18 16:27:53 hp6k1 kernel: sio4: <3Com Megahertz 3CXM756/3CCM756> at port 0x2f8-0x2ff irq 10 function 0 config 33 on pccard0
Dec 18 16:27:53 hp6k1 kernel: pcib2: device sio4 requested decoded I/O range 0x2f8-0x2ff
Dec 18 16:27:53 hp6k1 kernel: pcib2: device pccard0 requested decoded I/O range 0x2f8-0x2ff
Dec 18 16:27:53 hp6k1 kernel: device_probe_and_attach: sio4 attach returned 6

but sio device unusable:
$ ls /dev/cuaa*
cuaa0

Additional information:
$ uname -spr
FreeBSD 5.2-CURRENT i386

Any idea?

-- 

Rgdz,                        /"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,       \ /    AGAINST HTML MAIL
http://ozz.pp.ru/             X          AND NEWS
                             / \
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.