I want to focus first on "The One True Way" a BSP is supposed to do things,
automate detecting violations, and fix as much as we can. Start with interrupt
and PCI.. move on to things like does the BSP have reset and is it on the
expected filename?
A by product of this work should be more rules
>
>From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org] on behalf
>of Matt Wette [mwe...@alumni.caltech.edu]
>Sent: Monday, June 03, 2013 5:28 PM
>To: rtems-devel@rtems.org
>Subject: Re: [GSOC] Unified APIs Project
>
>Is there any interest in
Hi Matt,
Protected code (e.g. supervisor mode) is not in the current RTEMS direction.
-Gedare
On Jun 3, 2013 8:29 PM, "Matt Wette" wrote:
> Is there any interest in a "syscall" API that would allow future expansion
> into supporting "protected regions" of code?
>
> On Jun 3, 2013, at 10:15 AM,
Is there any interest in a "syscall" API that would allow future expansion into
supporting "protected regions" of code?
On Jun 3, 2013, at 10:15 AM, Vipul Nayyar wrote:
>
> Hello,
>
> Being accepted into GSOC with RTEMS is very exciting. This has been possible
> due to the constant support of
Hi, all
I'm very glad to be accepted by the GSoC2013. It's my first time to
participate in this program. I will build a CAN simulation environment
based on the QEMU, then if possible I will port a Linux CAN driver - LinCAN
- to RTEMS.
The simulation may base on i386, because this platform is stabl
Dhananjay Balan wrote:
PFA patch to add an exception for distro version calculation for non-LSB
distros.
Applied. Thanks.
Chris
___
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
Peng Fan wrote:
---
rtl-rap.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
Apply. Thanks.
Chris
___
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
Hello,
Being accepted into GSOC with RTEMS is very exciting. This has been possible
due to the constant support of Joel & Cynthia. A special thanks to Gedare for
an in depth criticization of my proposal, which helped me improve it.
I'll be working this summer on the 'Unified APIs' Project. Th
GSoC Students,
TL;DR: submit documentation, join rtems-devel, come to IRC.
Make sure to submit your documentation to Google. By now hopefully the
relevant information has been posted to the GSoC Students' mailing
list.
If you have not yet posted your project summary to rtems-devel please
do so,
>
>> On 05/31/2013 03:42 PM, Ralf Kirchner wrote:
>>> diff --git a/testsuites/fstests/fsdosfsname01/image_bin_le_multibyte.h
>>> b/testsuites/fstests/fsdosfsname01/image_bin_le_multibyte.h
>>> +/*
>>> + * Declarations for C structure representing a disk image
>>> + *
>>> + * WARNING: Automaticall
Hi Joel,
Unfortunately the modifications required for UTF-8 are pretty deep down
in the FAT file system.
Thus I think except of having Iconv and utf8proc available in the RTEMS
source tree respectively in the tool chain there is not much to be
gained for UTF-8 support in other file systems.
And tes
PFA patch to add an exception for distro version calculation for non-LSB
distros.
--
Regards,
Dhananjay M Balan,
0001-distro_ver-fails-on-Non-LSB-distros.patch
Description: Binary data
___
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtem
On 06/03/2013 02:14 AM, Chris Johns wrote:
+if (name_size> 0) {
+ /*
+ * Finally convert from UTF-8 to codepage
+ */
+ name_size_tmp = sizeof ( name_to_format_buf );
+ eno = (*converter->handler->utf8_to_codepage) (
I have not been over all the code to check so I
On 06/02/2013 12:54 PM, Ralf Corsepius wrote:
On 05/31/2013 03:42 PM, Ralf Kirchner wrote:
diff --git a/testsuites/fstests/fsdosfsname01/image_bin_le_multibyte.h
b/testsuites/fstests/fsdosfsname01/image_bin_le_multibyte.h
new file mode 100644
index 000..bb0e565
--- /dev/null
+++ b/testsuites
14 matches
Mail list logo