From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org, Daniele Lacamera <daniele.lacamera@tass.be>
Subject: Re: [RFC] picotcp.20140530
Date: Mon, 2 Jun 2014 10:46:21 +0200 [thread overview]
Message-ID: <20140602084621.GZ15686@pengutronix.de> (raw)
In-Reply-To: <20140530131833.e6960587743c31fd85cd7788@gmail.com>
On Fri, May 30, 2014 at 01:18:33PM +0400, Antony Pavlov wrote:
> Hi All!
>
> My new barebox with picotcp support brunch is pushed to github:
>
> https://github.com/frantony/barebox/tree/picotcp.20140530
>
> For this version reworked content of Daniele Lacamera's push request
> is used (see https://github.com/frantony/barebox/pull/1).
>
> Changes since picotcp.20140525:
>
> * rebased over latest barebox;
> * the latest picotcp is used (warnings and big-endian
> tests fixed);
> * add picotcp dhcp client support by Daniele Lacamera
> * qemu mips malta defconfig is dropped as barebox qemu
> malta has no network device support (you can rebase
> over experimental pci branch but it is very different story ...)
> * other small fixes.
I tried this version. I still didn't get it working, but some
improvements.
What I changed is:
* call eth_send() instead of edev->send directly. This makes sure the
carrier is initialized correctly
* implemented pico_zalloc as memalign(32, x); memset(ptr, 0 x); Some
drivers (such as fec_imx.c I tested with) need bigger alignment for
network packets to be able to do DMA transfers.
* move picotcp_net_init from coredevice_initcall to device_initcall.
In my case the poller infrastructure is not available during
coredevice_initcall and barebox crashes. Maybe the poller
infrastructure could be made more robust here, but we don't want to
to networking in this early stage anyway, right?
* select POLLER is missing
With this I get:
barebox@Phytec phyCORE-i.MX27:/ ifconfig eth 192.168.23.67 255.255.0.0
up
Assigned ipv4 192.168.23.67 to device eth
barebox@Phytec phyCORE-i.MX27:/ picoping 192.168.23.4
eth0: 100Mbps full duplex link detected
ARP: Destination Unreachable
ARP: Destination Unreachable
ARP: Destination Unreachable
ARP: Destination Unreachable
ARP: Destination Unreachable
---- Ping timeout!!!
I haven't investigated what's happening here.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-02 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:18 Antony Pavlov
2014-06-02 8:46 ` Sascha Hauer [this message]
2014-06-02 16:56 ` Antony Pavlov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140602084621.GZ15686@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=daniele.lacamera@tass.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox