From: Christer Weinigel <christer@weinigel.se>
To: Jamie Lokier <jamie@shareable.org>
Cc: Neil Horman <nhorman@tuxdriver.com>,
David Miller <davem@davemloft.net>,
shemminger@vyatta.com, s.hauer@pengutronix.de, yanok@emcraft.com,
linux-arm-kernel@lists.arm.linux.org.uk, netdev@vger.kernel.org,
wd@denx.de, dzu@denx.de
Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver
Date: Thu, 12 Mar 2009 20:43:05 +0100 [thread overview]
Message-ID: <49B965C9.5090209@weinigel.se> (raw)
In-Reply-To: <20090312192504.GB16611@shareable.org>
Jamie Lokier wrote:
> In other words, glibc doesn't work on some embedded targets even if
> you have plenty of room: they don't support dynamic libs.
It might be possible to build glibc to always use hosts+DNS for name
lookup, but since I almost always use uclibc on embedded systems I
haven't really tried to do it. If I use glibc, it's on a NFS root and
those systems are large enough anyway.
>> uclibc also seems to have issues with networking and statically linked
>> binaries, but I just haven't had time to figure out why yet.
>
> I've never had an issue with uclibc and networking.
I'm not sure what is happening, but a statically linked uclibc binary
that does TCP networking will work happily with one userspace but not
another. It would seem to me that a statically linked binary should
only depend on the kernel ABI and not on anything userspace (except the
text files in /etc like resolv.conf), but that does not seem to match
reality. If I use Unix sockets instead it works fine, so belive it is
something related to TCP. But well, this is all very fuzzy because I
haven't had time to look more closely at it yet.
/Christer
next prev parent reply other threads:[~2009-03-12 19:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 2:29 [PATCH] dnet: Dave DNET ethernet controller driver Ilya Yanok
2009-03-11 4:00 ` Eric Dumazet
2009-03-11 23:33 ` [PATCH] dnet: Dave DNET ethernet controller driver (updated) Ilya Yanok
2009-03-12 6:29 ` David Miller
2009-03-11 4:18 ` [PATCH] dnet: Dave DNET ethernet controller driver Stephen Hemminger
2009-03-11 8:44 ` Sascha Hauer
2009-03-11 8:49 ` David Miller
2009-03-11 8:57 ` Sascha Hauer
2009-03-11 9:09 ` Wolfgang Denk
2009-03-11 10:35 ` Sascha Hauer
2009-03-11 13:23 ` David Miller
2009-03-11 14:00 ` Dan Williams
2009-03-11 18:23 ` Robert Schwebel
2009-03-11 19:15 ` Riku Voipio
2009-03-12 0:44 ` David Miller
2009-03-11 20:56 ` Christer Weinigel
2009-03-11 21:33 ` Russell King - ARM Linux
2009-03-12 0:13 ` Stephen Hemminger
2009-03-12 10:41 ` Christer Weinigel
2009-03-12 12:55 ` David Miller
2009-03-12 14:21 ` Christer Weinigel
2009-03-12 14:34 ` Sascha Hauer
2009-03-12 15:01 ` David Miller
2009-03-12 15:12 ` Neil Horman
2009-03-12 16:25 ` Christer Weinigel
2009-03-12 17:43 ` David Miller
2009-03-12 17:52 ` Christer Weinigel
2009-03-12 18:06 ` Jamie Lokier
2009-03-12 18:39 ` Dan Williams
2009-03-12 18:48 ` Christer Weinigel
2009-03-12 19:04 ` Sascha Hauer
2009-03-12 19:15 ` Jamie Lokier
2009-03-12 19:16 ` Neil Horman
2009-03-12 19:21 ` Christer Weinigel
2009-03-12 20:14 ` Wolfgang Denk
2009-03-12 20:27 ` Sascha Hauer
2009-03-12 20:35 ` Russell King - ARM Linux
2009-03-12 17:49 ` Neil Horman
2009-03-12 18:25 ` Christer Weinigel
2009-03-12 19:05 ` Neil Horman
2009-03-12 19:14 ` Sascha Hauer
2009-03-12 19:29 ` Christer Weinigel
2009-03-12 21:59 ` Jamie Lokier
2009-03-12 23:42 ` Christer Weinigel
2009-03-13 0:21 ` Neil Horman
2009-03-13 1:29 ` Christer Weinigel
2009-03-13 10:30 ` Neil Horman
2009-03-13 0:16 ` Neil Horman
2009-03-12 19:25 ` Jamie Lokier
2009-03-12 19:43 ` Christer Weinigel [this message]
2009-03-12 20:24 ` Mike (mwester)
2009-03-13 0:29 ` Neil Horman
2009-03-12 13:41 ` Michael Cashwell
2009-03-12 14:05 ` David Miller
2009-03-12 14:26 ` Neil Horman
2009-03-12 18:02 ` Jamie Lokier
2009-03-13 19:49 ` Robert Schwebel
2009-03-13 20:12 ` David Miller
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=49B965C9.5090209@weinigel.se \
--to=christer@weinigel.se \
--cc=davem@davemloft.net \
--cc=dzu@denx.de \
--cc=jamie@shareable.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=s.hauer@pengutronix.de \
--cc=shemminger@vyatta.com \
--cc=wd@denx.de \
--cc=yanok@emcraft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.