On Mon, Oct 20, 2008 at 12:52 PM, Justin C. Sherrill <[EMAIL PROTECTED]> wrote: > On Sun, October 19, 2008 11:50 pm, Sepherosa Ziehau wrote: > >> Try setting following tunable (not sysctl) to 0xe0206000 >> hw.cbb.start_memory > > I put it in loader.conf - no change. Why "0xe0206000"?
The pccbb is on pci2.pcib1 pcib1 opens following memory window: pcib1: memory decode 0xe0200000-0xe02fffff fwohci0 is on pci2.pcib1 It could use two memory region: mem 0xe0200000-0xe0203fff,0xe0205000-0xe02057ff fxp0 is on pci2.pcib1 It could use on memory region: 0xe0204000-0xe0204fff The memory regions requested by fxp0 and fwohci0 consume 0xe0200000-0xe02057ff of pcib1's memory window, so pccbb could only use memory window starting from 0xe0206000 (0xe0205800-0xe02059ff could not be used due to start address alignment requirement) I will give you another patch to try when I get home. Setting hw.cbb.start_memory obviously is not enough. If my analysis is correct, cbb is actually reading from firewire's memory region (cbb0: lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xe0200000). Best Regards, sephe -- Live Free or Die
