On 07/01/16 02:38, Aun-Ali Zaidi wrote:
From: Tim Cussins
DHCP requests add the hostname option in dhcp_request_req() - this is cool,
except that the dhcp
spec requires that this option has a length >= 1 char.
Excerpt taken from RFC 2132:
3.14. Host Name Option
This option specifi
Hello Aurelio,
for the lm3s6965 you need a special Qemu version, see
https://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/lm3s69xx/README
I tried to integrate the patches in Qemu, but this required more time
than I had.
On 06/01/16 17:40, Aurelio Remonda wrote:
Hello, i am trying use Rtems
From: Tim Cussins
DHCP requests add the hostname option in dhcp_request_req() - this is cool,
except that the dhcp
spec requires that this option has a length >= 1 char.
Excerpt taken from RFC 2132:
3.14. Host Name Option
This option specifies the name of the client. The name may or ma
On 07/01/2016 03:40, Aurelio Remonda wrote:
Hello, i am trying use Rtems tester framework. The goal is to run the
test on qemu for a board with cortex m3 (lpc1768).
As far as i know qemu does not support lpc1768 so i choose Stellaris
lm3s6965 which has a cortex m3 too.
Im not sure i understand t
On Wed, Jan 6, 2016 at 2:53 PM, Amar Takhar wrote:
> On 2016-01-06 14:42 -0600, Joel Sherrill wrote:
> >
> > Ahh.. that would be under Amar's control. :)
>
> Oh, it was a vc email sorry I didn't notice.
>
> I've fixed it now, surprised it took this long for someone to notice. :)
>
> Thanks. I hav
On 2016-01-06 14:42 -0600, Joel Sherrill wrote:
>
> Ahh.. that would be under Amar's control. :)
Oh, it was a vc email sorry I didn't notice.
I've fixed it now, surprised it took this long for someone to notice. :)
Amar.
___
devel mailing list
devel@
On Wed, Jan 6, 2016 at 2:37 PM, Gedare Bloom wrote:
> The problem likely is in the hook on the server that sends the email.
> The git-author info on the commit is correct.
>
>
Ahh.. that would be under Amar's control. :)
> On Wed, Jan 6, 2016 at 3:17 PM, Joel Sherrill wrote:
> >
> >
> > On Wed
The problem likely is in the hook on the server that sends the email.
The git-author info on the commit is correct.
On Wed, Jan 6, 2016 at 3:17 PM, Joel Sherrill wrote:
>
>
> On Wed, Jan 6, 2016 at 8:18 AM, Amar Takhar wrote:
>>
>> On 2016-01-06 08:03 -0600, Joel Sherrill wrote:
>> > Amar, etc.
On Wed, Jan 6, 2016 at 8:18 AM, Amar Takhar wrote:
> On 2016-01-06 08:03 -0600, Joel Sherrill wrote:
> > Amar, etc.
> >
> > I committed this patch from rtbf64c. Where do I need to look for my name
> being
> > spelled incorrectly on this next line? I can't find it this morning.
>
> Either in /.git
Hello, i am trying use Rtems tester framework. The goal is to run the
test on qemu for a board with cortex m3 (lpc1768).
As far as i know qemu does not support lpc1768 so i choose Stellaris
lm3s6965 which has a cortex m3 too.
Im not sure i understand the information given by rtems-tester --list-bs
On Wed, Jan 6, 2016 at 10:13 AM, Gedare Bloom wrote:
> On Wed, Jan 6, 2016 at 8:45 AM, Joel Sherrill wrote:
> >
> >
> > On Tue, Jan 5, 2016 at 7:57 PM, Gedare Bloom wrote:
> >>
> >> The part about testing with a simulator is vague. But you can go ahead
> >> and generate tasks. Create 1 task per
On Wed, Jan 6, 2016 at 8:45 AM, Joel Sherrill wrote:
>
>
> On Tue, Jan 5, 2016 at 7:57 PM, Gedare Bloom wrote:
>>
>> The part about testing with a simulator is vague. But you can go ahead
>> and generate tasks. Create 1 task per architecture that remains, and
>> allow 5 instances for each.
>>
>
>
On 2016-01-06 08:03 -0600, Joel Sherrill wrote:
> Amar, etc.
>
> I committed this patch from rtbf64c. Where do I need to look for my name
> being??
> spelled incorrectly on this next line? I can't find it this morning.
Either in /.git/config or ~/.gitconfig or /etc/password
It checks these in o
Amar, etc.
I committed this patch from rtbf64c. Where do I need to look for my name
being
spelled incorrectly on this next line? I can't find it this morning.
Thanks.
On Wed, Jan 6, 2016 at 7:49 AM, Joel Sherril wrote:
> Module:rtems
> Branch:master
> Commit:c653559e05a7db94f921fa5
On Tue, Jan 5, 2016 at 7:57 PM, Gedare Bloom wrote:
> The part about testing with a simulator is vague. But you can go ahead
> and generate tasks. Create 1 task per architecture that remains, and
> allow 5 instances for each.
>
>
Huh? How about one per BSP Family? If we do it the way you suggest,
15 matches
Mail list logo