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 1001219] Ethernet driver for STM32 connectivity line with port on MMstm32f107 board. Date: Tue, 11 Oct 2011 20:39:00 -0000 [thread overview] Message-ID: <20111011203907.34C782F7800F@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001219-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=1001219 --- Comment #11 from Ilija Kocho <ilijak@siva.com.mk> 2011-10-11 21:39:04 BST --- (In reply to comment #7) > Created an attachment (id=1396) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1396) [details] > Variant modification needed by STM32 CL http://bugs.ecos.sourceware.org/attachment.cgi?id=1396&action=diff#ecos_clear/packages/hal/cortexm/stm32/var/current/include/var_io.h_sec7 Ethernet definitions are usually stored with Ethernet driver, either with C source or in a header file (I prefer the second). If you move it there than that would imply that names do not contain "_HAL_". http://bugs.ecos.sourceware.org/attachment.cgi?id=1396&action=diff#ecos_clear/packages/hal/cortexm/stm32/var/current/src/hal_diag.c_sec1 What is the reason for renaming of hal_stm32_serial_init() into hal_stm32_serial_init_channel() http://bugs.ecos.sourceware.org/attachment.cgi?id=1396&action=diff#ecos_clear/packages/hal/cortexm/stm32/var/current/src/stm32_misc.c_sec2 Changes like this may look attractive but (as well as previous one) may (will) break other user's applications. Conditional compilation may help but in this case I suggest to keep old code, it's simple and provides working conditions to all peripherals. http://bugs.ecos.sourceware.org/attachment.cgi?id=1396&action=diff#ecos_clear/packages/hal/cortexm/stm32/var/current/src/stm32_misc.c_sec3 Is this necessary? http://bugs.ecos.sourceware.org/attachment.cgi?id=1396&action=diff#ecos_clear/packages/hal/cortexm/stm32/var/current/src/stm32_misc.c_sec4 I'm referring to following: - hal_stm32_sysclk /= 2; + hal_stm32_sysclk = CYGARC_HAL_CORTEXM_STM32_INTERNAL_CLOCK / 2; If it works don't fix it :) Now some minor remarks: Comments like #endif // CYGINT_HAL_CORTEXM_STM32_CL>0 on some places are not consistent with their respective #ifs. And: (this is my personal only) #if CYGINT_HAL_CORTEXM_STM32_CL != 0 or #if CYGINT_HAL_CORTEXM_STM32_CL is more common than >0. -- 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-10-11 20:39 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-03 22:11 [Bug 1001219] New: " bugzilla-daemon 2011-05-04 7:41 ` [Bug 1001219] " bugzilla-daemon 2011-05-12 9:18 ` bugzilla-daemon 2011-10-08 14:02 ` bugzilla-daemon 2011-10-08 14:27 ` bugzilla-daemon 2011-10-10 20:51 ` bugzilla-daemon 2011-10-10 20:54 ` bugzilla-daemon 2011-10-10 20:56 ` bugzilla-daemon 2011-10-10 21:13 ` bugzilla-daemon 2011-10-10 21:50 ` bugzilla-daemon 2011-10-11 19:53 ` bugzilla-daemon 2011-10-11 20:39 ` bugzilla-daemon [this message] 2011-10-11 21:08 ` bugzilla-daemon 2011-10-11 21:45 ` bugzilla-daemon 2011-10-12 11:25 ` bugzilla-daemon 2011-10-12 20:34 ` bugzilla-daemon 2011-10-12 21:15 ` bugzilla-daemon 2011-10-16 14:12 ` bugzilla-daemon 2011-10-16 14:12 ` 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=20111011203907.34C782F7800F@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).