I have got some more issues on which I want some help. 1. I updated the rtems-libbsd to the latest version, and it looks like all the device_printf are closed in one of the update. I am not able to see any log coming from them. Is there any way to switch that on ?
2. I could not find file "rtems/bsd/local/opt_platform.h" in my build. This is used by if_smsc.c. What is the alternative file ? or should I just comment this out ? 3. Chris asked me to see the changes from the file sys/dev/cadence/if_cgem.c and apply in the usb_ethernet driver. I am unable to find alternative of the variable "n" at line "sc->ifp->if_collisions += n;" in the file if_smsc.c. 4. if_smsc.c is using the function "usbd_m_copy_in" which is present in the file sys/dev/usb/usb_busdma.c. But due to this macro #if USB_HAVE_MBUF the function is not getting compiled. From where to switch this macro on ? Thanks, Deval Shah On Mon, Jul 4, 2016 at 7:51 PM, Deval Shah <deval.ma...@gmail.com> wrote: > okay I get it. > > On Mon, Jul 4, 2016 at 11:31 AM, Chris Johns <chr...@rtems.org> wrote: > >> On 04/07/2016 15:46, Sebastian Huber wrote: >> >>> On 03/07/16 06:56, Chris Johns wrote: >>> >>>> On 30/06/2016 20:22, Deval Shah wrote: >>>> >>>>> On Tue, Jun 28, 2016 at 3:12 AM, Chris Johns <chr...@rtems.org >>>>> <mailto:chr...@rtems.org>> wrote: >>>>> >>>>> It might pay for us to add these to an RTEMS header to make porting >>>>> simpler. >>>>> >>>>> Can't we update our sys/net/if.c and sys/net/if_var.h files accourding >>>>> to new FreeBSD ? >>>>> >>>> >>> I don't think its a good idea to selectively update random files of the >>> network stack core. >>> >>> >> I am fine with this and understand the reasons. >> >> >>>> I do not know. Currently we have a policy of keeping as much at the >>>> snapshot point as we can. Sebastian has looked at moving to FreeBSD 10 >>>> and backed off doing so because it was more work than he could handle >>>> due to changes in FreeBSD 10. >>>> >>>> I am not against something like this being merged if the change is >>>> localised to just those files, it works, and the existing drivers >>>> work. If the change ripples out across the code base then it would be >>>> a problem. >>>> >>> >>> Partial updates make it harder and harder to do a major update. I did >>> this for complete subsystems like SDCard/MMC/USB, however, doing this >>> for individual files is really a problem if want to update. The blocking >>> point for an easy update to FreeBSD 10 or 11 are the user space command >>> line programs like ifconfig and route. We need a better general approach >>> to deal with user space programs. >>> >> >> It would be good to see if dynamic loading can be used to help here. I >> would need some time to sort through the issues but in theory we should be >> able to do this. >> >> We may have time to do an update later this year. >>> >> >> This would be good. >> >> Chris >> > >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
