Cillian ,
Thanks for the detailed answers , I will start the reading and will write a
first draft of the proposal in the way you mentioned and Will share the
link here
Thank you,
Vijay k.
On 4 Mar 2018 4:22 p.m., "Cillian O'Donnell" wrote:
On 3 March 2018 at 22:18, Vijay
On 9 Mar 2018 10:15 p.m., "Vijay Kumar Banerjee"
wrote:
On 9 Mar 2018 3:34 a.m., "Joel Sherrill" wrote:
On Sun, Mar 4, 2018 at 4:52 AM, Cillian O'Donnell
wrote:
>
>
> On 3 March 2018 at 22:18, Vijay Kumar Banerjee
> wrote:
>
>> Hello sir,
On 15 March 2018 at 02:43, Cillian O'Donnell wrote:
>
>
> On 14 March 2018 at 19:51, Cillian O'Donnell
> wrote:
>
>>
>>
>> On 14 March 2018 at 18:26, Vijay Kumar Banerjee > > wrote:
>>
>>> I'm still getting the Covoar not foun
14, 2018 at 4:13 PM, Cillian O'Donnell <
>>> cpodonne...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On 14 March 2018 at 19:51, Cillian O'Donnell
>>>> wrote:
>>>>
>>>>>
>>>>>
>
hello ,
as told by Joel , I started this thread to further discuss the coverage
analysis toolset .
Current status is , I'm trying to builld and run rtems-test from the
coverage-merge branch of the previous GSoC student Cillian .
https://github.com/cillianodonnell/rtems-tools/tree/coverage-merge
I have attached the output of the ls of that directory
-- vijay
On 15 March 2018 at 15:52, Cillian O'Donnell wrote:
>
>
> On 15 March 2018 at 03:58, Vijay Kumar Banerjee
> wrote:
>
>>
>> hello ,
>>
>> as told by Joel , I started this thread to furt
s-tools/tester/rtems-test --rtems-bsp=leon3-qemu
> --log=log-leon3.log --rtems-tools=$HOME/development/rtems/5
> --rtems-builddir=$HOME/development/rtems/kernel/leon3
> sparc-rtems5/c/leon3/testsuites/samples
>
> Do the tests run?
>
> On 15 March 2018 at 10:53, Vijay Kumar Ba
wrote:
>
>
> On 15 March 2018 at 12:26, Vijay Kumar Banerjee
> wrote:
>
>> It runs with a bunch of errors . I have attached the log file
>>
>
> Ok, I'm guessing you didn't set up Couverture-Qemu (special version of
> qemu designed for generating extra tra
at change into couverture-build
> branch and try it again. I'm not seeing any automake stuff here, so just
> check that and let me know.
>
> On 16 March 2018 at 14:59, Vijay Kumar Banerjee
> wrote:
>
>> building couverture-qemu from rtems-source-builder (
>> https://github.
u
>
>
> On 16 March 2018 at 16:48, Vijay Kumar Banerjee
> wrote:
>
>> still the same error
>>
>> -- vijay
>>
>> On 16 March 2018 at 21:39, Cillian O'Donnell
>> wrote:
>>
>>> Just checked and the build was failing because one of
the same error comes when I try to build qemu from the
RTEMS/rtems-source-builder as well
is the issue coming from my system ? I'm using fedora 27 64bit
On 17 Mar 2018 12:39 a.m., "Vijay Kumar Banerjee"
wrote:
> yes , the same thing happens
>
> On 17 Mar 2018 12:13
x to $PATH in .bashrc as well like before.
>
> export PATH=$HOME/qemu/install/bin:$PATH
>
> Then run rtem-test and see what happens
>
>
> On 16 March 2018 at 19:13, Vijay Kumar Banerjee
> wrote:
>
>> the same error comes when I try to build qemu from the
>>
hello ,
As suggested by Gedare , I have started this thread on the build error that
I'm getting .
I'm getting automake-1.12.6-x86_64-linux-gnu-1 building error while trying
to build autotools from rsb
I'm using fedora 27 64bit .
P.S: the error report is attached
-- vijay
RTEMS Tools Project -
It worked !
It's great to see it running ! I have attached the result .
-- vijay
On 18 March 2018 at 02:31, Cillian O'Donnell wrote:
>
>
> On 17 March 2018 at 20:08, Vijay Kumar Banerjee
> wrote:
>
>> yes it prints hello world
>>
>
> Alright I
s been updated to a recent enough version of the upstream
> qemu, then it is likely to fail the same way.
>
> --joel
>
> On Mar 17, 2018 9:46 AM, "Vijay Kumar Banerjee"
> wrote:
>
>> I built it manually
>>
>> the environment variable PATH looks lik
Joel and other mentors' review on my draft proposal,
so that I can also work on it and make any changes if needed.
Thanks .
-- vijay
On 18 March 2018 at 14:17, Cillian O'Donnell wrote:
>
>
> On 18 March 2018 at 06:47, Vijay Kumar Banerjee
> wrote:
>
>> It worke
parse.
> >
>
> I don't think this is the solution, because the failure happens while
> trying to build the autotools.
>
> > On Mar 17, 2018 11:34 AM, "Vijay Kumar Banerjee" <
> vijaykumar9...@gmail.com>
> > wrote:
> >>
> >> hello
-- vijay
On 18 March 2018 at 16:13, Gedare Bloom wrote:
> On Sun, Mar 18, 2018 at 6:41 AM, Gedare Bloom wrote:
> > Vijay,
> >
> > On Sun, Mar 18, 2018 at 6:36 AM, Vijay Kumar Banerjee
> > wrote:
> >>
> >> I have set the PATH like this
> >
I have tried
perl-5.24.3
perl-5.22.4
perl-5.20.3
still getting the same error, it be coming from something else
-- vijay
On 18 March 2018 at 16:15, Vijay Kumar Banerjee
wrote:
>
>
> -- vijay
>
> On 18 March 2018 at 16:13, Gedare Bloom wrote:
>
>> On Sun, Mar 18, 2018
, Vijay Kumar Banerjee
wrote:
> Thanks Cillian :)
>
> It's great to see it running , I'll do some background reading about RSB,
> and RTEMS-Tools along with the covoar code . And also work on my python
> skills.
>
> to try rtems-test on a bsp that runs gdb , I tr
> Thank you ,
>> -- vijay
>>
>> P.S : the previous version is in parentheses , I will remove them after
>> you review the changes .
>>
>> On 18 March 2018 at 16:05, Vijay Kumar Banerjee > > wrote:
>>
>>> Thanks Cillian :)
>>>
It's the last day before the deadline!
Please provide a final review of the proposal before submitting.
Thanks
-- vijay
On 24 March 2018 at 21:37, Vijay Kumar Banerjee
wrote:
> hello mentors and other developers of the community , there are only three
> days remaining to the GS
upload it.
>
> --joel
>
> On Mar 25, 2018 2:37 PM, "Vijay Kumar Banerjee"
> wrote:
>
>> It's the last day before the deadline!
>> Please provide a final review of the proposal before submitting.
>>
>> Thanks
>>
>> -- vijay
>
work. It isn't discussed as work during the
> summer.It would be nice to get gcov correctness done earlier
> because that might be the best way to nice reports. For
> example, running lcov on the .gcov files produced by covoar
> might be an option.
>
> --joel
>
>
> O
Hello ,
I'm currently going through the coverage code , Can you please help me
understand what are the specific changes that are needed for the coverage
to be running again?
thanks
-- vijay
On 26 March 2018 at 09:30, Vijay Kumar Banerjee
wrote:
> 1. Yes , I plan to work on identif
Hi Kinsey,
The patches look great. Thanks for the cleanup.
Best regards,
Vijay
On Tue, Nov 1, 2022 at 1:51 PM Kinsey Moore wrote:
>
> ---
> lwip.py | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/lwip.py b/lwip.py
> index c11ed1f..e6580eb 100644
> --- a/lwip.py
> +++ b/lwip.py
> @@
Thanks for the patch. The v2 looks good. Tested the build with beagleboneblack
On Wed, Nov 9, 2022 at 9:33 PM Kinsey Moore wrote:
>
> This moves all BSP-specific information out of lwip.py and into JSON
> descriptions of the files required to compile the drivers for each BSP.
>
> Note that file-i
Looks good to me.
Do we need copyright statements for these files?
On Wed, Nov 9, 2022 at 9:49 PM Kinsey Moore wrote:
>
> ---
> rtemslwip/bsd_compat_include/arpa/nameser.h | 1 +
> rtemslwip/bsd_compat_include/machine/rtems-bsd-kernel-space.h | 1 +
> rtemslwip/bsd_compat_incl
Looks great. It only affects the Zynqmp.
Thanks.
On Thu, Nov 10, 2022 at 2:23 PM Kinsey Moore wrote:
>
> This adds support for the CFC-400X BSP including an option to select
> SGMII instead of the default RGMII PHY interface and adds a way for
> ZynqMP BSPs to provide additional configuration vi
This is great! This makes it more adaptable with different BSPS. Also,
thanks for the documentation. :)
On Fri, Nov 11, 2022 at 3:03 PM Kinsey Moore wrote:
>
> This adds a basic configuration mechanism in config.ini to control which
> BSPs are enabled and to alter lwIP's define/macro-based config
RTEMS commit 2c07f24af210c4738fbe6f75a53c58fbd80fb658 removed the ambapp_plb
global variable
---
bsps/sparc/leon3/net/leon_greth.c| 3 ++-
bsps/sparc/leon3/net/leon_open_eth.c | 5 +++--
bsps/sparc/leon3/net/leon_smc9.c | 11 ++-
3 files changed, 11 insertions(+), 8 deletions(-)
Hi Chris,
The patch looks great. Thanks.
On Thu, Apr 13, 2023 at 11:21 PM wrote:
>
> From: Chris Johns
>
> ---
> include/rtems/rtems-net-legacy.h.in | 42 +
> netlegacy.py| 35 +---
> rtems_waf |
Hi Chris,
The updates look good to me. Thanks.
On Fri, Apr 14, 2023 at 7:10 PM wrote:
>
> From: Chris Johns
>
> - Tools picks up the stm32h7-stlink to handle SIGTRAP fix.
>
> - RTEMS picks up the motorola_powerpc updates including the mvme2700
> BSP and Makefile.inc fixes for building EPICS.
Hi Kinsey,
Thank you for sorting this out. I will merge it on Monday if no one objects.
Best regards,
Vijay
On Thu, Apr 14, 2022 at 11:33 AM Kinsey Moore wrote:
>
> Moving forward, each origin directory should have its own top-level
> COPYING.origin file to describe its license as well as a ORI
On Sat, Apr 16, 2022 at 10:48 AM Pavel Pisa wrote:
>
> Hello Joel,
>
> On Saturday 16 of April 2022 17:26:02 Joel Sherrill wrote:
> > On Sat, Apr 16, 2022, 9:54 AM Pavel Pisa wrote:
> > > On Thursday 14 of April 2022 22:08:00 Vijay Kumar Banerjee wrote:
> > &g
On Tue, May 31, 2022 at 3:13 PM Kinsey Moore wrote:
>
> On 5/12/2022 16:30, Vijay Kumar Banerjee wrote:
> > On Sat, Apr 16, 2022 at 10:48 AM Pavel Pisa wrote:
> >> Hello Joel,
> >>
> >> On Saturday 16 of April 2022 17:26:02 Joel Sherrill wrote:
> &g
on the included licenses. I believe that the approach in
that direction will also mature as we keep bringing new patches and
involve the wider community.
Thank you to everyone for providing valuable feedback.
Best regards,
Vijay
On Tue, May 31, 2022 at 8:04 PM Vijay Kumar Banerjee wrote:
>
> On
Hi Pavel,
On Thu, Jun 2, 2022 at 12:09 AM Pavel Pisa wrote:
>
> Dear Vijay,
>
> On Thursday 02 of June 2022 05:56:56 Vijay Kumar Banerjee wrote:
> > I have pushed this patch and I would like to add a note regarding that.
>
> thanks for the work and time.
>
No problem.
Congratulations, Gedare and Hesham!
I had the honor and privilege of working with both of you, and your
knowledge and passion have been a true inspiration to me.
Best,
Vijay
On Tue, Jun 28, 2022 at 8:23 AM Joel Sherrill wrote:
>
> Hi
>
> I'd like to congratulate two RTEMS core developers on rec
Hi Kinsey,
This patchset is looking great. Thank you!
Unfortunately, I won't be able to test the BBB right away but I see
that most patches are probably from the devel branch of lwip, which I
tested before. I am going to wait till Tuesday, to get any comments or
objections from others. If no chang
On Fri, Jul 1, 2022 at 5:49 PM Vijay Kumar Banerjee wrote:
>
> Hi Kinsey,
>
> This patchset is looking great. Thank you!
> Unfortunately, I won't be able to test the BBB right away but I see
> that most patches are probably from the devel branch of lwip, which I
correcti
On Fri, Jul 1, 2022 at 8:19 PM Kinsey Moore wrote:
>
> On 7/1/2022 18:50, Vijay Kumar Banerjee wrote:
>
> On Fri, Jul 1, 2022 at 5:49 PM Vijay Kumar Banerjee wrote:
>
> Hi Kinsey,
>
> This patchset is looking great. Thank you!
> Unfortunately, I won't be able to t
Hi,
On Fri, Jul 1, 2022 at 9:20 PM Vijay Kumar Banerjee wrote:
>
> On Fri, Jul 1, 2022 at 8:19 PM Kinsey Moore wrote:
> >
> > On 7/1/2022 18:50, Vijay Kumar Banerjee wrote:
> >
> > On Fri, Jul 1, 2022 at 5:49 PM Vijay Kumar Banerjee wrote:
> >
> > H
Thank you everyone for supporting the move!
On Tue, Jul 19, 2022 at 3:24 PM Chris Johns wrote:
>
> Thanks to everyone for this effort.
>
> Vijay, if you need a hand doing this please ping me on discord.
I have moved it to the top level and added the hooks using the doc I
wrote last time:
https://
---
README | 18 ++
1 file changed, 18 insertions(+)
diff --git a/README b/README
index 91e42ae..99800bf 100644
--- a/README
+++ b/README
@@ -12,3 +12,21 @@ The sources presented here originate in one of several
locations described by
the ORIGIN.* files and whose license is desc
here is that option is not
used. using the BSP argument only builds the mentioned bsps.
Best regards,
Vijay
> On 7/21/2022 14:16, Vijay Kumar Banerjee wrote:
> > ---
> > README | 18 ++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/READ
I will push this patch. The main intention of this patch is to test
the new top-level repo, but it also provides some essential build
instructions which will certainly be handy.
On Thu, Jul 21, 2022 at 2:05 PM Vijay Kumar Banerjee wrote:
>
> Hi Kinsey,
>
> thanks for the review
>
Patch pushed. The repository is working, and I see the commit email in vc.
Thanks,
Vijay
On Thu, Jul 21, 2022 at 2:06 PM Vijay Kumar Banerjee wrote:
>
> I will push this patch. The main intention of this patch is to test
> the new top-level repo, but it also provides some essent
Hello everyone!
I have been active on the project and had offlist discussions about it
with the mentors. To update the devel about the ongoing work I'm
writing this status report and planning to write such status reports
regularly to devel as most of the discussions are happening offlist
with the
On Wed, May 15, 2019 at 11:36 PM Christian Mauderer
wrote:
> Hello Vijay,
>
> >
> > My forked repository for the rtems-libbsd can be found here
> > https://github.com/thelunatic/rtems-libbsd
> > All my work so far is in three branches in my forked repo.
> > The am335x_lcd branch contains the comm
On Fri, May 17, 2019 at 1:05 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 20/03/2019 13:16, Sebastian Huber wrote:
> > Hello,
> >
> > the RTEMS project has a covoar tool:
> >
> > https://git.rtems.org/rtems-tools/tree/tester/covoar
> >
> > I have seen some reports generated
On Fri, May 17, 2019, 4:50 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 17/05/2019 10:49, Vijay Kumar Banerjee wrote:
> > covoar -S
> >
> /home/lunatic/development/rtems/rtems-tools/tester/rtems/testing/coverage/leon3-sis-symbols.ini
>
> >
---
CONTRIBUTING.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 78be5ca6..f2e5da21 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -181,6 +181,9 @@ original FreeBSD code.
`python ./userspace-header-gen.py
build/arm-rtems4.12-xilinx_zynq_
---
rtemstoolkit/path.py | 29 -
tester/rt/coverage.py | 4 ++--
2 files changed, 30 insertions(+), 3 deletions(-)
diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py
index 2b569ae..9051bb5 100644
--- a/rtemstoolkit/path.py
+++ b/rtemstoolkit/path.py
@@ -157,6 +
---
rtemstoolkit/path.py | 29 -
tester/rt/coverage.py | 4 ++--
2 files changed, 30 insertions(+), 3 deletions(-)
diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py
index 2b569ae..0044c7b 100644
--- a/rtemstoolkit/path.py
+++ b/rtemstoolkit/path.py
@@ -157,6 +
---
rtemstoolkit/path.py | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py
index 0044c7b..5cf6157 100644
--- a/rtemstoolkit/path.py
+++ b/rtemstoolkit/path.py
@@ -126,17 +126,17 @@ def mkdir(path):
os.maked
On Mon, May 27, 2019 at 1:24 PM Nils Hölscher wrote:
> Hi,
>
> I tried to rout the PRUs pins via device tree overlay this week.
> Sadly I wasn't able to produce results on linux with this method.
> Please check my blog post concerning this issue.
>
> https://nilshoel.home.blog/2019/05/27/setting-
On Mon, May 27, 2019 at 4:00 PM Nils Hölscher wrote:
> Hi Vijay,
>
> On Mon, 27 May 2019 at 12:15, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>>
>> On Mon, May 27, 2019 at 1:24 PM Nils Hölscher wrote:
>>
>>&g
Hello,
The project has progressed and I'm giving a status report of whatever
has been done since the last update.
I was working on the i2c-adaptation layer that would work on top of the
RTEMS application layer and will connect it to the FreeBSD API. The
current status is that the i2c-adaptation l
Hello everyone,
The patch set adds the iicbus drivers to the libbsd.
- The first two patches add the iicbus drivers to libbsd.
- The third path adds a generic rtems i2c adaptation driver to the libbsd. This
will enable the libbsd applications to use the rtems-i2c drivers. This
adaptation lay
---
freebsd/sys/dev/iicbus/iic.c| 506 ++
freebsd/sys/dev/iicbus/iic.h| 72
freebsd/sys/dev/iicbus/iicbus.c | 378
freebsd/sys/dev/iicbus/iicbus.h | 83 +
freebsd/sys/dev/iicbus/iiconf.c | 527 +
b/rtemsbsd/i2c/rtems-i2c.c
new file mode 100644
index ..5189e5fe
--- /dev/null
+++ b/rtemsbsd/i2c/rtems-i2c.c
@@ -0,0 +1,218 @@
+/*
+ * Copyright (c) 2019 Vijay Kumar Banerjee .
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modificatio
_shell_cmd_t rtems_shell_I2C_Command;
+
extern rtems_shell_cmd_t rtems_shell_PING_Command;
extern rtems_shell_cmd_t rtems_shell_PING6_Command;
diff --git a/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
b/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
new file mode 100644
index ..2e1da406
--- /dev/n
---
freebsd/usr.sbin/i2c/i2c.c | 733 +
1 file changed, 733 insertions(+)
create mode 100644 freebsd/usr.sbin/i2c/i2c.c
diff --git a/freebsd/usr.sbin/i2c/i2c.c b/freebsd/usr.sbin/i2c/i2c.c
new file mode 100644
index ..084682a1
--- /dev/null
+++ b/freeb
---
Makefile.todo | 11 ++
buildset/default.ini | 1 +
libbsd.py | 35
rtemsbsd/include/bsp/nexus-devices.h | 4 +
.../machine/rtems-bsd-kernel-namespace.h | 33
rtemsbsd/inc
---
freebsd/usr.sbin/i2c/i2c.c | 733 +
1 file changed, 733 insertions(+)
create mode 100644 freebsd/usr.sbin/i2c/i2c.c
diff --git a/freebsd/usr.sbin/i2c/i2c.c b/freebsd/usr.sbin/i2c/i2c.c
new file mode 100644
index ..084682a1
--- /dev/null
+++ b/freeb
_shell_cmd_t rtems_shell_I2C_Command;
+
extern rtems_shell_cmd_t rtems_shell_PING_Command;
extern rtems_shell_cmd_t rtems_shell_PING6_Command;
diff --git a/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
b/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
new file mode 100644
index ..2e1da406
--- /dev/n
---
freebsd/sys/dev/iicbus/iic.c| 506 ++
freebsd/sys/dev/iicbus/iic.h| 72
freebsd/sys/dev/iicbus/iicbus.c | 378
freebsd/sys/dev/iicbus/iicbus.h | 83 +
freebsd/sys/dev/iicbus/iiconf.c | 527 +
-git a/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
b/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
new file mode 100644
index ..61881e74
--- /dev/null
+++ b/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
@@ -0,0 +1,215 @@
+/*
+ * Copyright (c) 2019 Vijay Kumar Banerjee .
+ * All rights reserved.
+ *
+ * Redistributio
---
Makefile.todo | 11 ++
buildset/default.ini | 1 +
libbsd.py | 35
rtemsbsd/include/bsp/nexus-devices.h | 4 +
.../machine/rtems-bsd-kernel-namespace.h | 29 +++
rtemsbsd/incl
---
user/bsps/bsps-arm.rst | 68 +-
1 file changed, 67 insertions(+), 1 deletion(-)
diff --git a/user/bsps/bsps-arm.rst b/user/bsps/bsps-arm.rst
index eb972c6..290a6fc 100644
--- a/user/bsps/bsps-arm.rst
+++ b/user/bsps/bsps-arm.rst
@@ -93,7 +93,73 @@ TODO.
---
user/bsps/bsps-arm.rst | 69 +-
1 file changed, 68 insertions(+), 1 deletion(-)
diff --git a/user/bsps/bsps-arm.rst b/user/bsps/bsps-arm.rst
index eb972c6..e6826cd 100644
--- a/user/bsps/bsps-arm.rst
+++ b/user/bsps/bsps-arm.rst
@@ -93,7 +93,74 @@ TODO.
Hello Chris,
I'm getting the following error in python3.7:
===
rtems-tools $>./misc/rtems-boot-image -b u-boot-beaglebone -o .
$HOME/myimage
RTEMS Tools - Boot Image, 5 (881f7419784e modified)
Traceback (most recent call last):
File "./misc/tools/cmd-boot-image.py", line 41, in
boot.run(sys
On Mon, Jun 10, 2019, 6:13 PM Christian Mauderer wrote:
> On 09/06/2019 16:57, Vijay Kumar Banerjee wrote:
> > ---
> > user/bsps/bsps-arm.rst | 69 +-
> > 1 file changed, 68 insertions(+), 1 deletion(-)
> >
> > diff --gi
On Sat, Jun 8, 2019 at 6:20 PM Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
> ---
> Makefile.todo | 11 ++
> buildset/default.ini | 1 +
> libbsd.py | 35
> rtems
---
freebsd/sys/dev/iicbus/iic.c| 506 ++
freebsd/sys/dev/iicbus/iic.h| 72
freebsd/sys/dev/iicbus/iicbus.c | 378
freebsd/sys/dev/iicbus/iicbus.h | 83 +
freebsd/sys/dev/iicbus/iiconf.c | 527 +
-git a/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
b/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
new file mode 100644
index ..61881e74
--- /dev/null
+++ b/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
@@ -0,0 +1,215 @@
+/*
+ * Copyright (c) 2019 Vijay Kumar Banerjee .
+ * All rights reserved.
+ *
+ * Redistributio
---
Makefile.todo | 13 ++
buildset/default.ini | 1 +
libbsd.py | 35
rtemsbsd/include/bsp/nexus-devices.h | 4 +
.../machine/rtems-bsd-kernel-namespace.h | 29 +++
rtemsbsd/incl
_shell_cmd_t rtems_shell_I2C_Command;
+
extern rtems_shell_cmd_t rtems_shell_PING_Command;
extern rtems_shell_cmd_t rtems_shell_PING6_Command;
diff --git a/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
b/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
new file mode 100644
index ..2e1da406
--- /dev/n
---
freebsd/usr.sbin/i2c/i2c.c | 733 +
1 file changed, 733 insertions(+)
create mode 100644 freebsd/usr.sbin/i2c/i2c.c
diff --git a/freebsd/usr.sbin/i2c/i2c.c b/freebsd/usr.sbin/i2c/i2c.c
new file mode 100644
index ..084682a1
--- /dev/null
+++ b/freeb
---
Makefile.todo | 41 +++
buildset/default.ini | 2 +
libbsd.py | 100 ++
rtemsbsd/include/bsp/nexus-devices.h | 13 ++-
.../machine/rtems-bsd-kernel-namespace.h |
This Patch series contains the patches to import and port
the drivers for FB and TDA from FreeBSD. This is not a working
patch and the purpose of sending the patch to the list is to
ask for a help regarding a build issue with the FB files that
use /arm/include/bus.h file.
In rtemsbsd/ we have th
The PATCH 1/2 was too big for the devel. So, I'm posting the
github link for the commit here :
https://github.com/thelunatic/rtems-libbsd/commit/ae8c32365d1ce600a370c7fb7e0095375653a4f5
On Wed, Jun 19, 2019 at 1:23 AM Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
>
>
Hello all,
The current status of the project is that I could port the tda drivers
successfully but there are some bugs in the RTEMS bbb-i2c.c driver
in beagle BSP, as a result of which, the I2C-adaptation driver cannot
be used. Currently Christian is working on the bugs in the RTEMS
driver.
To tes
eeBSD I/O memory operations
> by just plain memory accesses. But sometimes (like for DMA) it is
> necessary to think about them and add cache handling.
>
> On 18/06/2019 21:53, Vijay Kumar Banerjee wrote:
> > ---
> > Makefile.todo |
On Tue, Jun 25, 2019 at 1:47 AM wrote:
> From: Christian Mauderer
>
> The old driver worked well for EEPROMS with the RTEMS EEPROM driver. But
> it had problems with a lot of other situations. Although it's not a
> direct port, the new driver is heavily modeled after the FreeBSD ti_i2c
> driver.
---
freebsd/usr.sbin/i2c/i2c.c | 733 +
1 file changed, 733 insertions(+)
create mode 100644 freebsd/usr.sbin/i2c/i2c.c
diff --git a/freebsd/usr.sbin/i2c/i2c.c b/freebsd/usr.sbin/i2c/i2c.c
new file mode 100644
index ..084682a1
--- /dev/null
+++ b/freeb
-git a/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
b/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
new file mode 100644
index ..b965f248
--- /dev/null
+++ b/rtemsbsd/sys/dev/iicbus/rtems-i2c.c
@@ -0,0 +1,231 @@
+/*
+ * Copyright (c) 2019 Vijay Kumar Banerjee .
+ * All rights reserved.
+ *
+ * Redistributio
---
freebsd/sys/dev/iicbus/iic.c| 506 ++
freebsd/sys/dev/iicbus/iic.h| 72
freebsd/sys/dev/iicbus/iicbus.c | 378
freebsd/sys/dev/iicbus/iicbus.h | 83 +
freebsd/sys/dev/iicbus/iiconf.c | 527 +
_shell_cmd_t rtems_shell_I2C_Command;
+
extern rtems_shell_cmd_t rtems_shell_PING_Command;
extern rtems_shell_cmd_t rtems_shell_PING6_Command;
diff --git a/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
b/rtemsbsd/rtems/rtems-bsd-shell-i2c.c
new file mode 100644
index ..2e1da406
--- /dev/n
---
Makefile.todo | 13 ++
buildset/default.ini | 1 +
libbsd.py | 35
rtemsbsd/include/bsp/nexus-devices.h | 4 +
.../machine/rtems-bsd-kernel-namespace.h | 29 +++
rtemsbsd/incl
Hello,
The First Evaluation is going on and I here I would summarize all the
progress
that the project has made in the first Phase.
1. The major progress is the completion of the I2C adaptation layer in the
libbsd
along with the iicbus driver imports. The v4 of the driver [1] has
been tested
On Tue, Jun 25, 2019 at 5:04 PM Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
> Hello,
>
> The First Evaluation is going on and I here I would summarize all the
> progress
> that the project has made in the first Phase.
>
> 1. The major progress is the compl
On Tue, Jun 25, 2019 at 9:32 PM Gedare Bloom wrote:
> On Tue, Jun 25, 2019 at 5:34 AM Vijay Kumar Banerjee
> wrote:
> >
> > Hello,
> >
> > The First Evaluation is going on and I here I would summarize all the
> progress
> > that the project has made i
---
Makefile.todo | 27 ++
buildset/default.ini | 1 +
libbsd.py | 46 ++
rtemsbsd/include/bsp/nexus-devices.h | 1 +
.../machine/rtems-bsd-kernel-namespace.h | 65 +
---
freebsd/sys/dev/fb/fbd.c | 11 ++
libbsd.py | 4 +++
rtemsbsd/include/bsp/nexus-devices.h | 1 +
.../machine/rtems-bsd-kernel-namespace.h | 35 +++
rtemsbsd/include/rtems/bsd/local/opt_fb.h | 0
5
---
Makefile.todo | 13 ++
libbsd.py | 12 +
rtemsbsd/include/bsp/nexus-devices.h | 2 +
.../machine/rtems-bsd-kernel-namespace.h | 2 +
rtemsbsd/include/rtems/bsd/local/fb_if.h | 45 ++
/4f1cde1ef64e4a401cf4acd71bc5e681628fb3ed
[PATCH 5/6] :
https://github.com/thelunatic/rtems-libbsd/commit/efe23128b1cf39bdd75040067c95d87c05ae7f00
On Sun, Jun 30, 2019 at 8:59 PM Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
> ---
> Makefile.todo
On Sun, Jun 30, 2019 at 9:08 PM Christian Mauderer
wrote:
> On 30/06/2019 17:33, Vijay Kumar Banerjee wrote:
> > The following patchset has only the port commits, the commits to import
> > are pushed to Github and the links are as follows:
> > [PATCH 1/6]
> > :
>
Hello everyone,
I'm happy to state that with the following patchset, I now have
the Framebuffer device (/dev/fb0) created in Beaglebone Black
and I have tested it in the Hardware with BBB RevC.
>From here, the next steps would definitely be to find a way to
write and read from the framebuffer dev
601 - 700 of 976 matches
Mail list logo
