From: Jerzy Dyrda <jerzdy@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: STM32F4 Discovery + LwIP
Date: Tue, 25 Mar 2014 18:32:00 -0000 [thread overview]
Message-ID: <CABmKEG9APWLOVnkL9mp4CbS7nu4SVA7Uvo8Q3VuvBgdi7Ytc4Q@mail.gmail.com> (raw)
In-Reply-To: <53319FED.7040802@dallaway.org.uk>
Hello John,
On Tuesday 25 of March 2014 15:25:33 John Dallaway wrote:
> On 25/03/14 12:34, Jerzy Dyrda wrote:
>
> > ... I have already brought up network interface on
> >
> > STM32F4DISCOVERY + DM-STF4BB (AFAIK this is original name of base
> > board from Embest, now as I see it's called STM32F4DIS-BB).
>
> Great! Maybe we can work together to get ethernet support for this
> platform added to the eCos repository.
Of course. It's vital to add new stuff in order eCos can be still "useable".
> I think it would be preferable to define a new target such as "stm32f4discovery_bb" in ecos.db which
> includes the STM32 ethernet package. We can then make the necessary
> changes within the platform HAL source code conditional on
> CYGPKG_DEVS_ETH_CORTEXM_STM32. We need to bear in mind that some users
> of the STM32F4-Discovery board may wish to wire up a different PHY
> component rather than using STM32F4DIS-BB.
OK.
Best regards,
jerzy
2014-03-25 16:25 GMT+01:00 John Dallaway <john@dallaway.org.uk>:
> Hi Jerzy and Valentin
>
> On 25/03/14 12:34, Jerzy Dyrda wrote:
>
>> ... I have already brought up network interface on
>>
>> STM32F4DISCOVERY + DM-STF4BB (AFAIK this is original name of base
>> board from Embest, now as I see it's called STM32F4DIS-BB).
>
> Great! Maybe we can work together to get ethernet support for this
> platform added to the eCos repository. I think it would be preferable to
> define a new target such as "stm32f4discovery_bb" in ecos.db which
> includes the STM32 ethernet package. We can then make the necessary
> changes within the platform HAL source code conditional on
> CYGPKG_DEVS_ETH_CORTEXM_STM32. We need to bear in mind that some users
> of the STM32F4-Discovery board may wish to wire up a different PHY
> component rather than using STM32F4DIS-BB.
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2014-03-25 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 8:28 [ECOS] " Valentin BOUSSON
2014-03-25 10:04 ` [ECOS] " John Dallaway
[not found] ` <CABmKEG8rHJqwf_PQp1ZH9e=fgwbK4hFOWJhv1SqaO6nBWQh1tA@mail.gmail.com>
2014-03-25 12:34 ` Jerzy Dyrda
2014-03-25 15:25 ` John Dallaway
2014-03-25 18:32 ` Jerzy Dyrda [this message]
2014-04-08 12:37 ` Valentin BOUSSON
[not found] ` <53466671.3050304@bousson.com>
[not found] ` <CABmKEG-1LBOsLy+44rCQrmFhmEVyKJffxJ3uscF6uSGGkUW7mg@mail.gmail.com>
2014-04-10 13:20 ` Valentin BOUSSON
[not found] ` <CABmKEG_ONPDk26UXzXxPLd==DDKMe7eGdX3FGWABgiffh_wGjQ@mail.gmail.com>
2014-04-11 15:00 ` Valentin BOUSSON
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=CABmKEG9APWLOVnkL9mp4CbS7nu4SVA7Uvo8Q3VuvBgdi7Ytc4Q@mail.gmail.com \
--to=jerzdy@gmail.com \
--cc=ecos-discuss@sourceware.org \
--cc=john@dallaway.org.uk \
/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).