From owner-freebsd-questions@FreeBSD.ORG  Tue Dec  1 01:57:24 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D447D1065672
	for <questions@freebsd.org>; Tue,  1 Dec 2009 01:57:24 +0000 (UTC)
	(envelope-from brett@lariat.net)
Received: from lariat.net (lariat.net [66.119.58.2])
	by mx1.freebsd.org (Postfix) with ESMTP id 1D3FE8FC0A
	for <questions@freebsd.org>; Tue,  1 Dec 2009 01:57:23 +0000 (UTC)
Received: from anne-o1dpaayth1.lariat.net (IDENT:ppp1000.lariat.net@lariat.net
	[66.119.58.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id SAA01359;
	Mon, 30 Nov 2009 18:57:17 -0700 (MST)
Message-Id: <200912010157.SAA01359@lariat.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 30 Nov 2009 18:57:05 -0700
To: Olivier Nicole <Olivier.Nicole@cs.ait.ac.th>
From: Brett Glass <brett@lariat.net>
In-Reply-To: <200912010013.nB10DSM6096812@banyan.cs.ait.ac.th>
References: <200911301930.MAA26709@lariat.net>
	<200912010013.nB10DSM6096812@banyan.cs.ait.ac.th>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: questions@freebsd.org
Subject: Re: CF Ethernet for FreeBSD?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2009 01:57:24 -0000

At 05:13 PM 11/30/2009, Olivier Nicole wrote:

>Not to mentione FreeBSD drivers, but only finding an Ethernet
>interface that plugs into a CF sockets seems very chalenging: you
>don't really send/receive the same information to memory and to
>network interface; CF can address GB of data, while the network card
>has a few KB at best; etc.

CF sockets usually can act as sockets for ATA/IDE compatible disk 
drives as well as for PCMCIA-like peripheral cards.

Also, there are some Ethernet interface chips that are designed to 
be memory-mapped. See, for example, the one by ASIX, which is often 
used in embedded systems because it can interface with pretty much any CPU.

--Brett Glass