On Mon, Nov 21, 2005 at 11:11:41AM +0100, Rico -mc- Gloeckner wrote: > On Mon, Nov 21, 2005 at 10:28:54AM +0100, Daniele Orlandi wrote: > > You may try changing hfc_wait_busy routine as follows: > > > > It will not hurt and 10ms will be enough for the card to initialize. > > > > Let me know if it fixes your problem. > > No :-/ I extended the loop to 1000*10000 (alot of time i know) and even > tried to extend the reset-signal to 600 us, doesnt seem to help either.
Another one, lspci -vv gave me something more to ponder, iam not much in hardware and/or kernel level coding, so someone may see more into that as i do: | 0000:00:0c.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI ] (rev 02) | Subsystem: Cologne Chip Designs GmbH ISDN Board | Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- | Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- | Latency: 16 (4000ns max) | Interrupt: pin A routed to IRQ 11 | Region 0: I/O ports at b800 [disabled] [size=8] | Region 1: Memory at dc800000 (32-bit, non-prefetchable) [size=256] | Capabilities: [40] Power Management version 1 | Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) | Status: D0 PME-Enable- DSel=0 DScale=0 PME- So whats confusing me here is, why are IO Ports declared to be disabled? -- http://www.ukeer.de/about.html "Geschichte wird nun einmal vorwärts gelebt und rückwärts betrachtet." --Klaus Parker _______________________________________________ Visdn-hackers mailing list [email protected] https://mailman.uli.it/mailman/listinfo/visdn-hackers
