ISDN4BSD (HPS version) is going into ports

[Hans Petter Selasky]

On Monday 03 December 2012 00:53:58 Andreas Longwitz wrote:
> Hans Petter Selasky wrote:
> > I see that my driver differs a bit from the origin. That's basically my
> > fault, when I did the porting, I tried to make things simpler. Maybe I
> > have to port more stuff from the working one. Mostly it requires some
> > 32-bit register magic instead of 8-bit register access. I'm using
> > transparent mode only for B- channels, and have optimised away some
> > programming in that regard.
> > 
> > http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/pci/ifpci2.c?annotate=1.1
> > 9.22.1
> > 
> > Can you try the attached patch?
> 
> Yes I did, but was not happy, nothing changed. I have introduced some
> messages in the source and get this every 10 seconds:
> 
> i4b-L1 ihfc1: avm_pci_chip_read: reg=0x00e0, len=1
> i4b-L1 ihfc1: avm_pci_chip_status_read: ista=0x01
> i4b-L1 ihfc1: avm_pci_chip_read: reg=0x00a0, len=1
> i4b-L1 ihfc1: avm_pci_chip_status_read: ista_d=0x80
> i4b-L1 ihfc1: avm_pci_chip_read: reg=0x00a6, len=1
> i4b-L1 ihfc1: avm_pci_chip_status_read: rbcld=0x05
> i4b-L1 ihfc1: avm_pci_chip_read: reg=0x00a8, len=1
> i4b-L1 ihfc1: avm_pci_chip_status_read: rstad=0xae
> i4b-L1 ihfc1: avm_pci_fifo_read: len=5
> i4b-L1 ihfc1: avm_pci_chip_read: reg=0x0080, len=5
> i4b-L1 ihfc1: avm_pci_chip_read: got 0x02d30151ae
> 
> The corresponding isdndecode looks like this:
> 
> -- NT->TE - unit:00  frame:000059 - time:03.12 00:07:14.744795 -
> length:5 -----
> L2 00 02 000000-- SAPI = 0              (Call Control)
>          ------1- C/R = Command
>          -------0 Extension Bit = 0     (with extension, octet follows)
> L2 01 D3 1101001- TEI = 105 = 0x69      (Automatic TEI)
>          -------1 Extension Bit = 1     (no extension, final octet)
> L2 02 01 00000001 S-Frame: RR           (Receiver Ready)
> L2 03 51 0101000- N(R) = 40             (receive sequence number)
>          -------1 P/F, Poll = Immediate Response Required
> L3 04 AE 10101110 Protocol = Other Layer 3 or X.25              (0xae)
> Dumping Layer3 data, 0 bytes:

Hi,

Could you show what code you added?

I think we are onto something. The rstad=0xae too, so apparently this byte is 
added to the FIFO.

Could you try to send a dummy frame that is greater than 64 bytes? I want to 
see if len = 0, is used at all.

--HPS