Hello Nickolay,
the sources must have a proper license header. Is there a particular
reason why you didn't use the standard SDHC driver:
https://git.rtems.org/rtems-libbsd/tree/freebsd/sys/dev/sdhci/sdhci.c
It depends a bit on your QorIQ variant, some have nasty silicon bugs in
the SDHC area
On 25/07/2016 11:56, Nickolay Kolchin wrote:
We are interested in inclusion this in official RTEMS and are ready to
provide support if required.
Thank you for the offer. If you are interested in contributing to RTEMS
I am happy to chat about some areas where we need help. Getting 4.11 and
the
CMake build system for RTEMS
Nickolay Semyonov
Version 0.5
Why
---
1. Use ninja as build tool to improve compile time performance.
2. Get rid of Cygwin/MSYS on Windows. I.e. under Windows we need only
compiler,
cmake and ninja.
3. Better dependencies tracking.
Intr
From: Nickolay Semyonov
Heavily tested with iozone.
---
c/src/lib/libbsp/powerpc/qoriq/Makefile.am |3 +
c/src/lib/libbsp/powerpc/qoriq/esdhc/esdhc.c | 1215 ++
c/src/lib/libbsp/powerpc/qoriq/include/bsp.h |2 +
3 files changed, 1220 insertions(+)
create mode
The linking error looks like some piece of configuration information is
missing from the application. This results in the configuration information
from the application but being complete and another set being pulled in
from librtemscpu.a. that has the default configuration in it.
On Jul 24, 2016
Thanks a lot. :) I2C framework uses IMFS that why I think this solution
worked.
On Sun, Jul 24, 2016 at 11:52 PM, Ben Gras wrote:
> All,
>
> Aha, I see the problem indeed.
> From the output I conclude default-configuration.o is providing symbols
> that conflict with your configuration symbols. T
All,
Aha, I see the problem indeed.
From the output I conclude default-configuration.o is providing symbols
that conflict with your configuration symbols. This suggests
default-configuration.o is pulled in to satisfy some configuration
requirement. This suggests we should put more info in init.c.
On 23/07/2016 7:41 PM, vivek kukreja wrote:
>
> Thank you for your prompt advice regarding tap interface.
> I followed this mail chain and successfully run the ping01 example in
> rtems-libbsd:
>
> https://lists.rtems.org/pipermail/users/2015-June/029063.html
>
> Now I can ping and FTP into the
https://github.com/punitvara/rtems/tree/new
You can reproduce linking error from this new branch.
On Sat, Jul 23, 2016 at 11:57 PM, Ben Gras wrote:
> All,
>
>
> I tried to reproduce this. The I2C branch of your repo doesn't build
> because of struct i2c not being defined. So I #if 0'd out all
