Re: [patch] fix odd byte problem on smsc91c111 revision 0 chips

[jeroen dobbelaere <jeroen dot dobbelaere at acunia dot com>]

Hello Mark,

Mark Salter wrote:
> Which platform are you using? Its been a while, but I ran into this
> problem and the fix appeared to be much more complicated. Could you
> refresh my memory about the errata? Just blindly assuming odd
> frames and increasing len seems wrong and I think it won't work on
> the platform I was using.
>
> --Mark

This is on one of our (old) webtablets (based on our Xingu technology) which
still has an old revision of this chip.

The idea is that it won't hurt to read an extra byte,
as the specific protocol also has it's length specified.

It is possible that this solution doesn't work when using protocols,
where this assumption doesn't hold, but so far I had no problems with this fix,
and a lot of problems without it.


> > > > > > jeroen dobbelaere writes:
>
>
> > This is a multi-part message in MIME format.
> > --------------060607050602040201070505
> > Content-Type: text/plain; charset=us-ascii; format=flowed
> > Content-Transfer-Encoding: 7bit
>
>
> > - Following patch fixes a problem when using revision 0 versions of the
> > smsc 91c111 chip.
> > - It will also identify and display the chip (version, revision).
>
>
> > (patch against eCos v2.0)
[...]

Greetings,
--
Jeroen Dobbelaere
Embedded Software Engineer

ACUNIA Embedded Solutions
http://www.acunia.com/aes