public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1002058] New: at91 emac lwIP fix against blocking tcp/ip stack
Date: Mon, 20 Apr 2015 12:09:00 -0000	[thread overview]
Message-ID: <bug-1002058-777@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002058

            Bug ID: 1002058
           Summary: at91 emac lwIP fix against blocking tcp/ip stack
           Product: eCos
           Version: unknown
            Target: at91sam7xek_256 (Atmel AT91SAM7X-EK board with
                    AT91SAM7X256)
  Architecture/Host ARM
                OS:
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: low
         Component: Ethernet
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: oli@snr.ch
                CC: ecos-bugs@ecos.sourceware.org

Created attachment 2587
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2587&action=edit
emac lwIP at91 fix

There are differnet problems in the lwIP / at91/emac combination.
- the at91 driver caculates the needed bufferspace wrong.
- the at91 driver dont remove every broken packet from the emac buffer.
- the at91 driver blocks on some transmit errors.
- the lwIP/eCOS interface has some polling loops which dont give the control to
other threads.
- there is a strange requirement for the PBUF and INPACKET buffer to be bigger
then the MAILBOX-size.

-- 
You are receiving this mail because:
You are the assignee for the bug.


             reply	other threads:[~2015-04-20 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 12:09 bugzilla-daemon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-20 12:09 bugzilla-daemon

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=bug-1002058-777@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@bugs.ecos.sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).