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 1001275] Cortex-M (armV7) architecture endian instructions / Applied on lwIP Date: Thu, 25 Aug 2011 08:20:00 -0000 [thread overview] Message-ID: <20110825081957.55C3A2F7800E@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001275-777@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=1001275 --- Comment #34 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-08-25 09:19:53 BST --- (In reply to comment #33) > (In reply to comment #32) > > (In reply to comment #29) > > > > > > AnonCVS. Now I repeated the tests on LPC-1766-STK (ECM > > > > attached). > > [snip] > > > Unfortunately, I have not Cortex-M targets and it was very helpful > > that you have spent your time on testing. > > If you need to put your hands on some specific device we have in our > lab (LPC- 17xx, STM32, Kinetis) I can provide you remote access to our > dev/eval boards - through PEEDI, (invitation valid to eCos maintainers > and contributors). It is tempting offer. I'll have it in mind. Thank you. > > Now your code in CVS. > > > > Thank you very much for your work. Thank you for your patience, > > thank you for your cooperation. > > Thank you for review and good advices. I'm glad we augmented eCos for > Cortex-M in a non-intrusive way. > > OFF-TOPIC: There are few my bugs that have been checked in, but not > yet formally resolved in Bugzilla. Can I resolve them? Sure! Please, reduce our backlog. Sergei -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2011-08-25 8:20 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-03 17:46 [Bug 1001275] New: Cortex-M (armV7) architecture endian instructions / lwIP bugzilla-daemon 2011-07-03 17:52 ` [Bug 1001275] " bugzilla-daemon 2011-07-03 17:56 ` [Bug 1001275] Cortex-M (armV7) architecture endian instructions / Applied on lwIP bugzilla-daemon 2011-08-15 20:18 ` bugzilla-daemon 2011-08-17 20:26 ` bugzilla-daemon 2011-08-18 21:14 ` bugzilla-daemon 2011-08-19 8:41 ` bugzilla-daemon 2011-08-19 15:10 ` bugzilla-daemon 2011-08-19 15:18 ` bugzilla-daemon 2011-08-21 13:46 ` bugzilla-daemon 2011-08-22 12:10 ` bugzilla-daemon 2011-08-22 13:01 ` bugzilla-daemon 2011-08-22 13:23 ` bugzilla-daemon 2011-08-22 13:36 ` bugzilla-daemon 2011-08-22 14:24 ` bugzilla-daemon 2011-08-22 18:26 ` bugzilla-daemon 2011-08-23 13:32 ` bugzilla-daemon 2011-08-23 14:18 ` bugzilla-daemon 2011-08-23 16:14 ` bugzilla-daemon 2011-08-23 16:17 ` bugzilla-daemon 2011-08-23 16:19 ` bugzilla-daemon 2011-08-23 16:21 ` bugzilla-daemon 2011-08-23 19:28 ` bugzilla-daemon 2011-08-23 20:15 ` bugzilla-daemon 2011-08-23 20:47 ` bugzilla-daemon 2011-08-24 6:51 ` bugzilla-daemon 2011-08-24 7:08 ` bugzilla-daemon 2011-08-24 13:34 ` bugzilla-daemon 2011-08-24 13:47 ` bugzilla-daemon 2011-08-24 16:43 ` bugzilla-daemon 2011-08-24 17:01 ` bugzilla-daemon 2011-08-24 17:56 ` bugzilla-daemon 2011-08-25 8:02 ` bugzilla-daemon 2011-08-25 8:20 ` bugzilla-daemon [this message] 2011-08-25 14:03 ` 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=20110825081957.55C3A2F7800E@mail.ecoscentric.com \ --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: 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).