Welcome, Guest. Please login or register.

Author Topic: NIC chipsets  (Read 3804 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline dammyTopic starter

  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 2828
    • Show only replies by dammy
NIC chipsets
« on: January 01, 2004, 06:51:27 PM »
What would be the most easiest NIC chipset to do a AROS driver for?

Dammy
Dammy

https://www.facebook.com/pages/Arix-OS/414578091930728
Unless otherwise noted, I speak only for myself.
 

Offline fx

  • Sr. Member
  • ****
  • Join Date: Mar 2002
  • Posts: 347
  • Country: se
  • Gender: Male
    • Show only replies by fx
    • UHC Tools
Re: NIC chipsets
« Reply #1 on: January 01, 2004, 07:26:27 PM »
the realtek chipsets seems to be popular, most of my cards have a rtl8139 chip, I have no idea if it's hard or easy to do a driver for them tough :/
Slightly bored and severly confused..
 

Offline Ilwrath

Re: NIC chipsets
« Reply #2 on: January 01, 2004, 07:43:23 PM »
I haven't actually written a device driver, myself, but I would suspect that you want to target a common chipset, such as the realtek 8139 or the venerable old NE1000.  There's lots of information and source code (from other platforms) out there for the common chipsets, so that should help make the job easier.
 

Offline Stedy

  • Sr. Member
  • ****
  • Join Date: Jul 2002
  • Posts: 259
    • Show only replies by Stedy
    • http://www.ianstedman.co.uk
Re: NIC chipsets
« Reply #3 on: January 01, 2004, 08:51:10 PM »
Hi,

The Realtek 8139 (already mentioned) a the family are popular. If you port an NE2000 driver you will get support for many cards as well as some older Realtek 10 mbit cards.

SMSC chips are used by some Zorro cards and you can get Linux source code from www.smsc.com. If you can add support for 3COM 3C509 series (10 mbit) and 3C905 (100mbit series) it would be nice. 3COM have driver documents and source code from their website.
 

Offline bloodline

  • Master Sock Abuser
  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 12113
    • Show only replies by bloodline
    • http://www.troubled-mind.com
Re: NIC chipsets
« Reply #4 on: January 01, 2004, 08:58:45 PM »
Quote

fx wrote:
the realtek chipsets seems to be popular, most of my cards have a rtl8139 chip, I have no idea if it's hard or easy to do a driver for them tough :/


Almost everything uses Realtek... I also have a 3Com and a SIS NIC here :-)

Offline downix

  • Hero Member
  • *****
  • Join Date: Jan 2003
  • Posts: 1587
    • Show only replies by downix
    • http://www.applemonthly.com
Re: NIC chipsets
« Reply #5 on: January 01, 2004, 10:37:21 PM »
Tulip, easily.

I have a pile of these cards if you need one.
Try blazedmongers new Free Universal Computer kit, available with the GUI toolkit Your Own Universe, the popular IT edition, Extremely Reliable System for embedded work, Enhanced Database development and Wide Area Development system for telecommuting.
 

Offline shIva

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 751
    • Show only replies by shIva
    • http://preshi.blogspot.com
Re: NIC chipsets
« Reply #6 on: January 01, 2004, 10:53:49 PM »
Quote
Tulip, easily.

please not such special ones, or do they use common chipsets (like the mentioned rtl) ?

in our region the most popular chipsets are 3com and realtek.
would be nice to see a device driver for a 10/100 mbit rtl chip - this one could directly be handed over to oli_hd for his coldfire ;-)
shIva
the answer is [color=CC3300]42[/color] Support  Distributed Amiga - moo ;)
 

Offline Stedy

  • Sr. Member
  • ****
  • Join Date: Jul 2002
  • Posts: 259
    • Show only replies by Stedy
    • http://www.ianstedman.co.uk
Re: NIC chipsets
« Reply #7 on: January 01, 2004, 11:53:56 PM »
Quote
Tulip, easily.

Forget this, it's obsolete. When Intel bought DEC semiconductor rights they copied the design to make the 82559.

I remembered 2 links:
Realtek 8139 driver source for linux &
NE2000 card driver source

The most popular chipsets, in no particular order are, AMD, Intel, Realtek, National Semiconductor, 3COM & SMSC. In the UK I have come across the Intel, 3COM and Realtek parts the most.

Develop the Realtek 8139 and NE2000 drivers and you will satisfy most users, myself included.

If you want help/advice on ethernet drivers and IP stacks, contact me privately. I've ported Linux ethernet drivers, written them from scratch and wrote my own IP stack.
 

Offline downix

  • Hero Member
  • *****
  • Join Date: Jan 2003
  • Posts: 1587
    • Show only replies by downix
    • http://www.applemonthly.com
