From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jens Scharsig <js_at_ng@scharsoft.de>
Date: Wed, 01 Sep 2010 19:37:16 +0200
Subject: [U-Boot] [PATCH V3] AT91 Fix: return value of get_tbclk
In-Reply-To: <4C7E0114.5090404@emk-elektronik.de>
References: <4C5D9CB6.8090501@scharsoft.de>	<201008090834.41511.alexander.stein@systec-electronic.com>	<0F5F73E36031FD46AD3F2E6948F0C0A0042AE80C@frimb01.corp.atmel.com>
	<201008300852.07385.alexander.stein@systec-electronic.com>
	<4C7CB10B.6020407@emk-elektronik.de> <4C7D2C4B.40307@scharsoft.de>
	<4C7E0114.5090404@emk-elektronik.de>
Message-ID: <4C7E8F4C.1020801@scharsoft.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Am 2010-09-01 09:30, schrieb Reinhard Meyer:
> 
> at91_emac AND macb?
> 
> macb works for AVR32AP700x and (at least) for AT91SAM9260/9G20/9XE.
> 
> What is the deal with at91_emac? Is it required for some AT91's
> because macb does not work there?
> 
> Does it provide better "results" than macb?
> 
> Best Regards
> Reinhard
Hello,

I think the separation has historical reasons.
For AT91RM and AT91SAM existed separate drivers and separate arch.
I remeber in older datascheets the ethernet inteface also marked with MACB.
In my opinion, the at91_emac the latest drivers (NET_MULTI api SoC
access via c structurs).

But I dont know the exact differences are not of single use devices.
Please ask Xu, Hong

Best regards

Jens