From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1000910] New port: Ethernet over SPI driver for ENC424J600
Date: Thu, 27 Oct 2011 14:41:00 -0000 [thread overview]
Message-ID: <20111027144110.E168C2F78011@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1000910-104@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=1000910
Ilija Stanislevik <ilijas@siva.com.mk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #1132|0 |1
is obsolete| |
--- Comment #14 from Ilija Stanislevik <ilijas@siva.com.mk> 2011-10-27 15:41:08 BST ---
Created an attachment (id=1421)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1421)
Patch to stm3210e-eval HAL - initialization of enc424j600
(In reply to comment #12)
> I see the stm3210e changes include a change to increase RAM use by 16k to allow
> for network-enabled redboot. That's quite a large change for something that
> most people don't need. I think a different MLT file would be better for that.
> You could either create a new HAL startup type, or you could just add a new
> option, and change CYGHWR_MEMORY_LAYOUT to be something like:
>
> calculated { (CYG_HAL_STARTUP == "RAM" ) ?
> (CYGMEM_HAL_CORTEXM_STM32_STM3210E_RESERVE_EXTRA_BASE_RAM ?
> "cortexm_stm3210e_eval_extrabaseram : "cortexm_stm3210e_eval_ram") :
> (CYG_HAL_STARTUP == "SRAM" ) ?
> "cortexm_stm3210e_eval_sram" :
> (CYG_HAL_STARTUP == "ROM" ) ?
> "cortexm_stm3210e_eval_rom" :
> (CYG_HAL_STARTUP == "ROMINT" ) ?
> "cortexm_stm3210e_eval_romint" :
> (CYG_HAL_STARTUP == "JTAG" ) ?
> "cortexm_stm3210e_eval_jtag" :
> "undefined" }
>
> Although I'm suggesting
> CYGMEM_HAL_CORTEXM_STM32_STM3210E_RESERVE_EXTRA_BASE_RAM for the option name,
> you may well be able to choose something with a better name.
>
> Let me know what you think.
I agree. I've introduced new option
CYGMEM_HAL_CORTEXM_STM32_STM3210E_EXTRA_BASE_RAM and corresponding ldi files.
Also, there is a provision to specify the quantity of reserved RAM.
In addition, I've modified the HAL to produce non-conflicting values for
enc424j600 related options. I believe this is better than having conflicting
values at the beginning.
--
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-10-27 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1000910-104@http.bugs.ecos.sourceware.org/>
2011-02-17 9:49 ` bugzilla-daemon
2011-02-17 10:43 ` bugzilla-daemon
2011-10-27 14:22 ` bugzilla-daemon
2011-10-27 14:41 ` bugzilla-daemon [this message]
2011-10-27 14:43 ` bugzilla-daemon
2012-04-02 20:21 ` bugzilla-daemon
2012-04-05 6:22 ` bugzilla-daemon
2012-04-05 15:52 ` bugzilla-daemon
2012-04-20 8:00 ` bugzilla-daemon
2012-04-20 8:07 ` bugzilla-daemon
2012-05-04 16:36 ` bugzilla-daemon
2012-05-04 16:37 ` bugzilla-daemon
2012-05-04 16:37 ` bugzilla-daemon
2012-05-04 16:38 ` bugzilla-daemon
2012-05-04 16:38 ` bugzilla-daemon
2012-05-04 16:39 ` bugzilla-daemon
2012-05-04 16:40 ` bugzilla-daemon
2012-05-07 16:43 ` bugzilla-daemon
2012-05-10 15:48 ` 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=20111027144110.E168C2F78011@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).