You can reach the person managing the list at
> devel-ow...@rtems.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
>
> Today's Topics:
>
>1. RTEMS 5.0 error occurred in
Hello everyone,
I am new to RTEMS, and was trying to build a new bsp for RTEMS 5 for tms570
family of boards.
While doing the make, i come across this error.
I had done --enable-tests in the previous command.
Can anyone help me with this? Output from terminal is shown below.
( represent so
Hi all
I read the bsp_specs files contained in some bsps, which reside in libbsp/arm,
libbsp/bfin and libbsp/m32r
*endfile:
%{!qrtems: *(old_endfiles)} %{qrtems: crtend.o%s crtn.o%s }
^
I think it should be %.
I wrote a specs file and tested using gcc 4.8.2.
__
Hi, everybody
I am trying to write driver for an I2C eeprom, m24c08.
The problem is that the 7bit eeprom i2c slave address will vary according to
address I am trying to access.
7bit i2c address consist of 4bit device type, 1bit eeprom pin status, 2bit the
MSB of the address of eeprom
but i
yes , you are right. I should be more careful
thank you very much
At 2014-12-10 15:45:12, "Sebastian Huber"
wrote:
>The is no bug, since we have
>
> busses[i].name = nmcpy;
> nmcpy = 0;
>
>and a free(NULL) is a nop.
>
>On 10/12/14
cpukit/libi2c/libi2c.c
rtems_libi2c_register_bus
this function saves the specified i2c bus name in a malloced space,
but in the end of this function, the malloced space is freed.
And in rtems_libi2c_register_drv , busses[busno].name is used to construct
the specific device file.
c/src/libchip/serial/serial.h
typedef struct _console_fns {
bool(*deviceProbe)(int minor);
int (*deviceFirstOpen)(int major, int minor, void *arg);
int (*deviceLastClose)(int major, int minor, void *arg);
int (*deviceRead)(int minor);
ssize_t (*deviceWrite)(int minor
