this, but please apply if you
feel it is correct.
- Arnon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Ungerer
Sent: Friday, June 15, 2007 03:54
To: uClinux development list
Subject: Re: SV: [uClinux-dev] Odd network problem IXDP425
Hi Arnon,
Arnon
, and it made no
difference.
Any help would be appreciated,
- Arnon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Ungerer
Sent: Friday, April 13, 2007 03:33
To: uClinux development list
Subject: Re: SV: [uClinux-dev] Odd network problem IXDP425
Hi
would be appreciated,
- Arnon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Ungerer
Sent: Friday, April 13, 2007 03:33
To: uClinux development list
Subject: Re: SV: [uClinux-dev] Odd network problem IXDP425
Hi Knut,
Knut Johansson wrote:
Hi Assaf
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Ungerer
Sent: Friday, April 13, 2007 03:33
To: uClinux development list
Subject: Re: SV: [uClinux-dev] Odd network problem IXDP425
Hi Knut,
Knut Johansson wrote:
Hi Assaf, all
I have tried different boards they are all the same, and if I go
Hi Knut,
Knut Morten Johansson wrote:
On Friday 13 April 2007 02:32:37 Greg Ungerer wrote:
Though this wouldn't explain the eepro100 not working.
Indeed, this one still remains. SInce it (miss)behaves the same, could it be a
PHY detection problem on this one too?
I thought the PHY was
Thanks Greg and Leon
The PHYs was indeed the problem. One down, one one to go:-)
On Friday 13 April 2007 02:32:37 Greg Ungerer wrote:
I have seen this type of behavior (working on 2.4 and not on 2.6) if
the PHY detection code is not quite right in the AccessLibrary code.
Check that first,
