public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001177] Redboot DHCP client race condition, XID, and retry problems. Date: Sat, 26 Mar 2011 18:01:00 -0000 [thread overview] Message-ID: <20110326180146.AA4112F78001@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001177-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001177 Grant Edwards <grant.b.edwards@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1182|0 |1 is obsolete| | --- Comment #9 from Grant Edwards <grant.b.edwards@gmail.com> 2011-03-26 18:01:42 GMT --- Created an attachment (id=1184) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1184) Second pass at BOOTP/DHCP rewrite. Comments are welcome on the second pass at the BOOTP/DHCP rewrite. Changes from the first pass are: 1) Miscellaneous cleanup. 2) Fixed DHCP support so that it works in "fall-back" mode if the server only does plain BOOTP and not DHCP. 3) Created new option CYGPKG_REDBOOT_NETWORKING_BOOTP (default 1) which controls whether or not BOOTP/DHCP support (src/net/bootp.c) is built. This new package contains the sub-options: CYGSEM_REDBOOT_NETWORKING_DHCP (default 1) CYGSEM_REDBOOT_NETWORKING_BOOTP_VERBOSE (default 0) CYGSEM_REDBOOT_DEFAULT_NO_BOOTP (default 0) That last one used to be contained in CYGDAT_REDBOOT_DEFAULT_IP_ADDR. Building with no BOOTP-related options specified should result in the same behavior as previously. I've done test builds for i386 PC platform with all combinations of "absent/0/1" for the following: CYGPKG_REDBOOT_NETWORKING_BOOTP CYGSEM_REDBOOT_DEFAULT_NO_BOOTP CYGSEM_REDBOOT_NETWORKING_DHCP CYGSEM_REDBOOT_NETWORKING_BOOTP_VERBOSE CYGDAT_REDBOOT_DEFAULT_IP_ADDR About a dozen of the combinations have been tested with both DHCP and BOOTP-only servers. One thing I don't have the ability to test is flash-config support, so it wouldn't hurt if somebody took a look at that. I tried building for the i386 PC platform with CYGSEM_REDBOOT_FLASH_CONFIG enabled, but that didn't work. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2011-03-26 18:01 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-21 14:50 [Bug 1001177] New: " bugzilla-daemon 2011-03-24 14:35 ` [Bug 1001177] " bugzilla-daemon 2011-03-24 17:37 ` bugzilla-daemon 2011-03-24 17:37 ` bugzilla-daemon 2011-03-24 17:37 ` bugzilla-daemon 2011-03-24 18:12 ` bugzilla-daemon 2011-03-24 19:33 ` bugzilla-daemon 2011-03-24 19:36 ` bugzilla-daemon 2011-03-25 16:20 ` bugzilla-daemon 2011-03-26 2:17 ` bugzilla-daemon 2011-03-26 4:21 ` bugzilla-daemon 2011-03-26 18:01 ` bugzilla-daemon [this message] 2011-06-08 16:13 ` bugzilla-daemon 2012-03-02 21:10 ` bugzilla-daemon 2012-03-03 3:44 ` bugzilla-daemon 2012-03-03 3:44 ` bugzilla-daemon 2012-03-06 16:47 ` bugzilla-daemon 2011-03-21 14:50 [Bug 1001177] New: " bugzilla-daemon 2011-03-24 14:36 ` [Bug 1001177] " bugzilla-daemon 2011-03-24 17:37 ` bugzilla-daemon 2011-03-24 17:37 ` bugzilla-daemon 2011-03-24 17:37 ` 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=20110326180146.AA4112F78001@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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: linkBe 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).