This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: network problem
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Rick Davis <rickdavisjr at comcast dot net>
- Cc: 'Andrew Lunn' <andrew at lunn dot ch>, 'John Mills' <john dot m dot mills at alum dot mit dot edu>, 'eCos Users' <ecos-discuss at ecos dot sourceware dot org>
- Date: Sat, 1 Sep 2007 14:30:36 +0200
- Subject: Re: [ECOS] network problem
- References: <004701c7e990$9e57b8e0$db072aa0$@net> <Pine.LNX.4.44.0708281248260.12499-100000@otter.localdomain> <20070901103839.GA18291@lunn.ch> <00a901c7ec90$55eed630$01cc8290$@net>
> I am
> currently going to be using the latest eCos for the MPC85xx processor. A&M
> has a port for their Python board (MPC8541) but it hasn't been applied?
Probably because A&M have not contributed the port.
> As for the zpool, a couple/few years ago there was a thread regarding the
> lack of locking and they added a mutex that was used to prevent pre-emption
> inside of zalloci and zfreei.
I found a mention of this. It does not look like a patch was
submitted. I've not looked in too much detail, but it looks like there
could be a race here. So if somebody could submit a patch that would
be great.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss