On 02/04/15 03:22, Chris Johns wrote:
On 1/04/2015 7:07 pm, Alexander Krutwig wrote:
during my work with FreeBSD timecounters, I found out that the FreeBSD
timecounters start with an uptime value of 1 second. Developers of
FreeBSD told me that this is due to problems in the ARP code.
RTEMS uptim
Hello Alexandru-Sever,
in case you use the latest RTEMS version, then I would consider to use
the new I2C support:
https://docs.rtems.org/doxygen/cpukit/html/group__I2C.html
For example see:
https://git.rtems.org/rtems/tree/cpukit/dev/i2c
https://git.rtems.org/rtems/tree/testsuites/libtests
From: Alexandru-Sever Horin
libi2c registration of a device fails if the device initialization fails
Benefits: allows for device probing on multiple addresses
---
cpukit/libi2c/libi2c.c | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/cpukit/libi2
Hi,
I was yet to submit the patch for hello world.
Attaching it here.
On Thu, Mar 26, 2015 at 7:15 PM, Gedare Bloom wrote:
> Yes this is acceptable, thanks! Please post your patch too.
> -Gedare
>
> On Thu, Mar 26, 2015 at 1:07 AM, Rohini Kulkarni
> wrote:
> > Hi All,
> >
> > I have chosen Ras
On 1/04/2015 7:07 pm, Alexander Krutwig wrote:
>
> during my work with FreeBSD timecounters, I found out that the FreeBSD
> timecounters start with an uptime value of 1 second. Developers of
> FreeBSD told me that this is due to problems in the ARP code.
> RTEMS uptime is initialized to an uptime
Hello Hugo,
On Wednesday 01 of April 2015 12:58:33 zj...@york.ac.uk wrote:
> Hi:
>
> I am a student to work with RTEMS these days.
>
> I like this OS, but I found there's few information about RTEMS, I am
> really desired to know how can I add a new driver for it, such as LCD
> driver or others.
>
Hello Gedare,
On Wednesday 01 of April 2015 16:38:05 Gedare Bloom wrote:
> On Wed, Apr 1, 2015 at 7:01 AM, Pavel Pisa wrote:
> > https://github.com/AoLaD/rtems-tms570-utils/blob/Headers/headers/headers/
> >CRC.h
>
> For headers/code that is automatically generated, I'd like to see a
> very permis
Hello Martin,
On Wednesday 01 of April 2015 21:08:19 Martin Galvan wrote:
> On Wed, Apr 1, 2015 at 8:01 AM, Pavel Pisa wrote:
> > To Martin Galvan: What is your opinion? Would you join the work in
> > this direction?
>
> So if I understood correctly, what you did was converting the
> datasheet PD
Hi
Hesham.. I can't get hello world to run with either framework.
Can you take a look?
Thanks.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherr...@oarcorp.comOn-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Avail
On 4/1/2015 2:02 PM, Gedare Bloom wrote:
> On Wed, Apr 1, 2015 at 2:54 PM, Sebastian Huber
> wrote:
>> - Gedare Bloom schrieb:
>>> On Wed, Apr 1, 2015 at 11:58 AM, Joel Sherrill
>>> wrote:
On 4/1/2015 10:01 AM, Gedare Bloom wrote:
> I didn't read much of this, but it needs do
On Wed, Apr 1, 2015 at 8:01 AM, Pavel Pisa wrote:
> To Martin Galvan: What is your opinion? Would you join the work in
> this direction?
So if I understood correctly, what you did was converting the
datasheet PDF to some parseable format, then you parsed that file to
extract the registers and bit
On Wed, Apr 1, 2015 at 2:54 PM, Sebastian Huber
wrote:
>
> - Gedare Bloom schrieb:
>> On Wed, Apr 1, 2015 at 11:58 AM, Joel Sherrill
>> wrote:
>> >
>> >
>> > On 4/1/2015 10:01 AM, Gedare Bloom wrote:
>> >> I didn't read much of this, but it needs doxygen, and probably part of
>> >> the previ
- Gedare Bloom schrieb:
> On Wed, Apr 1, 2015 at 11:58 AM, Joel Sherrill
> wrote:
> >
> >
> > On 4/1/2015 10:01 AM, Gedare Bloom wrote:
> >> I didn't read much of this, but it needs doxygen, and probably part of
> >> the previous patch should be merged in here, or some better
> >> splitting/
On Wed, Apr 1, 2015 at 2:42 PM, Sebastian Huber
wrote:
>
> - Joel Sherrill schrieb:
>>
>>
>> On 4/1/2015 9:18 AM, Gedare Bloom wrote:
>> > Would you then subtract 1 from uptime when reporting it? Or would
>> > users be expected to know that uptime is off-by-1?
>> I would prefer we subtract on
- Joel Sherrill schrieb:
>
>
> On 4/1/2015 9:18 AM, Gedare Bloom wrote:
> > Would you then subtract 1 from uptime when reporting it? Or would
> > users be expected to know that uptime is off-by-1?
> I would prefer we subtract one when reporting to the user.
The question is reporting via wh
I noticed this wasn't merged.
Ben.. ?
some comments interspersed.
On 3/10/2015 4:21 PM, ragu nath wrote:
> Hi All,
>
> I was exploring the beagle code base to find a task to get hands on
> experience with RTEMS internals. I found that "Real time Clock (RTC)" support
> is
> missing for beaglebon
OK, sorry to nitpick, but could you do one more favor and split the
commit message up into a short one-liner and longer text separated by
a blank line, like:
---
cpukit/libi2c allowed to probe on device init
libi2c registration of a device fails if the device initialization fails
Benefits: allows
Thanks Sebastian, I saw your comment about holding a patch back and
figured we better push this release to avoid a large backlog. I think
we can expect to cut the branch next week, after DanielH gets a chance
to push his drvmgr and pci code.
On Wed, Apr 1, 2015 at 11:51 AM, Sebastian Huber
wrote:
On Wed, Apr 1, 2015 at 11:58 AM, Joel Sherrill
wrote:
>
>
> On 4/1/2015 10:01 AM, Gedare Bloom wrote:
>> I didn't read much of this, but it needs doxygen, and probably part of
>> the previous patch should be merged in here, or some better
>> splitting/recombining of patches so I don't have to revi
On 4/1/2015 10:01 AM, Gedare Bloom wrote:
> I didn't read much of this, but it needs doxygen, and probably part of
> the previous patch should be merged in here, or some better
> splitting/recombining of patches so I don't have to review code that
> gets fixed. It's worth repeating, the "rtems_*t
I hold back new stuff like
- fine grained locking for semaphores and message queues,
- FreeBSD timecounters,
- watchdog SMP improvements, and
- SPARC FPU context switch improvments.
I am really looking forward to working with the new build system.
- Gedare Bloom schrieb:
> I'd like to cut t
From: Alexandru-Sever Horin
---
cpukit/libi2c/libi2c.c | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/cpukit/libi2c/libi2c.c b/cpukit/libi2c/libi2c.c
index 233cb68..315a761 100644
--- a/cpukit/libi2c/libi2c.c
+++ b/cpukit/libi2c/libi2c.c
@@ -736
On Wed, Apr 1, 2015 at 11:25 AM, Joel Sherrill
wrote:
>
>
> On April 1, 2015 10:14:48 AM CDT, Daniel Hellstrom wrote:
>>On 04/01/2015 05:05 PM, Gedare Bloom wrote:
>>> Daniel,
>>>
>>> On Wed, Apr 1, 2015 at 11:02 AM, Daniel Hellstrom
>> wrote:
On 04/01/2015 04:40 PM, Gedare Bloom wrote:
Two line length/break issues, and I think we're set!
On Wed, Apr 1, 2015 at 11:18 AM, Alexandru-Sever Horin
wrote:
> From: Alexandru-Sever Horin
>
> ---
> cpukit/libi2c/libi2c.c | 21 +
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/cpukit/libi2c/libi2c.
On April 1, 2015 10:14:48 AM CDT, Daniel Hellstrom wrote:
>On 04/01/2015 05:05 PM, Gedare Bloom wrote:
>> Daniel,
>>
>> On Wed, Apr 1, 2015 at 11:02 AM, Daniel Hellstrom
> wrote:
>>> On 04/01/2015 04:40 PM, Gedare Bloom wrote:
I'd like to cut the 4.11 branch as soon as we get the drvmgr/pci
From: Alexandru-Sever Horin
---
cpukit/libi2c/libi2c.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/cpukit/libi2c/libi2c.c b/cpukit/libi2c/libi2c.c
index 233cb68..43daa86 100644
--- a/cpukit/libi2c/libi2c.c
+++ b/cpukit/libi2c/libi2c.c
@@ -736,6 +736
On 04/01/2015 05:05 PM, Gedare Bloom wrote:
Daniel,
On Wed, Apr 1, 2015 at 11:02 AM, Daniel Hellstrom wrote:
On 04/01/2015 04:40 PM, Gedare Bloom wrote:
I'd like to cut the 4.11 branch as soon as we get the drvmgr/pci
patches merged. Please state if you have any other necessary patches
or blo
Daniel,
On Wed, Apr 1, 2015 at 11:02 AM, Daniel Hellstrom wrote:
> On 04/01/2015 04:40 PM, Gedare Bloom wrote:
>>
>> I'd like to cut the 4.11 branch as soon as we get the drvmgr/pci
>> patches merged. Please state if you have any other necessary patches
>> or blockers for release. The plan will b
This patch could use some more explanation, and probably some
documentation in the BSP guide. Why is erc32 being changed, for what
purpose?
On Wed, Apr 1, 2015 at 10:37 AM, Alexander Krutwig
wrote:
> ---
> c/src/lib/libbsp/shared/clockdrv_shell.h| 31 -
> c/src/lib/libbsp/spa
On 04/01/2015 04:40 PM, Gedare Bloom wrote:
I'd like to cut the 4.11 branch as soon as we get the drvmgr/pci
patches merged. Please state if you have any other necessary patches
or blockers for release. The plan will be to create a 4.11 branch and
tag 4.11.0 and then only bug-fixes should go into
I didn't read much of this, but it needs doxygen, and probably part of
the previous patch should be merged in here, or some better
splitting/recombining of patches so I don't have to review code that
gets fixed. It's worth repeating, the "rtems_*time" functions are not
following the API conventions
On Wed, Apr 1, 2015 at 10:37 AM, Alexander Krutwig
wrote:
> ---
> cpukit/score/Makefile.am | 10 ++
> cpukit/score/include/rtems/score/timecounter.h | 23 +++
> cpukit/score/include/sys/timeffc.h | 2 +
> cpukit/score/include/sys/timetc.h
Alex,
Can you resend with git-send-email? Also, please be sure to use the
same style as the rest of the file, or the RTEMS Style rules
otherwise. In particular, use { on same line as if, and spaces around
().
Other than style, I think this looks ok.
Gedare
On Wed, Apr 1, 2015 at 10:31 AM, Alex
I'd like to cut the 4.11 branch as soon as we get the drvmgr/pci
patches merged. Please state if you have any other necessary patches
or blockers for release. The plan will be to create a 4.11 branch and
tag 4.11.0 and then only bug-fixes should go into 4.11 branch, and
master becomes the next rele
On Wed, Apr 1, 2015 at 7:01 AM, Pavel Pisa wrote:
> Hello all,
>
> I would like to inform you that Premysl Houdek is near to finishing
> preparation of complete registers header files for TMS570LS3137.
> The register and fields definition are interactively retrieved
> with help of some macro from
---
cpukit/score/include/sys/_ffcounter.h | 42 +
cpukit/score/include/sys/timeffc.h| 389 +++
cpukit/score/include/sys/timepps.h| 249
cpukit/score/include/sys/timetc.h | 89 ++
cpukit/score/include/sys/timex.h | 171 +++
cpukit/score/src/kern_tc.c| 20
---
c/src/lib/libbsp/shared/clockdrv_shell.h| 31 -
c/src/lib/libbsp/sparc/erc32/clock/ckinit.c | 54 +++--
2 files changed, 66 insertions(+), 19 deletions(-)
diff --git a/c/src/lib/libbsp/shared/clockdrv_shell.h
b/c/src/lib/libbsp/shared/clockdrv_shel
---
cpukit/libnetworking/rtems/rtems_bsdnet_internal.h | 3 +-
cpukit/libnetworking/rtems/rtems_glue.c| 4 -
cpukit/posix/src/clockgettime.c| 3 +-
cpukit/posix/src/posixtimespecabsolutetimeout.c| 2 +-
cpukit/posix/src/timergettime.c
---
cpukit/score/Makefile.am | 10 ++
cpukit/score/include/rtems/score/timecounter.h | 23 +++
cpukit/score/include/sys/timeffc.h | 2 +
cpukit/score/include/sys/timetc.h | 2 +
cpukit/score/preinstall.am
Hello,
I am currently working on a project which uses I2C devices through libi2c
API.
The problem that I am facing is that this function:
rtems_libi2c_register_drv actually registeres the device before
drvtbl->ops->initialization_entry returns success or failure. This means
that it is impossible
On 4/1/2015 9:22 AM, Gedare Bloom wrote:
> P.S. you may like to check out the work that has been done to add GPIO
> interface to raspberry pi, by Andre Marques in last years GSoC. It has
> not been merged, but you can find links to the code through the rtems
> wiki, open projects, improve raspber
P.S. you may like to check out the work that has been done to add GPIO
interface to raspberry pi, by Andre Marques in last years GSoC. It has
not been merged, but you can find links to the code through the rtems
wiki, open projects, improve raspberry pi project page.
Gedare
On Wed, Apr 1, 2015 at
Hugo,
RTEMS does not currently have much infrastructure for device drivers.
There are some efforts underway that may lead to it, but for now,
device drivers normally are written directly within a BSP, so you'd
write the custom code to run your LCD driver directly, and provide
your application with
On 4/1/2015 9:18 AM, Gedare Bloom wrote:
> Would you then subtract 1 from uptime when reporting it? Or would
> users be expected to know that uptime is off-by-1?
I would prefer we subtract one when reporting to the user.
> On Wed, Apr 1, 2015 at 4:07 AM, Alexander Krutwig
> wrote:
>> Hello,
>>
>
Would you then subtract 1 from uptime when reporting it? Or would
users be expected to know that uptime is off-by-1?
On Wed, Apr 1, 2015 at 4:07 AM, Alexander Krutwig
wrote:
> Hello,
>
> during my work with FreeBSD timecounters, I found out that the FreeBSD
> timecounters start with an uptime val
Hi
I was looking into a failure for sp26 and noticed that it is calling
a printf() variant after _Terminate has been called. I am getting
an exception during the __swsetup_r call. I am wondering if
there is an ordering issue:
Program received signal SIGEMT, Emulation trap.
0x0004b216 in __swsetu
Hello all,
I would like to inform you that Premysl Houdek is near to finishing
preparation of complete registers header files for TMS570LS3137.
The register and fields definition are interactively retrieved
with help of some macro from MCU PDF manual files.
We decided to store retrieved data in JS
Hi:
I am a student to work with RTEMS these days.
I like this OS, but I found there's few information about RTEMS, I am really
desired to know how can I add a new driver for it, such as LCD driver or others.
From the official information, there is only some API and function interface,
is there
On 1/04/2015 6:16 pm, Sebastian Huber wrote:
>
> if_dwc: Workaround for missing FDT support
>
I have this ported to RTEMS if you are interested.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hello,
during my work with FreeBSD timecounters, I found out that the FreeBSD
timecounters start with an uptime value of 1 second. Developers of
FreeBSD told me that this is due to problems in the ARP code.
RTEMS uptime is initialized to an uptime value to 0 seconds.
Are there any problems if
50 matches
Mail list logo
