From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-la0-x22a.google.com ([2a00:1450:4010:c03::22a]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZH9tI-00008e-C0 for barebox@lists.infradead.org; Mon, 20 Jul 2015 12:09:53 +0000 Received: by lahe2 with SMTP id e2so33214487lah.1 for ; Mon, 20 Jul 2015 05:09:28 -0700 (PDT) Date: Mon, 20 Jul 2015 15:16:33 +0300 From: Antony Pavlov Message-Id: <20150720151633.50a5762da6ac6b724ac4cc87@gmail.com> In-Reply-To: <20150720104524.GC18700@pengutronix.de> References: <1437336443-8076-1-git-send-email-antonynpavlov@gmail.com> <20150720071013.GX18700@pengutronix.de> <20150720130649.24ddbd5dd3f7e3cd7de9b3a0@gmail.com> <20150720104524.GC18700@pengutronix.de> Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [RFC v2 00/16] barebox picotcp integration (2015.07.19) To: Sascha Hauer Cc: barebox@lists.infradead.org On Mon, 20 Jul 2015 12:45:24 +0200 Sascha Hauer wrote: > On Mon, Jul 20, 2015 at 01:06:49PM +0300, Antony Pavlov wrote: > > On Mon, 20 Jul 2015 09:10:13 +0200 > > Sascha Hauer wrote: > > = > > > Hi Antony, > > > = > > > On Sun, Jul 19, 2015 at 11:07:07PM +0300, Antony Pavlov wrote: > > > > I have just published latest picotcp-enabled barebox. > > > > Please see my 20150719.picotcp branch in my github barebox repo > > > > (https://github.com/frantony/barebox/tree/20150719.picotcp). > > > > = > > > > This version is based on the latest barebox-next and picotcp v1.5.0 > > > > (there is also picotcp v1.5.1, but is has no interested > > > > for barebox changes since v1.5.0). > > > > = > > > > = > > > > Changes since 2015.07.15 (see http://lists.infradead.org/pipermail/= barebox/2015-June/024174.html): > > > > = > > > > * net: UDP API changed to satisfy the picotcp integration needs; > > > > * nfs, tftp and dns subsystems have no picotcp-related stuff an= ymore. > > > > * netconsole works on top of picotcp with no additional changes. > > > > = > > > > = > > > > Here are some notes: > > > > = > > > > 1. just now tftp/nfs file transfer on top of picotcp is slower th= an > > > > the same transfer on top of legacy network stack; > > > > = > > > > 2. there is no $ anymore, > > > > so dhcp, tftp and ifup commands don't work on top of picotcp. > > > > The ifconfig command is used for network interfaces setup. > > > > = > > > > N.B. There is an old patch for dhcp support on top of picotcp > > > > https://github.com/frantony/barebox/commit/94021b6d7bb933cd= 50b7ea9e2c55725b5c404205 > > > > = > > > > 3. The picoping command is used insted of traditional ping comman= d. > > > = > > > First of all I applied patches 1-4 to next. > > = > > Sascha! > > = > > Please comment patches 5-7! > > = > > Probably these patches will be changed in the next picotcp integration = patchseries version, > > but your comment on them could be very beneficial. > = > From looking at them they are ok. I haven't found the place where you > allocate packets now, but please make sure they are aligned for dma > accesses, i.e. use net_alloc_packet(). Otherwise this happens: > = > eth0: Transmit data not aligned: c0416acc! I see only one possibility: fix pico_zalloc() macro definition in net/picot= cp/include/arch/pico_barebox.h. Could you please check it on your hardware? --=A0 Best regards, =A0 Antony Pavlov _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox