Hello,
> I am sorry for the subject line, but I am so confused right now I couldn't
> think of with a better one.
Not anymore. Do you know how when you want to ask a perfect question, you find
the answer yourself?
Below is an excerpt from the make log. First line is obviously an invocation of
On Tue, Dec 23, 2014 at 1:53 PM, Dominik Táborský wrote:
> Hello,
>
>> I am sorry for the subject line, but I am so confused right now I couldn't
>> think of with a better one.
> Not anymore. Do you know how when you want to ask a perfect question, you
> find the answer yourself?
>
> Below is an
Sebastian,
Makes sense. I think I understand the idea a little better now, we are
using the linux uapi i2c API, but not the actual i2c bus and device driver
implementations from linux, right?
For the Pi ( and others like the Beagleboard ) we need to come up with an
i2c BSP bus driver ( similar to
From: Daniel Ramirez
---
c/src/lib/libbsp/sparc/shared/spw/grspw.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/c/src/lib/libbsp/sparc/shared/spw/grspw.c
b/c/src/lib/libbsp/sparc/shared/spw/grspw.c
index b311500..d3eb9b9 100644
--- a/c/src/lib/libbsp/sparc/
This is a patch proposed for PR 1761
[https://devel.rtems.org/ticket/1761]. Comment if OK or not.
On Tue, Dec 23, 2014 at 10:05 PM, Gedare Bloom wrote:
> From: Daniel Ramirez
>
> ---
> c/src/lib/libbsp/sparc/shared/spw/grspw.c | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions