public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jerzy Dyrda <jerzdy@gmail.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>,
	Richard Rauch <rrauch@itrgmbh.de>
Subject: [ECOS] Re: SDHC support. [Was Re: AW: [ECOS] Fwd: New features required on Cortex-M platform]
Date: Sat, 14 Jun 2014 22:47:00 -0000	[thread overview]
Message-ID: <CABmKEG_GGgHbwPH-84K3Z91xqKXxVMLmkED7zr+rq4Jkwuvr+A@mail.gmail.com> (raw)
In-Reply-To: <539B48F7.9060208@siva.com.mk>

Hello Ilija,

2014-06-13 20:54 GMT+02:00 Ilija Kocho <ilijak@siva.com.mk>:
> 3) SD bus support. I know that I can use SD card in SPI mode but on some
>>> board like STM32F4DISCOVERY SD card i only available on SD bus.
>>> It's high time to add this miss part of system.
>> - SD card interface. Unfortunately this is very processor specific. Each
>> Microcontroller has its own IP for accessing SD card.
>> But only low level SD bus driver. Upper layer for MMC/SD card is common.
>
> This is MMC/SD disk driver for Freescale Kinetis and iMX.
> https://sourceforge.net/projects/ecosfreescale/files/devs/SDHC/
> Upper layer (based on SPI MMC driver) and HW dependent (Freescale) parts
> are placed in separate packages.
>
> Jerzy, can you see if STM support can be added?
After first look I seems that yes.
IMHO it's required some code re-factoring i.e. :
1) CYGPKG_DEVS_DISK_MMC_SDHC should be pushed into CYGPKG_DEVS_DISK_MMC
package as a component similar to CYGPKG_DEVS_DISK_MMC_SPI component.
2) Using Freescale middle layer (sdhc.c) from platform specific
package and pushing it to generic
part. The aim of this layer is support for SDHC transaction what is generic.
3) And we should provide low level platform specific driver for SD bus
not as Freescale in
/devs/disk/mmc/sdhc/ but create new place /devs/sd/cortexm/stm similar
to /devs/spi/cortexm/stm
with simliar functionality i.e. xfer function supporting poling and DMA mode.
4) Regarding license most of code in platform specific part is a Freescale code.
Can we use it?

Best regards,
jerzy

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2014-06-14 22:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 15:15 [ECOS] Fwd: New features required on Cortex-M platform Jerzy Dyrda
2014-06-13 15:33 ` AW: " Richard Rauch
2014-06-13 15:53   ` Jerzy Dyrda
2014-06-13 18:55     ` [ECOS] SDHC support. [Was Re: AW: [ECOS] Fwd: New features required on Cortex-M platform] Ilija Kocho
2014-06-13 19:30       ` [ECOS] " Jerzy Dyrda
2014-06-14 22:47       ` Jerzy Dyrda [this message]
2014-06-16  6:23         ` Ilija Kocho
2014-06-16  2:08 ` [ECOS] RE: New features required on Cortex-M platform Andrew Hannam
2014-06-16 11:02   ` Jerzy Dyrda
2014-06-16 18:46   ` Ilija Kocho
2014-06-17  0:31     ` Andrew Hannam

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=CABmKEG_GGgHbwPH-84K3Z91xqKXxVMLmkED7zr+rq4Jkwuvr+A@mail.gmail.com \
    --to=jerzdy@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    --cc=rrauch@itrgmbh.de \
    /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).