Re: NIC chipsets
« Reply #8 on: January 01, 2004, 11:56:22 PM »
@Stedy

he asked for easiest tho, and from my perspective Tulip is quite easy to code for.  

The NS2000 is a fine choice as well.
Try blazedmongers new Free Universal Computer kit, available with the GUI toolkit Your Own Universe, the popular IT edition, Extremely Reliable System for embedded work, Enhanced Database development and Wide Area Development system for telecommuting.
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: NIC chipsets
« Reply #9 on: January 02, 2004, 12:05:13 AM »
Could it be possible adapt cnet.device source code into AROS? It is
written for Amiga PCMCIA hardware but there is also C
reimplementation.
My Amigas: A500, Mac Mini and PowerBook
 

Offline dammyTopic starter

  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 2828
    • Show only replies by dammy
Re: NIC chipsets
« Reply #10 on: January 02, 2004, 06:26:12 PM »
by Stedy on 2004/1/1 18:53:56

Quote
If you want help/advice on ethernet drivers and IP stacks, contact me privately. I've ported Linux ethernet drivers, written them from scratch and wrote my own IP stack.


Well there is a small bounty for tcp/ip at TeamAROS.

Dammy
Dammy

https://www.facebook.com/pages/Arix-OS/414578091930728
Unless otherwise noted, I speak only for myself.
 

Offline downix

  • Hero Member
  • *****
  • Join Date: Jan 2003
  • Posts: 1587
    • Show only replies by downix
    • http://www.applemonthly.com
Re: NIC chipsets
« Reply #11 on: January 02, 2004, 06:34:24 PM »
Always looking for help, sure.
Try blazedmongers new Free Universal Computer kit, available with the GUI toolkit Your Own Universe, the popular IT edition, Extremely Reliable System for embedded work, Enhanced Database development and Wide Area Development system for telecommuting.
 

Offline Methuselas

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2205
    • Show only replies by Methuselas
Re: NIC chipsets
« Reply #12 on: January 02, 2004, 06:36:23 PM »
Dammy, do 3Com or N1000. ;^) I have those. I'll test for bugs for ya. (hint, hint.)  :-D
\'Using no way as way. Having no limitation as limitation.\' - Bruce Lee

\'No, sorry. I don\'t get my tits out. They\'re not actually real, you know? Just two halves of a grapefruit...\' - Miki Berenyi

\'Evil will always triumph because good is dumb.\' - Dark Helmet :roflmao:

\'And for future reference, it might be polite to ask someone if you can  quote them in your signature, rather than just citing them to make a  sales pitch.\' - Karlos. :rtf
 

Offline iamaboringperson

  • Hero Member
  • *****
  • Join Date: Jun 2002
  • Posts: 5744
    • Show only replies by iamaboringperson
Re: NIC chipsets
« Reply #13 on: January 02, 2004, 09:50:41 PM »
I agree with NE2000, and I could also add some SiS chipset (I think)

Then I can be rather selfish and name my unpopular brand of NIC, however I've currently forgotten its name :(
 

Offline Razor

  • Newbie
  • *
  • Join Date: Jan 2004
  • Posts: 1
    • Show only replies by Razor
Re: NIC chipsets
« Reply #14 on: January 02, 2004, 10:07:07 PM »
Regarding the RL8139:

Here are some comments from the FreeBSD driver:

Quote

 * The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is
 * probably the worst PCI ethernet controller ever made, with the possible
 * exception of the FEAST chip made by SMC. The 8139 supports bus-master
 * DMA, but it has a terrible interface that nullifies any performance
 * gains that bus-master DMA usually offers.
 *
 * For transmission, the chip offers a series of four TX descriptor
 * registers. Each transmit frame must be in a contiguous buffer, aligned
 * on a longword (32-bit) boundary. This means we almost always have to
 * do mbuf copies in order to transmit a frame, except in the unlikely
 * case where a) the packet fits into a single mbuf, and b) the packet
 * is 32-bit aligned within the mbuf's data area. The presence of only
 * four descriptor registers means that we can never have more than four
 * packets queued for transmission at any one time.
 *
 * Reception is not much better. The driver has to allocate a single large
 * buffer area (up to 64K in size) into which the chip will DMA received
 * frames. Because we don't know where within this region received packets
 * will begin or end, we have no choice but to copy data from the buffer
 * area into mbufs in order to pass the packets up to the higher protocol
 * levels.


and further down:

Quote

/*
* Here's a totally undocumented fact for you. When the
* RealTek chip is in the process of copying a packet into
* RAM for you, the length will be 0xfff0. If you spot a
* packet header with this value, you need to stop. The
* datasheet makes absolutely no mention of this and
* RealTek should be shot for this.
*/


You can check the driver here.