On 7/08/2015 3:01 pm, emanuel stiebler wrote:
> should it still work, didn't see anything about it for a while on this
> list, tried yesterday, and the source-builder failed in newlib:
Can you please try '--jobs=none' on the RSB command line ?
I wonder if this is a GNU make and cgywin dll issue.
I have thought of creating BSP for x86_64 but unfortunately I was busy
in my exam and class hectic schedule.Shall I create or work on BSP
for X86_64 ?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hi all,
should it still work, didn't see anything about it for a while on this
list, tried yesterday, and the source-builder failed in newlib:
microblaze-rtems4.11-ar rc ../libc.a *.o
microblaze-rtems4.11-ranlib libc.a
rm -rf tmp
make[8]: Leaving directory
'/cygdrive/d/_home/emu/RTEMS.Work/rte
Hi Pisa Pavel,
On Aug 03, 2015, at 11:43 AM, Pavel Pisa wrote:
Hello Qiao Yang,
On Monday 03 of August 2015 22:06:31 QIAO YANG wrote:
On Aug 03, 2015, at 08:34 AM, QIAO YANG wrote:
> On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
>> On 29/07/2015 8:04 pm, Sebastian Huber wrote:
>>> A cus
These macroses are placed here
https://github.com/gtament/rtems-libbsd/blob/cf3f0fcafef3bcb9b0ec80d8c57e1304689ebace/rtemsbsd/include/machine/rtems-bsd-sysinit.h
And of course I added proper lines to specific testsuites, like
init01. And IRC, without this macro driver just won't be linked
2015-08-
On 8/6/2015 4:29 PM, Yurii Shevtsov wrote:
Isn't this line enough?
SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus)
I was looking in nexus-devices.h since that is BSP specific.
I wasn't expecting a generic macro.
But where is that referenced? That is a macro that somewhere
should be referenci
Isn't this line enough?
SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus)
2015-08-07 0:23 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 4:16 PM, Yurii Shevtsov wrote:
>>
>> 2015-08-07 0:08 GMT+03:00 Joel Sherrill :
>>>
>>>
>>>
>>> On August 6, 2015 3:57:40 PM CDT, Yurii Shevtsov
>>> wrote:
On 8/6/2015 4:16 PM, Yurii Shevtsov wrote:
2015-08-07 0:08 GMT+03:00 Joel Sherrill :
On August 6, 2015 3:57:40 PM CDT, Yurii Shevtsov wrote:
What do you mean by "getting pulled"?
As I understood things, you had a linked executable but an empty section. Just
curious if your devices were
2015-08-07 0:08 GMT+03:00 Joel Sherrill :
>
>
> On August 6, 2015 3:57:40 PM CDT, Yurii Shevtsov wrote:
>>What do you mean by "getting pulled"?
>
>
> As I understood things, you had a linked executable but an empty section.
> Just curious if your devices were showing up at all.
Yes, exactly. If
On August 6, 2015 3:57:40 PM CDT, Yurii Shevtsov wrote:
>What do you mean by "getting pulled"?
As I understood things, you had a linked executable but an empty section. Just
curious if your devices were showing up at all.
>2015-08-06 23:48 GMT+03:00 Joel Sherrill :
>>
>>
>> On 8/6/2015 3:42
What do you mean by "getting pulled"?
2015-08-06 23:48 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 3:42 PM, Yurii Shevtsov wrote:
>>
>> 2015-08-06 23:36 GMT+03:00 Joel Sherrill :
>>>
>>>
>>>
>>> On 8/6/2015 3:22 PM, Yurii Shevtsov wrote:
Ping! Any news?
>>>
>>>
>>>
>>> The people wi
On 8/6/2015 3:42 PM, Yurii Shevtsov wrote:
2015-08-06 23:36 GMT+03:00 Joel Sherrill :
On 8/6/2015 3:22 PM, Yurii Shevtsov wrote:
Ping! Any news?
The people with experience with the libbsd code is quite small. :(
2015-08-05 18:29 GMT+03:00 Yurii Shevtsov :
The problem is that rtemsr
2015-08-06 23:36 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 3:22 PM, Yurii Shevtsov wrote:
>>
>> Ping! Any news?
>
>
> The people with experience with the libbsd code is quite small. :(
>
>>
>> 2015-08-05 18:29 GMT+03:00 Yurii Shevtsov :
>>>
>>> The problem is that rtemsroset.bsd.nexus.content doe
On 8/6/2015 3:22 PM, Yurii Shevtsov wrote:
Ping! Any news?
The people with experience with the libbsd code is quite small. :(
2015-08-05 18:29 GMT+03:00 Yurii Shevtsov :
The problem is that rtemsroset.bsd.nexus.content doesn't exist in
final elf. If I change driver's name in RTEMS_BSD_DEF
Ping! Any news?
2015-08-05 18:29 GMT+03:00 Yurii Shevtsov :
> The problem is that rtemsroset.bsd.nexus.content doesn't exist in
> final elf. If I change driver's name in RTEMS_BSD_DEFINE_NEXUS_DEVICE
> macro, linker will throw an error
> (.rtemsroset.bsd.nexus.content+0x10): undefined reference to
Surrender is executed with isr disabled around it, so no.
On Wed, Aug 5, 2015 at 8:33 PM, Saurabh Gadia wrote:
> For surrender we don't disable thread dispatching for uniprocessor. So is
> that the thread can be interleaved?
>
> Thanks,
>
> Saurabh Gadia
>
> On Wed, Aug 5, 2015 at 9:01 AM, Gedare
16 matches
Mail list logo
