Hello GSoC and SOCIS students (mentors, and interested parties),
We'll have our first "all hands meeting" for GSoC students tomorrow at
11:00 AM EST (UTC-4). Since the coding period has not officially
started, this will be more of a meet-and-greet than anything else.
I look forward to checking in
On 5/18/2015 10:17 AM, Yurii Shevtsov wrote:
> commit 66ec94a3fc3c41470f90b7d20913ea1fafc019a9
> make install prints this http://paste.kolibrios.org/show/394/
> I copied _timeval.h (found it somewhere in rtems folder) to
> rtemsbsd/include/rtems/bsd/sys/. It seemed like it helped but I got
> new
commit 66ec94a3fc3c41470f90b7d20913ea1fafc019a9
make install prints this http://paste.kolibrios.org/show/394/
I copied _timeval.h (found it somewhere in rtems folder) to
rtemsbsd/include/rtems/bsd/sys/. It seemed like it helped but I got
new errors http://paste.kolibrios.org/show/395/
Result doesn'
On Fri, May 15, 2015 at 7:41 AM, Sebastian Huber
wrote:
> From: Alexander Krutwig
>
> Replace timestamp implementation with FreeBSD bintime and timecounters.
>
> New test sptests/sptimecounter02.
>
> Update #2271.
> ---
Very nice work. Did you test with the old networking stack? Do you all
plan t
On Fri, May 15, 2015 at 7:47 AM, Sebastian Huber
wrote:
> From: Alexander Krutwig
>
> Update #2271.
> ---
I only looked at a few of these, they are fairly mechanical. Is there
a status sheet somewhere that indicates which BSPs have which clock
support? This would be useful to have, probably in a
On Mon, May 18, 2015 at 3:50 AM, Sebastian Huber
wrote:
>
>
> On 17/05/15 15:22, Gedare Bloom wrote:
>>
>> On Fri, May 15, 2015 at 7:47 AM, Sebastian Huber
>> wrote:
>>>
>>> From: Alexander Krutwig
>>>
>>> FreeBSD assumes that u_int is a 32-bit integer type. This is wrong for
>>> some 16-bit ta
On Mon, May 18, 2015 at 3:36 AM, Sebastian Huber
wrote:
>
>
> On 17/05/15 04:21, Gedare Bloom wrote:
>>
>> Not really related, but what is the "rule" for when we should use
>> RTEMS_INLINE_ROUTINE versus being able to say "static inline"?
>
>
> This file already used "static inline" and this is fi
On Mon, May 18, 2015 at 3:20 AM, Sebastian Huber
wrote:
>
>
> On 17/05/15 14:14, Gedare Bloom wrote:
>>
>> On Sun, May 17, 2015 at 7:04 AM, Gedare Bloom wrote:
>>>
>>> On Fri, May 15, 2015 at 7:41 AM, Sebastian Huber
>>> wrote:
/**
- * @brief Gets a pointer to the "first" threa
On 17/05/15 15:22, Gedare Bloom wrote:
On Fri, May 15, 2015 at 7:47 AM, Sebastian Huber
wrote:
From: Alexander Krutwig
FreeBSD assumes that u_int is a 32-bit integer type. This is wrong for
some 16-bit targets supported by RTEMS.
Update #2271.
---
Can we undef u_int and redefine it to ui
On 18/05/15 09:46, Sebastian Huber wrote:
On 17/05/15 15:19, Gedare Bloom wrote:
+ * $FreeBSD$
>+ */
>+
I assume the code in this commit is all directly imported from some
FreeBSD so I'm not going to review it too closely, but I do have one
question. How are we tracking the upstream version
On 17/05/15 15:19, Gedare Bloom wrote:
+ * $FreeBSD$
>+ */
>+
I assume the code in this commit is all directly imported from some
FreeBSD so I'm not going to review it too closely, but I do have one
question. How are we tracking the upstream version? Should we include
the populated $FreeBSD$ t
On 17/05/15 04:21, Gedare Bloom wrote:
Not really related, but what is the "rule" for when we should use
RTEMS_INLINE_ROUTINE versus being able to say "static inline"?
This file already used "static inline" and this is fine, since it
requires at least C11 or C++11.
We should eliminate RTEM
On 17/05/15 13:23, Gedare Bloom wrote:
On Fri, May 15, 2015 at 7:41 AM, Sebastian Huber
wrote:
Move thread queue discipline specific operations into
Thread_queue_Operations. Use a separate node in the thread control
block for the thread queue to make it independent of the scheduler data
stru
On 17/05/15 14:14, Gedare Bloom wrote:
On Sun, May 17, 2015 at 7:04 AM, Gedare Bloom wrote:
On Fri, May 15, 2015 at 7:41 AM, Sebastian Huber
wrote:
/**
- * @brief Gets a pointer to the "first" thread on the_thread_queue.
+ * @brief Returns the first thread on the thread queue if it exist
On 17/05/15 04:36, Gedare Bloom wrote:
-/* FIXME: This locking approach for SMP is improvable! */
+ ++watchdogs->generation;
We should probably try to file a ticket associated with any FIXME type
comments, and refer to it in the FIXME too.
Yes, in this case it is:
https://devel.rtems.org/ti
On 16/05/15 20:53, Afshin Jamaali (Arian) wrote:
Hi Sebastian,
Sorry, it seems a problem exists. The link
"http://git.rtems.org/rtems-libbsd.git/"; says:
"No repositories found"
Sorry, the right link is:
https://git.rtems.org/rtems-libbsd
Best Regards,
Afshin Jamaali
-Original Message
16 matches
Mail list logo