---
cpukit/libmisc/stackchk/check.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/cpukit/libmisc/stackchk/check.c b/cpukit/libmisc/stackchk/check.c
index e8e360d..39650f5 100644
--- a/cpukit/libmisc/stackchk/check.c
+++ b/cpukit/libmisc/stackchk/check.c
@@ -232,7
---
cpukit/score/cpu/arm/arm-exception-frame-print.c | 34 +---
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/cpukit/score/cpu/arm/arm-exception-frame-print.c
b/cpukit/score/cpu/arm/arm-exception-frame-print.c
index eaeef94..3ec927a 100644
--- a/cpukit/score/
---
c/src/libchip/network/dwmac-1000-core.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/c/src/libchip/network/dwmac-1000-core.c
b/c/src/libchip/network/dwmac-1000-core.c
index 770078a..3aaf0b0 100644
--- a/c/src/libchip/network/dwmac-1000-core.c
+++ b/c/
Oh, I forgot to remove this driver. It is now located in the libbsd. I
will remove it.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : P
Hello Alan,
thanks much for testing.
I have rebased RPi related changes to the actual master
head and rebuild toolchain to Newlib 2.4.0.20160527 and
GCC 6-20160526. The test on RPi1 from U-boot goes
OK so I have pushed changes to the master.
On Monday 30 of May 2016 23:04:36 Alan Cudmore wrote:
Hello Pavel,
On 30/05/16 15:57, Pavel Pisa wrote:
Hello Jin-Hyun and Sebastian,
On Monday 30 of May 2016 15:06:40 Sebastian Huber wrote:
>Wouldn't it make sense to use the libbsd for this network interface driver?
my feeling is that from long run perspective is libBSD.
But I think that virti
A beginner question:
Can someone point me to a tutorial on how to read and write serial ports
under RTEMS?
--
Mike Westfall
Control Systems Software Engineer
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hello,
I have managed to resolve previous errors and the driver is finally
building. I want to test this on hardware now. I tried running "USB01"
testsuit for this. But I could not see any output on minicom.
Is there any debug flag/macro which I can turn on in order to get all the
error log? Or a
On 31/05/2016 18:14, Sebastian Huber wrote:
Oh, I forgot to remove this driver. It is now located in the libbsd. I
will remove it.
Is this driver in the legacy stack not working? What about leaving it if
it works and remove it when the stack is removed from rtems.git which
will be after 4.12
Hello Sai Charan Sane and others,
I have included mainline lwIP as a submodule in src/lwip
of your repository. Then I have filterred our lwip-omk
https://sourceforge.net/p/ulan/lwip-omk/ci/master/tree/
repository commits to include only ports commits there.
I have moved our ports to src/ports su
On Tue, May 31, 2016 at 7:46 PM, Pavel Pisa wrote:
> Hello Sai Charan Sane and others,
>
> I have included mainline lwIP as a submodule in src/lwip
> of your repository. Then I have filterred our lwip-omk
> https://sourceforge.net/p/ulan/lwip-omk/ci/master/tree/
> repository commits to include o
Reminder: Second meeting tomorrow. I won't send more reminders.
On Tue, May 24, 2016 at 11:01 AM, Gedare Bloom wrote:
> We will have our first weekly IRC meeting for GSoC students tomorrow,
> Wednesday May 25 10:00 A.M. Eastern Daylight Savings Time (EDT: UTC-4)
> hence 14:00 UTC/GMT. The purpose
On 01/06/2016 01:50, Michael Westfall wrote:
Can someone point me to a tutorial on how to read and write serial ports
under RTEMS?
RTEMS supports termois. There are a number of examples of termios
programming around. A quick search turned up
https://en.wikibooks.org/wiki/Serial_Programming/te
[ hijacked thread ]
On 31/05/2016 21:05, Sebastian Huber wrote:
the x86 architecture is not really interesting for me. So, I am not
against a mainline integration.
Great.
However, I think we reached a dead end with the pc386 BSP.
I do not agree, the BSP is alive and working ... ... yeap
On 31/05/16 23:34, Chris Johns wrote:
On 31/05/2016 18:14, Sebastian Huber wrote:
Oh, I forgot to remove this driver. It is now located in the libbsd. I
will remove it.
Is this driver in the legacy stack not working? What about leaving it
if it works and remove it when the stack is removed
On 01/06/16 06:42, Chris Johns wrote:
The RTEMS driver infrastructure is not capable
enough to deal with a plug-and-play architecture like x86.
This does not make sense to me and I fail to see how it relates to the
previous statement. The original classic API for RTEMS is based on a
VME bus
Hello Deval,
I would use a hardware debugger or Qemu to tackle this problem.
On 31/05/16 19:32, Deval Shah wrote:
Hello,
I have managed to resolve previous errors and the driver is finally
building. I want to test this on hardware now. I tried running "USB01"
testsuit for this. But I could n
Hello Mudit,
On 30/05/16 10:13, Mudit Jain wrote:
Hi all,
I have ported the code from the present FreeBSD.
Link : https://github.com/spark1729/rtems-libbsd/commits/rpi_sd_card
nice work.
Kindly review the same and suggest changes.
The commits are a bit unstructured, the second last one b
On 26/05/16 01:04, Chris Johns wrote:
On 25/05/2016 21:30, Sebastian Huber wrote:
I get now an undefined reference error:
Making all in loopback
gmake[6]: Entering directory
`/build/git-build/b-sis/sparc-rtems4.12/c/sis/testsuites/samples/loopback'
sparc-rtems4.12-gcc -B../../../../../sis/
On 01/06/2016 15:22, Sebastian Huber wrote:
On 31/05/16 23:34, Chris Johns wrote:
On 31/05/2016 18:14, Sebastian Huber wrote:
Oh, I forgot to remove this driver. It is now located in the libbsd. I
will remove it.
Is this driver in the legacy stack not working? What about leaving it
if it work
On 01/06/2016 15:39, Sebastian Huber wrote:
Sorry about this, it looks like my --enable-network build is not
working. I will take a look.
Maybe an --enable-networking typo?
I have thrown those scripts away and I am adding a tool to the RTEMS
tools project to do this. I have something going
21 matches
Mail list logo
