<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 10, 2019 at 12:50 PM Christian Mauderer <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 09.04.19 um 18:12 schrieb Vijay Kumar Banerjee:<br>> Hi,<br>> <br>> I have imported and ported the the drivers in 2 pairs(import and port)<br>> of commits <br>> for each one. Please have a look at this branch <br>> <a href="https://github.com/thelunatic/rtems-libbsd/commits/tda19988" rel="noreferrer" target="_blank">https://github.com/thelunatic/rtems-libbsd/commits/tda19988</a><br>
<br>One detail: You have a commit named "tda19988.c: import from FreeBSD".<br>Please remove the ".c".<br>
<br></blockquote><div>Noted. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Maybe it would be a good idea to split of the I2C part and put it in<br>front of the other two parts. You can develop and test that independent<br>with a test that just accesses some of the I2C devices on the board via<br>the FreeBSD API and the translation driver discussed below.<br>
<br></blockquote><div>This is a good idea, I'll import iicbus separately and add the other </div><div>two on top of it. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> <br>> I have also tried running the media01.exe and have seen it running fine<br>> without<br>> throwing any exceptions.<br>> <br>> I have used the fb.c and iicbus.c codes from the freebsd source. From<br>> what I <br>> understand, I think the next big steps would be to write an RTEMS <br>> implementation layer for these portions of the code? And then a test in the <br>> libbsd, like media01, to write to the /dev/fb0 <br>> <br>> Can you please help me chalk out a rough outline of the next set of<br>> actions? :)<br>
<br>As far as I can tell, there are two possible I2C buses here:<br>
<br>1. The one between the AM335x and the TDA19988.<br>
<br>2. The one directly on the HDMI connector (called HDMI_DSCL and<br>HDMI_DSDA). I assume that's an I2C bus too.<br>
<br>For 1. the RTEMS driver should be used. You'll need some code that<br>translates the FreeBSD API to the one used in RTEMS. Basically that will<br>just be a FreeBSD-I2C-driver.<br>
<br>For 2: If that even is an independent I2C bus, you can use the driver<br>provided by FreeBSD. I don't think that it is necessary to translate to<br>the RTEMS API here.<br>
<br></blockquote><div>I had a look at the iic and iicbus codes in freebsd and the bbb-i2c.c</div><div>This looks very confusing to me. Are we looking for something like a</div><div>rtems-iicbus.c in the rtemsbsd that works like a wrapper to the bbb-i2c</div><div>code, and uses the freebsd api of DEVMETHODs?</div><div><br></div><div>I've not been able to figure out at one look, how to relate them and </div><div>get a wrapper like that. Any suggestions on how to approach this?</div><div><br></div><div>Can we not totally use the iicbus in the freebsd source?</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> <br>> Thanks<br>> <br>> On Tue, Apr 9, 2019 at 5:28 AM Chris Johns <<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a><br>> <mailto:<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>>> wrote:<br>> <br>> On 8/4/19 12:30 am, Vijay Kumar Banerjee wrote:<br>> > On Sun, Apr 7, 2019 at 6:24 PM Christian Mauderer<br>> <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> > <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>>> wrote:<br>> > Am 07.04.19 um 14:50 schrieb Vijay Kumar Banerjee:<br>> > > On Sun, Apr 7, 2019 at 6:08 PM Christian Mauderer<br>> <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> > <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>><br>> > > <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>>>> wrote:<br>> > > Am 07.04.19 um 14:35 schrieb Vijay Kumar Banerjee:<br>> > > > On Sun, Apr 7, 2019 at 5:37 PM Christian Mauderer<br>> > > <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>><br>> > <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>>><br>> > > > <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>><br>> > <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>>>>> wrote:<br>> > > > Am 07.04.19 um 13:08 schrieb Vijay Kumar Banerjee:<br>> ><br>> > I don't think that there are a lot of docs for how to test.<br>> Although I'm<br>> > sure that there are some scripts to run a number of libbsd<br>> tests, I'm<br>> > not sure where. Maybe in the RTEMS tester but I think that is<br>> mainly for<br>> > the core tests?<br>> <br>> The documentation for testing can be found here ...<br>> <br>> <a href="https://docs.rtems.org/branches/master/user/testing/index.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/testing/index.html</a><br>> <br>> > so far I know, RTEMS Tester is only for core tests.<br>> <br>> The `rtems-test` command checks the for test start and end banners.<br>> I am not<br>> sure if libbsd supports the test banners. Maybe it could now with<br>> Sebastian's<br>> movement of the test support code into libtest.<br>> <br>> > I'll ask in the devel if there's some way to run libbsd test with<br>> the tester.<br>> <br>> There is the `rtems-run` command which has similar args to<br>> `rtems-test`. It does<br>> suffer from a limitation I have not fixed which is stdin is not<br>> passed through<br>> to the console of the target. I also think the command has a timeout<br>> running,<br>> but I am not sure about this one.<br>> <br>> Chris<br>> <br>
<br>-- <br>--------------------------------------------<br>embedded brains GmbH<br>Herr Christian Mauderer<br>Dornierstr. 4<br>D-82178 Puchheim<br>Germany<br>email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>Phone: +49-89-18 94 741 - 18<br>Fax: +49-89-18 94 741 - 08<br>PGP: Public key available on request.<br>
<br>Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
</blockquote></div></div>