[U-Boot] [PATCH V3] AT91 Fix: return value of get_tbclk

[Xu, Hong]

Hi, 

> -----Original Message-----
> From: Jens Scharsig [mailto:js_at_ng at scharsoft.de] 
> Sent: Thursday, September 02, 2010 1:37 AM
> To: Reinhard Meyer
> Cc: Xu, Hong; u-boot at lists.denx.de
> Subject: Re: [U-Boot] [PATCH V3] AT91 Fix: return value of get_tbclk
> 
> 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

I believe there must be historic reasons. I'm not familiar with AT91RM series. But from the mainline code,

$ grep CONFIG_DRIVER_AT91EMAC include/configs/* | wc -l
11
$ grep CONFIG_MACB include/configs/* | wc -l
19

Many boards are dependent on both. And currently AT91SAM always uses CONFIG_MACB, I don't see any
change in the near future.

BR,
Eric