On Sun, Jun 30, 2019 at 10:17 PM Christian Mauderer <l...@c-mauderer.de>
wrote:
> On 30/06/2019 18:29, Vijay Kumar Banerjee wrote:
> > > @@ -366,6 +374,9 @@ driver_t fbd_driver = {
> > > devclass_t fbd_devclass;
> > >
> > > DRIVER_MODULE(fbd, fb, fbd_driver, fbd_devclass, 0, 0);
> > > +#ifdef __rtems__
> > > +DRIVER_MODULE(fbd, am335x_lcd, fbd_driver, fbd_devclass, 0, 0);
> >
> > Why is this necessary in this case? I don't see a similar connection
> in
> > FreeBSD.
> >
> > the fbd needs to be linked to the am335x_lcd which provides the fb0
> device
> > and the fbd needs to attach to fb0.
>
> It seems that this connection (or a similar one) hasn't been there on
> FreeBSD. So I wonder why it should be necessary on RTEMS.
>
> Note that the situation is a bit different from the one of the i2c bus.
> There your driver implemented a base for a bus system. Therefore the
> generic bus had been connected to a device specific driver. I'm not sure
> that's the case here.
>
> It's quite possible that you just have to link the fbd with a line like
> the following in nexus-devices.h:
>
> SYSINIT_MODULE_REFERENCE(fbd);
>
> This is not working :
```
fb0: failed to attach fbd device
```
> Best regards
>
> Christian
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
