Re: Marvell/SysKonnect YukonII source code available

2006-01-24 Thread Ganbold

At 09:55 AM 1/25/2006, you wrote:

On Tue, Jan 24, 2006 at 11:19:05AM +0100, Andre Oppermann wrote:
  Marvell/SysKonnect made the source code to the YukonII chips available
  today under a BSD license:
 
   http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz
 
  I haven't tested the driver yet and I don't know if it available directly
  from the their website already.
 
  Many thanks to Gerald and Frank at SysKonnect for working with us and
  making this possible!
 
Yes, that's great news.

Is there any chance to get a copy of data sheet for Yukon chips?
I've tried hard to make Rx TCP/UDP checksum offload work but
failed. ATM both Linux and OpenBSD use Rx IP checksum offload only
but this driver enabled Rx checksum offload for TCP/UDP. So I guess
there is somthing not listed in SK-NET Genesis data sheet. :-(

Quick reading the source shows that this driver has the following
issues.
1. Incomplete bus_dma(9) support. The driver uses BUS_SPACE_MAXADDR
   when it creates DMA tags which means its DMA supports any address
   without limitations. However, I'm sure Rx/Tx descriptors should
   reside in  4GB. So the driver wouldn't work on systems with  4GB
   memory.
2. Since the driver makes use of mbpool(9) it wouldn't work when
   bounce buffers are involved. In fact, I think the use of mbpool(9)
   is really bad as it lacks bus_dmamap_sync(9) operation.
3. Lack of ALTQ support.
4. The driver may not work on big-endian architectures.
5. The driver may not work on architectures with strict-alignment.

Btw, new sk(4) is availabe at the following URL. Due to lack of
documentation it doesn't support YukonII yet.
http://people.freebsd.org/~yongari/sk/if_sk.c
http://people.freebsd.org/~yongari/sk/if_skreg.h


I'm still having sk0: watchdog timeout in my system and I'll try new sk driver.
I will let you know if there is any issue.

Ganbold


--
Regards,
Pyun YongHyeon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Marvell/SysKonnect YukonII source code available

2006-01-24 Thread Ganbold

At 09:55 AM 1/25/2006, you wrote:

Btw, new sk(4) is availabe at the following URL. Due to lack of
documentation it doesn't support YukonII yet.
http://people.freebsd.org/~yongari/sk/if_sk.c
http://people.freebsd.org/~yongari/sk/if_skreg.h


Pyun,

I'm confused, I got drivers dated back Jan 19, however above are dated Jan 17.
And I'm still getting:

Jan 24 15:30:40 gw kernel: sk0: watchdog timeout
Jan 24 15:30:40 gw kernel: fxp0: device timeout

errors.

Ganbold



--
Regards,
Pyun YongHyeon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Marvell/SysKonnect YukonII source code available

2006-01-24 Thread Pyun YongHyeon
On Wed, Jan 25, 2006 at 10:15:11AM +0800, Ganbold wrote:
  At 09:55 AM 1/25/2006, you wrote:
  Btw, new sk(4) is availabe at the following URL. Due to lack of
  documentation it doesn't support YukonII yet.
  http://people.freebsd.org/~yongari/sk/if_sk.c
  http://people.freebsd.org/~yongari/sk/if_skreg.h
  
  Pyun,
  
  I'm confused, I got drivers dated back Jan 19, however above are dated Jan 
  17.
  And I'm still getting:
  
  Jan 24 15:30:40 gw kernel: sk0: watchdog timeout
  Jan 24 15:30:40 gw kernel: fxp0: device timeout
  
  errors.
  
  Ganbold
  

Did you use expeimental code in
http://people.freebsd.org/~yongari/sk/sk_test/ ?

If the driver still emit watchdong timeout I have no idea atm.
I've never met such errors but I suffered from mbuf cluster leak
on CURRENT. I believe the leak comes from kernel not sk(4) as it
also happens em(4) on i386 SMP.
When you see the error would you check mbuf status with netstat(1)?

-- 
Regards,
Pyun YongHyeon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Marvell/SysKonnect YukonII source code available

2006-01-24 Thread Ganbold

At 10:27 AM 1/25/2006, you wrote:

On Wed, Jan 25, 2006 at 10:15:11AM +0800, Ganbold wrote:
  At 09:55 AM 1/25/2006, you wrote:
  Btw, new sk(4) is availabe at the following URL. Due to lack of
  documentation it doesn't support YukonII yet.
  http://people.freebsd.org/~yongari/sk/if_sk.c
  http://people.freebsd.org/~yongari/sk/if_skreg.h
 
  Pyun,
 
  I'm confused, I got drivers dated back Jan 19, however above are 
dated Jan

  17.
  And I'm still getting:
 
  Jan 24 15:30:40 gw kernel: sk0: watchdog timeout
  Jan 24 15:30:40 gw kernel: fxp0: device timeout
 
  errors.
 
  Ganbold
 

Did you use expeimental code in
http://people.freebsd.org/~yongari/sk/sk_test/ ?


Yes.


If the driver still emit watchdong timeout I have no idea atm.
I've never met such errors but I suffered from mbuf cluster leak
on CURRENT. I believe the leak comes from kernel not sk(4) as it
also happens em(4) on i386 SMP.
When you see the error would you check mbuf status with netstat(1)?


Actually I can't because I'm connecting to this machine remotely and 
external NIC fxp also times out.


Ganbold


--
Regards,
Pyun YongHyeon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]