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 1000910] New port: Ethernet over SPI driver for ENC424J600 Date: Thu, 17 Feb 2011 10:43:00 -0000 [thread overview] Message-ID: <20110217104349.09C552F78005@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1000910-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=1000910 Ilija Stanislevik <ilijas@siva.com.mk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1033|0 |1 is obsolete| | --- Comment #11 from Ilija Stanislevik <ilijas@siva.com.mk> 2011-02-17 10:43:46 GMT --- Created an attachment (id=1132) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1132) Patch to ecos.db, ChangeLog and STM3210eval HAL STM3210e_eval HAL: STM3210e_eval HAL defined resources used for SPI Ethernet driver are now parented in SPI Ethernet driver. User enters port and pin to which interrupt from SPI Ethernet controller is connected. Default values are intentionally made unacceptable, so the user is given a chance to think and enter data which match his hardware situation. Interrupt vector is automatically calculated based on pin entered. User can select to which of the STM32's SPI buses is connected the Ethernet chip. Only the buses which are enabled in SPI driver are available for selection. This option requires at least one SPI bus to be enabled. If none is enabled, the "requires" mechanism automatically enables bus 1. I find this safe enough because if there is only this SPI device in the system, it is highly likely that it is connected to bus 1. If someone adds more SPI devices, or a device to another SPI bus, he/she will be aware of the possibilities and will enable and select correct buses. Using the same logic, the chip select number defaults to 0 (indicating the first cs from the list defined in SPI driver), which I made the lowest legal_value. I wasn't able to establish a hard upper limit, so I put one which I deem fair enough. SPI bus pin toggle rate is required to be 50MHz, which accommodates for enc424j600's SPI 14MHZ rate. -- 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-02-17 10:43 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-1000910-777@http.bugs.ecos.sourceware.org/> 2011-02-17 9:49 ` bugzilla-daemon 2011-02-17 10:43 ` bugzilla-daemon [this message] [not found] <bug-1000910-13@http.bugs.ecos.sourceware.org/> 2010-11-30 14:23 ` bugzilla-daemon 2010-11-30 15:10 ` bugzilla-daemon 2010-11-30 20:45 ` bugzilla-daemon 2011-02-17 9:23 ` bugzilla-daemon 2011-02-17 9:49 ` bugzilla-daemon 2011-02-17 10:44 ` bugzilla-daemon 2011-10-27 14:23 ` bugzilla-daemon 2011-10-27 14:41 ` bugzilla-daemon 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:41 ` bugzilla-daemon 2012-05-07 16:43 ` bugzilla-daemon 2012-05-10 15:48 ` bugzilla-daemon [not found] <bug-1000910-776@http.bugs.ecos.sourceware.org/> 2010-11-30 14:21 ` bugzilla-daemon 2010-11-30 14:24 ` bugzilla-daemon 2010-11-30 15:10 ` bugzilla-daemon 2011-02-17 9:23 ` bugzilla-daemon 2011-02-17 9:49 ` 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=20110217104349.09C552F78005@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).