public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alban Bedel <alban.bedel@avionic-design.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net: asix: Fix ASIX 88772B with driver model
Date: Thu, 4 Aug 2016 11:07:39 +0200	[thread overview]
Message-ID: <20160804110739.032b9b25@avionic-0020> (raw)
In-Reply-To: <1470237811.3331.18.camel@toradex.com>

On Wed, 3 Aug 2016 15:23:30 +0000
Marcel Ziswiler <marcel.ziswiler@toradex.com> wrote:

> On Wed, 2016-08-03 at 15:51 +0200, Marek Vasut wrote:
> > On 08/03/2016 11:46 AM, Alban Bedel wrote:
> > > 
> > > On Wed, 3 Aug 2016 09:00:42 +0200
> > > Marek Vasut <marex@denx.de> wrote:
> > > 
> > > > 
> > > > On 08/03/2016 07:32 AM, Alban Bedel wrote:
> > > > > 
> > > > > Commit 147271209a9d ("net: asix: fix operation without eeprom")
> > > > > added a special handling for ASIX 88772B that enable another
> > > > > type of header. This break the driver in DM mode as the extra
> > > > > handling
> > > > > needed in the receive path is missing.
> > > > So add the extra handling ?
> > > I can do that too, but I though u-boot preferred to avoid useless
> > > code.
> > Yes, if it is useless.
> > 
> > > 
> > > > 
> > > > > 
> > > > > However this new header mode is not required and only seems to
> > > > > increase the code complexity, so this patch revert this part of
> > > > > commit 147271209a9d.
> > > > Why is it not required ?
> > > It works fine without, since 2012. In fact this change is not even
> > > mentioned in the log of commit 147271209a9d, so I really don't know
> > > why
> > > it was added in the first place. As can be seen in the revert all
> > > it
> > > does is adding 2 bytes to the USB packets that are then just
> > > skipped.
> > > Seems pretty useless to me.
> > I would like to get some feedback on this from Marcel, since he added
> > this stuff.
> 
> Yes, sorry. I just came back from vacation and started looking into it
> now. As far as I remember on our hardware without this Ethernet did not
> quite work reliably. This also means that with driver model so far it
> does not work for us which I fed back to Simon once but so far this has
> not been resolved. That fix came from some early U-Boot work done by
> Antmicro way back and I am missing some of the history.

Then I'll do a new patch that just fix the driver model receive path.

Alban

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160804/93886a01/attachment.sig>

  reply	other threads:[~2016-08-04  9:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  5:32 [U-Boot] [PATCH] net: asix: Fix ASIX 88772B with driver model Alban Bedel
2016-08-03  7:00 ` Marek Vasut
2016-08-03  9:46   ` Alban Bedel
2016-08-03 13:51     ` Marek Vasut
2016-08-03 15:23       ` Marcel Ziswiler
2016-08-04  9:07         ` Alban Bedel [this message]
2016-08-04  9:12           ` Marek Vasut
2016-08-09 12:14             ` Marcel Ziswiler
2016-08-09 12:32               ` Marek Vasut
2016-08-11  8:52                 ` Alban Bedel
2016-08-11  9:26                   ` Marek Vasut
2016-08-11 10:28                     ` Alban Bedel
2016-08-11 14:18                       ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160804110739.032b9b25@avionic-0020 \
    --to=alban.bedel@avionic-design.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox