Re: GSoC Linux UIO driver for PRU

On Sat, 20 Jul 2019 at 03:01, Chris Johns wrote: > On 19/7/19 8:32 pm, Nils Hölscher wrote: > > I am currently adding more and more libbsd deps to my build, that are > not in > > rtems or rtems-libbsd. > > Now I have been touching these to files of the BSD kernel: > > >

Re: GSoC Linux UIO driver for PRU

On 19/7/19 8:32 pm, Nils Hölscher wrote: > I am currently adding more and more libbsd deps to my build, that are not in > rtems or rtems-libbsd. > Now I have been touching these to files of the BSD kernel: >

Re: GSoC Linux UIO driver for PRU

On Thu, 18 Jul 2019 at 19:18, Chris Johns wrote: > On 18/7/19 7:11 pm, Nils Hölscher wrote: > > @chr...@rtems.org but where do we place the > shell > > part, which exists between BSD and RTEMS? > > LibBSD has a number of shell commands so this should not be a problem.

Re: GSoC Linux UIO driver for PRU

On 18/7/19 7:11 pm, Nils Hölscher wrote: > @chr...@rtems.org   but where do we place the shell > part, which exists between BSD and RTEMS? LibBSD has a number of shell commands so this should not be a problem. > However this doesn't have priority right now, does it? I

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 11:14, Nils Hölscher wrote: > > > On Thu, 18 Jul 2019 at 10:48, Christian Mauderer > > wrote: > > On 18/07/2019 10:30, Nils Hölscher wrote: > > Hi, > > > > Do I need to add an rtems_filesystem_file_handlers_r struct to

Re: GSoC Linux UIO driver for PRU

On Thu, 18 Jul 2019 at 10:48, Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > On 18/07/2019 10:30, Nils Hölscher wrote: > > Hi, > > > > Do I need to add an rtems_filesystem_file_handlers_r struct to the pru > > driver to register it or are the cdevsw sufficient? > > Current

Re: GSoC Linux UIO driver for PRU

Thanks everyone, @Sebastian Huber I was just confused because of the examples I got earlier using rtems IMFS but now everything is clear. The BSD Documentation helps thanks again. @Christian Mauderer Thanks for pointing out the relevant parts I wasn't seeing at the moment. The defines were

Re: GSoC Linux UIO driver for PRU

On 18/7/19 6:48 pm, Sebastian Huber wrote: > On 18/07/2019 10:41, Nils Hölscher wrote: >> So I will be fine just using the BSD structs? > > I don't know what you want to do. If you already have FreeBSD kernel code, > then > using the FreeBSD API is probably easier. Does this determine where we

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 10:30, Nils Hölscher wrote: > Hi, > > Do I need to add an rtems_filesystem_file_handlers_r struct to the pru > driver to register it or are the cdevsw sufficient? > Current status of the driver: > https://github.com/nilhoel1/rtems-pru/blob/pruss-shell/pruss.c#L806 > > I am still

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 10:41, Nils Hölscher wrote: So I will be fine just using the BSD structs? I don't know what you want to do. If you already have FreeBSD kernel code, then using the FreeBSD API is probably easier. But how do I register devices with the FreeBSD API, since the examples you

Re: GSoC Linux UIO driver for PRU

So I will be fine just using the BSD structs? But how do I register devices with the FreeBSD API, since the examples you provided earlier don't hold anymore. Or am I getting something wrong on my side? On Thu, 18 Jul 2019 at 10:38, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: >

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 10:30, Nils Hölscher wrote: Do I need to add an rtems_filesystem_file_handlers_r struct to the pru driver to register it or are the cdevsw sufficient? Current status of the driver: https://github.com/nilhoel1/rtems-pru/blob/pruss-shell/pruss.c#L806 I am still not clear what the

Re: GSoC Linux UIO driver for PRU

Hi, Do I need to add an rtems_filesystem_file_handlers_r struct to the pru driver to register it or are the cdevsw sufficient? Current status of the driver: https://github.com/nilhoel1/rtems-pru/blob/pruss-shell/pruss.c#L806 I am still not clear what the differences between these two structs

Re: GSoC Linux UIO driver for PRU

Hi, I applied the patch and now all compiles. But I haven't tested anything yet, I am currently working on an application for testing. I will keep in contact concerning the mmap patch. Best, Nils On Tue, 16 Jul 2019 at 15:47, Christian Mauderer < christian.maude...@embedded-brains.de> wrote: >

Re: GSoC Linux UIO driver for PRU

On 16/07/2019 15:35, Vijay Kumar Banerjee wrote: > > > > On Tue, Jul 16, 2019 at 6:57 PM Nils Hölscher > wrote: > > Thanks I have been able to resolve this. > > But I have run into another issue. > RTEMS port of the character device switch table doesn't

Re: GSoC Linux UIO driver for PRU

On Tue, Jul 16, 2019 at 6:57 PM Nils Hölscher wrote: > Thanks I have been able to resolve this. > > But I have run into another issue. > RTEMS port of the character device switch table doesn't support a .d_mmap > entry. > >

Re: GSoC Linux UIO driver for PRU

Thanks I have been able to resolve this. But I have run into another issue. RTEMS port of the character device switch table doesn't support a .d_mmap entry. https://github.com/RTEMS/rtems-libbsd/blob/610349693dd31d8b0efd33776516b7187cc5cda2/freebsd/sys/sys/conf.h#L199 And I am not certain how

Re: GSoC Linux UIO driver for PRU

On Tue, Jul 16, 2019, 6:34 AM Nils Hölscher wrote: > Hi, > > I am currently porting the pruss driver functions, that I want to add in: > rtems_filesystem_file_handlers_r pruss_irq_handler. > But when I add my functions like this: > .open_h = ti_pruss_irq_open > I receive the following

Re: GSoC Linux UIO driver for PRU

Hi, I am currently porting the pruss driver functions, that I want to add in: rtems_filesystem_file_handlers_r pruss_irq_handler. But when I add my functions like this: .open_h = ti_pruss_irq_open I receive the following compiler warnings: ../../pruss.c:156:13: warning: initialization from

Re: GSoC Linux UIO driver for PRU

Thanks this is very helpful. But has anyone an existing example of a similar driver? I wasn't able find one in /bsps, maybe I didn't search long enough. On Mon, 15 Jul 2019 at 08:47, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/07/2019 01:34, Joel Sherrill wrote: > > On

Re: GSoC Linux UIO driver for PRU

On 14/07/2019 01:34, Joel Sherrill wrote: On Sat, Jul 13, 2019 at 1:42 PM Chris Johns > wrote: On 13/7/19 5:16 pm, Nils Hölscher wrote: > Hi, > > After I made sure that my fdt is correct I wondered why the pruss was still not > accessible.

Re: GSoC Linux UIO driver for PRU

On 14/7/19 7:13 pm, Nils Hölscher wrote: > Thanks for your help. > I will go with the bitbucket libraries and will start to rewrite the bsd > >  driver > for rtems. Excellent. Please post here

Re: GSoC Linux UIO driver for PRU

Thanks for your help. I will go with the bitbucket libraries and will start to rewrite the bsd driver for rtems. Have you also seen the pructrl bitbucket repo?

Re: GSoC Linux UIO driver for PRU

On 13/7/19 5:16 pm, Nils Hölscher wrote: > Hi, > > After I made sure that my fdt is correct I wondered why the pruss was still > not > accessible. > When I researched more about userspace drivers in Linux I found out, that I > have > overseen the pru UIO module in Linux. > This is the part

GSoC Linux UIO driver for PRU

Hi, After I made sure that my fdt is correct I wondered why the pruss was still not accessible. When I researched more about userspace drivers in Linux I found out, that I have overseen the pru UIO module in Linux. This is the part that links the PRUs to the /dev/uio[0-7]. Which then would be