[PATCH v1 0/6] [libbsd] Fix e1000 driver for i386 in master and 5

Gedare Bloom gedare at rtems.org
Wed Sep 9 15:28:08 UTC 2020


On Wed, Sep 9, 2020 at 2:16 AM Chris Johns <chrisj at rtems.org> wrote:
>
> On 9/9/20 4:55 pm, Jan.Sommer at dlr.de wrote:
> > Hi Chris,
> >
> >> -----Original Message-----
> >> From: Chris Johns <chrisj at rtems.org>
> >> Sent: Friday, August 14, 2020 11:43 PM
> >> To: Sommer, Jan <Jan.Sommer at dlr.de>; devel at rtems.org
> >> Subject: Re: [PATCH v1 0/6] [libbsd] Fix e1000 driver for i386 in master and 5
> >>
> >> On 15/8/20 5:57 am, Jan Sommer wrote:
> >>> Hello,
> >>>
> >>> I finally got around to port the e1000 driver fixes which are already
> >>> present in the 5-freebsd-12 branch of rtems-libbsd also for the master
> >>> (and 5) branch.
> >>
> >> Thanks. I will push these soon.
> >>
> >
> > As mentioned over at the users list, could you please push these changes?
>
> Yes I will tomorrow if no one else does it.
>
> > They should enable compilation for i386 again and we could establish Ethernet connections with Intel network devices.
> > The patches should apply to libbsd master and 5 branch, as they are both based on FreeBSD master.
> >
> >> I am not sure if the 5 branch in the rtems-libbsd.git repo is right and if it
> >> should be made from the 5-freebsd-12 branch? I feel it is currently confusing
> >> but either way it has issues.
> >>
> >
> > Maybe, we can continue to discuss that outside of this patch set? Renaming a branch later should be no trouble.
> > An option could be to rename 5 -> 5-freebsd-master, then the mapping between rtems and FreeBSD would always be explicit.
>
> Yes this is one Joel mentioned the other day and I missed the context in
> relation to these patches. I think moving 5 to 5-freebsd-master makes sense.
> What we have is confusing.
>
+1

Would be good to get Christian or Sebastian to comment/agree :)

> Chris
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel


More information about the devel mailing list