[I know this is old, but it may save someone else some pain...]
On Thu, Jun 5, 2008 at 11:59 AM, Russell McGuire
<[EMAIL PROTECTED]> wrote:
> To save most the banter, and rephrasing:
>
> What is the 'EXPECTED' current behavior of the 83xx/6xx architecture for the
> most current 1.3.3+ GIT release
Russell McGuire wrote:
> To save most the banter, and rephrasing:
>
> What is the 'EXPECTED' current behavior of the 83xx/6xx architecture for the
> most current 1.3.3+ GIT release of passing MACs into Linux 2.6.24. Lastly, I
> am using the UEC 83xx driver.
>
> I have defined QE_OF.
> I have defi
To save most the banter, and rephrasing:
What is the 'EXPECTED' current behavior of the 83xx/6xx architecture for the
most current 1.3.3+ GIT release of passing MACs into Linux 2.6.24. Lastly, I
am using the UEC 83xx driver.
I have defined QE_OF.
I have defined CONFIG_UEC_ETH.
I have defined CON
Russell McGuire wrote:
> Guys,
>
> I am sure this has been brought up a number of times, so forgive me in
> advance.
>
> I did notice however, not sure which version, but between 1.3.1 and
> 1.3.3 U-boot That my MAC for my Ethernet device was no longer being
> passed into linux, or perhaps over
In message <[EMAIL PROTECTED]> you wrote:
>
> I am sure this has been brought up a number of times, so forgive me in
> advance.
No. We do not forgive ignorance nor intentional ignoring established
netiquette which for example requires you to actually search the
archives and to read the FAQ before
Guys,
I am sure this has been brought up a number of times, so forgive me in
advance.
I did notice however, not sure which version, but between 1.3.1 and 1.3.3
U-boot
That my MAC for my Ethernet device was no longer being passed into linux, or
perhaps over written by the blob.
So for a
